Windows 10 Auto deployment via In-place upgrade

[German]In enterprise environments, administrators may face the problem of having to distribute Windows 10 upgrades automatically, possibly via SCCM or similar tools. Here is a solution, using a batch file to deploy an in-place upgrade approach for Windows 10.


Advertising

Josh Hefner, who presented the solution in his blog, writes that he recently faced the scenario with a client that he had no Configuration Manager infrastructure available. He normally uses Intune to manage workstations, but ran into problems configuring MDT to support Windows 10 upgrades.

Josh points out that there are still some known problems with MDT and Windows 10. These are described in this Technet article from 2015.

However, Josh Hefner had to automate the deployment of Windows 10 for end users. He is using a very elegant solution: Instead of distributing feature updates, he uses a cmd file to trigger an in-place upgrade of the client to the desired Windows 10 version.

Installationsdateien
(Install files, Source: joshheffner.com)

  • First, copy all files of the installation image required for installation into a folder structure of a network drive (see above image)..
  • Create a batch file Install.cmd within a the folder of the structure shown above, to start the deployment. The cmd file contains the following command.

start /wait .\Win10\setup.exe /auto upgrade /migratedrivers all /dynamicupdate enable /showoobe none /pkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Basically, the command only starts the setup.exe and lets the system upgrading via an in-place update. Parameters can be used to control the upgrade and also enter the product key for the client. You can read more details in Josh’s article.


Advertising


Advertising
This entry was posted in Update, Windows and tagged , , , . Bookmark the permalink.

1 Response to Windows 10 Auto deployment via In-place upgrade

  1. Karl Wester-Ebbinghaus says:

    As documented on docs.microsoft.com :)
    He can also use WSUS instead of MDT.

Leave a Reply

Your email address will not be published. Required fields are marked *