Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

PowerShell crashes when you use Windows Server Migration Tools in Windows


Summary

Consider the following scenario:
  • You are using Windows Storage Server 2012 or Windows Storage Server 2012 R2.
  • You are using the Windows Server Migration Tools to import data from a Windows Server 2003 or a Windows Storage Server 2003 machine.

In this scenario, when you try to import the migration data, PowerShell crashes and the data import fails.

↑ Back to the top


Cause

This issue occurs because a role supported on Windows Server 2003 and Windows Storage Server 2003 is incorrectly migrated to Windows Storage Server 2012 or Windows Storage Server 2012 R2.

↑ Back to the top


Status

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

↑ Back to the top


Workaround

Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.


To avoid this issue, go to the "Fix it for me" section. If you prefer to avoid this issue yourself, go to the "Let me fix it myself" section.

Fix it for me

To avoid this issue, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

Notes
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email message.


Let me fix it myself
To avoid this issue, delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerMigration\Roles\207 registry key after installing Windows Server Migration Tools. To do this, follow one of these methods:

Method 1: Delete registry key with Registry Editor

  1. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.
  2. In the search box, type regedit, and then tap or click regedit to open the Registry Editor.

    Note If you are prompted to enter an administrator password, type the password. If you are prompted to provide confirmation, provide confirmation.
  3. Delete the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerMigration\Roles\207

Method 2: Delete registry key with command prompt

  1. Open command prompt with administrator permissions.
  2. Type the following command:
    reg delete HKLM\SOFTWARE\Microsoft\ServerMigration\Roles\207 /f 




↑ Back to the top


More Information

Windows Server Migration Tools (WSMT) does not support migration between operating systems that have a different system UI language (the language that is used during installation). Windows Storage Server 2003 is only available in English, and therefore the system UI language is always English. Because of this, when you try to migrate a Windows Storage Server 2003 system to a non-English operating system, the migration fails.

Note The UI of the Windows Storage Server 2003 system may not be English if additional language packs are installed, but the system UI language will always be English.

For more information about WSMT, visit the following Microsoft website:

↑ Back to the top


Keywords: kbfixme, kbmsifixme, kb

↑ Back to the top

Article Info
Article ID : 2967658
Revision : 1
Created on : 1/7/2017
Published on : 8/6/2014
Exists online : False
Views : 89