2.3 Perform an Active Directory to Active Directory Cross-Empire Data Migration

2.3.1 Establish a Forest Trust Configuration in the Admin Client

  1. Launch the Admin Client and click the Home tab.

  2. Click Forest Trusts and select the check box next to the displayed source forest.

  3. Click Apply.

  4. Close out of the Admin Client.

  5. Launch the Admin Client and log in.

  6. From the Home tab, click Forest Trusts and verify that the status for forest trust reads:

    Trust is fully configured and usable.

2.3.2 Assign Administrative Rights to the fdproxyrights Group

Follow these procedures to add the fdproxyrights group of the target forest as a member of the local administrators group on the server or appliance in the source forest.

  1. On the source server, launch Active Directory Users and Computers.

  2. From the Builtin directory of the forest, double-click Administrators.

  3. Click the Members tab.

  4. Click Add.

    This opens the Select Users, Contacts, Computers, Service Accounts, or Groups dialog box.

  5. Click Locations.

    This opens the Locations dialog box.

  6. Select the target forest and click OK.

  7. In the Enter the object names to select field of the Select Users, Contacts, Computers, Service Accounts, or Groups dialog box, type fdp and click check names.

    This opens the Multiple Names Found dialog box.

  8. Select fdproxyrights and click OK.

  9. Click OK to close the Select Users, Contact, Computers, Service Accounts, or Groups dialog box.

    fdproxyrights is added to the list of members in the Administrators dialog box.

  10. Click OK to close the Administrators dialog box.

2.3.3 Assign Permissions to the fdproxyrights Group

Follow these procedures to assign the fdproxyrights group of the target server, FULL Share Permissions to shares that File Dynamics will be migrating from the source forest.

  1. Using Windows Explorer on the source server, right-click the shares you plan to migrate and select Properties.

    This opens the Properties dialog box.

  2. Click the Sharing tab and click Advanced Sharing.

    This opens the Advanced Sharing dialog box.

  3. Click Permissions.

    This opens the Permissions dialog box.

  4. Click Add.

    This opens the Select Users, Computers, Service Accounts, or Groups dialog box.

  5. Click Locations.

    This opens the Locations dialog box.

  6. Select the target forest and click OK.

  7. In the Enter the object names to select field of the Select Users, Computers, Service Accounts, or Groups dialog box, type fdproxy and click Check names.

    This opens the Multiple Names Found dialog box.

  8. Select fdproxyrights and click OK.

  9. In the Permissions dialog box pertaining to the share you selected previously, assign fdproxyrights Full Control.

  10. Click OK to save the setting and close the Permission dialog box.

  11. Repeat these steps for all other shares you plan to migrate.

  12. Close the Advanced Sharing and Properties dialog boxes.

2.3.4 Verify that the Admin Client Can See Shares on the Source Server

Follow these procedures to verify that the Admin Client can see the shares that you plan to migrate.

  1. Launch the Admin Client and click the Home tab.

  2. Click Storage Resources.

  3. Verify that the shares you want to migrate are listed.

  4. (Conditional) If the shares are not listed, click Rebuild.

2.3.5 Create an Identity Map

File Dynamics uses an identity map to specify associations between the users and groups of the source forest with the users and groups of the target forest.

As specified in Section 2.2, Prerequisite Tasks, you must create the associated target server users, groups, and shares before you migrate as the Active Directory to Active Directory Cross-Empire Data Migration subsystem does not create these associated objects on the target server.

IMPORTANT:If you are creating an identity map of more than 25,000 objects, we recommend 8GB to 12GB of memory for the workstation or server running the Admin Client.

  1. Launch the Admin Client and click the Cross-Empire Data Migration tab.

  2. Click Active Directory to Active Directory.

  3. Select the source Active Directory forest.

  4. Click Edit Identity Map.

  5. Click Identity Map Entry Wizard.

  6. Select both the User to User and Group to Group check boxes.

  7. From the Match Attribute drop-down menu, select one of the following options:

    SAM-Account-Name: This attribute can be used when you want to populate the identity map with objects in the source and target forest that have the same corresponding attribute value. By choosing SAM-Account-Name (SAM) as the Match Attribute, (depending on your Source and Target Scopes) the engine will search the source and target forests for objects whose SAM are the same value.

    Common-Name: This attribute selection functions in the same manner as the SAM-Account Name, but for Common-Names (CN).

    Object-SID: This option is only applicable in the case where accounts have been migrated from the source to the target using a tool such as Active Directory Migration Tool (ADMT). When ADMT is used, you can opt to copy the Object-Sid. This results in the target object containing the Object-Sid of the originating source object in the SID-History attribute.

    For more information, refer to these Microsoft documents:

    When this Match Attribute is chosen, the engine will enumerate objects in the source and then search for objects whose SID-History attribute contains the source object's Object-Sid. If objects have not been migrated such that the source's Object-Sid is in the target's SID-History, you must use either SAM-Account-Name or Common-Name to populate the identity map.

    Well-known SIDS: This option should be used when you want to populate the identity map with well-known SIDs whose relative identifiers (RIDs) are relative to each domain (e.g. chronicle\administrator) and whose domain identifier is not "Builtin" (32).

    For more information, refer to this Microsoft document: https://msdn.microsoft.com/en-us/library/windows/desktop/aa379649(v=vs.85).aspx

    Builtin well-known SIDs can be added and mapped manually in the Identity Map editor by selecting an object from the Well-known SIDs tab, right-clicking and selecting Add Identity Map Entry.

  8. Verify that the source forest and target forest in the Source Scope and Target Scope regions respectively, are correct and click Next.

  9. Observe the matching results of source and target groups and users.

  10. Click Next.

  11. In the Import Map Entries page, leave the Auto-save Identity Map updates to Engine check box selected and click Finish.

    The users and groups on the source and target forests are now matched.

2.3.6 Preview the Source Paths for the Migration

Follow these procedures to preview the migration source paths as well as add and match any missing objects to the identity map.

  1. In the Identity Map interface, click Source Paths > Generate Preview Report.

  2. In the Preview Migration Source Paths dialog box, in the upper left-hand pane, navigate to the desired share and double-click it to add it to the Path window to the right.

  3. From the Path Scan Options drop-down menu, select from the following options:

    Scan Folders Only: Scans only the folder permissions in the specified paths.

    Scan File Owners: Scans the folder permissions and the file owners in the specified paths.

    Scan File Owners and Permissions: Scans the folder permissions, file owners, and file permissions in the specified paths.

  4. Click Preview Paths.

    For ease in identifying all unmapped (orphaned) SIDs, use the sort arrow which is located on the first column heading in the lower portion of the interface.

  5. Repeat Step 2 for all shares you want to migrate.

  6. Click the Owner Entries tab and view the orphaned SIDs, meaning all of the folders and files without owners.

  7. Click the Unique IDs tab and view the unmatched objects.

    These are objects that you will need to add to the identity map.

  8. Click Add Entries to add the new entries to the identity map.

  9. Click Close to close the Preview Paths page.

2.3.7 Add Unmapped Objects to the Identity Map

Follow these procedures to add any unmapped objects listed in the Unique IDs tab to the identity map.

  1. In the identity map, click the Target Account column heading to sort unmapped objects so they are all listed as a group at the top of the list.

  2. From the Browser Target tab on the right pane, locate an object you want to indicate as an owner for an unmapped object and drag the object up to the unmapped object’s corresponding Target Account column entry.

    This changes the unmapped object’s Target Account listing from [Do Not Translate] to the new owner object.

  3. When you are finished specifying owners for your unmapped objects, click Apply.

  4. Click OK.

2.3.8 Generating a Preview Report Before Migrating

You can easily generate a preview report as a CSV file before you migrate. This might be useful if you needed to provide a report to a CIO or other members of the migration team.

  1. Launch the Admin Client and click the Cross-Empire Data Migration tab.

  2. Click Preview Source Path.

  3. Double-click the top entry in the list.

  4. From the View Report page, click the CSV icon to save the report as a CSV file.

2.3.9 Determine If You Are Going to Migrate the Data in Two Phases or One

Before you migrate data from the source to the target forest, you must determine if you will be migrating in two phases or one.

Two-Phase Migration

In the first phase, you migrate all unopened files while skipping all opened files. In the second phase, you get all of your users to log off of the network (assuring that they have no files opened), then you migrate all of the skipped files, then all of the new and modified files.

A two-phased migration is more suitable to organizations with data sets too large to migrate over a weekend.

Single-Phase Migration

This approach lets you migrate all of the data in one phase. You must have all users logged off of the network and be able to migrate the data before the users return to work.

2.3.10 Migrate Group Data

HINT:To view the status of the migration, we recommend that you install and run a Tail program and use it to tail the Agent log path located at: "%programdata%\Micro Focus\File Dynamics\Agent\log\fsagent-xxx-xxx.log”

Follow these procedures to migrate group data from the source forest to the target forest.

  1. In the Admin Client, click the Cross-Empire Data Migration tab.

  2. Click Active Directory to Active Directory.

  3. Select Migration Wizards > Data and Security.

    This launches the Folder to Folder Migration wizard.

  4. Do one of the following:

    • If you plan to do a two-phase migration by skipping open files, leave the Generate Automatic Mappings check box deselected and click Next. Browse to specify the source and target folders and click Next.

      This method will create a single source path and single target path, which alleviates potential problems that can surface when skipping open files during a migration.

    • If you plan to do a single-phase migration, you can select the Generate Automatic Mappings check box to create any needed subfolders on the target that do not already exist. Browse to specify the source and target folders and click Next.

  5. In the Define Mappings page of the wizard, observe the migration events that are now queued up.

  6. Click Next.

  7. (Conditional) If you are doing a two-phase migration, in the Data Copy Options page, select the Skip Open Files check box.

    1. Click the Browse button that corresponds to the Delta File field and through the path browser, select the folder where you want to store the delta file.

    2. Right-click and select New Folder and click OK.

      The delta file name is created and displayed in the Delta File field.

  8. Click Next.

  9. In the Data and Security page, select the Use the Identity Map check box.

  10. Select either the Merge Security or Overwrite Security option.

    Merge Security: This option merges the permissions of the source folder with those of the target folder.

    Overwrite Security: This option overwrites the permissions of the target folder with those of the source folder.

  11. From the Owner for Target Folder drop-down menu, select your preferred option.

    1. If you select either Default Owner if not in Identity Map or Set Explicit Owner, browse to assign an owner.

  12. From the Owner for Target Folder Contents drop-down menu, select your preferred option.

    1. If you select either Default Owner if not in Identity Map or Set Explicit Owner, browse to assign an owner.

  13. Click Next.

  14. Click Migrate.

    The queued migration events are listed.

  15. Click Finish.

  16. In the Admin Client, from the Identity Driven tab, click Events to view the status of the migration.

  17. (Optional) If you have a Tail program, you can view the status of the migration.

2.3.11 Migrate User Data

Use these procedures to migrate user home folders from the source forest to the target forest.

  1. In the Admin Client, click the Cross-Empire Data Migration tab.

  2. Click Active Directory to Active Directory.

  3. Select Migration Wizards > Data and Security.

    This launches the Folder to Folder Migration wizard.

  4. Do one of the following:

    • If you plan to do a two-phase migration by skipping open files, leave the Generate Automatic Mappings check box deselected and click Next. Browse to specify the source and target folders and click Next.

      This method will create a single source path and single target path, which alleviates potential problems that can surface when skipping open files during a migration.

    • If you plan to do a single-phase migration, you can select the Generate Automatic Mappings check box to create any needed subfolders on the target that do not already exist. Browse to specify the source and target folders and click Next.

  5. In the Define Mappings page of the wizard, observe the migration events that are now queued up.

  6. Click Next.

  7. Select the appropriate Overwrite and Directory Quota options, and whether the migrated user data will be located in a subfolder of the target, then click Next.

  8. In the Security and Ownership page, select the Use the Identity Map check box.

  9. Select either the Merge Security or Overwrite Security option.

  10. Within the Owner for Target Folder and Owner for Target Contents drop-down menus, leave the Copy Existing Source Owner options selected.

    As a best practice, each user should be established as the owner of their files and folders. For those instances where folders and files that aren’t owned by the users, we will address them later once we create a policy and then perform Management Actions following the migration.

  11. Click Next.

  12. In the Copy Filter page, select the User Copy Filter check box.

  13. Click Add to create a copy filter of those files you do not want to copy to the target forest.

    For example, you probably want to avoid copying .TMP files.

  14. Click Validate and observe what will be migrated.

    If you observe any potential problems, you will want to correct them at this time.

  15. Click Migrate.

    The queued migration events are listed.

  16. Click Finish.

  17. In the Admin Client, from the Identity Driven tab, click Events to view the status of the migration.

  18. (Optional) If you have a Tail program, you can view the status of the migration.

2.3.12 Determine If Any Files Were Skipped

Follow these procedures to see if the Delta file lists any skipped files.

  1. From the location where you saved the Delta file, open it to see if any files are listed.

    If any are listed, those are all of the files that were skipped during the first phase of the migration.

  2. (Conditional) If files are listed, you must have the owners of these files close the files before proceeding with Section 2.3.13, Migrate Skipped, Modified, and New Files

2.3.13 Migrate Skipped, Modified, and New Files

Follow these procedures to migrate any files that were skipped, modified or that were created since the first phase of the migration.

  1. In the Admin Client, click the Cross-Empire Data Migration tab.

  2. Click Active Directory to Active Directory.

  3. Select Migration Wizards > Data and Security.

  4. In the Select Migration Type Options page, click Next.

  5. In the Define Mappings page, specify the same source and target paths that you specified in Section 2.3.11, Migrate User Data and click Next.

  6. In the Data Copy Options page, from the Overwrite Options drop-down menu, select Overwrite if Newer, select the Skip Open Files check box, and browse to the location where you stored your original Delta file to create a new Delta file.

  7. Click Next.

  8. In the Security and Ownership page, select the Use Identity Map check box, and specify the same Owner for Target Folder, Owner for Target Folder Contents, and related paths as you did in Section 2.3.11, Migrate User Data.

  9. Click Next.

  10. Click Validate and observe what will be migrated.

    If you observe any potential problems, you will want to correct them at this time.

  11. Click Migrate.

    The queued migration events are listed.

  12. Click Finish.

  13. In the Admin Client, from the Identity Driven tab, click Events to view the status of the migration.

  14. (Optional) If you have a Tail program, you can view the status of the migration.

2.3.14 Using CEDMScanCompare.exe to Compare Folders and Files Between the Source and Target

With the skipped, modified, and new files and folders migrated, you are now ready to compare the folders and files between the source and target forests to verify that everything migrated properly.

  1. Launch the CEDMScanCompare utility that you copied earlier.

    The following message appears:

  2. Click OK.

  3. Browse to a folder where you want to store the comparison data and click Select Folder.

    The CEDMScanCompare utility interface is launched.

    The selected folder location is specified in the Working Directory field.

  4. In the Source region, for the Path to Scan field, browse to specify the UNC path to the folder in the source forest you want to scan.

    For example: \\WIN-2012-A1ForestB.ORG\NYCvol1\DeptShares

  5. In the Target region, for the Path to Scan field, browse to specify the UNC path to the folder in the target forest you want to scan.

    For example: \\WIN-2012-R2.CCTEC.COM\NYC\Departments

  6. In the Source region, click Scan.

  7. In the Scan Result region, note the findings in the Folders and Files fields.

  8. In the Target region, click Scan.

  9. In the Scan Result region, note the findings in the Folders and Files fields.

  10. In the Compare / Analyze region, from the FileName drop-down menu, select Cross-Empire Data Migration-AD.

  11. Click Compare.

  12. Do one of the following:

  13. Click Open Full Differences File.

    A spreadsheet appears listing:

    • All files on the source that are newer than the same named files on the target, along with the source and target path of each file.

    • All files on the source that are missing from the target.

  14. View the files that are newer on the source server as well as those files on the source server that were not migrated.

  15. Have all of your network users close any open files in the source area, and once again, follow the procedures in Section 2.3.13, Migrate Skipped, Modified, and New Files.

  16. Run the CEDMScanCompare utility again. When the you have verified that all of the folders and files have migrated, proceed with Section 2.3.15, Manage the Migrated User Folders through a File Dynamics Home Folder Policy.

2.3.15 Manage the Migrated User Folders through a File Dynamics Home Folder Policy

Once you have migrated all of the user data, you will want to manage it through File Dynamics. Follow these procedures to create a Home Folder policy and then enforce the policies settings through Management Actions.

Prerequisite

If the container where you migrated the user home folders does not already have a File Dynamics policy, create a Home Folder policy by following the procedures in Creating a User Home Folder Policy in the Micro Focus File Dynamics 6.5 Administration Guide.

Enforcing the Policy through Management Actions

Perform the following tasks and Management Actions to enforce the policy settings on the migrated home folders.

  1. Run a Consistency Check.

    For more information, see Performing a Consistency Check in the Micro Focus File Dynamics 6.5 Administration Guide.

  2. Perform the following Management Actions:

    • Assign Managed Path

      See Assign Managed Path in the Micro Focus File Dynamics 6.5 Administration Guide.

    • Manage

      See Manage in the Micro Focus File Dynamics 6.5 Administration Guide.

    • Apply Permissions

      See Apply Permissions in the Micro Focus File Dynamics 6.5 Administration Guide.

    • Apply Owner

      See Apply Owner in the Micro Focus File Dynamics 6.5 Administration Guide.