User unable to launch Third Party Applications after Migration to Target Domain. Applications enc (4296345)

After workstations have been migrated to target domain and Resource Updating has been completed, a user logs on to the target domain and attempts to launch third party applications, such as BlackBerry Desktop Manager or Palm Pilot, or applications that use a run time version of Microsoft Access, the application will not launch. An error occurs stating that the msi files are corrupt and the installation needs to be repaired. The Installation Repair wizard launches but fails, as it cannot locate the msi files.

CAUSE

This problem occurs when the third party application stores its MSI settings under the following registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\ the source account SID\. This registry key contains the user's source SID, not the target SID because during resource updating this SID is not converted to target. So when the target user logs on and launches the MSI application, the SID doesn't match and the Windows Installer attempts to perform a repair. In most cases, if the application's installation files are located on the computer or there is direct access to these files, the Installer repairs the configuration information successfully (i.e. copies it under the user's target SID). However, when there are no installation files at hand, the repair fails.