Make an existing MDT (2012 update 1) enviroment ready for Windows 10

In this post, I will describe the steps needed to update a existing Microsoft Deployment Toolkit (MDT) 2012 environment to MDT 2013 Update 2. This MDT update is needed to prepare for a new automated Windows 10 deployment.

Requirements

MDT 2013 Update 2 has the following requirements

Install Windows ADK for Windows 10

On the existing MDT server, download the Windows ADK for Windows 10 update files. I have placed these files on D:\Downloads\ADK.

  1. Log on to the server with an account that has administrator rights.
  2. Start the ADK Setup (D:\Downloads\ADK\adksetup.exe), and click Continue.
  3. On the Select the features you want to change page, select the features below and complete the wizard using the default settings:
    1. Deployment Tools
    2. Windows Preinstallation Environment (Windows PE)
    3. User State Migration Tool (UMST)

Install MDT 2013 Update 2

Download the MDT 2013 Update 2 files to D:\Downloads\MDT

  1. Install MDT (D:\Downloads\MDT 2013\MicrosoftDeploymentToolkit2013_x64.msi) with the default settings
  2. Start the Deployment Workbench
  3. Right click on your Deployment Share and click ‘Upgrade Deployment Share’. This update can take a while, depending on the size of your MDT environment.

Request an overview of installed Microsoft Hotfixes using Powershell

One of my customers requested a overall view of the servers where one or more Microsoft Hotfixes were installed. I’ve used a small and simpel PowerShell script to do that.

This scripts uses a text file (serverlist.txt) to check which servers it needs to use to look for the Hotfix(es). Place each server ona  different line. I have placed the text file on d:\ServerLixt.txt. Use it like this:

server1
server2
server3
..etc

GetHotfix.ps1 generates a overview of installed hotfixes (in this case KB2486635) on the requested servers.

$Servers = Get-Content 'd:\ServerList.txt'
 
Invoke-Command -ComputerName $Servers -ScriptBlock {
    $Result = Get-Hotfix | where {$_.hotfixid -eq 'KB2486635'}
    if ($Result) {
        New-Object PSObject -Property @{Host = hostname; Value = $true}
    } else {
        New-Object PSObject -Property @{Host = hostname; Value = $false}
    }
}

Looking up multiple hotfixes is possibile to extend the script with multiple ‘KB12345678’. For more information about the Get-Hotfix command: slook here.