Migration Manager for Active Directory is capable of Reverting RUM (Resource Update Manager) Options including Local Profiles. These steps come in handy in situations where:
a. the Profile Updates either need to be reverted or the
b. Target user has logged on before a successful RUM Profile Update ran (thus causing an incorrect new profile to be created)
c. Running as a precaution to prevent failed profile updates do to scenario b. previously mentioned.
NOTE: This procedure is safe to be performed against any machine and will not affect source profiles or cause problems even if target users have not logged into the Machine. In this case these steps are only executed as a precaution.
This article applies to all QMM RUM versions, but steps (terms, names of features) might slightly vary, depending on QMM RUM version being used.
Recommended Procedure:
Note: Assumption is that users have been migrated/synchronized already. When term source users is used Migrated Source user is assumed.
1. Start QMM, then start RUM (Resource Updating Manager).
2. Determine the workstations to be updated and add it to a collection.
3. Create a new processing task for this workstation or for the collection.
4. Choose the Radio Button Option "Revert to the original local group, user rights...".
5. During the next step deselect (unselect) all checked boxes and select Local Profiles only.
6. Finish and execute the task.
7. Once this processing task is finished the log file can be reviewed.
At this point the Workstation(s) will only contain source user profiles. The previously created Target User Profile directory will not be deleted but the registry presence which Migration Manager looks for will be removed.
8. Create a new "regular" Processing task, and process the workstation as usual.
Important: If target user has logged on before a successful RUM Profile Update ran and target user is now logged on then the user needs to log off, then the "Revert to the original local group, user rights..." task will be able to delete the incorrect entry from the registry.
Alternative way of reverting machine back if RUM is unable to do it through the GUI is:
1) create RUM processing task using "Revert to" option, but set the task schedule to "decide later"
2) navigate to Tasks tab on the right pane, find the newly created Processing task, right-click it and select "Export settings to file". Save it as VMOVER.INI
3) Copy VMOVER.INI and proper version of VMOVER (32 or 64 bit) from C:\Program Files (x86)\Common Files\Aelita Shared\Migration Tools\Resource Updating\Agent to the processed machine
4) open CMD in "run as admin" mode and go to the folder where Vmover.exe and INI files were copied
5) run "vmover.exe /c /system=<machinename>" command, where <machinename> is the hostname of the processed machine
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center