Freigeben über

Tip of the Day: Windows ADK for Windows 10, version 1803

  • Artikel

Today's tip...

The Windows Assessment and Deployment Kit (Windows ADK) has the tools you need to customize Windows images for large-scale deployment, and to test the quality and performance of your system, its added components, and the applications running on it. The latest version of this kit is available for download below.

Direct download of the Windows ADK for Windows 10, version 1803 – https://go.microsoft.com/fwlink/?linkid=873065

What’s new in the Windows ADK for Windows 10, version 1803:

  • New PowerView tool
  • Answer file setting changes
  • MDM: Enhanced device and PC engagement

References:

Comments

  • Anonymous
    May 17, 2018
    Hi Once the adksetup.exe is download the when we try to install / or download the full ADK for 1803 seems to be getting stuck at the USMT cab file download / extract stage ( approx 32% at installation and 72% at Download process ) seems an issue on the server side Any ideas ?
    • Anonymous
      June 01, 2018
      Can you clarify more? Have you already downloaded the adksetup.exe and are trying to install all features, including USMT or are you downloading the adksetup.exe and hitting a stall when it reaches USMT?
  • Anonymous
    February 04, 2019
    When using USMT, is it possible to restore (loadstate) the store to the currently logged in user on a non domain joined PC? If not, is it possible for USMT to create the local user associated with the store created by scanstate? I have tried to use loadstate with the /all parameter and even though it does successfully restore everything, it never generates the user account(s).
    • Anonymous
      February 07, 2019
      Asked to local USMT SMEs and both mentioned that the /mu option may be the best bet here. We have an example documented for local to domain here: https://docs.microsoft.com/en-us/windows/deployment/usmt/usmt-loadstate-syntax, but I don't see anything for the opposite. USMT will create a local account unless you tell it not to. So if you scanstate a local account and the user hasn’t logged in to the new machine yet, then USMT will create the account when you loadstate the info. Not sure how this might go for scanning a domain account and then loading on a non-domain joined machine.It seems that USMT would try to restore the info and just create a local account.