Answered by:
Same USMT printer migration scenario works differently on Windows 10 1607 vs Windows 10 1511

Question
-
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>
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.
- Edited by AreYouGonnaGoMyWay Thursday, September 8, 2016 9:36 AM
Monday, August 29, 2016 9:46 AM
Answers
-
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.
- Proposed as answer by Frank Dong Monday, September 12, 2016 5:28 AM
- Marked as answer by Frank Dong Monday, September 12, 2016 5:28 AM
- Edited by AreYouGonnaGoMyWay Monday, September 12, 2016 5:49 AM
Friday, September 9, 2016 10:07 AM
All replies
-
Hello,
please check the following thread which has the same issue, although that is for win 7 but there is smiliar issue which you have.
if the above doesnot provide any help then share the more details about the error/issue you are getting, log file and all.
Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.
- Edited by SinghSharad Monday, August 29, 2016 9:51 AM
Monday, August 29, 2016 9:50 AM -
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?Monday, August 29, 2016 11:54 AM
-
I was hoping that the new cumulative update KB3176938 would solve this issue, but it's not :(Thursday, September 1, 2016 11:31 AM
-
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.
- Proposed as answer by Frank Dong Monday, September 12, 2016 5:28 AM
- Marked as answer by Frank Dong Monday, September 12, 2016 5:28 AM
- Edited by AreYouGonnaGoMyWay Monday, September 12, 2016 5:49 AM
Friday, September 9, 2016 10:07 AM -
Hey, has this been fixed? I'm having same issue, but do not see where a hotfix was released.Tuesday, September 5, 2017 6:46 PM
-
I'm also interested in an update on this - seem to be unable to migrate network printer connections from Windows 7 (x86) to Windows 10 1704 (x64) - if that's even possible?
My Personal Blog: http://madluka.wordpress.com
Friday, September 29, 2017 11:02 AM -
Hi,
I am trying to achieve the same. I am going to migrate windows 7 to windows 10 - Format and install - I am not backing up user data, it is taken care by desktop backup solution but I stuck with Network printers for users. Can you share your experience and TS if possible.
Thanks
Khan MCTS,MCSE Saudi Arabia
Thursday, March 28, 2019 7:23 AM