Archive for the ‘MDT’ Category

SCCM 1511 Prereq upgrade warning: Unsupported Operating System

Hi All,

A couple of days ago I decided to upgrade my SCCM DEMO environment to the newest version of SCCM 1511.


When running the prereq checker, I got the “normal” warning about SQL Server process memory allocation, but I also got a new warning that I hadn’t seen before.

Warning: Unsupported site system operating system version for upgrade!




My only server for SCCM was running Windows Server 2012 R2 so I found the warning a bit odd.

Looking into the log file c:\ConfigMgrPrereq.log I found the “issue”

My SCCM DEMO environment has an Intune connector installed and a Cloud DP


The prereq checker will also check OS version at and obviously fails Smiley med åben mund


So without further thinking I clicked “Begin Install” and the upgrade succeeded.



Jens Ole


MDT 2013 Update1 – Force Application installation order using UDI


Working at a customer who wanted to install Office 2013 instead of Office 2010 using the User Driven Installation (UDI) Wizard, I ran into a little issue.

Normally it’s not a big deal. We added the Office 2013 installation to the UDI Wizard and moved it to the top as other installed software depends of the Office installation.

Then we did a test deployment and Office 2013 was not installed as the first application and as the Outlook Add-In application was depended of Outlook – the deployment failed installing the applications.


Looking in the file located in the MDT Toolkit Files package script folder, you can find the application ID number and do a quick fix Smiley, der blinker

In this case the Outlook Add-In has a lower number than Office, which will result in a failure.





I wanted Office to be the first install so I changed Office 2013 to ID 8. (my lowest App ID)

The application which had ID 8, got ID 9 and finally the Outlook Add-In got ID 25


Selected Application list should be changed too according to the new App IDs.



To assure that you did not make any errors, I always open the UDIWizard_config.xml in the UDI Wizard designer and do a save.

I updated the MDT Toolkit Files Package a the DP and deployed a new machine.

The result worked as expected



I assume that I could have deleted the Outlook Add-In in the UDI Wizard Designer and added it back in. It should then have had ID 26, but if you want to “arrange” your applications, this must be the way Smiley, der blinker

Applying an ICD provisioning package (Part 3)

16/11/2015 2 comments

1. part – I installed Windows Imaging and Configuration Designer (ICD) tool

2. part – I created a provisioning package

In this final part I’ll apply the created provisioning package to a Windows 10 Pro client system.


Here I got the non domain joined machine with a non standard computer name.

The computer is running Windows 10 Pro.



Copy the newly created provisioning package to the computer or a USB.




Run the Provisioning package? Yes, sure



Du you trust the creator? Yes, add it



NOTE: I removed the password in my test setup. In production you will be prompted for a password to apply the package.


The provisioning package is applied……





After the provisioning package is applied you’ll be signed out and the computer will restart a couple of times.



We sure did change something Smiley, der blinker



Verify that you now can login with your domain account.



After login. Cool…



The computer is now domain joined, have a standard computer name and the Windows version is now Enterprise.



Verify that the computer is in the right OU in Active Directory too and the mission is accomplished.



The Power of Windows Imaging and Configuration Designer (Part 2)

The Windows Imaging and Configuration Designer (ICD) tool can be used to a lot of different stuff. But for now I see the biggest gain for companies to use the tool for people that buy a new computer and is not near a company location where a new computer can be deployed or if the bought computer model is not on the official hardware certification list.

This guide will change the following at a Windows 10 Pro computer.

New standard computer name

Domain joined

Get the computer staged in the right OU

Upgrade the SKU to Enterprise

Let’s get started.

Start Windows Imaging and Configuration Designer (ICD)


Select New provisioning package


Enter Project details and choose a folder.


Select what Windows versions can use the package. I’ll choose Common to all Windows desktop editions


As this is a new package, I’ll not import any package, click Finish


To filter out some settings, select Common IT Pro settings


Enter the account used to do the domain join


Target OU


Enter Computername. In the case I use a variable to get different computernames.



Enter DomainName


Set domain join password


To upgrade the OS version to Windows Enterprise enter an appropriate PID.


Save the project


Click Export and select Provisioning package


Give the provisioning package a name and select ranking


You should encrypt the package, so no one can read the passwords stored inside the package or the license key.

Further more only admins/users with the password can use the provisioning package and there by join computers to the domain.






Done, Finish


The provisioning package is  now ready for use.


Next part I’ll run the package at a non domain joined Windows 10 Pro machine.

SCCM OSD error: There is not enough space on the disk (error 112)

02/11/2013 1 comment

A couple of days ago, I ran into a strange problem, that I have never seen before.

The system is Configuration Manager 2007 SP2 R3 with MDT 2012 UDI and the Operating System deployed is Windows 7 SP1 x64.
I used a couple of hours over a few days to solve the problem.

First error was that the UDI Status page showed a warning on a unknown application. The application was the last one in the list and was about 1,5 Gb in size.

I checked the Advertisement Status first:

31-10-2013 21-10-52

31-10-2013 21-13-12

The operating system reported error 112: There is not enough space on the disk.

I have seen this error before when trying to download the WIM file to a wrong partition Smiley, der blinker but not when installing applications.

I tried running the Task Sequence in a virtual environment and got the following UDI Status:



I got hold of the smsts.* from the computer but the information was overwritten so I could not see the information about the application as I needed.

Changed the parameters in the “Setup Windows and ConfigMgr” step to:

01-11-2013 09-21-36

Ran the OS Deployment (Physical machine) once more and now I could see the error in the smsts.log:

31-10-2013 21-23-28

There is not enough disk space left on this machine for staging the content…

Then I thought that the standard cache size was the problem. I could install in a virtual environment and not on a physical machine, but the physical machine downloaded a driver pack and I didn’t do that in the virtual machine. Could that be my problem, that the cache was full ?

Changed the cache size as a part of the “Setup Windows and ConfigMgr” step.

01-11-2013 09-22-26

The Task Sequence failed with the same error ;-(

The it hit me, BitLocker was enabled as a part of the task sequence:

31-10-2013 21-16-39

When BitLocker is enabled it reserves som space on the disk to continue working, while BitLocker finishes encrypting the harddrive.

Could that be the problem?

I changed the task sequence so BitLocker was enabled after the applications were installed.

31-10-2013 21-14-40

Ran a deployment once more, and…….



Hope this will help you as I could not find much information about this error.


MDT 2012 Update1 bug – Regional Settings not set correctly using UDI

08/10/2012 3 comments


If you are using SCCM and MDT 2012 Update1 User Driven Installation (UDI) to deploy language specific OS Images, you might hav noticed that the regional settings always is set to EN-US even if you selected another language in the UDI Wizard. The reason is a bug in UDIWizard.wsf script.


In UDIWizard.wsf comment out the following line:

oEnvironment.Item(“UserLocale”) = oEnvironment.Item(“InputLocale”)


I have tested the solution with: EN-UK, Da-DK, PL-PL and that works like a charm.

Original source:

Categories: ConfigMgr, MDT