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.

Windows 7 x86 to Windows 7 x64 migration of mapped printer connections fails using USMT 4/5


Symptoms

Mapped printer connections fail to migrate in the following scenarios:
  • Windows 7 x86 to Windows 7 x64 migration using USMT 4 or USMT 5
  • Windows 8 x86 to Windows 8 x64 migration using USMT 5
Excerpts from the loadstate log look similar to the following:

2012-10-23 10:16:47, Status                [0x000000] Processing State Microsoft-Windows-Printing-Spooler-Networkclient[@version="6.2.9200.16384" and @arch="x86" and @culture="neutral" and @context="perUser"]/settings/PrinterConnections/PrinterConnections/[@keyValue=",,server1.contoso.com,HP Universal Printing PCL 5"]

2012-10-23 10:16:47, Warning               [0x080000] Could not create object {User}-{Microsoft-Windows-Printing-Spooler-Networkclient}-{6.2.9200.16384}-{x86}-{neutral}-{settings\PrinterConnections\PrinterConnections\[@keyValue=",,server1.contoso.com,HP Universal Printing PCL 5"]}-NULL. Exception class Mig::SideAwareWin32Exception: The system cannot find the file specified. [0x00000002] void __cdecl Mig::CStateDataStore::Create(class Mig::CDataUnit *)

2012-10-23 10:16:47, Info                  [0x080000] Error 2 during apply of object {User}-{Microsoft-Windows-Printing-Spooler-Networkclient}-{6.2.9200.16384}-{x86}-{neutral}-{settings\PrinterConnections\PrinterConnections\[@keyValue=",,server1.contoso.com,HP Universal Printing PCL 5"]}-NULL. Will ask shell application for resolution.

2012-10-23 10:16:47, Info                  [0x080000] Error 2 while applying object {User}-{Microsoft-Windows-Printing-Spooler-Networkclient}-{6.2.9200.16384}-{x86}-{neutral}-{settings\PrinterConnections\PrinterConnections\[@keyValue=",,server1.contoso.com,HP Universal Printing PCL 5"]}-NULL. Shell application requested ignore


↑ Back to the top


Cause

The built-in manifest for migrating printers on Windows 7 and Windows 8 does not properly handle the x86 to x64 migration when the OS is Windows 7 to Windows 7 or Windows 8 to Windows 8. 

↑ Back to the top


Resolution

At the time of this writing, there is no hotfix available for this issue for USMT 4 or USMT 5.


↑ Back to the top


Workaround

A work-around is available that will allow mapped printer connections to migrate in the scenarios described in this article. To work-around this issue, create a custom XML file and specify it on scanstate and loadstate using /i. The XML file should contain the following:


<?xml version="1.0" encoding="utf-8" ?>

<!--                 
==========================================================
Version migPrinters.XML 
==========================================================                                        
-->
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/IR_Config">
  <!-- Printer and Network -->
  <component type="System">
    <displayName>This should migrate the users Printers key</displayName>
    <role role="Settings">
      <rules context="UserAndSystem">
        <include>
          <objectSet>
            <pattern type="Registry">HKCU\Printers\* [*]</pattern>
          </objectSet>
        </include>
      </rules>
    </role>
  </component>
</migration>


↑ Back to the top


Keywords: kb

↑ Back to the top

Article Info
Article ID : 2776503
Revision : 1
Created on : 1/7/2017
Published on : 12/13/2012
Exists online : False
Views : 81