Chat now with support
Chat with Support

Migration Manager for AD 8.14 - Resource Kit User Guide

InputBox

InputBox provides a graphical user interface to command-line utilities. It can be used with Migration Manager Resource Kit utilities or any other applications that accept their parameters from the command line.

Using InputBox

Using InputBox

Use the following command-line parameters:

InputBox[.exe] [{/prompt:text | /p:text}]  [{/title:caption | /t:caption}]  {/command:argument | /c:argument}  [{/remain | /r}]  [{/default:value | /d:value}]  [/{interactive | /i}]
/prompt: or /p:text

Specifies the message to be displayed in the dialog box.

/title: or /t:text

Specifies the string to be displayed in the title bar of the dialog box.

/command: or /c:parameter

The program you want to run and its command line arguments. Arguments may include %1, which will be replaced by the user input from the dialog box.

/remain: or /r

Don't close the command interpreter window after executing the command.

/default: or /d:value

Specifies the string to be displayed in the text box as the default response if no other input is provided.

/interactive: or /i

Show the command interpreter window.

Example

The following command runs the Netdom utility and prompts the user for a new name for the computer. You can write the command in a CMD file and send this file to users so they can rename their computers as they like without having to use the command line.

InputBox /p:" Please input new computer name" /t:"Rename computer" /d:%computername% /c:"netdom renamecomputer %computername% /newname:%1" /r /i

NOTE: If you run InputBox from a CMD or BAT file, use %%1 instead of %1, because %1 is interpreted as a parameter of the command file.

GPMCExport

The GPMCExport custom add-in allows administrators to migrate group policy objects (GPOs) when performing domain migration, as follows:

  1. The custom add-in retrieves account mapping information from the migration project and stores it in a file that can be imported into Microsoft Group Policy Management Console (GPMC).
  2. When migrating GPOs with GPMC, simply select the mapping file. All source security principals will automatically be translated into the corresponding target objects.

The following group policy settings contain security principals (users, security groups, and computers) and can be updated using the mapping file:

  • Security policy settings of the following types:
    • User rights assignment
    • Restricted groups
    • System services
    • File system
    • Registry
  • Advanced folder redirection policy settings.
  • The GPO Discretionary Access Control List (DACL), if you choose to preserve it during a copy operation.
  • The DACLs on software installation objects, if any. These DACLs are preserved only if the option to copy the GPO DACL is specified.

GPMCExport allows GPMC to translate all of these settings during GPO migration. Thus, all settings within GPOs, GPO security filtering (restricting GPO application), and GPO delegation (permissions on the GPO objects) can be set to the correct target domain accounts.

GPO Migration Procedure

GPO Migration Procedure

GPO migration consists of two steps:

  1. Export account mapping from Migration Manager.
  2. Migrate GPOs with GPMC.

Step 1. Export Account Mapping from Migration Manager for Active Directory

After you have completed the domain migration with Migration Manager for Active Directory, the migration project has account mapping information for all users, groups, and computers that were migrated.

Use the following procedure to export the mapping information:

  1. Make sure that your current account has at least Read access to the migration project. You can check this by running the Migration Manager console.
  2. In a Windows command prompt, change the directory to the Migration Manager ‘Resource Kit’ folder.
  3. Run GPMCExport.vbs with the following parameters:
  4. GPMCExport.vbs /host:computer /pdn:partitiondn [/port:number]

Where:

For example:

GPMCExport.vbs /host:MyServer /pdn:CN=Migration /port:389

GPMCExport will produce the following files:

  • GPMCExport.log, the custom add-in log file.
  • For each source/target domain pair, a file named SourceDomainName_TargetDomainName.migtable. If such a file already exists, it will be overwritten.

All files will be created in the folder in which the custom add-in is located.

Step 2. Migrate GPOs with GPMC

Use the following procedure to migrate GPOs:

  1. Run GPMC in the target forest (connect to a domain controller within the target forest).
  2. Add the source forest.
  3. Browse to the GPOs located in the Group Policy Objects node within the source domain.
  4. Use the GPMC user interface to copy and paste (or drag and drop) the desired GPOs from the source domain to the target domain. The Cross-Domain Copying Wizard will start.
  5. If you want the Security Filtering and Delegation lists to be migrated and translated with the Migration Manager mapping, choose the Preserve or migrate the permissions from the original GPOs option. Click Next to continue.

  1. In the Migrating References step, click Browse… and select the mapping file created by the GPMCExport custom add-in.

Finish the wizard. The GPOs will be migrated to the target forest. All the account settings that used to be set for the source accounts are translated to the corresponding target domain accounts.

After that you can link the GPOs to the appropriate domains, sites, and OUs in the target forest.

Related Documents