Automatic installation of enterprise users Windows 7 deployment strategy

Compared to previous versions, Microsoft Windows 7 brings us so many new features and experiences. Whether it's an upgrade or a new deployment, the real experience of Windows 7 requires a time-consuming process. Fortunately, Microsoft provides different installation methods for different user types, let us have a chapter to follow.

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

I. About methods

MDT 2010 can be used 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 fewer support calls (all without the need for significant infrastructure investment).

Advantages of using MDT 2010 as an automated installation method include:

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

- Deployment is simpler because MDT 2010 handles applications, device drivers, and update installations.

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

Second, method requirements

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

- Microsoft Evaluation and Planning Toolkit

- Batches from Microsoft Authorization (VL) Media

- Microsoft Deployment Toolkit (MDT) 2010

- Application Compatibility Toolkit (ACT) 5.5

- Windows Automated Installation Kit ( Windows AIK), the kit contains the Windows User State Migration Toolkit (USMT) and other tools required by MDT 2010

- File Servers that store distribution shares

- One of the following types:

- Launching media used by client computers during deployment

- A server configured with the Windows Deployment Services role

III. Deployment process

1. Assess the company's readiness. Use the Microsoft Assessment and Planning Toolkit to determine your company's readiness for Windows 7.

2. Analyze application compatibility. Use ACT to grade your applications, determine their compatibility status, and merge applications. ACT will help you identify and fix applications that have compatibility issues.

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

4. Install MDT 2010 and the 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 a deployment share and prepare the operating system, applications, device drivers, and updates there.

6. Build a task sequence for installing Windows 7. In MDT 2010, create and customize a task sequence for each configuration you want to deploy. Instructions for installing Windows 7 are included in the task sequence.

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

8. Copy the boot image to your portable storage device. When creating media for deployment sharing, create a device to launch a Windows PE image by preparing a bootable DVD or USB flash drive (UFD) using an image created with MDT 2010. Alternatively, add a Windows PE image to Windows Deployment Services to start the image faster during deployment.

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

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

Fourth, method limitations

The automatic installation method does not impose any major restrictions on medium-sized businesses, but requires limited interaction at the beginning of the installation. As your business grows, you can easily extend MDT 2010 by configuring your database and deploying the Windows Deployment Services role for an almost zero-touch experience. Eliminate user interaction with the deployment process by automating application installation and operating system configuration, helping to reduce deployment and support costs.