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.

Use the Regwalker.exe utility, found in the Migration Manager for AD Resource Kit and also attached to this solution, to create a registry hive with the target account SID and copy all of the application's settings from source SID hive to the target one.

The Regwalker utility is described in detail in the Quest Migration Manager Resource Kit User's Guide on pages 21 - 41.

http://support.quest.com/support_downloads/Resources/Migration%20Manager%20for%20AD/MigrationManagerResKit_7.1_UserGuide_052005.pdf

The regwalker.zip file attached to this solution contains two folders: LogonScript and RunLocally. As the folder names imply, there are two ways to run the regwalker.exe utility, which are from the logon script and locally.

Usage instructions for both methods can be found below:

Run from the logon script:

The LogonScript folder contains the following files:

login.bat - the file to specify as a logon script
Migration.xml - task file
RegModA.dll - dynamic library needed for regwalker functionality
RegModU.dll - dynamic library needed for regwalker functionality
RegWalker.exe - utility
RegWalkerMig.ini - regwalker configuration file

1. Copy all files to the Netlogon share of the domain (source or target - where workstation belongs).
2. Copy vmover.ini file (which was used for workstation processing) to the same Netlogon share.
3. In the RegWalkerMig.ini file change <Domain> to the NetBios name of the domain.
4. Specify login.bat as a logon script for the corresponding accounts.
5. Script needs to run under target account.

Run locally:

The RunLocally folder contains the following files:

computers.lst - a list of computers and accounts to process
Migration.xml - task file
RegModA.dll - dynamic library needed for regwalker functionality
RegModU.dll - dynamic library needed for regwalker functionality
RegWalker.exe -utility
RegWalkerMig.ini - regwalker configuration file

1. Copy all the files to a convenient location.
2. Copy vmover.ini file (which was used for workstation processing) to the same location.
3. In the computers.lst file specify computer and account name of the accounts to be processed. One computer and account name per line. The format of the string can be found in computers.lst file. Use target user account as in this example: "Workstation ; Target_domain\Target_user"
4. In the RegWalkerMig.ini specify the path to a folder where regwalker.exe should put the logs.
5. Run the regwalker.exe utility with the following syntax: regwalker.exe RegWalkerMig.ini

IMPORTANT NOTES:

- Ensure the account being used to run regwalker has administrative rights on the computers specified in the computers.lst file.
- The task XML file should be saved as Unicode.
- Computers.lst, RegWalkerMig.ini  and  Vmover.ini  files should be saved as ANSI.
- The folder containing these files should include VMover.ini file generated from QMM project where users to be processed were migrated.