To add migration options:
On the Migration Options page, click the Add button. The Migration Options window appears.
Reboot Delay - The delay before rebooting.
If set to any value other than zero (0), the user will receive a pop-up notification informing them that the workstation will be rebooted when the cutover is performed. If set to zero, no notification will appear.
Empty Recycle Bin? - How to handle the Recycle Bin during cutover, either Empty or Don't Empty
Users may get an error message that their Recycle Bin has been corrupted after migration if the Recycle Bin is not empty. See Troubleshooting for more information about this issue.
To add network profiles:
On the Network Profiles page, click the Add button. The Network Profiles window appears.
Set DNS Servers For the Computer? - Options include: Don't Change This Setting, Use DHCP For DNS Server, or Manually Assign DNS Servers.
If you manually assign DNS settings, be sure that the DNS server(s) that you include here can resolve the Migrator Pro for Active Directory Agent SRV record.
The default Device ReACL profile is used if a different profile is not defined and set on the computers. The default Device ReACL profile can be edited.
To add Device ReACL profiles:
On the Device ReACL Profiles page, click the Add button. The Device ReACL Profile window appears.
Select the components to process.
Local Files/Folders: Selected by default.
Registry Permissions: Selected by default.
User Profiles: Selected by default.
Local Group Memberships: Selected by default.
Local Printer Permissions: Selected by default.
Network Share Permissions: Selected by default.
Printer Share Permissions: Selected by default.
Roaming Profiles: Unselected by default.
If you select Roaming Profiles, users must be logged out of their roaming profiles during the ReACL process.
Windows Services: Selected by default. The Windows Services option will ensure that any source domain accounts that were given permission to a service will include the corresponding matched target domain account after a ReACL process.
Windows Service Accounts: Unselected by default. We recommend that the Windows Service Accounts box is left UNCHECKED. A change in the ACL of the services accounts of the target may have an impact on the applications currently running. Although the ReACL process can usually be rolled back in case of issues, there could be a temporary disruption in service until that can be resolved. Selecting the Windows Service Accounts box will switch the domain account that Windows services are running under to the corresponding matched target domain account after a completed ReACL process.
User Rights Assignments: Selected by default.
System ACLs: Selected by default. The System ACLs option allows for the proper translation of accounts within the security audit logs.
Preserve the "Archive" Bit: Unselected by default. If the Preserve the "Archive" Bit box is left unchecked, the archive bit will be reset. If checked, the archive bit will not be reset.
Normally all files and folders are included in the ReACL process. If it is preferred to provide a specific list, enter the list in the Only Process the Following and Their Subfolders box. Separate each entry by pressing Enter. You may use just a file path using backslashes, or provide an exact drive letter. If a drive letter is provided, the ReACL is limited to that exact path.
Note that if you choose to list folders here, these are the ONLY folders that will be included in the ReACL process. (The exception is if you check the User Profiles box: those Profiles will always be included automatically in addition to your list.)
In the Exclude These Paths From Processing box, enter folder paths that will not be included in the ReACL process. Wild card characters (* and ?) can be used when specifying blacklist folders. Separate the paths by pressing Enter. By default, the following folders are blacklisted:
In the Exclude These Registry Keys From Processing box, enter registry keys that will not be included in the ReACL process. A leading '\' is not necessary. Separate the paths by pressing Enter. The following wild card characters are permitted when specifying registry keys:
Select an option from the Elevated Permissions Failure Action drop-down list to choose the action that should be taken if any part of the ReACL process encounters errors.
In order to successfully adjust permissions, Migrator Pro for Active Directory must create a process with a security token that has been assigned additional permissions. The token is said to have elevated rights/permissions. If this process fails, it is likely that the ReACL will be largely unsuccessful in updating the operating system for use by target user accounts.
Select an option from the Preserve Rollback Metadata in ACLs drop-down list.
Migrator Pro for Active Directory inserts a "breadcrumb” during the ReACL process to allow seamless rollback of the ReACL process if needed. You can control the insertion of these breadcrumbs (which are removed during the Cleanup process) if desired, here.
The default is Always and does not affect performance. We recommend this setting. This is the only setting where the changes performed by the ReACL process can be rolled back, or undone, in all scenarios.
If you choose Only If Ambiguous, metadata will only be included when the rollback settings would be ambiguous. Only If Ambiguous results in the addition of fewer breadcrumbs, preserving usage for times when it may be impossible to determine the original file or folder permissions. For example, when users have accounts in multiple domains that will be consolidated into a single domain.
Note that Only If Ambiguous guarantees a ReACL can be rolled back to the original state only when the file system permissions remained unchanged. Modification of ACLs on the file system could create a state where a rollback cannot complete with 100% success. To ensure the ability for a ReACL Rollback in all scenarios, Always should be selected.
If you are an experienced migration architect, you may choose Never to never include metadata.
If Never is selected, a complete rollback may not be possible.