Updates fail or time out when WSUS is used during an MDT or SCCM capture

microsoft black logo

This guide assumes that you use Microsoft Deployment Toolkit (MDT build 8443) or Microsoft System Center Configuration Manager (SCCM) capturing Windows 10.

You capture a task sequence, and the capture computer does not have Internet access. When the task sequence is running and the computer is checking for updates (pre-application installation), the installation freezes for 2 hours while searching for updates. After that, all approved updates are scrolled through and installed in seconds. But after several attempts, the process then fails and times out, and you receive error messages like the following:

Failed to download: 4816e53b-6f86-43c5-a740-0cafbe6317f5  result(4) : Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4015583) ZTIWindowsUpdate 4/18/2017 4:15:59 PM 0 (0x0000)

Failed to download: f6df2191-75f3-445d-87b8-557ef2b3536c  result(4) : Security Update for Adobe Flash Player for Windows 10 Version 1703 (for x64-based Systems) (KB4018483) ZTIWindowsUpdate 4/18/2017 4:15:59 PM 0 (0x0000)

Cause

This issue occurs when the computer is configured to use Windows Server Update Services (WSUS), but the computer tries to connect sls.update.microsoft.com for updates.

Resolution

To fix this issue, run the following command to set the download mode of Windows Update Delivery Optimization to bypass delivery optimization and use Background Intelligent Transfer Service (BITS) so that clients can use BranchCache:

REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization /v DODownloadMode /t REG_DWORD /d 100

Feedback

If you have any questions on this guide or any feedback you would like to leave, please feel free to leave us a comment at the bottom of this page in our comments section.

Windows 10 1709 Fall Creators Update – SCCM Build and Capture Task Sequence Failing

Blue and White Windows 10 Logo

We recently had put together a SCCM Build and Capture task sequence to update our images up to Windows 10 version 1709.

We copied the install.wim from the sources folder of the Windows 10 v1709 ISO and added this as our operating system capture image. We took our existing task sequence (which has lots of things in it like Office for example) and just pointed the Apply Operating System step at the new wim file.

We booted a fresh Hyper-V machine using PXE boot (using the Unknown Computers collection) and it booted straight into WinPE and found the task sequences available to the collection. So we selected the build and capture task sequence and let it run.

All seemed to be going fine; it partitioned the hard drive, applied the operating system, installed the ConfigMgr client, install the required applications and even ran through a Windows Update pass.

Then it all started to go wrong….

After rebooting itself to go into the Sysprep and capture steps, something strange started to happen. It ran through the Sysprep stage without any issue, rebooted itself back into WinPE and then started the capture phase – at which point it crashed and ended the task sequence unsuccessfully. We collected the logs and started the diagnostics head scratching. For reasons we could not explain, after the machine was Sysprep’d right at the end of the task sequence, once it had rebooted back into WinPE for the capture phase, it seemed as if the machine had lost its network connection. But how? its a virtual machine, it booted into WinPE at the first phase without any issue, its gone through the entire sequence working perfectly well – it surely cannot be a network issue – can it?

Diagnostic Investigation…

So, the investigation began. We checked the Cisco switches for all sorts of configuration checks (like IP helper, span tree etc…), we ensured the network card drivers were in the boot images and finally we hit F8 for a command prompt just as the capture step started and then, when the capture failed, we had a command prompt where we could carry out some quick checks. So, in the command prompt, we ran an ipconfig – no network connected, no IP, nothing. So, its the network connection – but it booted into WinPE using the same boot image and worked fine at the first PXE boot phase. This was driving us insane.

Always check the basics….

We started to then check that we had all the correct and up to date drivers in the boot image. We redeployed the boot image just in case, but still it kept failing at the capture phase. Then, after much Googling, we stumbled across a post about the new ADK for Windows 10 being released. So we checked our version and it had not been updated for a while so we went ahead and installed it and recreated our boot images. Once that had completed and distributed, we changed the task sequence to use the new boot image and PXE booted away. It loaded, it partitioned, it installed the OS, applications and Sysprep’d itself. Then rebooted back into WinPE – then the sight I never thought we would see – the capture step starts, then completes successfully.

Slightly infuriated with ourselves for not checking the basics first (like having the correct version of ADK!) but mostly chuffed to bits that we had finally sorted it, we deployed the new captured wim and started building a batch of new desktop computers. All of which worked perfectly!

So, the morale of story – always check the basics as most of the time, its the little things you overlook that are usually the problem.

Resources

For your information – below is the web ink for downloading the latest version (as of time of post) of the Windows 1709 ADK:

https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

Feedback

If you have any questions or feedback on this guide/story, please feel free to leave us a message at the bottom of this page in our comments section.

SCCM OSD – Restart a task sequence wizard in WinPE without rebooting

SystemCenter logo

If you have started a task sequence in Configuration Manager and you hit a problem, the last thing you want to do is to have to go through the reboot process back into Windows PE.

So, if you want to just restart the task sequence without rebooting, carry out the following steps:

  • Press F8 to bring up the command prompt (which will also stop the computer automatically rebooting
  • Run the following command: X:\smsb\ini\386\TsBootShell.exe

You should now find that your task sequence has restarted.

Comments

If you have any questions or feedback on this guide, please feel free to leave us a comment below and we will try to get back to you as soon as possible.

Using Windows Expand Tool to Extract CAB Files

3

If you are a regular user of downloaded CAB driver packs then you are probably using something like 7-Zip to extract them.

Well there is an alternative way of extracting the CAB file using a basic Windows tool.

Download your CAB file and make note of the file location. Then open a command prompt and go to the location of your CAB file:

Using Windows Expand Tool to Extract CAB Files 1
Click to enlarge

Then type in the following command:

expand cabfilename.cab . -f:*

where:

  • cabfilename.cab = the name of the CAB file you want to extract

For this guide purposes we will use the Dell Latitude 5480 Windows 10 drivers:

Using Windows Expand Tool to Extract CAB Files 2
Click to enlarge

Hit Enter and the process will start the extraction:

Using Windows Expand Tool to Extract CAB Files 3
Click to enlarge

Once complete, it will show many files have been extracted:

Using Windows Expand Tool to Extract CAB Files 4
Click to enlarge

You can then go and take a look in File Explorer and you should see the full extracted file structure now available to you:

Using Windows Expand Tool to Extract CAB Files 5
Click to enlarge
Using Windows Expand Tool to Extract CAB Files 6
Click to enlarge

Video Demo

We have created a quick video demo on this process to go through the steps as above:

Comments

If you have any questions or feedback on this guide, please feel free to leave us a comment below and we will try to get back to you as soon as we can.

Inject Windows Updates into WIM Image Files Using PowerShell

ssc 0

To inject Windows Updates into custom-built images that you are using in your Configuration Manager OSD environment, you may find that keeping them up to date is a real problem. If you are happy with the image itself and do not want to make any changes to it, why should you need to rebuild and recapture it to include all the latest Windows Updates?

One solution is to install Windows Updates during your OSD task sequence which is great, but very time consuming if your image is a few months (in some cases years!) old.

However, there is a way of injecting Windows Updates into your custom WIM files offline and then simply redistributing your WIM file to your local and remote distribution points. You used to have to install WAIK to do this, however, as Windows 10 has DISM built into it, you can now simply use your standard client Windows operating system and take advantage of a little PowerShell scripting.

Below is the guide on how to carry this out and a list of downloads that you will require.

Download

Download WSUS Offline Updater

Instructions

STAGE 1 – Download required offline Windows Updates

Download the WSUS Offline Tool from the link above and extract the zip file to a directory on your computer – for this guide purposes, we will use “D:\WSUS” (although most people will use a C: drive location).

Inject Windows Updates into WIM Image Files Using PowerShell 7

Run the “UpdateGenerator.exe” file located in the root of extracted files.

You will be presented with a program and you can select the versions of Windows, Office and Legacy products that you wish to update. Remember to include (or exclude) the x86 and x64 versions if you want to update these different architectures.

Inject Windows Updates into WIM Image Files Using PowerShell 8

You also have the option to use a WSUS server on your local network to retrieve the Windows Updates from (this is much quicker if you have a slower internet connection). To do this, click the WSUS button at the bottom and enter the URL of your WSUS server:

Inject Windows Updates into WIM Image Files Using PowerShell 9

If you wish to download all the available updates from Windows Update server, do not enter any information into this setting.

Once you have selected all the options that you want to download updates for, press the Start button at the bottom left. A command box will appear and will start to download all the required updates – this can take a long time depending on your selections and internet speed. These updates will be copied into the folder structure of the extracted files (“D:WSUS”).

Please note that although the first set of downloads will take a while, you can then run this process again at a later date and it will only download any newer updates required. This way you can keep an up to date repository of offline Windows Updates.

Once all your updates have been downloaded, you should then continue with the next stage of the process.

STAGE 2 – Inject Windows Updates into your WIM file

You should copy your WIM file to a location on your Windows 10 client machine, for this guide, we will use “D:\WIM”.

You then need to create a temporary directory that will be used to mount the WIM image, we will go ahead and use “D:\WIMTEMP”.

You then need to ensure that you use the correct index number by running the following command:

dism /get-wiminfo /wimfile:D:\WIM\wimname.wim

Inject Windows Updates

As you can see from the above image, the index we need to use for this process is “index:2” – however this can change depending on how you have created or captured your WIM file so you should always check this first before trying to mount a WIM file.

PowerShell Script

You then need to open your Windows 10 Powershell ISE program and enter the below code into the editing box:

#Add your own variables below
$UpdatesPath = “D:\WIM\wsusoffline108\wsusoffline\client\w61\glb*” #Path to the offline updates folder for the image OS (in this case Windows 7 x86)
$MountPath = “D:\WIM\Mounted” #Temporary image mount folder
$WimFile = “D:\WIM\Original\Win7x86\Win7x86.wim” #Source of image WIM file
$IndexNumber = “1” #Image Index Number
#Start of WIM mount process
DISM /Mount-Wim /WimFile:$WimFile /index:$IndexNumber /Mountdir:$MountPath
#Start of updates injection
$UpdateArray = Get-Item $UpdatesPath
ForEach ($Updates in $UpdateArray)
{
DISM /image:$MountPath /Add-Package /Packagepath:$Updates
Start-Sleep –s 10
}
Write-Host “Updates Applied to Mount Image”
#Start of space saving on mounted image
DISM /online /Cleanup-Image /StartComponentCleanup
DISM /online /Cleanup-Image /StartComponentCleanup /ResetBase
DISM /online /Cleanup-Image /SPSuperseded
Write-Host “Image Space Saving Completed”
#Start of unmount of mounted WIM file
DISM /Unmount-Wim /Mountdir:$MountPath /commit
#Start of cleanup on WIM file
DISM /Cleanup-Wim

Alternatively you can download the PS1 file using the button below:

Download Windows Updates Powershell Script

You should now edit the variables at the top of the script to match your own settings, ensuring that you are using the correct directory within your earlier downloaded updates for your WIM file. So, if your WIM file is Windows 7 x64, you should go to:

D:\WSUS\client\w61-x64\glb

If your WIM file is Windows 7 x86, you should go to:

D:\WSUS\client\w61\glb

If your WIM file is Windows 8.1 or Windows 10 x64 you should go to:

D:\WSUS\client\w63-x64\glb

Once you are happy with all your variables, run the PowerShell script and this will then run through the following process:

  1. Mounts the WIM file to your temporary location
  2. Searches for all available updates for your WIM files
  3. Injects all updates into your WIM file
  4. Cleans up the image as much as possible included the WinSXS folder
  5. Unmounts the image
  6. Runs a WIM cleanup on the file
  7. Completed

Your newly updated WIM file can then be redistributed using your Configuration Manager environment.

Comments

If you have any problems with this or have any questions at all, please use our comments section below.

HP Driver Pack Matrix

hp

If you are looking for HP driver packs then you can use the HP Driver Pack Matrix below:

Notebooks & Tablets Windows 10 64-bit Windows 8.1 64-bit
HP Elite x2 1012 G1 Tablet

HP Elite x2 1012 G1 Tablet with Travel Keyboard

sp77863.exe

(Updated: 2016-10-07)

HP EliteBook 1030 G1 Notebook PC sp77666.exe

(Updated: 2016-10-07)

HP EliteBook 1040 G3 Notebook PC sp77205.exe

(Updated: 2016-08-18)

HP EliteBook 820 G3 Notebook PC

HP EliteBook 840 G3 Notebook PC

HP EliteBook 850 G3 Notebook PC

HP ZBook 15u G3 Mobile Workstation

sp77184.exe

(Updated: 2016-08-18)

sp77187.exe

(Updated: 2016-10-25)

HP Spectre Pro x360 G2 Convertible PC sp76272.exe

(Updated: 2016-06-15)

sp76271.exe

(Updated: 2016-06-08)

HP ZBook 15 G3 Mobile Workstation

HP ZBook 17 G3 Mobile Workstation

sp77664.exe

(Updated: 2016-09-22)

HP ZBook Studio G3 Mobile Workstation sp76875.exe

(Updated: 2016-07-28)

HP EliteBook 720 G1 Notebook PC

HP EliteBook 740 G1 Notebook PC

HP EliteBook 750 G1 Notebook PC

HP EliteBook 820 G1 Notebook PC

HP EliteBook 840 G1 Notebook PC

HP EliteBook 850 G1 Notebook PC

HP ProBook 640 G1 Notebook PC

HP ProBook 645 G1 Notebook PC

HP ProBook 650 G1 Notebook PC

HP ProBook 655 G1 Notebook PC

HP ZBook 14 Mobile Workstation

HP ZBook 15 Mobile Workstation

HP ZBook 17 Mobile Workstation

sp66435.exe

(Updated: 2014-05-20)

HP EliteBook 720 G2 Notebook PC

HP EliteBook 740 G2 Notebook PC

HP EliteBook 750 G2 Notebook PC

HP EliteBook 820 G2 Notebook PC

HP EliteBook 840 G2 Notebook PC

HP EliteBook 850 G2 Notebook PC

HP ZBook 14 G2 Mobile Workstation

HP ZBook 15u G2 Mobile Workstation

sp70142.exe

(Updated: 2014-12-17)

HP EliteBook 725 G2 Notebook PC

HP EliteBook 745 G2 Notebook PC

HP EliteBook 755 G2 Notebook PC

HP EliteBook Folio 9480m Notebook PC

HP ZBook 15 G2 Mobile Workstation

HP ZBook 17 G2 Mobile Workstation

sp68878.exe

(Updated: 2014-09-11)

HP EliteBook 725 G3 Notebook PC

HP EliteBook 745 G3 Notebook PC

HP EliteBook 755 G3 Notebook PC

sp77188.exe

(Updated: 2016-08-18)

sp74782.exe

(Updated: 2016-02-08)

HP EliteBook Folio 1020 G1 Bang & Olufsen Limited Edition

HP EliteBook Folio 1020 G1 Notebook PC

sp70362.exe

(Updated: 2015-01-11)

HP EliteBook Folio G1 Notebook PC sp77665.exe

(Updated: 2016-09-22)

HP EliteBook Revolve 810 G3 Tablet sp70166.exe

(Updated: 2014-12-19)

HP Pro Tablet 608 G1 sp77445.exe

(Updated: 2016-09-07)

sp75486.exe

(Updated: 2016-04-04)

HP Pro x2 612 G1 Tablet

HP Pro x2 612 G1 Tablet with Power Keyboard

HP Pro x2 612 G1 Tablet with Travel Keyboard

sp77225.exe

(Updated: 2016-08-22)

sp68914.exe

(Updated: 2014-09-15)

HP ProBook 640 G2 Notebook PC

HP ProBook 645 G2 Notebook PC

HP ProBook 650 G2 Notebook PC

HP ProBook 655 G2 Notebook PC

sp77192.exe

(Updated: 2016-08-18)

sp74730.exe

(Updated: 2016-02-01)

HP Elite x2 1011 G1 Tablet

HP Elite x2 1011 G1 Tablet with Power Keyboard

sp70365.exe

(Updated: 2015-01-11)

HP EliteBook Folio 1040 G1 Notebook PC sp66435.exe

(Updated: 2014-05-20)

HP EliteBook Revolve 810 G1 Tablet
HP EliteBook Revolve 810 G2 Tablet sp71402.exe

(Updated: 2015-05-11)

HP ElitePad 1000 G2 Healthcare Tablet

HP ElitePad 1000 G2 Rugged Tablet

sp67945.exe

(Updated: 2014-08-01)

HP ElitePad 1000 G2 Tablet sp77446.exe

(Updated: 2016-09-09)

sp67945.exe

(Updated: 2014-08-01)

HP EliteBook 2170p Notebook PC

HP EliteBook 2570p Notebook PC

HP EliteBook 8470p Notebook PC

HP EliteBook 8470w Mobile Workstation

HP EliteBook 8570p Notebook PC Bundle

HP EliteBook 8570w Mobile Workstation

HP EliteBook 8770w Mobile Workstation

HP EliteBook Folio 9470m Notebook PC

HP EliteBook Folio 9470m Ultrabook

HP ProBook 6470b Notebook PC

HP ProBook 6475b Notebook PC

HP ProBook 6570b Notebook PC

HP EliteBook 2560p Notebook PC

HP EliteBook 2760p Tablet PC

HP EliteBook 8460p Notebook PC

HP EliteBook 8460w Mobile Workstation

HP EliteBook 8560p Notebook PC

HP EliteBook 8560w Mobile Workstation

HP EliteBook 8760w Mobile Workstation

HP ProBook 5330m Notebook PC

HP ProBook 6360b Notebook PC

HP ProBook 6460b Notebook PC

HP ProBook 6465b Notebook PC

HP ProBook 6560b Notebook PC

HP ProBook 6565b Notebook PC

HP EliteBook Folio 1040 G2 Notebook PC sp70163.exe

(Updated: 2014-12-19)

Workstations Windows 10 64-bit Windows 8.1 64-bit
HP Z240 Small Form Factor Workstation

HP Z240 Tower Workstation

sp71640.exe

(Updated: 2015-06-28)

HP Z440 Workstation

HP Z640 Workstation

HP Z840 Workstation

sp76483.exe

(Updated: 2016-06-28)

sp76299.exe

(Updated: 2016-06-21)

HP Z1 G2 Workstation sp72467.exe

(Updated: 2015-08-16)

sp65876.exe

(Updated: 2014-03-28)

HP Z230 Small Form Factor Workstation

HP Z230 Tower Workstation

sp72465.exe

(Updated: 2015-08-16)

sp65557.exe

(Updated: 2014-03-04)

HP Z1 Workstation
HP Z220 Convertible Minitower Workstation

HP Z220 Small Form Factor Workstation

HP Z420 Workstation

HP Z620 Workstation

HP Z820 Workstation

sp68648.exe

(Updated: 2014-09-08)

HP Z210 Convertible Minitower Workstation

HP Z210 Small Form Factor Workstation

HP Z400 Workstation

HP Z600 Workstation

HP Z800 Workstation

Desktops Windows 10 64-bit Windows 8.1 64-bit
HP Elite Slice

HP Elite Slice for Meeting Rooms

sp76591.exe

(Updated: 2016-07-05)

HP EliteDesk 705 G2 Desktop Mini PC

HP EliteDesk 705 G2 Microtower PC

HP EliteDesk 705 G2 Small Form Factor PC

sp77667.exe

(Updated: 2016-09-26)

sp77862.exe

(Updated: 2016-10-07)

HP EliteDesk 800 35W G2 Desktop Mini PC

HP EliteDesk 800 65W G2 Desktop Mini PC

HP EliteDesk 800 G2 Small Form Factor PC

HP EliteDesk 800 G2 Tower PC

HP EliteDesk 880 G2 Tower PC

HP EliteOne 800 G2 23-inch Non-Touch All-in-One PC

HP EliteOne 800 G2 23-inch Touch All-in-One PC

HP ProDesk 600 G2 Desktop Mini PC

HP ProDesk 600 G2 Microtower PC

HP ProDesk 600 G2 Small Form Factor PC

HP ProOne 600 G2 21.5-inch Non-Touch All-in-One PC

HP ProOne 600 G2 21.5-inch Touch All-in-One PC

sp77668.exe

(Updated: 2016-09-26)

sp77859.exe

(Updated: 2016-10-07)

HP EliteDesk 700 G1 Microtower PC

HP EliteDesk 700 G1 Small Form Factor PC

HP EliteDesk 705 G1 Desktop Mini PC

HP EliteDesk 705 G1 Microtower PC

HP EliteDesk 705 G1 Small Form Factor PC

HP EliteDesk 800 G1 Desktop Mini PC

HP EliteDesk 880 G1 Tower PC

HP EliteOne 705 G1 23-inch Non-Touch All-in-One PC

HP EliteOne 800 G1 21.5-inch Non-Touch All-in-One PC

HP ProDesk 600 G1 Desktop Mini PC

HP ProDesk 680 G1 Tower PC

sp69541.exe

(Updated: 2014-10-29)

HP EliteDesk 800 G1 Base Model Small Form Factor PC

HP EliteDesk 800 G1 Base Model Ultra-slim PC

HP EliteDesk 800 G1 Tower PC

HP EliteOne 800 G1 All-in-One PC

HP ProDesk 600 G1 Small Form Factor PC

HP ProDesk 600 G1 Tower PC

HP ProOne 600 G1 All-in-One PC

sp69541.exe

(Updated: 2014-10-29)

HP Compaq Elite 8300 All-in-One PC

HP Compaq Elite 8300 Convertible Minitower PC

HP Compaq Elite 8300 Microtower PC

HP Compaq Elite 8300 Small Form Factor PC

HP Compaq Elite 8300 Ultra-slim PC

HP Compaq Pro 6300 All-in-One PC

HP Compaq Pro 6300 Microtower PC

HP Compaq Pro 6300 Small Form Factor PC

HP Compaq Pro 6305 Microtower PC

HP Compaq Pro 6305 Small Form Factor PC

HP Compaq 6200 Pro Microtower PC

HP Compaq 6200 Pro Small Form Factor PC

HP Compaq 8200 Elite All-in-One PC

HP Compaq 8200 Elite Convertible Minitower PC

HP Compaq 8200 Elite Microtower PC

HP Compaq 8200 Elite Small Form Factor PC

HP Compaq 8200 Elite Ultra-slim PC

HP Compaq 6000 Pro All-in-One PC
HP Compaq 8100 Elite Convertible Minitower PC

HP Compaq 8100 Elite Small Form Factor PC

HP Compaq 6005 Pro Ultra-slim Desktop PC
HP EliteDesk 705 G3 Desktop Mini PC

HP EliteDesk 705 G3 Microtower PC

HP EliteDesk 705 G3 Small Form Factor PC

sp76592.exe

(Updated: 2016-07-11)

HP EliteOne 705 G2 23-inch Touch All-in-One PC sp77667.exe

(Updated: 2016-09-26)

sp77862.exe

(Updated: 2016-10-07)

HP MP9 G2 Retail System

SCCM – Windows 10 Sysprep Capture Errors

sccm logo

So today we built a new custom Windows 10 image on a virtual machine and created our new SCCM capture media from the very latest version and every single time we ran the capture it failed at the Sysprep step.

Infuriated by this as we have done captures hundreds of times, we started the annoying method of going through the log files. As the capture was failing at the sysprep part we knew to take a look at the sysprep error logs first which can be found in this location on your machine:

C:\Windows\System32\Sysprep\Panther

You should see a file called something like setuperr.log – look in here and you should find the reason for the system prep failure.

Amazingly, in our case, it was the pre-installed Twitter and Candy Crush Windows Store Apps that were causing the problem. So, we uninstalled these and tried again – there you go, capture went through without any issues and worked perfectly.

Feedback

If you have any questions or comments, please feel free to leave us a message below using our comments system below.

Setting Computer Name automatically during OSD Process – SCCM/ConfigMgr 2012

microsoft windows white logo

We have been looking into getting our OSD process to automatically change the computer name to what we want it to be for a while now but never really had much luck with it.

Reading various forums and blogs, many people have said to use WSNAME and many others saying use scripts, all of which never seemed to quite work for us.

What we wanted was a three letter prefix with the serial/tag number of our machines. Most of our machines (99%) are Dell’s and we wanted to use the 7 digit asset tag with a 3 letter prefix but things like the WSNAME only seemed to work with our HP’s using the %SERIALNUM% variable. Using this method, all our Dell machines were reporting the %SERIALNUM% as blank, so instead of:

ABC6TQX8X1

It came out as just:

ABC

Not really much use!

So, we decided that we really needed to spend some time on this and get it working once and for all. After actually dedicating some time to it instead of just messing about with it for five minutes here and there, we finally got it working.

For those of you that know MDT, we used this with a mixture of Gather and Set Task Sequence Variable. Tested it, works a treat!

So, a quick how to guide for those wanting to know how to do it as we have really struggled to find a simple step by step guide to doing such a simple task.

First of all, you need to have MDT installed which you can download from here:

Download Latest MDT

You also need to make sure that you have ConfigMgr integration working, please note that this guide does assume that you have MDT fully up and running to use in your Task Sequences within ConfigMgr….if you need to know how to get this to work, leave a comment at the bottom of this post and we will look at getting a guide uploaded for doing that….

Edit your selected Task Sequence and just after the “Deploy OS” step, add your “Use MDT Package” step.

Setting Computer Name automatically during OSD Process - SCCM/ConfigMgr 2012 10

Then, directly after this step, add the “Gather” step and set it to “Gather only local data (do not process rules)

Setting Computer Name automatically during OSD Process - SCCM/ConfigMgr 2012 11

Then, the final bit which applies the computer name, add “Set Task Sequence Variable” then make sure that the Task Sequence Variable is set to OSDComputerName. The value can be whatever you want it to be, the standard is:

%SERIALNUMBER%

Setting Computer Name automatically during OSD Process - SCCM/ConfigMgr 2012 12

This will set the computer name as the, you guessed it, Serial Number.

If you want to customise it slightly, just add the text before the %SERIALNUMBER%, so as an example:

ABC%SERIALNUMBER%

Setting Computer Name automatically during OSD Process - SCCM/ConfigMgr 2012 13

Save your task sequence and it should work.

Few things to remember that are very important, this part must be added AFTER the Deploy OS step, but also BEFORE the Apply Windows Settings step.

Comments

If you have any problems please use our comments system below to leave a comment and we will get back to you as soon as we can.

SCCM – Add Local User to Administrators Group During OSD

sccm logo

You may have seen our previous post about adding a local user to a machine during SCCM OSD using a “Run Command Line”. Well in this guide we will show you how to add a local user into the Administrators Group on the local machine. This means that you can add a local user and then make them a local administrator all within the SCCM OSD task sequence.

Instructions

You will need to add a “Run Command Line” step towards the end of your task sequence ensuring it is after the Windows deployment and the ConfigMgr Client installation.

Then, you should use the following command:

cmd.exe /c net localgroup "Administrators" "LocalAdmin" /add

The details for what each part of this command line mean are below:

  • cmd.exe /c – required to run a successful command
  • net localgroup – command line to make amendments to local groups
  • “Administrators” – the name of the local administrators group
  • “LocalAdmin” – the name of your local user account
  • /add – to add the stated user to the stated localgroup

When you have finished, your step should look something like this:

2

Now, when you run through your task sequence, this will run the command line and add your stated user to the local administrators group.

If you want to run this with also creating a new local user, ensure that you have this step after the create local user step or it will fail.

Comments

If you have any questions about this guide, please feel free to leave us a message below using our comments system.

SCCM – Add Local User During OSD

sccm logo

If you want to add a local machine user to your deployed machine during your SCCM OSD process then you can do this using a standard “Run Command Line” step.

Guide

So, you need to add a “Run Command Line” step in your task sequence towards the end, after the Windows deployment and after the ConfigMgr Client install. You should then give it a meaningful name and use the following command line:

cmd.exe /c net user LocalAdmin Pa55w0rd# /add /comment:"Local Admin Account" /expires:never /fullname:"Local Admin Account"

Each of these parts are detailed below and can be changed to your own requirements:

  • cmd.exe /c – required to run a successful command
  • net user – run the “net user” command
  • LocalAdmin – name of the local admin account you want to create
  • Pa55w0rd# – the password of the local admin account you want to create
  • /add – to add the user
  • /comment:”Local Admin Account” – this is the description of the local account
  • /expires:never – means the account will never expire (note account NOT password will never expire)
  • /fullname:”Local Admin Account” – full name details for the local account

When you have completed this, you should have something that looks a little like this:

1

Now when the task sequence runs through it will run this command and add the local user. Note that this will add the user add a “Standard” user, if you want to then make this user (or any other local user) as a local administrator then take a look at our guide for this here.

Feedback

If you have any feedback about this guide, please feel free to leave us a message below using our comments section.

SCCM – Set Time Zone During OSD

sccm logo

If you are using SCCM for your operating system deployments across different countries, then you may want to set the time zone within the task sequence.

To do this, you can take advantage of the built in Windows tool call tzutil.exe.

In this example we will set the time zone for a computer deployment based in Amsterdam, The Netherlands which is Western European Standard Time (GMT +1).

Towards the end of your task sequence and after the Apply Image and Install ConfigMgr Client steps, add a Run Command Line step. Then give it a descriptive name. Add the following code for the command line:

cmd.exe /c tzutil.exe /s “W. Europe Standard Time”

You will also need to set the Start In as C:WindowsSystem32

So, when you have completed the step, it should look like this:

1

If you want to use a different time zone, you can see the full list (and correct command to use) by typing the following command in a command box on any Windows machine:

tzutil.exe /l

COMMENTS

If you have any questions on this guide then please feel free to leave a message below using our comments system.

SCCM – Missing Boot Image Tabs

SCCM Logo

If you have recently upgraded your SCCM to version 1511, you will have had to have upgraded your ADK to the Windows 10 version. However, did you first note down your customisation and network card drivers that you had in your boot image? If not, you will now find that those tabs are missing.

So, you will end up with your previous/current boot image looking like this:

SCCM Boot Image Missing Tabs
SCCM Boot Image Missing Tabs

We have simply recreated our boot images as we had everything documentated but if you are looking for a fix, then you could try this guide for help:

ADK Windows 10 Boot Images Fix

Comments

If you have any questions or comments on this guide, please feel free to leave us a message below using our comments system.