Archive

Archive for November, 2015

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.

image

Looking in the UDIWizard_Config.xml.app 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.

 

image

image

 

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.

image

 

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

image

 

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.

image 

 

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

 

image

 

Run the Provisioning package? Yes, sure

image

 

Du you trust the creator? Yes, add it

image

 

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……

 

image

image

 

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

image

 

We sure did change something Smiley, der blinker

image

 

Verify that you now can login with your domain account.

image

 

After login. Cool…

image

 

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

image

 

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

 

/Enjoy

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)

image

Select New provisioning package

image

Enter Project details and choose a folder.

image

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

image

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

image

To filter out some settings, select Common IT Pro settings

image

Enter the account used to do the domain join

image

Target OU

image

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

TESTPC%SERIAL%

image

Enter DomainName

image

Set domain join password

image

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

image

Save the project

image

Click Export and select Provisioning package

image

Give the provisioning package a name and select ranking

image

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.

image

Save

image

Building

image

Done, Finish

image

The provisioning package is  now ready for use.

image

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

Installing Windows Imaging and Configuration Designer (Part 1)

The Windows Imaging and Configuration Designer (ICD) is a new tool, introduced with Windows 10.

ICD is a part of Windows Assessment and Deployment Kit for Windows 10 (ADK) and you can use Windows ICD to do the following tasks:

  • View all of the configurable settings and policies for a Windows 10 image or provisioning package.
  • Create Windows provisioning answer files.
  • Add third-party drivers, apps, or other assets to an answer file.
  • Create variants and specify the settings that apply to each variant.
  • Build and flash a Windows image.
  • Build a provisioning package.

Read more about ICD here

Download setup for Windows 10 ADK here

Start the installation and choose where the toolkit should be installed and if you want to send Microsoft anonymous data.

image

image

Accept the license agreement

image

Ensure that you select Imaging and Configuration Designer (ICD).

Note the prerequirements.

image

The tools are installed.

image

image

image

Click Close and you are ready to streamline, customize and provision Windows images.

Expect a new blog post soon.

/Jens Ole