User Driven Installation (UDI) with Configuration Manager
Just wanted to cover something which feel is really interesting but didn’t get the chance to pen it down though I presented this a couple of times already. So here goes. UDI or User Driven Installation was a feature introduced with MDT 2010 Update 1 and when integrated with Configuration Manager allows your end users to customise their operating system while also allowing the administrator to control over the deployment experience.
The installation; It is extremely straight forward so that is why I am not going to cover that. However though right after you’ve installed it you may need to run the “Configure ConfigMgr Integration” task again if you have a previous installation of MDT integrated with your Configuration Manager.
It should look like this when it is successful.
It is a good thing to run the install for UDI Config Service. One thing you should note though is that if you’re running on Windows 2003, your IIS version is going be on version 6.0 and the UDI web service requires IIS7 plus other pre-requisites which you will see later. The good news though, UDI will still work if you’re running on WS03 without running the install for UDI Config Service.
Note the prerequisites.
Accept the EULA.
You might get stuck here. If you do, you gotta get the URL Rewrite Module installed and the IIS6 Management Compatibility component installed.
Go here to download and install the URL Rewrite Module.
You can add the IIS6 Management Compatibility component from the Server Manager console of WS08.
Once you’re done with that, the next thing to do is to customise the UDI Wizard. And to do that, you use, yes the UDI Wizard Designer. 🙂
You should open an existing .xml file and edit from it. Browse to your local drive and look for the “UDIWizard_Config.xml” file normally found in the scripts folder of your MDT Files Package which you should have created that when you created a Microsoft Deployment tasks sequence from the Configuration Manager console.
Much of the UDI Wizard Designer is simple. I just wanted to highlight on the applications. Some of you may encounter this like how I bumped into it. You go to the OSD Applications and added a new application item. And then tried to attach a new program.
And you get this thinking that you should have at least several programs listed in the Configuration Manager Packages window. But all you get is an empty Configuration Manager Packages window.
This may be because you forgot to enable that particular program that you want to deploy through OSD to be installed from the Install Software task sequence.
Okay, so you’ve done that but still seeing that the list of programs that you selected to run from a task sequence is not showing up. This could be the case similar to mine where the list of package selection was wrong. The easiest and to eliminate an error is to include all the packages that you want to work with in OSD. Simply select all and then add to the Selected Packages column.
You should now see your apps that you’ve selected and also marked to run in task sequence without being advertised.
Don’t forget to save the configuration file and once you’ve saved it, also remember to update the distribution point of the MDT Files Package. From here onwards, the rest should be a breeze to advertise the task sequence to your desired target collection. Sit back and enjoy the ride. Happy trying.