Integrating UDI into your SCCM OSD Task Sequences
I think a lot of people look at UDI (User Driven Installation) Task Sequences as just that - an option for users in an organization to perform actions associated with the deployment of an Operating System. Well, that's perfectly acceptable however when I first installed Configuration Manager 2012 in my lab I looked at the new UDI options and immediately saw a way of replacing my old HTA that I had with Configuration Manager 2007. I was fairly sure I could adapt the UDI Wizard to suit my deployment model taking full advantage of what the MDT team had already written. The following blog briefly describes what I have done with UDI in my organization.
Implementing the out of box UDI solution is actually fairly straight forward.
- Integrate MDT with your Configuration Manager 2012 installation
- Create your MDT files package, I have done this with MDT 2012 Update 1
- Create a standard MDT client task sequence, this will automatically include the steps that call the UDI Wizard
- Test your Task Sequence to ensure that it works and calls the UDI Wizard as expected.
Once you have these basics configured you can then take a closer look at customizing what built-in panes the wizard presents and how that information is collected and used.
It's worth noting as this point that I haven't had a need to create any custom panes which set variables. Having said that, you can do this and MDT 2013 includes the ability to create your own pages using a GUI which is a vast improvement on what was offered in MDT 2012 Update 1.
Using the UDI Wizard Designer, I have removed quite a few of the built-in panes. This is because I have tailored it for my Service Desk technicians to use and rely on the other built in Task Sequence steps to set variables. I have modified the **New Computer **and **Refresh *page libraries and have a separate USMT scripted process for the replace scenario.
*
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_133314.jpg
New Computer UDI Steps
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_140310.jpg
Refresh Computer UDI Steps
I have created separate UDI XML files for each Operating System that I deploy or refresh so that I can control settings and what applications are installed. To call different UDI Wizard XML files, save your UDI XML template file with an appropriate name into your MDT Files package then modify the** two** **UDI Wizard **steps in the Task Sequence.
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_140608.jpg
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_133757.jpg
You can customize the default header image (as I have) so the UDI Wizard is customized to your organization. To do this you will need to locate the **UDI_Wizard_Banner.bmp **file located in your MDT Files package. Modify both copies of this file within the \Tools\x86 and **\Tools\x64 **folders respectively. The image needs to be 759 x 69 pixels. Rename the old file to **UDI_Wizard_Banner.original **in case you wish to roll back. Once your changes are complete, update your Distribution Points.
http://damonjohns.files.wordpress.com/2013/08/2013-08-20_094912.jpg
http://damonjohns.files.wordpress.com/2013/08/2013-08-20_094756.jpg
Here are some screen captures on my New Computer UDI Wizard. You can use the wizard to add Organizational OU's, a pre-populated Domain Name, Applications and other variable settings.
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_134119.jpg
Collecting Computer and Network Settings
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_134436.jpg
Application Selection and Installation
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_134521.jpg
Summary Page
As the MDT Gather step runs before the UDI Wizard starts, you can also pre-populate other variables which will then automatically appear within the UDI panes. For example, you may wish to run a separate script to generate a computer name, if this is run prior to the UDI Wizard running, it will be displayed in the pane that contains the field referencing that variable. Another good example of this is to pre-populate the domain join account username and password using CustomSettings.ini.
http://damonjohns.files.wordpress.com/2013/08/2013-08-19_135828.jpg
You can also use the UDI Wizard to present groupings of Applications which when selected will then be installed as part of the base variable **COALESCEDAPPS **during the **Install Applications step of your TS . To correctly configure this for OSD you will need to create a collection within your Configuration Manager Console, then Deploy each Application to that collection that you want to make available during an OSD Task Sequence. The Deployment type needs to be set to ***available. *Alternatively, you can use an existing collection if you have one setup, that already has your Applications deployed in this manner.
Note: If you rename an application in Configuration Manager 2012, you will have to update your UDI XML file, save and redistribute your MDT Files package.
http://damonjohns.files.wordpress.com/2013/08/2013-08-20_100030.jpg
When this has been completed you can use the UDI Wizard Designer to create your Software Groups. Ensure that you have set the **Site Settings **within the designer by selecting the **Configuration Manager **ribbon button. You will need to set your Site Server Name and the name of the Application Collection that you have created and deployed your Applications to otherwise your Applications will not appear when you try to search and add them.
Note: You need to tick the option "Allow this application to be installed from the Install Application task sequence action without being deployed" for each Application that you want to install as part of a TS
http://damonjohns.files.wordpress.com/2013/08/2013-08-20_101716.jpg
http://damonjohns.files.wordpress.com/2013/08/2013-08-20_100603.jpg
Using UDI as an alternative has allowed me to transition into Configuration Manager 2012 OSD easily, retiring my old HTA. I have been able to take advantage of the built-in panes and were suitable, set and populate information automatically. With the new version of MDT 2013 around the corner, the new Custom Page Designer will no doubt add further options and capabilities in this area.
Hopefully, this blog gives you some broad ideas around how you can implement UDI in your organization and what is possible to achieve when using it.
http://damonjohns.files.wordpress.com/2013/08/2013-08-20_103446.jpg
Cheers Damon