Jump to content


Search the Community

Showing results for tags 'Windows 10 1607'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 1 result

  1. 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.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.