How to successfully process (Re-ACL) network resources on Network Attached Storage (NAS) devices (non-windows and windows based)?
For NAS devices running windows-based OS (Operating System):
a) vmover.exe /c /system=
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 NAS 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. File system permissions (permissions, audit and owner settings on files and folders for users and groups) and share permissions will be processed.
b) Alternatively, for QMM 8.4 and higher, use the 'RUM |
NOTE: Some registry processing errors can be logged, even in case of a successful server update.
IMPORTANT: Some storage devices, for example SAN volumes attached via fiber network channels, may not be updated just with the /system switch. In order to update all resources completely Vmover has to be executed once with the /system and the second time with the /volume switch. The /system switch will update all the disks attached locally including the share permissions on all file resources, and the /volume switch is used to update the security permission on the SAN volumes attached mainly via fiber network. As another workaround these volumes can be attached via iSCASI interface to appear as locally attached volumes.
For Non-Windows based NAS devices , for example NetApp filers running NetApp's proprietary operating system called Data ONTAP, which includes code borrowed from Berkeley Net/2 BSD Unix and other operating systems.
STEP 1: Process share permissions on the servervmover.exe /c /system=<ServerName>
Alternatively, for QMM 8.4 and higher, use the 'RUM |
STEP 2: Process NTFS permissions (file system only)vmover.exe /c /volume=<ShareEntryUNCPath>
For the instructions on how to process roaming profiles please see this Knowledge Base article SOL17006:
"How to use VMover for processing roaming profiles residing on file server?"
Please also refer to this Knowledge Base article SOL27673:
"Resource Updating Manager does not process all drives attached to a computer."