Lars' System Center Blog

MDT2012 Beta 1 and SCCM 2012 Beta 2 OS Deployment Part I: Creating a TS for a Reference computer

SCCM2012 beta2 has been release since MMS 2011 in march but I waited with testing the product until now because the MDT2010 was not compatible with SCCM2012. Since a few weeks the beta1 of MDT2012 has been released so let’s see what this killer combo for deployment looks like in these new versions. My test environment is just 1 virtual server configured with ADDS, DHCP, DNS, IIS and WSUS roles. I have 2 additionals VM’s for the test PC’s for OSD deployments. It is a clean installation of SCCM and MDT.

First we create a MDT task sequence for our Reference computer:

In the Configuration Manager console, navigate to the Software library workspace, expand the Operating Systems and select Task Sequences.

In the ribbon click Create MDT task Sequence to start the Create MDT Task Sequence Wizard start

On the Choose template screen, click Next

On the General screen, name your task sequence and click Next

On the General screen complete the domain, account information, Username, Organization and click Next

In the Capture settings screen,select This task Sequence may be used to capture an image, complete your Capture destination, Capture account and click Next

In the Boot Image screen, select Create a new boot image package

In the General Settings screen, provide a Name and click Next

In the Components screen , selext x64 and click Next

In the Customization screen select Enable command Support (F8) and click Next

In the MDT Package screen, select create a new Micrsoft Deployment Toolkit Files Packages and click Next

In the OS image screen, select Create a new OS install Package, complete the OS installation folder location, Package Source Folder to be created and click Next

In the Install Source screen, complete Name and version and click Next

In the Client Package screen, select Create a new ConfigMgr Client Package and click Next.

In the USMT Package screen select Create a new USMT package and click Next

In the Settings Package screen, select Create a new settings package, complete the Package source folder to be created and click Next

Since we are deploying windows 7 we don’t need a sysprep package, so:
In Sysprep package screen, click Next

In the Summary screen click Next

All packages and the task sequence will be created J

In the Confirmation screen, click Finish

The task sequence for creating a Reference and packges computer have been created:

BUT…… the packages are not yet distributed to the DP’s!

So go to Software Library, expand the Application Management node and select Packages

Select the all the packages in the content pane (New for SCCM2012!)

In the Ribbon click Distribute Content to start the Distribute Content Wizard

In the General screen click Next

In the Content Destination screen, click on Add, then select Distribution Point

In the Add Distribution Point screen, select your distribution Point and click OK

In the Content Destination screen, Click Next

In the Summary screen click Next

In the Completion screen click Close

The content will be copied to the DP:

In SCCM2007 we needed to advertise the TS in SCCM 2012 we deploy:

In the Software library workspace, expand the Operating Systems Node, select task sequences and select the task sequence you want to deploy:

In the Ribbon, click on Deploy to start the Deploy software wizard

In the General screen click Browse

In the Browse collection window, select Unknown computers and click OK

In the General screen click Next

In the Deployment Settings screen, select Make available to boot media and PXE and click Next

In the Scheduling screen click Next

In the User Experience screen click Next

In the Distribution Points screen click Next

In the Summary screen click Next

In the Completion screen click Close

The TS for the reference computer is now deployed to the unknown computers collection and ready to be tested

In Part II we will create the Boot image for the reference computer.

Greetzzzz

Lars Verbist