Return
-
Title
How to Map SIDs using a custom file for Resource Updating Manager -
Description
Certain projects may not allow the migrating of sidhistory due to security concerns. How can a custom security mapping file be created for use with Resource Updating Manager / Vmover / Secure Copy?
What are the step by step instructions to achieve this? -
Cause
n/a -
Resolution
Step 1
Initially an account matching CSV file must be created which contains a list of migration pairs in the following format, one pair per line in the format below:
SourceNetBIOSDomainName\SourceUserName,SourceUserSID,SourceUPN,SourceDomainDNSName,TargetNetBIOSDomainName\TargetUserName,TargetUserSID,TargetUPN,TargetDomainDNSNameThe following is an example of a potential account matching file:SOURCE1\user1.name,S-1-5-21-sourceUser1SID,user1@source1.principal.name,source1.com,TARGET1\user1.name,S-1-5-21-targetUser1SID,user1@target1.principal.name,target1.comSOURCE2\user2.name,S-1-5-21-sourceUser2SID,user2@source2.principal.name,source2.local,TARGET2\user2.name,S-1-5-21-targetUser2SID,user2@target2.principal.name,target2.localPlease note the creation of such a CSV file is a customer task and support cannot engage on this directly.
Step 2Following the creation of the CSV file select the Resource Update Manager option "Operate with accounts from file", and select the CSV file.
Step 3
Run a standard RUM processing task on the desired system
Step 4 (Optional)
If required export the resultant ini file for Vmover or Secure Copy usage