The Importgpo.wsf script that is provided with Group Policy Management Console does not import the changes in the migration table on a Windows Server 2003-based computer

When you use the Importgpo.wsf script that is provided with Group Policy Management Console (GPMC) on a Microsoft Windows Server 2003-based computer, the script does not import the changes that are defined in the migration table and that are called by the /MigrationTable: argument.

This problem occurs because of a coding error in line 162 of the Importgpo.wsf script.

To resolve this problem, open the Importgpo.wsf script in a text editor such as Notepad and make the following change to line 162 of the script.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Existing code

Replacement code

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The Importgpo.wsf script makes a backup copy of a Group Policy object (GPO) and then imports the settings from the backup GPO into a specified GPO.

You can use the optional /MigrationTable: argument when you import a GPO to map security principals and paths across domains. For example, you could run the Importgpo.wsf script with the following options:

For more information about the Importgpo.wsf script, see the GPMC Help file (GPMC.chm). The GPMC Help file is located in the following folder on the drive where GPMC is installed: