locked
Network Printer Migration is getting failed using USMT RRS feed

  • Question

  • Hi experts,

    we are migrating users' desktops from Windows XP to Windows 7. We need to migrate network printer setting by using Windows User State Migration Tool (USMT 4.0). While testing the migration for network printer setting we are not able to migrate them.

    Please find the Printer.xml coding below.

    <?xml version="1.0" encoding="UTF-8"?>
    <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/custom">


    <component context="UserAndSystem" type="System" defaultSupported="FALSE">

    <displayName _locID="migsys.Printer">Printer</displayName>
    <role role="Settings">
    <rules>
    <destinationCleanup>
    <objectSet>


    <pattern type="Registry">HKCU\software\microsoft\windows NT\currentVersion\Windows\* [*]</pattern>
    <pattern type="Registry">HKCU\software\microsoft\windows NT\CurrentVersion\Devices\* [*]</pattern>
    <pattern type="Registry">HKCU\software\microsoft\windows NT\CurrentVersion\printerPorts\* [*]</pattern>
    <pattern type="Registry">HKCU\software\microsoft\windows NT\CurrentVersion\Windows\* [*]</pattern>
    <pattern type="Registry">HKCU\software\microsoft\windows NT\CurrentVersion\Print\Printers\* [*]</pattern>
    <pattern type="Registry">HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\* [*]</pattern>
    <pattern type="Registry">HKLM\SYSTEM\ControlSet001\Control\Print\Environments\WindowsNT x86\Drivers\* [*]</pattern>
    <pattern type="Registry">HKLM\SYSTEM\CurentControlSet\Control\Print\Printers\* [*]</pattern>
    <pattern type="Registry">HKLM\SYSTEM\ControlSet001\Control\Print\Printers\* [*]</pattern>
    <pattern type="Registry">HKLM\SYSTEM\CurrentControlSet\Services\servername\Shares\* [*]</pattern>
    <pattern type="Registry">HKLM\SYSTEM\ControlSet001\Services\servername\Shares\* [*]</pattern>
    </objectSet>
      </destinationCleanup>
    </rules>
    </role>
    </component>


    <!-- This component migrates the printers and network drives -->
    <component type="System">
        <displayName>Printers and Network Drives</displayName>
            <role role="Settings">
                <rules context="UserAndSystem">
                    <include>
                        <objectSet>
                            <pattern type="Registry">HKCU\Printers\* [*]</pattern>
                            <pattern type="Registry">HKCU\Network\* [*]</pattern>
                        </objectSet>
                    </include>
                </rules>
            </role>
    </component>

    </migration>

    Kindly Help. thanks in advance.

    Friday, September 21, 2012 4:09 AM

Answers

All replies

    • Marked as answer by Sabrina Shen Wednesday, September 26, 2012 8:33 AM
    Monday, September 24, 2012 6:21 AM
  • I can see that this is an old post, however i am having the same issue.

    What if i am using just USMT without MDT? Is there a file that i need to modify as well?

    Thursday, October 31, 2013 6:44 PM
  • This behavior may occur if you run the LoadState.exe portion of the User State Migration Tool from a mapped network drive that is not available to the user whose account you are trying to migrate.

    The user account Cookies, network printers, and mapped network drives are restored when the user logs on to the computer after you run the LoadState.exe command. If the mapped network drive (the drive from which you ran LoadState.exe) is not available to the user, these user account items are not restored. Loadstate.exe runs again when the user logs on for the first time. When the Loadstate.exe command is added to the users Runonce registry key, a modified copy of the original command-line is used, including the path information. The migrated user must have access to the Loadstate.exe file for the user account information to be successfully restored.


    To resolve this issue, run the LoadState.exe command from a Universal Naming Convention (UNC) path (for example,\\<var>server</var>\<var>share</var>) instead of a mapped network drive. Make sure the user whose account is being migrated has access to the UNC path. If you run the LoadState.exe command from the UNC path, the remaining information is migrated when the user logs on to the computer after you run LoadState.exe.


    Monday, November 18, 2013 5:08 PM