-
Title
How to use VMover for processing roaming profiles residing on file server? -
Description
What is the procedure of using VMover to update roaming profiles on the file server?
-
Cause
The behavior is by design.
-
Resolution
File servers holding the roaming profiles can be processed remotely from the command line. This can be done from any computer on the network running a Windows based operating system and containing the vmover.exe utility locally. It is highly recommended to use a computer on the same subnet as the file server because performance can be significantly improved. The Vmover.ini file needs to reside in the same folder as vmover.exe. Alternatively, the /ini option can be used to specify the location of ini file. Please refer to the Migration Manager User Guide on how to create vmover.ini file. There are two possible ways to approach the syntax:
OPTION 1vmover.exe /c /system=<ServerName>
File system permissions (permissions, audit and owner settings on files and folders for users and groups) and share permissions will be processed. Roaming profiles will be processes ONLY if "RoamingProfiles=Yes" entry is present inside Vmover.ini file. This entry is created automatically provided that Vmover.ini was generated with "Roaming profiles" checked under Permissions Management Options in Export INI | Resource Updating dialogue.
OPTION 2If /volume and /roaming parameters are specified. In this case Vmover ignores any options present inside Vmover.ini file like "RoamingProfiles=Yes", "Registry=Yes", "IIS=Yes" etc. This was done to simplify processing of roaming profiles. The syntax is:
vmover /c /roaming=<UserDatPath> /volume=<RoamingProfilePath>
<RoamingProfilePath> needs to point to the top level share where roaming profiles are residing and <UserDatPath> is location of single user's roaming profile where DAT file is present. For example in the scenario where user's roaming profiles User1, User2, User3 reside underneath "Profiles" share on server MyServer the syntax will be:
vmover /c /roaming=\\MyServer\Profiles\User1 /volume=\\MyServer\Profiles\User1
"Volume" switch is only needed to process NTFS permissions below the path specified including all the subfolders while "Roaming" switch defines the location of NTUser.DAT file. For more details, please refer to the "Command-Line Resource Update" section in the Migration Manager User Guide.
IMPORTANT: In case of the syntax below where /volume=\\MyServer\Profiles points to the top level share
vmover /c /roaming=\\MyServer\Profiles\User1 /volume=\\MyServer\Profiles
all the NTFS permissions will be updated below \\MyServer\Profiles but only roaming profile for the User1 will be updated.
For the syntax where /roaming=\MyServer\Profiles points to the top level share
vmover /c /roaming=\\MyServer\Profiles /volume=\\MyServer\Profiles (or /volume=\\MyServer\Profiles\User1 )
all the NTFS permissions will be updated below \\MyServer\Profiles (or below \\MyServer\Profiles\User1) but NO roaming profiles will be processed. This is by design and considered a limitation. Please use option #1 described above if multiple roaming profiles have to be updated at once. If this is NAS device and not all volumes can be processed with /system switch - please map volume with roaming profiles using iSCASI interface. This will make volume appear as local disk and process all roaming profiles as described in option 1 above.
-
Additional Information
Please also see these Quest KB articles SOL14864 and SOL27673:
"How to use VMover for NetAPP filers processing"
https://support.quest.com/SUPPORT/index?page=solution&id=SOL14864&pmv=true"Resource Updating Manager does not process all drives attached to a computer"
https://support.quest.com/SUPPORT/index?page=solution&id=SOL27673&pmv=true&ct=1