using SCCM 2012 RC in a LAB – Part 8. Deploying Windows 7 X64

In Part 1 of this series we got our AD and SCCM servers ready, and then we installed System Center 2012 Configuration Manager as a standalone Primary site. In Part 2 we configured the SCCM server further by adding some Windows Server roles necessary for the following Configuration Manager 2012 functionality, Software Update Point (SUP) and Operating System Deployment. In Part 3 we configured the server further by Enabling Discovery methods and creating Boundary’s and Boundary Groups. In Part 4 we configured Client Settings, Added roles and Distributed the Configmgr Client to our Computers within the LAB, then in Part 5 we enabled the Endpoint Protection Role and configured Endpoint Protection settings and targeted a collection called All Windows 7 Computers with these settings and policies. In Part 6 we configured our SUP further to Deploy software updates to our All Windows 7 Computers and Build Windows 7 X64 collections. In Part 7 we used the Build and Capture
process to create our Base Windows 7 X64 wim image. In this part we’ll
use the captured image in our Deploy Windows 7 X64 task sequence and
we’ll set some User Device Affinity collection variables and use a USMT 4 package to migrate the users data using hardlinking.

Step 1. Create the USMT 4 package

Perform the following on your SCCM 2012 server as SMSadmin.

If you want to migrate data in a Deploy
Task Sequence you’ll need to have the USMT 4 package ready, so let’s
create it now so that we can access the necessary migration files in our
Deploy Windows 7 X64 task sequence.

On your SCCM server in Windows Explorer, browse to C:\Program Files\Windows AIK\Tools\

Right click on the USMT folder and choose Copy,

Attached Image: monthly_11_2011/post-1-0-66356600-1321130171.png

select your sources folder (mine is on D:\) and paste the USMT folder in sources\os so that it’s path is sources\os\usmt

Attached Image: monthly_11_2011/post-1-0-93401200-1321130282.png

In the ConfigMgr Console, select Software Library, Application Management, Packages, right click and choose Create Package.

Attached Image: monthly_11_2011/post-1-0-30974700-1321130415.png

fill in the details about the package, call it USMT version 4 and point
to the UNC path of our newly copied files, \\sccm\sources\os\usmt

Attached Image: monthly_11_2011/post-1-0-84666700-1321130652.png

for Program Type select Do not create a program

Attached Image: monthly_11_2011/post-1-0-13365500-1321130725.png

Complete the Wizard

Attached Image: monthly_11_2011/post-1-0-67055400-1321130772.png

Step 2. Distribute the USMT package to our Distribution Points

Select the USMT package and click on Distribute Content in the Ribbon

Attached Image: monthly_11_2011/post-1-0-58507200-1321131213.png

for Content Destination, click on Add, select Distribution point, select our DP,

Attached Image: monthly_11_2011/post-1-0-57184000-1321131232.png

click through the rest of the wizard

Attached Image: monthly_11_2011/post-1-0-79617000-1321131279.png

Step 3. Import the captured Windows 7 X64 wim file

Perform the following on your SCCM 2012 server as SMSadmin.

In the Software Library, Operating Systems section of the Configmgr console, click on Operating System Images, you’ll note that it is empty because we havn’t imported any images yet. Right click and choose Add Operating System Image

Attached Image: monthly_11_2011/post-1-0-03743900-1321117240.png

browse to the UNC of where we captured the image in Part 7 and select the captured wim file

eg: \\sccm\sources\os\captures\windows7x64.wim

Attached Image: monthly_11_2011/post-1-0-45314100-1321124021.png

fill in some details about the image

Attached Image: monthly_11_2011/post-1-0-09656000-1321124140.png

click through the summary, progress to completion

Attached Image: monthly_11_2011/post-1-0-13270100-1321126031.png

Step 4. Distribute the image to the Distribution points

Perform the following on your SCCM 2012 server as SMSadmin.

We now need to distribute our imported image to our distribution points. Select Our Windows 7 Enterprise X64 image and in the ribbon above click on Home and then Distribute Content

Attached Image: monthly_11_2011/post-1-0-78256600-1321126646.png

when the Distribute Content Wizard appears, click next

Attached Image: monthly_11_2011/post-1-0-34101000-1321126871.png

to specify the destination, click on add and select distribution point

Attached Image: monthly_11_2011/post-1-0-84297600-1321127067.png

select our Distribution Point from the list

Attached Image: monthly_11_2011/post-1-0-93973600-1321127122.png

the DP appears selected

Attached Image: monthly_11_2011/post-1-0-29700500-1321127193.png

click next through summary/progress to completion

Attached Image: monthly_11_2011/post-1-0-52470900-1321127293.png

Step 5. Create the Deploy Task Sequence

Perform the following on your SCCM 2012 server as SMSadmin.

Now that we have added our captured operating system image to Configmgr, and distributed it to our dp’s we want to create a Deploy Task sequence to Deploy the image. In Task Sequences, right click and choose Create Task Sequence.

Attached Image: monthly_11_2011/post-1-0-07586800-1321127470.png

choose to Install an existing image package

Attached Image: monthly_11_2011/post-1-0-71455600-1321127577.png

fill in some details about the image and click browse and select the X86 boot image, click next to proceed

Attached Image: monthly_11_2011/post-1-0-52861100-1321127699.png

now select the Windows 7 image by clicking on browse and set an administrator password, uncheck Partition and format the target computer before installing the operating system if you want to use hardlinking for User state migration, otherwise files cannot be stored locally

Attached Image: monthly_11_2011/post-1-0-01855800-1321128027.png

for the Configure the Network step, we want to join the domain so click on browse beside join a domain

Attached Image: monthly_11_2011/post-1-0-20664300-1321128190.png

and now we need to specify the user that has permissions to join the
domain, i use the DomJoin user just or this task (create the user and
delegate them enough permissions to add computers to the domain)

Attached Image: monthly_11_2011/post-1-0-32019100-1321128315.png

I’m not specifying an OU in this step, you can, but don’t select the Computers Container if you do…

Attached Image: monthly_11_2011/post-1-0-09070200-1321128384.png

for the Install the Configuration Manager client step click on browse and select the client package from defintion we created in the last part

Attached Image: monthly_11_2011/post-1-0-05260100-1321131483.png

click next and for State Migration, select our USMT 4 package

Attached Image: monthly_11_2011/post-1-0-58019400-1321131694.png

change the setting to Save user settings Locally (this will mean we can use Hard Links)

Attached Image: monthly_11_2011/post-1-0-24849000-1321131809.png

for Include Updates select All Software Updates

Attached Image: monthly_11_2011/post-1-0-96096900-1321131883.png

and click next through to completion (we are not installing any applications at this point).

Attached Image: monthly_11_2011/post-1-0-69177800-1321132002.png

Step 6. Create a Deploy Windows 7 X64 collection

Perform the following on your SCCM 2012 server as SMSadmin.

In the ConfigMgr console, click on Assets and Compliance, select Device Collections, click on Create Device Collection in the Ribbon

Attached Image: monthly_11_2011/post-1-0-13479600-1321132229.png

fill in the collection details, call it Deploy Windows 7 X64, limit it to All Systems

Attached Image: monthly_11_2011/post-1-0-70600000-1321132372.png

click next through the wizard, we will not add any computers to it yet, and we will not create any queries.

Attached Image: monthly_11_2011/post-1-0-04242700-1321132434.png

Step 7. Create Collection variables

Perform the following on your SCCM 2012 server as SMSadmin.

We want to set UDA variables on our
collection, so that a UDA user gets assigned as the primary user of
computers deployed in this collection. We are doing this to show you
that you can set a primary user to a device based on Collection

We could do this in other ways, for example using task sequence steps to set the variables or prestart
commands or a frontend HTA, I will come back to this subject later, but
for now, let’s just see it in action by specifying the two variables

Right click on the Deploy Windows 7 X64 Collection and choose Properties

Attached Image: monthly_11_2011/post-1-0-35656500-1321132524.png

click on the Collection Variables tab, click on the yellow startburst and add a new variable called SMSTSAssignUsersMode, set the value to Auto and remove the checkmark from Do not display this value in the Configuration Manager console

Attached Image: monthly_11_2011/post-1-0-72955300-1321132954.png

do the same again for another variable called SMSTSUdaUsers, specify the user as domain\user

Attached Image: monthly_11_2011/post-1-0-98623300-1321133109.png

Step 8. Deploy our Task Sequence

Perform the following on your SCCM 2012 server as SMSadmin.

To make the task sequence available to computers we need to Deploy it. In Software Library, select our Deploy Windows 7 X64 task sequence and choose Deploy

Attached Image: monthly_11_2011/post-1-0-33469700-1321133527.png

select our Deploy Windows 7 X64 collection and click ok to the warning

Attached Image: monthly_11_2011/post-1-0-18246600-1321133623.png

change purpose to Available (this keeps it optional, Required is Mandatory ! and dangerous as a result), place a checkmark in Make available to boot media and PXE

Attached Image: monthly_11_2011/post-1-0-39935400-1321133720.png

click next through the task sequence, until distribution points, by Default it will be set to Download content locally when needed by running task sequence, you can get this to change to Access content directly by editing each package referenced in the task sequence and setting the Data Access tab for each package, place a checkmark in Copy the content in this package to a package share on Distribution points

Attached Image: monthly_11_2011/post-1-0-22081700-1321133967.png

click next through the wizard to completion.

Attached Image: monthly_11_2011/post-1-0-47902900-1321134157.png

In our next part we will create an Application, and create a deployment type for that application to only install if the Primary User
is True for that device (User Device Affinity), we will then add a
computer to the new collection, PXE boot it and watch the process from
start to finish.

Original post here on

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.