Enterprise User Windows 7 automatic installation

This article describes how enterprise users can deploy Windows 7 systems using automated installation methods. This method requires limited interaction at the start of the installation, but the rest of the process is automatic. If your company has a dedicated IT staff and a managed network of 200-500 client computers, we recommend using this method.

I. ON methods

You can use MDT 2010 as an automatic installation method. Using MDT 2010 is likely to require only the infrastructure you already have, with no other requirements (the file server is the only infrastructure requirement). Using MDT 2010 as an automated installation method simplifies deployment and reduces support costs by providing a more consistent configuration with less support for calls (none of which requires significant investment in infrastructure).

The advantages of using MDT 2010 as an automatic installation method include:

-Fewer problems because the configuration is consistent with all client computers.

-Deployment is simpler because the MDT 2010 can handle applications, device drivers, and update installations.

-Simplified maintenance because deploying applications, device drivers, and updates is extremely simple.

Second, the method requirements

In order to use the automatic installation method, the following elements are required:

-Microsoft Assessment and Planning Toolkit

-Volume Licensing (VL) media provided by Microsoft

-Microsoft Deployment Kits (MDT) 2010

-Application Compatibility Toolkit (ACT) 5.5

-Windows Auto-Install Kit (Windows AIK), which contains the Windows User State Migration Toolkit (USMT) and other tools required by MDT 2010

-Storage of file servers for distribution shares

-One of the following types:

-Start the media used by the client computer during deployment

-a server configured with the Windows deployment service role

III. deployment Process

1. Assess the readiness of the company. Use the Microsoft Assessment and planning kit to determine the company's readiness for Windows 7.

2. Analyze application compatibility. Use ACT to rank applications, determine their compatibility status, and merge applications. ACT helps you identify and fix applications that have compatibility problems.

3. Prepare the infrastructure for deployment. Prepare the infrastructure for MDT 2010 by creating a file server as a deployment share. Alternatively, install and configure the Windows Deployment Services role in Windows Server 2008. Starting a client computer by using Windows Deployment Services is the easiest way to start a network deployment.

4. Install MDT 2010 and necessary components. Install Windows AIK and MDT 2010 on the file server and other components required by the server.

5. Create a deployment share. Create deployment shares and prepare operating systems, applications, device drivers, and updates in them.

6. Build a sequence of tasks to install Windows 7. In MDT 2010, create and customize task sequences for each configuration that you want to deploy. The task sequence contains instructions for installing Windows 7.

7. Create a boot image. In MDT 2010, create the media that is used to connect to the deployment share. This media contains a Windows preinstallation (Windows PE) image that is used to start the client computer during deployment.

8. Copy the boot image to a portable storage device. Create a device to start a Windows PE image by preparing a bootable DVD or USB flash drive (UFD) by using the image created by MDT 2010 When you create the media to deploy the share. Alternatively, add a Windows PE image to the Windows Deployment service to start the image more quickly during deployment.

9. Deploy Windows 7 to each computer. Start each client computer by using a Windows PE image, and then follow the instructions to log on to the distribution share, select a task sequence, and install Windows 7.

10. Activate Windows 7. If your company does not use Key Management Services (KMS), manually activate Windows 7 with Microsoft.

IV. Methodological limitations

The automated installation method does not have any significant limitations on midsize enterprises, but requires limited interaction at the start of the installation. As your business grows, you can easily extend the MDT 2010 by configuring the database and deploying the Windows Deployment Services role to achieve an almost 0-touch experience. Eliminates user interaction with the deployment process by automating application installation and operating system configuration, which helps reduce deployment and support costs.