Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part IIIJanuary 18, 2011 at 2:54 am | Posted in Deployment, Microsoft Deployment Toolkit (MDT), Windows 7 | 34 Comments
Tags: Deployment, Lite Touch, MDT 2010, Microsoft Deployment Toolkit (MDT) 2010, Microsoft Office 2010, Unattended Deployment, Windows 7
Other posts in this series:
Now that we’ve reviewed in Post I of this series how we can complete the initial configurations in MDT 2010, added a clean Windows 7 image and the task sequence to deploy it; and in Post II we’ve imported Microsoft Office 2010 into MDT and configure it for a customized, silent and unattended; in this third part of this series we are going to work directly in the capture and deployment process.
We’ll review how to deploy Windows 7 to a machine, achieving in the same deployment the automated installation of Microsoft Office 2010 and right after that, also automated, capturing that operating system. With a new a customized Windows 7 image we will add it to MDT 2010 for later deployments.
The interesting part about having this customized image imported in Microsoft Deployment Toolkit 2010 is that it can be our base image for all of our users. If you have several type of users in your organization, I’m pretty sure you can find some applications all of these types of users share (Microsoft Office is a good example); using MDT you can deploy this base image plus adding in the Task Sequences the automated deployment of the applications for each user.
Deploying and Capturing Reference Image
Since we have already the Task Sequence created for deploying Windows 7 + Microsoft Office 2010, we only need to use the LiteTouch media created in the Deployment Share to run the deployment wizard.
In my case, I’m going to use the WIM file with a Windows Deployment Services (WDS) server already running in my environment; this way I don’t have to use any local media in the client machine, just using a network connection will do.
1. In the WDS console, right click “Boot Images” and select “Add Boot Image”.
2. Select the LiteTouchePE WIM files existing in the Deployment Share directory of our MDT 2010.
3. Complete the WDS wizard.
4. In the client machine, we can boot from network using F12.
5. Select the LiteTouch Pre-installation Environment (PE).
6. Once the boot image is loaded, we can see that the LiteTouch wizard appears. Select “Run the Deployment Wizard to install a new Operating System”.
7. Type in the domain credentials from which you have access to the Deployment Share created by MDT 2010.
8. Select the Task Sequence created. In my case there’s only one “Deploy Windows 7 Clean Image”. Click on “Next”.
9. Enter the computer name and click on “Next”. Since we are capturing it, the name here has no relevance; the sysprep process will wipe all this information.
10. Select “Join a workgroup” and click on “Next”. If you are going to capture this image, DO NOT SELECT “Join a domain”; if this option is selected the capture step is disabled.
11. Since we are not migrating any user data, select “Do not restore user data settings”, click on “Next”.
12. Select the options in “Language and other preferences”.
13. Select the “Time Zone”.
14. Select the option “Capture an image of this reference computer”, and specify the options for the location and name of the WIM file to be created. Click on “Next”.
Remember that the location can be any shared folder available in the network (the credentials inserted earlier must have read/write permissions to this folder).
15. Review the details and click on “Begin”.
With that, the Task Sequence starts running. The first step will format the hard drives for the operating system deployment.
The operating system installation will start next.
And after a new reboot, the Task Sequence completes the work with the operating system installed and with the user logged in; Microsoft Office 2010 64-bit starts the installation completely automated and silent.
The installation takes a few minutes, and if you want to verify the process completed successfully just access the Start Menu before the machine reboots again.
Before the reboot, the sysprep process starts running which will erase all of the specific information from this operating system related to the machine (computer name, Product Key, SID, etc.).
Once the computer is rebooted, the process for creating the WIM file for this operating system starts; and of course sending that file to the destination folder we’ve chosen.
That process can takes several minutes to complete so you just have to be patient.
Importing the Captured Image into MDT 2010
Once the image has been captured, the importation process is simpler:
1. Open the MDT Console, expand the MDT Deployment Share, right-click “Operating Systems” and select “Import Operating System”.
2. Select “Custom image file” and click on “Next”.
3. Specify the path of the captured WIM file and click on “Next”. Also I’m selecting the option “Move the files to the deployment share…” to optimize disk space.
4. Select “Setup and Sysprep files are not needed” and click on “Next”. Since we’ve already prepared this operating system, there’s no need to include these files.
5. Specify the name for the destination folder and click on “Next”. In my case, I’m using “Windows 7 Pro x64 + Office 2010”.
6. In the summary page click on “Next”.
7. And in confirmation click on “Finish”.
With that, the operating system is imported to MDT 2010.
Creating the Task Sequence for Deployment
We now have the customized operating system imported into MDT, now we just need to create the Task Sequence to deploy it. The procedure is even simpler and we should now be familiarized with the environment to complete it without any problem.
1. Right-click “Task Sequences” and select “New Task Sequence”.
2. Complete the Task Sequence data. Remember to use a different “Task sequence ID” than the selected earlier, in my case “WIN7OFFICE2010”.
3. Select “Standard Client Task Sequence” and click on “Next”.
4. Select the operating system we’ve imported “Windows 7 Pro x64 + Office 2010” (I’ve changed the name for a more friendly one). Click on “Next”.
5. You can specify the product key in this step. Click on “Next”.
6. Complete the “OS Settings” and click on “Next”.
7. Specify the Administrator password or you can skip it. The administrator password set (if we did it) in the image we’ve captured maintains even if we executed sysprep. Click on “Next”.
8. Review the “Summary” and again the process should take a few seconds, once its completed click on “Finish”.
Deploying the Reference Image
We have completed all the configuration steps, and the only thing missing is deploying this image to the client.
1. In a client machine, boot from the network and select the LiteTouchPE boot image we’ve added earlier.
2. Run the “Deployment Wizard” in the same way we’ve executed before.
3. Specify credentials. Click on “Next”.
4. Select the task sequence to deploy the reference image, in my case “Deploy Windows 7 x64 + Office 2010”. Click on “Next”.
5. Join the machine to the domain if you prefer to. Click on “Next”.
6. Since we are not migrating profiles, select “Do not restore user data and settings”. Click on “Next”.
7. Select Language and Time Zone. Click on “Next”.
8. Since the image already has Microsoft Office 2010 installed, there’s no need to install it again. Click on “Next”.
9. Click on “Begin” and the installation process will start.
The operating system will complete its installation in a few minutes.
With that we’ve completed the third part of this series, I’m hoping I’ll prepare a few more about automating even more the deployments and add a few more features in the scenario.
I hope you found this useful.
Other posts in this series: