Skip to main content

Deploying Windows 10

In middle of August Windows 10 have supposedly reached more than 50 million computers (info here), and with users trying it out at home and loving it, the pressure to get it at work computers also are build up.

Microsoft have done different measure to make sure that enterprises will have more control over their Windows 10 deployment.

The Windows 10 upgrade should be automatically blocked on computers or devices in the following scenarios:

  • The computer or device is joined to a domain.
  • The computer is managed through MDM.
  • The computer is running any of the following systems that are excluded from this reservation offer:
    • Windows 8.1 Enterprise or Windows 8 Enterprise
    • Windows RT 8.1 or Windows RT
    • Windows Embedded 8.1 Pro
    • Windows Embedded 8 Standard
    • Windows Embedded 8.1 Industry or Windows Embedded 8 Industry
    • Windows 7 Enterprise
    • Windows 7 for Embedded Systems
    • Windows Embedded Standard 7
    • Windows Embedded POSReady 7
More info here

To help enterprises to deploy Windows 10, Microsoft have too day released MDT 2013 Update 1, with the ADK here. You can read Aaron Czechowski blog about it here

And on Technet you will find a comprehensive library of great Windows 10 deployment information here

https://technet.microsoft.com/en-us/library/mt158221(v=vs.85).aspx
 
You will get step by step guidance on how to upgrade to or deploy Windows 10, and newer stuff like provisioning packages


Other great resources:
Johan Arwidmark's
Deployment Research - A Geeks Guide for upgrading MDT 2013 to MDT 2013 Update 1

Mikael Nystrom
The Deployment Bunny

Michael Niehaus
Windows and Office deployment ramblings - MDT 2013 Update 1 Preview: What’s Changed

Popular posts from this blog

Changing Windows product key (license) for a MDT OS deployment task

Creating a new OS deployment task in MDT you will be asked to specify product key


That’s easy enough, but what if you type in the wrong key or just want to change it (add it) later? You might even have gotten a new MAK.

That is not as easy, you cannot do it from the graphical interface, you have to do it from one of the configuration files. Well you might to it from graphical interface by typing it in every time deploying a computer gets deployed but that is not a great solution.

MDT - The task sequence has been suspended. LiteTouch is trying to install applications

Every now and then I get this error message when fuelling a computer with MDT:
"The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

How to get and use the Windows key from UEFI/BIOS

I found myself in the situation that I needed to get the Windows key out from the ACPI in the UEFI bios and preferable get to use it in a task sequence in MDT.

There are different ways of doing this, but I wanted to do this with little code and easy to understand.
There is a nice tool created to get the key on github, created by Christian Korneck, called get_win81key. This tool gives you the key in plane text. You can get it
HERE: https://github.com/christian-korneck/get_win8key


If I were supposed to do this manually, I now would just take that key and type it in with slmgr command or in the GUI. But I want to do this within a task in MDT.
Testing a couple of solutions without using the get_win8key with my great scripting guru colleague Håvard ( www.grondal.me) and figuring out that it cannot be done with default powershell stuff, it needs more code. Therefore, we quickly figured out that some use of the “get_win8key” files is the easiest way, but we need a way of setting the output fro…