Search the Community
Showing results for tags 'UMST'.
Found 2 results
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.
I have an issue with our SCCM 2012 SMP not deleting files on the schedule dictated in the settings (5 days). Attached is a screen shot of the Task Sequence where the loadstate is requested and the release state store should be occurring. Any suggestions are welcome. I can include additional data if helpful. Matt