Is it possible to process resources and move computers from source to target domain without using Resource Updating Manager?
In certain migration scenarios using the Resource Updating Manager graphical user interface to update resources and move the computers is not viable.
In this case it can be done using command line utilities vmover.exe from Quest Migration Manager resource kit and netdom.exe from Windows Support Tools.
Command-Line Resource Update
The command-line tool VMover.exe, located in the %ProgramFiles%\Common Files\Aelita Shared\Migration Tools folder by default, can be used to update resources without installing an agent. The update can be performed directly from the command-line interface or via a logon script.
Among the main applications of VMover are the following tasks:
- Updating remote resources
- Processing roaming profiles
- Processing file system permissions on NT-compatible non-NT systems
Vmover can be used to process resources on a computer running NT 3.51 or later (NT 4 SP4 or later if SIDHistory mapping is used). To perform the updates, VMover retrieves the source-target account pairs from the INI file or target accounts SIDHistory. The INI file also contains the required parameters. Some parameters can be set from the command line.
Command-Line Parameters
VMover should be run using the following command-line syntax:
VMOVER.EXE /c [/ini=IniFile] [/roaming=UserDatPath] [/volume=Path] [/system=Computer]
Explanation:
/c Mandatory parameter for command-line usage.
/ini Optional parameter. Name of the INI file that contains the parameters for the update.
By default, the Vmover utility searches its folder for the Vmover.in_ (compressed) file, and then if the file is not found, for the Vmover.ini (uncompressed) file. You can use the Vmover/ini parameter to specify an alternative INI file name and location. In this case Vmover will also first search for the files compressed version. For example, if you specify File.txt, Vmover will first attempt to locate File.tx_, and then File.txt. Thus, if you specify an uncompressed INI file to be created, but there is a compressed file with the same name in Vmovers folder, Vmover will use the compressed file instead of the specified one.
For more information on creating INI files for processing resources, refer to the Creating the INI File for Resource Update section of the User Guide and the link to solution SOL82189 in Additional Information below.
/roaming Processes roaming profiles.
If you specify the /volume or /roaming parameters, Vmover will not process any other options in the INI file (such as group membership or user rights). This was done to simplify the updating of roaming profiles with these keys.
/volume Processes file system permissions in the specified location.
If you specify the /volume or /roaming parameters, Vmover will not process any other options in the INI file (such as group membership or user rights). This was done to simplify the updating of roaming profiles with these keys.
/system Specifies the computer name. By default, the local computer is updated.
Remote Update
By default, VMover applies the changes specified in the INI file on the local computer. To make VMover update a remote computer, use the /system command-line parameter or add the System=TargetComputerName key to the INI file.
The following example shows how to use the /system command-line parameter:
Vmover.exe /c /system=Mars
When VMover is updating a remote computer, it locates all the system shares of the computer (such as c$, d$) and updates all the files and folders located in the shares.
To update a specific share of the computer, use the /volume command-line parameter. In this case, no other shares will be affected.
The following example shows how to use the /volume parameter:
Vmover.exe /c /volume=\\Mars\Demos
If you use the /volume parameter, Vmover will not process any other options in the INI file (such as group membership or user rights). Only file system permissions of the specified share will be processed.
For a successful remote update, the account under which VMover is started must be administrative and have the following privileges on the remote and local computers (granted explicitly or by establishing a net use connection):
- Restore files and directories
- Backup files and directories
- Take ownership of files and other objects
- Manage auditing and security log
- Bypass traverse checking
For a successful IIS permissions processing on the remote computer, IIS must also be installed on the computer on which Vmover is running and the account under which Vmover is started must be a local administrator on the computer being processed.
Command-Line computer move
Moving the computers can be done using Microsofts utility netdom.exe
The syntax for netdom move command is given in the following Microsoft article: http://technet.microsoft.com/en-us/library/cc788127.aspx
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center