Thomas@ehler.dk

Established Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Thomas@ehler.dk

  • Rank
    Newbie
  1. 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..
  2. Hi I'm in deep here but old trustworthy Google turned up this: - Try looking under ClientIDManagerStartup.log: https://blogs.technet.microsoft.com/configurationmgr/2015/08/10/support-tip-configmgr-2012-client-fails-to-register-cross-forest-when-installed-using-the-command-line/ /Sam
  3. All PC's on the old domain are visible under devices on the new SCCM? Then you should be able to push the client to them from the new SCCM? What about new SCCM local Administrator rights on the Pc's in the old domain. Did you add that with a policy and is it effectuated?
  4. Hi Did you publish successfully to the new domain (Administration, Hierarchy, Activ Directory forests)?
  5. Finally!! The USMT release for Windows 10 version 1704 will have full support for migration to Office 2016. Also the tool seems to have been thoroughly worked through in this release. There is aditions to AppV and also look into Johan Arwidmarks walkthrough of the new ADK. You can download the Windows ADK 10 Insider Preview v15021 on the below link - log in with your insider account (create one if need be): Windows Insider Preview Downloads https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewADK