Migrating network printers to Windows 10 (1607) using USMT

[MeMyselfAndI]

Hi all,

I created a USMT scenario which worked fine for data/setting transfers between Windows 7 and Windows 10 (1511.)

I've updated our image to the new Windows 10 (1607). From then on the problems with the migration started. In my test case, only 1 of the 7 printers are transfered to the new Windows 10 (1607) image. Bofore that (transfer to 1511), all worked fine.

 

I use the following xml code for the transfer:

<!-- This component migrates network printers -->
<component type="Documents" context="User">
   <displayName>Mapped Printers</displayName>
      <role role="Data">
	<rules>
	  <include>
	    <objectSet>
	      <pattern type="Registry">HKCU\Printers\Connections\* [*]</pattern>
	      <pattern type="Registry">HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows [Device]</pattern>
	    </objectSet>
	  </include>
	</rules>
    </role>
</component>

The loadstate.log is exactly the same on Windows 10 1511 and Windows 10 1607. It seems that Windows 10 1607 handles the printers (or drivers?) differently?

 

Is anyone else having problems with printer migration to Windows 10 (1607)?

 

PS: Already tried the USMT from ADK 1511 and USMT from ADK 1607, both give the same issues.

[MeMyselfAndI]

Created a ticket with Microsoft.

It's a known issue. Their answer:

 

Cause: Known bug.

Resolution: Hotfix is expected to be released in October to solve the issue.

[Witcher]

Hi MeMyselfAndl,

 

any News about this?

 

KR

 

Witcher

[Thomas@ehler.dk]

I use USMT a LOT and i've not had any problems with network printers with the 1607 or 1703 ADK.
Opposite it does NOT work if I try avoiding mapped drives and printers.
I've tried adding a switch for my GUI but mapped printers/drives persist no matter what..