Chat now with support
Chat with Support

Binary Tree Power365 Current - Help Center

Help Center Home Power365 Platform Tenant-to-Tenant Directory Sync Migration for Active Directory Release Notes Known Limitations Support

Variables

What are Variables?  

Variables, also known as Global Variables, can be defined and be used across multiple scripts when defining Custom Actions. For example, a global variable to add the current date can be added to multiple scripts. Global variables will appear when selecting a starter script when creating a Custom Action if the "Global Variables" option is selected.

 

How is a Variable created?  

To add a Global Variable:

  1. Open the left navigation menu.
  2. Click Configuration.
  3. Click Variables.
  4. Click the Add button.
    1. Enter values in the following fields:

      • Variable Name (Required): Enter a name for the global variable. The name must contain alphanumeric characters and underscores only.
      • Variable Value (Required): The value of the global variable. Check the Encrypted box to encrypt the value in the database and hide the variable value in the interface.
  5. Click the Save button.

Migration Waves

What is a Migration Wave?  

A Migration Wave in Power365 Migration for Active Directory is a named logical grouping of Devices. This can be a useful tool for organizing, tracking, and staging your migrations.

 

How do I manage Migration Waves?  

There are two ways to manage Migration Waves in Power365 Migration for Active Directory. First, you can add Devices to a Wave by applying the ‘Set to Migration Wave’ Action to Devices from the Ready Devices table. The other way to manager Migration Waves is from the Migration Waves page which is accessible through ‘Waves’ in the left navigation menu. On that page you can create new Waves, Edit Wave names, Remove empty waves, and view how many Devices are in a Wave.

 

What can I do with a Migration Wave?  

Migrations Waves in Power365 Migration for Active Directory can be used to filter the Ready Devices table to view Device status and apply Actions.

 

How do I create a New Migration Wave?  

  1. Login to Power365 Migration for Active Directory.
  2. Select "Waves" in the left navigation menu.
  3. A new page will open listing your current migration waves.
  4. Click the Add icon.
  5. Name the Migration Wave, remember use a logical name representing the migration event.
  6. Click “Save.”
  7. Now that the Migration Wave is created, Devices can be added to the Wave by applying the ‘Set to Migration Wave’ Action to Devices from the Ready Devices table.

 

How do I remove a Migration Wave?  

  1. Login to Power365 Migration for Active Directory.
  2. Select "Waves" in the left navigation menu.
  3. A new page will open listing your current migration waves.
  4. Select one or more wave in the table.
  5. Click the Remove icon.
  6. Click "Yes" to confirm the removal.

 

How do I edit the name of a Migration Wave?  

  1. Login to Power365 Migration for Active Directory.
  2. Select "Waves" in the left navigation menu.
  3. A new page will open listing your current migration waves.
  4. Select a wave in the table.
  5. Click the Edit icon.
  6. Edit the name of the Migration Wave.
  7. Click “Save.”

 

How do I filter Devices by Migration Wave?  

  1. Login to Power365 Migration for Active Directory.
  2. Select "Devices + Servers" in the left navigation menu.
  3. On the Ready Devices tab, click the Filter icon.
  4. Select one or more wave under the Waves filter category.

Migrate and Navigate

Devices and Servers

What is the Devices + Servers page used for?  

The Servers + Devices screen allows the administrator to register devices and servers, change the agent polling interval, set the ReACL profile, upload migration logs, and manage the device Discovery, ReACL, Cutover, and Cleanup processes.

 

What is the difference between a "Ready Device" and a "Not Ready Device?"  

"Ready Devices" are devices that have the necessary agent installed, are communicating, and are ready for actions to be scheduled. "Not Ready Devices" are devices which that have not yet had an agent installed and communicating.

Note: Initial agent registration is uniformly distributed over a four hour interval from agent start time.

 

What actions can be performed on Devices and Servers?  

The following actions can be performed on devices by selecting the devices in the list, selecting an action from the drop-down list, and then clicking the Apply Action button.

  • Discovery

    The Discovery process gathers properties (OS versions, network properties, and so on) from the device to allow additional future functionality. The first discovery process begins for a device when the device becomes registered with Power365 which will automatically occur after the Device Agent has been installed, as long as the environment is properly configured.

    To select when the process will begin check Do not start before and then enter or select a date and time. If using the Do not start before option, the Discovery Status will be displayed as Queued in the Devices table and the "Do Not Start Before" column in the Device Jobs table will be populated with the selected date.

  • ReACL

    The ReACL process updates the Device’s domain user profiles for use by the matching target user after cutover.

    Note: It is recommended to remove or disable anti-virus software immediately prior to the ReACL process and only after a recent clean scan has been completed.

    Note: At least one group must be migrated to populate the map.gg file or the ReACL process will fail.

    Before ReACL can occur, the target Users and Groups which have permissions set on the Device must be migrated to the target.

    To select when the process will begin check Do not start before and then enter or select a date and time. If using the Do not start before option, the ReACL Status will be displayed as Queued in the Devices table and the "Do Not Start Before" column in the Device Jobs table will be populated with the selected date.

    Note: Two checks are performed at the start of the ReACL process. The first check is for invalid Source Profiles, which will be logged as a WARNING and those profiles will be skipped. The second check is for invalid Target Profiles, where a user may have created a profile with the target account before their machine is ReACL’d and cutover. By default, this is logged as a FATAL ERROR and will halt the ReACL process. However, it can be changed to a WARNING with the –t switch passed by editing the command in SQL.

    The ReACL Agent will automatically create two files on the device being ReACL’d, map.usr and map.gg. These files are used to find the source permissions and add the appropriate target permissions during the ReACL process. System groups, such as Domain\Domain Admins and Domain\Domain Users are included in the map.gg file for updating the group permissions during the ReACL process. If the Active Directory environment is non-English, the values in the sAMAccountName column of the BT_SystemGroup table in the SQL database will need to be changed after Directory Sync is installed to have the appropriate non-English values.

    If the Mapped Network Drive is being mapped via GPO or using an integrated credential such as the current Windows logon session, ReACL will create a warning entry in the log “…WARNING: The UserName value for drive U was empty and could not be mapped to the target user.” This warning does not mean that the mapped drive cannot be accessed after Cutover.

    Note: For Windows 10 and Windows Server 2016 devices, the ReACL process is decoupled from the actions against files, folders, and the registry.

    A ReACL against a Windows 10 or Windows Server 2016 device will update all files and folders and registry entries found on the machine except for the user profile specific registry keys in HKLM, ntuser.dat, and usrclass.dat even if the user profiles option is selected in the ReACL profile.

    After a ReACL has been run against a Windows 10 or Windows Server 2016 device, the user profile components will not be prepared during a cleanup process.

    The prepare and cleanup process should be completed along with the remaining ReACL activities against the user profile specific registry keys in HKLM, ntuser.dat and usrclass.dat at time of device cutover (prior to domain join command).

  • Cache Credential

    The Cache Credentials process assigns a Cache Credentials job to workstation(s). See the Credential Cache and Offline Domain Join topic for more information.

  • Offline Domain Join

    The Offline Domain Join process is similar to the Cutover process for machines that are directly connected to the network. See the Credential Cache and Offline Domain Join topic for more information.

    Warning: Do not perform the Cutover process on Offline Domain Join workstations. The Offline Domain Join process takes the place of Cutover for workstations connecting via VPN.

  • Cutover

    The Cutover process moves a Device from the source domain to the new target domain.

    Check Ignore ReACL Status to cutover the device regardless of the ReACL status (otherwise the cutover process will not proceed if there is an error with ReACL process).

    Check Do not start before and then enter or select a date and time when the process will begin. If using the Do not start before option, the Cutover Status will be displayed as Queued in the devices table and the "Do Not Start Before" column in the Device Jobs table will be populated with the selected date. The Cutover process will begin as soon as possible if not using this option.

    Note: Devices should not be ReACL'd once they have been cutover to the Target. This is not a best practice and is not supported as this can cause problems with the registry and user profiles.

  • Cleanup

    The Cleanup process removes the Source SIDs after the Cutover process completes.

    Note: Cleanup should be done when the migration project is completed. Before running the Cleanup process if a trust is in place, the trust can be broken to test if any application permissions are broken.

    In the Job Options window, click Apply to begin the Cleanup process as soon as possible. To select when the process will begin check Do not start before and then enter or select a date and time. If using the Do not start before option, the Cleanup Status will be displayed as Queued in the Devices table and the "Do Not Start Before" column in the Device Jobs table will be populated with the selected date.

  • Upload Logs

    Log files from the Active Directory Agent can be uploaded to the Active Directory Web Server using Microsoft BITS. To enable this functionality, the installer enables BITS Server Extensions for IIS and create a virtual directory called DeviceLogs where all uploaded files will be stored.

    In the Job Options window, click Apply to begin the Upload Logs process as soon as possible. To select when the process will begin check Do not start before and then enter or select a date and time. If using the Do not start before option, the Do Not Start Before column in the Device Jobs table will be populated with the selected date.

    The logs will be stored in the configured Agent Logs Repository

    The device logs will be zipped, and the file names will be in the following format with a unique file name: SMART-WIN7X86-1_201573111235.zip

  • Rollback

    The Rollback process moves a Device back to the original source domain and restores any modified network settings. The Device must have attempted Cutover for this explicit Rollback process to work.

    In the Job Options window, click Apply to begin the Rollback process as soon as possible. To select when the process will begin check Do not start before and then enter or select a date and time. If using the Do not start before option, the "Do Not Start Before" column in the Device Jobs table will be populated with the selected date.

  • ReACL Rollback

    The ReACL Rollback process rolls back all changes made by the ReACL process. ReACL Rollback can be performed on Devices that have completed the ReACL process.

    In the Job Options window, click Apply to begin the ReACL Rollback process as soon as possible. To select when the process will begin check Do not start before and then enter or select a date and time when the process will begin. If using the Do not start before option, the "Do Not Start Before" column in the Device Jobs table will be populated with the selected date.

  • Status Resets

    Use the Status Resets action to reset the statuses of the selected devices.

  • Set Device ReACL Profile

    Use the Set Device ReACL Profile action to assign a Device ReACL profile to the selected devices.

  • Set Migration Wave

    Use the Set Migration Wave action to set a migration wave to the selected devices.

  • View Jobs

    Use the View Jobs action to view the device jobs of the selected devices.

    Note: Jobs can be canceled when the Status or Rollback Status is either Queued, Scheduled, Started, or In Progress.

  • View Profiles

    Use the View Profiles action to view the profiles of the selected devices.

  • View Properties

    After the Discovery process has been completed for a Device, you can view the properties of that Device.

    Click the Export All button to export the content of the window in Excel, text, CSV, or HTML format.

  • Custom Actions

    If any Custom Actions have been created for Devices, they will appear in the Actions menu.

    In the Job Options window, check Do not start before and enter a date if you do not want the job to begin immediately. Select the Admin Agent and the Agent Admin Credentials to use from the drop-down lists. The Cutover options will also appear if the selected Admin Agent action includes the Cutover action.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating