What is the format and structure of ini file that is used to update resources with Migration Manager for AD?
NOTE: The formats can slightly change between product versions. It is not recommended to create it manually.If QMM cannot generate working ini file (for example due to someproblems with ADAM database that cannot be restored) it is better to modify the existing file generated from the similar QMM version installed in the LAB.
I. For
adp.ini - ADPW (Active Directory Processing Wizard) (It has a little different format at the domain pair section where GUIDs are also added)
exchange2k.ini - Exchange 2000/2003 Processing Wizard
exchange55.ini - Exchange 5.5 Processing Wizard
smswizard.ini - SMS Processing Wizard
sqlwizard.ini - SQL Processing Wizard
The format is (information in brackets is for more detailed explanation and needs to be removed):
[dmw7]
[Options]
Clone=No (YES if Reassign group membership and object permissions to the target users with Leave source Account permissions and membership are checked)
Undo=No (Yes if Revert to the original group membership and object permissions are checked)
CleanUp=No (YES if Cleanup legacy group membership and object permissions of migrated users are checked)
Overwrite=No (YES if Reassign group membership and object permissions to the target users with Replace Existing Target accounts permissions are checked)
[]
SOURCE1;S-1-5-21-1246391366-47651237-1538882281;source1.local
TARGET;S-1-5-21-2535937604-3492534726-422498870;target.local
1002;User1;23889;;;;1
305;User2;23888;;;;1
21;User3;23890;;;;1
[]
SOURCE2;SOURCE_DOMAIN_SID;source2.local
TARGET;TARGET_DOMAIN_SID;target.local
1082;User11;23937;;;;1
195;GlobalGroup_Sec;23938;;;;2
23;GlobalGroup_Distr;23939;;;;3
1;LocalGroup_Sec;23940;;;;4
133;LocalGroup_Distr;23935;;;;5
1;UnivGroup_Sec;23938;;;;6
69;UnivGroup_Distr;23938;;;;7
509;Computer$;23936;;;;8
The first twolines in this sectionare source and target domain names in the following format:
A list os objects has the following format:
<source_RID_or_difference>;<source_sAMAccountName>;<target_RID>;<target_sAMAccountName>;<source_UPN>;<target UPN>;<source_object_type>;<target_object_type>;<source_GUID>;<target_GUID>
First row for the object mapping always contains the source and targets RID portions of the SID (the very last letters)
All the subsequent rows contain the number that needs to be added to the previous line to obtain the next objects RID. In the above example GlobalGroup_Sec RID = 1082+195 = 1277, GlobalGroup_Distr RID = 1277+23 = 1300
Not all columns are populated.If target name is the same as source one then its skipped.
Number at the end stands for the type of object:
User - 1
Global Group Security - 2
Global Group Distribution - 3
Local Group Security - 4
Local Group Distribution- 5
Universal Group Security - 6
Universal Group Distribution - 7
Computer$ - 8 ($ is always attached to the name)
II. VMover.ini for QMM RUM (Resource Updating Manager)
The format is similar to the above except [Options] section is different. Yes/No sets weather this type of processing will be performed or not.
[Options]
[Options]
FileSystem=Yes
Shares=Yes
LocalGroups=Yes
UserPrivileges=Yes
Printers=Yes
IIS=Yes
Registry=Yes
Profiles=Yes
Services=Yes
ScheduledTasks=Yes
DCOM=Yes
COMPlus=Yes
RoamingProfiles=Yes
InstallProfilesAgent=Yes
Clone=Yes
CleanUp=No
Undo=No
AutoRemove=No
MaxErrors=10
LogMask=15
LogFile=VMover.log
StateFile=VMover.txt
Version=400
MaxCriticalErrors=1
MaxRegUsage=95
ProcessRegGroupOwner=No
UpdateStateSec=1
SetArchiveBit=No
SharesExtendedLogging=Yes
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center