Tuesday, August 18, 2015

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

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

Wednesday, July 1, 2015

Windows 10 Build 10158 and up product keys

The Insider Preview build of Windows 10 are getting new products keys. If you are upgrading from a previous build you should not get any problem with the old activated keys.

If you are doing a new clean install you will need to type in the right product keys.
Clean install can be done when the ISO file is available later (when the build hits slow ring), or when you create your own ISO with this guide from the ESD file

Friday, June 12, 2015

Windows Server 2003/R2 End of life 14. July 2015

A great friend will leave us on july the 14. 2015. He have served us well and his descendants will for sure continue to server us into the future. Thanks for your services my old friend

What does this mean and what can/should we now do?

Thursday, May 21, 2015

Windows 10 breakfast seminar slide deck are now ready for download

Lots of topics cover in what time we had available today. Some minor problem with running it all on a build of Windows 10 made public about 12 hours before the seminar (of course display driver related ;-), but still a fun session to do.

Slides HERE

Tuesday, May 19, 2015

Noen ledige plasser på Windows 10 frokost semniar i Bergen 21.mai

Det er et par ledige plasser på frokost seminaret jeg skal holde på torsdag 21.mai.

Jeg kommer til å se på versjoner av Windows 10, oppdateringering (inkludert "Current branch for business" og "Long term servicing branch"), sikkerhet og mye mer.

Mer informasjon HER og påmelding HER

Saturday, May 9, 2015

Ignite - Slides from my session

Ignite is over, a great week with lots of highlights.
After 3 session with The Blues Brother as a starter topic, it was a real pleasure on the 4 and last session to get visited bye them on stage.

My session can be downloaded here
Picuture from unitedsandhausen

Wednesday, May 6, 2015

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

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 from the file into a variable that we can use with the slmgr command.

Testing out some different solutions we ended up in this nice little line:

for /F "delims=" %%a in ('%~dp0get_win8key.exe') do set key=%%a

The get_win8key.exe files need to be located in the same folder as the cmd files that we want to run the script. We now have a variable with the result from the get_win8key

Next thing is that we want to insert that key into Windows with the “slmgr” and active it. We also want this to be done quiet. The quiet part are done with the parameter //B in cscript. We then need 2 lines of slmgr :

cscript //B %windir%\system32\slmgr.vbs /ipk %key%

cscript //B %windir%\system32\slmgr.vbs /ato

Pasting the code together it will look like this:

The next step is to copy both the get_win8key.exe and a cmd file with the script into the script folder at out MDT deployment share. I have simply called the script file “Get-Winkey.cmd”

I then need to modify the task sequence that I use to install Windows Pro (Remember that you need to have a BIOS with the key for this to work, and if you are deploying anything else then a version matching the version of the key in BIOS it will fail. Try doing it manually if you are unsure)

Thursday, April 30, 2015

My sessions at Ignite 2015

Just days away from Ignite in Chicago, and I am already on the way from Norway.
I will do 2 different sessions this year with a repeat on both.

This is Windows Theater sessions so that means it will be 15-20 intense minutes, no time for bull.