[Events] Overview of Code Camp 2011 and Materials
December 5, 2011 at 12:20 am | Posted in App-V, Deployment, Events, Microsoft Deployment Toolkit (MDT), Virtual Desktop Infrastructure (VDI), Windows Server 2008 R2 | Leave a commentTags: App-V, Deployment, Microsoft Deployment Toolkit (MDT) 2010, Server App-V, VDI, Virtual Desktop, Virtual Desktop Infrastructure
I’ve had the great pleasure to present in October, once again, in one of the main Microsoft events in Argentina, Code Camp 2011. This time with two new tracks: “Desktop of the Future” and “Standardizing Windows Server 2008 R2 images”.
As I mentioned earlier in older posts of mine, Code Camp is an event organized and developed by Microsoft Academics which is held in some important universities of Buenos Aires, this time the selected institution was, as a few years back, Universidad Abierta Interamericana (UAI).
The event contains over 50 tracks presented by students and professionals not only as IT but also as developers. Some of the main topics this year were: Windows Azure, Cloud Computing, SQL Server 2012, Mango and Windows Phone, XBOX and Kinect, VDI, Deployment solutions and so on.
Regarding my topics, the tracks were focused on Virtual Desktop Infrastructure (VDI) integrated with App-V; and a deep dive into Microsoft Deployment Toolkit (MDT) to automate Windows Server’s deployments.
Desktop of the Future
I’ve presented this session (the original Spanish name: “El Escritorio del Futuro”) with Emiliano Estevez, friend and colleague of mine in Algeiba IT where he works as the Services Director.
This track introduces Virtual Desktop Infrastructure (VDI) technology as a result for some current demands in today’s business. By reviewing some of the basic concepts of VDI, we’ve completed the main steps to prepare the Virtual Desktops infrastructure in our company using Hyper-V and Remote Desktop Services (RDS).
We’ve also introduced App-V as the main solution to optimize application management in virtual desktops scenarios, and also with the highly important “Shared Cache” feature to save a lot of money in storage. And finally we had a quick glance about Server App-V, the new technology included in SCVMM 2012 to virtualize server’s applications.
The presentation can be downloaded from this link.
Standardizing Windows Server 2008 R2 Images
This track (the original Spanish name: “Estandarizando Servidores Windows Server 2008 R2”) was presented with another colleague in Algeiba IT, Alejandro Barrionuevo, who’s working as an IT Consultant.
In this session, we’ve reviewed with Alejandro the main benefits of using Microsoft Deployment Toolkit (MDT) 2010, combined with other free tools, to standardize and automate the deployment for Windows Server 2008 R2 OS. We had a quick look about understanding the Solution Accelerators from Microsoft.
We had a detailed look about the process involved in this automation, including some practical demos about using MDT 2010 task sequences, scripts and also editing MDT files used in the deployment process for a complete automated deployment.
The presentation can be downloaded from this link.
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III
January 18, 2011 at 2:54 am | Posted in Deployment, Microsoft Deployment Toolkit (MDT), Windows 7 | 26 CommentsTags: Deployment, Lite Touch, MDT 2010, Microsoft Deployment Toolkit (MDT) 2010, Microsoft Office 2010, Unattended Deployment, Windows 7
Other posts in this series:
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II
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:
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II
January 16, 2011 at 3:54 pm | Posted in Deployment, Microsoft Deployment Toolkit (MDT), Windows 7 | 16 CommentsTags: Deployment, MDT 2010, Microsoft Deployment Toolkit, Microsoft Deployment Toolkit (MDT) 2010, Microsoft Office 2010, Unattended Deployment, Windows 7
Other posts in this series:
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III
After completing the first post of this series where we’ve installed and configured MDT 2010 Update 1, added a Windows 7 clean image to the Deployment Share and created the Task Sequence to deploy it; in this second part of “Deploying Windows 7 + Office 2010 using Microsoft Deployment Toolkit (MDT) 2010” we are going to work with Microsoft Office 2010 application.
In this post we will add Microsoft Office 2010 as an application in our Deployment Share, and configure the environment to achieve a silent and unattended installation for this suite.
The unattended possibilities for deploying applications in MDT always depend on the application we are using, fortunately Microsoft Office is highly prepared to accomplish this unattended installation, and with the possibility to customize it by easily selecting the features we would like to install in Config.xml answer file.
Adding Microsoft Office 2010 to MDT
Adding applications to Microsoft Deployment Toolkit 2010 requires only running a simple wizard which should not be any problem.
Note
We do need of course the Microsoft Office 2010 binaries, and since we would like to use the unattended possibilities complemented with MDT 2010, we are going to need the installation files we can find in the Office 2010 DVD.
The stand alone installer (for example: en_office_professional_plus_2010_x64_515489.exe) can be used but we cannot edit the properties in MDT console.
Let’s start with the wizard:
1. In the MDT console, expand the Distribution Share we’ve created right-click “Applications” and select “New Application”.
2. Select “Application with source files” and click on “Next”.
3. Complete the information for this new application and click on “Next”.
4. Select the source directory where we can find the “setup.exe” file.
In my case I’m using the DVD which contains the x86 and x64 versions, since we can only add one architecture at a time, you must select one sub folder. And considering we are deploying a 64-bit operating system, I’m going to install the 64-bit Microsoft Office 2010 version.
5. Specify the directory name to be stored, in my case “Microsoft Office 2010 x64”. Click on “Next”.
6. In “Command Line” type “setup.exe” for the installer file to be executed, the “Working directory” can be left with the default option.
7. In “Summary” review the options selected and click on “Next”.
The importation process will start and should not take much longer.
8. Once completed, click on “Finish”.
With the application added we can double click it to access its properties.
As you can see importing a Microsoft Office product includes a tab in the MDT properties called “Office Products” which contains options to simplify the unattended process.
Configuring Office 2010 Unattended Installation
Now that we have the application imported, we can configure a silent, unattended and customized installation of Microsoft Office 2010 within a few steps:
1. In the properties section, select the “Office Products” tab.
2. Select the following options and click on “Apply”:
“Office product to install”: The version you are using, in my case Professional Plus “ProPlus”.
“Office languages”: Language available, in my case “en-us”.
“Product Key”.
“Customer Name”.
“Display Level”: “None”. With this, in the installation process we won’t see any window running.
“Accept EULA”: Enabled.
“Always suppress reboot”: Enabled.
All these options are stored in one file: Config.xml; which is used of course as an answer file for the unattended installation for Office 2010. In this file we must also set the features we would like to install, and the type of installation.
For more information, take a look to this link: Config.xml file OptionState ID values for Office 2010.
3. Click on “Edit Config.xml” to view and edit the unattended installation file. You will see something like this:
We are going to edit this adding the features we would like to install. Here’s an example of the Config.xml file I’ll be using in this series, download it in this link.
I’m ignoring the lines with “<!—” since they are used for comments and examples.
<Configuration Product=”ProPlusr”>
<Display Level=”None” CompletionNotice=”No” SuppressModal=”No” AcceptEula=”Yes” />
<COMPANYNAME Value=”Augusto Alvarez” />
<Setting Id=”SETUP_REBOOT” Value=”Never” />
<AddLanguage Id=”match” />
<AddLanguage Id=”en-us” ShellTransform=”Yes” />
<PIDKEY Value=”xxxxxxxxxxxxxxxxxxxxxxxxx” />
<OptionState Id=”AccessFiles” State=”absent” Children=”force” />
<OptionState Id=”ExcelFiles” State=”Local” />
<OptionState Id=”GrooveFiles” State=”Absent” Children=”force” />
<OptionState Id=”OneNoteFiles” State=”Local” Children=”force” />
<OptionState Id=”OUTLOOKFiles” State=”Local” />
<OptionState Id=”PPTFiles” State=”Local” />
<OptionState Id=”PubPrimary” State=”Absent” Children=”force” />
<OptionState Id=”WORDFiles” State=”Local” />
<OptionState Id=”XDOCSFiles” State=”Absent” Children=”force” />
<OptionState Id=”SHAREDFiles” State=”Local” />
<OptionState Id=”TOOLSFiles” State=”Local” />
<OptionState Id=”EXCELFiles” State=”Local” />
</Configuration>
In this example the following features are being installed: Word, Excel, OneNote, Outlook, Office Tools (like Office Picture Manager, HTML source editor, etc.) and Shared Files. All of this is using the “Local” type of installation, which in this scenario is usually a better choice than “Install on first use”.
Adding Office 2010 to the Task Sequence
With the application imported and the unattended file in place, we just need to edit the Task Sequence we’ve created in the first post to use this application.
1. Expand the Distribution Share, “Task Sequences” and double click on the task sequence we’ve created earlier “Deploy Windows 7 Clean Image”.
2. In the last phase of the task sequence, “State Restore”, click on “Install Applications” and select “Install a single application” where you can select Office 2010 using the “Browse…”
With that, we have Microsoft Office 2010 64-bit added to MDT 2010 and configured for a customized and unattended installation within our Windows 7 deployment process.
In the next post, we will not only deploy this Windows 7 + Office 2010 but we will also prepare for an automated capture of this image and upload it to our MDT 2010.
Other posts in this series:
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part I
July 13, 2010 at 2:56 am | Posted in Deployment, Microsoft Deployment Toolkit (MDT), Windows 7 | 20 CommentsTags: Automatic Deployment, Deployment, MDT 2010, Microsoft Deployment Toolkit, Microsoft Deployment Toolkit (MDT) 2010, Microsoft Office 2010, Office 2010, Windows 7
Other posts in this series:
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III
I’ve started (finally!) re-editing a set of posts created a while ago: “Microsoft Deployment Toolkit 2010 Beta 1: Using MDT to Prepare, Install and Capture Customized Windows 7 Images”: Part I, Part II and Part III. Within those posts we had the chance to review some step-by-step procedures to create customized images of Windows 7, including Microsoft Office 2007 and achieve an automatic deployment; using always the Beta version of Microsoft Deployment Toolkit 2010.
Now we are going to evaluate some interesting step-by-step procedures for automated deployment of Windows 7 + Microsoft Office 2010 using Microsoft Deployment Toolkit (MDT) 2010.
The current version of this free deployment tool is Microsoft Deployment Toolkit 2010 with Update 1. This latest update brings some nice improvements:
- Comprehensive tools and guidance to efficiently manage large-scale deployments of Microsoft Office 2010.
- A new User-Driven Installation (UDI) deployment method that utilizes System Center Configuration Manager. UDI lets end users initiate and customize an OS deployment on their PCs—via an easy-to-use wizard.
- Automatically detects the true supported platforms for drivers, reducing deployment issues.
As in the previous set of posts, using the final and latest version of MDT 2010, we will use the Lite Touch Installation (LTI) for the deployment of Windows 7. For the Zero Touch Installation of Windows 7 we can use Microsoft Deployment Toolkit 2010 with System Center Configuration Manager 2007 R2 SP2.
Note: Only using SCCM 2007 with SP2 is the supported platform for deploying Windows 7; prior this release, the environment is not supported to use Configuration Manager Operating System Deployment (OSD).
What We Are Going To Do?
These posts will represent a step-by-step procedure for the following tasks:
- · Install and configure Microsoft Deployment Toolkit 2010 – Update 1.
- · Create a Task Sequence and deploy clean Windows 7 images.
- · Adding and configuring Microsoft Office 2010 in MDT 2010 for deployment.
- · Creating and capturing a reference image of Windows 7 and Microsoft Office 2010.
- · Automatic deployment of the customized Windows 7 images with Microsoft Office 2010 installed.
Requirements
Before starting with any procedure we need to review the requirements for the environment. In my case I’ll be using:
- Active Directory and DNS infrastructure working and operational.
- DHCP configured with Windows Deployment Services (WDS).
- Windows Deployment Services (WDS) configured.
- Windows 7 source files.
- Microsoft Office 2010 installation files.
Note: This previous post of mine shows how WDS must be configured to work together with DHCP.
As in software and features necessary:
- Windows Automated Installation Kit (WAIK) 2.0. You can download it from here.
Note: The download page indicates that the WAIK version is “1”; but don’t worry, the actual version is 2.0.
- · MSXML 6.0.
- · PowerShell.
- · .Net Framework 3.5 SP1. Available for download here.
Note: Even though .Net Framework 2.5 SP1 is not a requirement for MDT 2010 installation; one of its features, User-Driven Installation (UDI), does requires the latest Microsoft Framework installed.
Here’s a message you will see when you try to run the UDI launcher:
MDT 2010 Installation
As for all the Microsoft Deployment Toolkit versions, the installation is a straight forward procedure: Just download, execute the installer and complete the installation wizard.
![clip_image001[1]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image0011.png "clip_image001[1]")
Once installed, we can access any of the components from the “Start Menu”.
![clip_image001[3]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image0013.png "clip_image001[3]")
One of the coolest options we can find in Microsoft Deployment Toolkit 2010 (and in most of Microsoft platforms) is the idea of designing the User Interface as places to find everything you need to know about what to do next.
“Getting Started”: All the steps involved to get MDT 2010 functional.
![clip_image001[5]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image0015.png "clip_image001[5]")
“Documentation”: All necessary links to start working with the tool.
![clip_image001[7]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image0017.png "clip_image001[7]")
Also another important section is “Components” where we can verify that all necessary requirements were installed (plus other optional installations).
![clip_image001[9]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image0019.png "clip_image001[9]")
Adding a Clean Image to MDT 2010
With the application installed, we can now start working directly with the operating system deployment. The configurations needed in MDT 2010 maintains as the Beta version and the older versions of the Deployment Toolkit.
The process is the following:
1. Create the distribution share.
2. Add operating system files to the distribution share.
3. Create a task sequence for the reference computer.
Creating the Distribution Share
1. In the MDT Console, right click on “Deployment Shares” and select “New Deployment Share”.
![clip_image001[11]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00111.png "clip_image001[11]")
2. In the wizard, click on “Browse”.
3. Select a folder where you want to store all the binaries (applications, operating system, etc.) MDT will use. As a recommendation use a separate partition.
![clip_image001[13]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00113.png "clip_image001[13]")
4. Click on “Next”.
![clip_image001[15]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00115.png "clip_image001[15]")
5. Accept the name of the “Share Name” and click on “Next”.
![clip_image001[17]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00117.png "clip_image001[17]")
6. In the next page we can add a short description for the distribution share. Click on “Next”.
7. Ensure that the option “Ask if an image should be captured” is checked and click on “Next”.
![clip_image001[19]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00119.png "clip_image001[19]")
8. Another option we can select in this stage is if we are going to let users who are deploying an image can set the local administrator password. In large environment this is normally not recommended since not all users in charge of the deployment should be local administrators of the operating systems.
![clip_image001[21]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00121.png "clip_image001[21]")
Click on “Next”.
9. Leave deselected also the option for “Ask user for a product key”. This option will be set in the task sequence of each operating system deployment. Click on “Next”.
![clip_image001[23]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00123.png "clip_image001[23]")
10. Review the “Summary” page and click on “Next”.
11. Wait for the process to complete and click on “Finish”.
![clip_image001[25]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00125.png "clip_image001[25]")
Once the process completes, we should see this in our MDT 2010 Management Console.
![clip_image001[27]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00127.png "clip_image001[27]")
Adding Windows 7 Operating System
Once the deployment share is created, the next step is to add the files from the Windows 7 image. In my case I’ll be using a Windows 7 64bits image.
1. In “Deployment Shares”, expand the deployment share we’ve just created, right click “Operating Systems” and select “Import Operating System”.
![clip_image001[29]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00129.png "clip_image001[29]")
2. Since this is a clean image from the Windows 7 media, select “Full set of source files” and click on “Next”.
![clip_image001[33]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00133.png "clip_image001[33]")
3. I’m selecting the D:\ directory since I have attached the Windows 7 media in this drive. Click on “Next”.
![clip_image001[31]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00131.png "clip_image001[31]")
4. Select the “Destination directory name” and click on “Next”.
![clip_image001[35]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00135.png "clip_image001[35]")
5. In the “Summary” page click on “Next”.
6. Once the process is complete, click on “Finish”.
![clip_image001[37]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00137.png "clip_image001[37]")
In my case, the images added will look like this in the MDT console.
![clip_image001[39]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00139.png "clip_image001[39]")
Creating the Deployment Task Sequence
Now we have the distribution share with a clean image of Windows 7, we can create a task sequence to deploy the operating system.
1. In “Deployment Shares”, expand the deployment share created, right click “Task Sequences” and select “New Task Sequence”.
![clip_image001[41]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00141.png "clip_image001[41]")
2. Insert a “Task Sequence ID”, I’m using “WIN7”. And a “Task Sequence name”, in my case “Deploy Windows 7 clean image”. Click on “Next”.
![clip_image001[45]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00145.png "clip_image001[45]")
3. Accept the default option in “Template”: “Standard Client Task Sequence”. Click on “Next”.
![clip_image001[47]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00147.png "clip_image001[47]")
4. Select the operating system to deploy. Since I have several options, I’ll be using “Windows 7 Professional”. Click on “Next”.
![clip_image001[49]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00149.png "clip_image001[49]")
5. The “Product Key” section can be used to not specify a key at this point. Click on “Next”.
![clip_image001[51]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00151.png "clip_image001[51]")
6. Complete the information about the registered user and click on “Next”.
![clip_image001[53]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00153.png "clip_image001[53]")
7. In my case I’m also selecting the local Administrator password. Click on “Next”.
![clip_image001[55]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00155.png "clip_image001[55]")
8. In the “Summary” page click on “Next”.
![clip_image001[59]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00159.png "clip_image001[59]")
9. Once the process is complete we can click on “Finish”.
![clip_image001[57]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00157.png "clip_image001[57]"){kind=small}
Note there’s an option of “View Script”, which we can use to retrieve an automated script to use for every time we want to create a similar Task Sequence (we only need to change the values used)
Once the Task Sequence is added, we should see something like this:
10. The process is completed once we update the Deployment Share. In the Deployment Share name, right click and select “Update Distribution Share”.
![clip_image001[61]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00161.png "clip_image001[61]")
11. Leave selected the option for “Optimize the boot image updating process”. Click on “Next”.
![clip_image001[63]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00163.png "clip_image001[63]")
12. Click on “Next” on “Summary”. This process can take a few minutes since it will be creating new files, including the boot images “LiteTouchPE_x86.iso” and “LiteTouchPE_x64” which can be used for the clean operating system deployment.
![clip_image001[65]](http://augustoalvarez.files.wordpress.com/2010/07/clip_image00165.png "clip_image001[65]")
Within this process the Distribution Share is populated with several files which will be used in the operating system deployment. Even though we didn’t use the option, Microsoft Deployment Toolkit also includes the section for “Out-of-box Drivers”.
The drivers section includes a simple wizard where we can add device drivers into the operating system deployment. Using only the “.inf” files from these drivers, we can add the components directly; but always remember to use the “Update Distribution Share” once those are added; with that the drivers are injected automatically.
In the next post we will add Microsoft Office 2010 to MDT 2010, the Task Sequence involved and configuring this application for a silent install.
Stay tuned!
Other posts in this series:
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part II
Deploying Windows 7 + Office 2010 Using Microsoft Deployment Toolkit (MDT) 2010 – Part III
-
-
-
About Me
Computer geek, totally fan of the latest's IT platform solutions. Since 2006 I've been mentioned as Microsoft Student Partner, I continue working with them, collaborating on different academic and technological events. On this blog, you'll find most of the experience I have evaluating, designing, implementing and managing those technologies.
-
-
App-V Book
-
Visitors Map
-
Recent Comments
Farzan on Deploying Windows 7 Using Wind… gizachew on Five Easy Steps to Configure W… Mark on Deploying Windows 7 Using Wind… Christopher Dean on Deploying Windows 7 Using Wind… Christopher Dean on Deploying Windows 7 Using Wind… Technorati
Blog at WordPress.com. | Theme: Pool by Borja Fernandez.
Entries and comments feeds.
