Environments
How do I set up environments?
To begin set up of Power365 Migration for Active Directory you must first configure an environment. Environments are managed in Power365 Directory Sync.
Please visit the Environments topic for more information.
Define Scope: Under the Environment Settings, Organizational Units section, be sure you have included the OUs which contain the Device (computer) Objects you want discovered for migration.
Include Devices: Under the Environment Settings, in the Filters section be sure to check the checkbox next to Devices under the Include Objects header.
Workflows
A workflow is a series of steps that ultimately lead to the migration of objects. Workflows are manged in Power365 Directory Sync. Please see the Workflows topic for more information.
For Power365 Directory Sync Workflows which will be used for Device migrations in Power365 Migration for Active Directory most of the settings will be similar to the settings for other kinds of migrations. There are two key settings which pertain to Device objects that you must enable when configuring for Device migrations: Workflow steps and Template Object settings.
For a Device migration to be successful the users and groups which have permissions to files on that machine must be in the Power365 Directory Sync database and have matching objects defined in the target. Otherwise, the Device ReACL process will not be able to correctly update the file access permissions on the device in preparation for moving to the new domain. It is not necessary to include User or Group objects in the same Workflow as Devices. Users and Groups will require Read In, Match, Stage Data, and Write Out Workflow steps. Device objects themselves at minimum require only the Reading and Matching steps.
A key part of Workflow settings which will apply to Device migrations are the Objects settings for the Template you use. In the Devices section of those Template Objects settings you can configure options to control how creation and updates of objects are handled.
Profiles
Migration Profiles
What is a Migration Profile?
A Migration Profile is a collection of common settings used to manage the domain join process during Device Cutover which can be defined once and then applied to multiple Devices.
How are Migration Profiles created?
In Power365 Migration for Active Directory only users with the Client Admin or Power User roles can create and modify Migration Profiles.
To create a Migration Profile:
On the Migration section of the Profiles page, click the Add button. The Add Your Migration Profile window appears.
Enter values for the following fields, then click Next:
Profile Name - A name to identify this profile (for example, "10 Second Reboot Delay").
Domain Join Delay - The delay time a Device agent processing a Cutover job applies before attempting to change the computer's domain to join the new domain.
Reboot Delay - The time for a Device agent processing a Cutover job to delay after joining the new domain before rebooting the computer.
Note: 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.
Enter values for the following fields, then click Next:
Empty Recycle Bin? - How to handle the Recycle Bin during Cutover, either Empty or Don't Empty.
Note: End 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.
Specify Target OU - The target OU where the Device will be created. If this field is left blank, they will default to the Computers container.
Join to Existing Computer Account - Select Yes if you expect to join the Device to the existing target Computer during Cutover. Select No if you want the Device to be created in the target by the Cutover job.
- Click Save Profile. The new migration profile is added to the list.