what is the best way to deploy a windows 7 installation to several systems

Figuring out the best manner to deploy Windows 7 in a large-scale environment (and of course, the deployment itself) can be a seemingly daunting task. However, with the proper preparation, the right tools, and a bit of know-how, it doesn't have to be. Today nosotros'll go over the different methods of deploying Windows 7 to assist you lot determine which method is correct for you and your organization.

Windows seven Deployment Options

Yous take four Windows 7 deployment strategy options to choose from:

• High-bear upon deployment with retail media
• High-impact deployment with standard epitome
• Low-cal-affect, high-volume deployment
• Zero-touch, high-volume deployment

The strategy that y'all'll ultimately choose will most probable be based on skill level and the amount of computers you program to deploy to, ranging from just a few, to over 500 computer systems. Once you go through all of your options and decide which strategy is best for yous, you can refer to this guide to figure out what tools you lot'll need then you can properly ready yourself for the job at manus.

Think about your current state of affairs, how many computers are involved, and what kinds of tools yous're already comfortable using. I would recommend putting all of the data you know near the deployment (or hypothetical deployment) on newspaper or even a listen-mapping program to better analyze your state of affairs. I discover that I am usually a lot more productive during the planning stages if I can put what I know down on paper to clear my mind for the bodily planning process.

Allow's have a expect at the different Windows 7 deployment strategies, and go over what they entail.

High-Touch Windows 7 Deployment (with Retail Media)

The high-affect with retail media selection is the most mutual deployment strategy and is aimed towards deployments with fewer than 100 computer systems. For smaller businesses and organizations, this method makes the most sense every bit the It on board will have to do the least amount of prep work, and focus on each system individually to ensure compatibility and functionality.

This strategy volition accept reward of:

• Windows Automated Installation Kit (AIK)
• A wink drive
• Retail Windows vii media

While there are many different ways to perform a high-bear on deployment, the easiest would be to use an "Unattend.xml" file or "answer file". By creating and using an reply file, you eliminate the demand for user input when manually installing/deploying Windows 7. Y'all would still need to put the retail media in, but by using an reply file, the default settings (computer names, time zone, workgroup names, drivers, etc.) would automatically be inputted for yous.

Y'all should follow this path when using the loftier-bear upon with retail media deployment method:

1. Create an "Unattend.xml" file for Windows 7 using Windows System Image Manager. Be sure to include whatsoever drivers y'all program to deploy with the image.
2. Copy the resulting file to your USB wink drive. Windows looks for this file in a variety of places, but storing information technology on a flash drive is the easiest to go along track of, update and transport.
3. Inset the USB flash bulldoze and retail media into the PC, and either refresh or upgrade as required.
4. Yous tin can optionally use Windows Piece of cake Transfer to restore the users' documents and settings to the estimator. This step is only necessary if yous refreshed the reckoner with a new installation in the previous step. Upgrades will automatically keep all user settings and documents.
5. Complete the deployment by installing applications and configuring the estimator as required.
6. Continue on to the next computer.

Learn more well-nigh this blazon of deployment on TechNet: High-Bear on Deployment with retail media

Loftier-Affect Windows 7 Deployment (with Standard Image)

The loftier-bear upon with standard image deployment strategy is most ordinarily used for deployments between 100 and 200 calculator systems, merely skilled It staff can take advantage of this method for smaller deployments too, to salvage time. The primary do good to this strategy is being able to include whatever applications and files inside the paradigm, and so yous don't demand to add together them after each installation.

This strategy will take advantage of:

• Retail or book-licensed media
• A Flash drive
• Windows Automated Installation Kit (AIK)
• Microsoft Deployment Toolkit (MDT) 2010
• Awarding Compatibility Toolkit (ACT)

Equally an added do good to this strategy, once the epitome has been created, businesses and organizations tin can provide the epitome to their original equipment manufacturers (OEMs) so that when a new computer is purchased, it will be ready to set upward and connect to the network.

Although this is a keen strategy to use for about organizations, information technology doesn't calibration well. Using an image prevents the ability to use the upgrade feature and restoring user data is harder for larger organizations. As well, because this is a high-touch deployment, a technician and flash bulldoze are required to deploy out to each computer system, something that would be costly to do for larger organizations. Larger organizations with multiple departments may also come across bug, since each department might need a different set of applications, creating a need for multiple images.

Yous should follow this path when using this deployment method:

1. Optional, though recommended, you lot can use the Applications Compatibility Toolkit (ACT) to prioritize applications, make up one's mind whatsoever compatibility bug that y'all might face up, and consolidate applications.
2. Set a client automobile as the canvas for creating your first prototype. Install everything normally from the retail media or VL media. Microsoft recommends you "use an answer file (Unattend.xml) to install Windows on the reference computer to brand this process consistent and reproducible."
3. Install any applications, drivers, settings, and updates that you would like to include in the final prototype.
4. Run Sysprep to generalize the epitome for deployment.
5. Kicking into the computer using the Windows Pre-installation Surroundings (Windows PE) and capture the prototype using ImageX.
6. Re-create the image to flash drive, external hard drive, or network share.
7. Next, we demand to prepare the installation media; there are two ways to go about this. Beginning, you can create an reply file (Unattend.xml) and point it to the image y'all copied to the drive or network share. Alternatively, you lot tin can create a new installation media by replacing the Install.wim file with the image file you captured previously.
8. Optionally, you tin utilise the Windows Piece of cake Transfer magician to relieve documents and settings from client computers.
9. Start deploying onto each client calculator, either by using the reply file (Unattend.xml) or using the setup media you created.
10. If you lot completed Step 8, you tin now use the Windows Easy Transfer wizard to restore users' documents and settings.
11. Finally, the machines must be activated online.

Learn more about this type of deployment on TechNet: High-Touch deployment with standard paradigm

Calorie-free-Touch, Loftier-Volume Deployment

The lite-touch, high-volume deployment strategy is aimed at much larger organizations with a skilled IT professional with deployment experience. More often than not, organizations with 200-500 figurer systems should employ this strategy. Using standardized images and network access using pull automation, limited interaction is required at the beginning of the installation.

This strategy will take reward of:

• A server configured with the Windows Deployment Services role
• Book-licensed (VL) media
• Windows Automatic Installation Kit (AIK)
• Microsoft Deployment Toolkit (MDT) 2010
• Application Compatibility Toolkit (Deed)
• Microsoft Assessment and Planning Toolkit (MAPT)
• Windows Deployment Services (WDS)

The light-touch strategy is great for organizations within the range mentioned to a higher place since it offers express interaction, lowering the time and costs required for deployment. Configurations are consistent across all calculator systems, then less bug are likely to occur. MDT 2010 handles all application, driver, and update installations on its own. Not to mention easier maintenance options for updating applications, drivers, and software updates.

This is the path you should follow when using this deployment method:

1. Utilise the Microsoft Assessment and Planning Toolkit to determine compatibility issues with a new operating system.
2. Use the Applications Compatibility Toolkit (Deed) to prioritize applications, determine any compatibility problems that you might face, and consolidate applications.
3. Prepare the infrastructure for MDT 2010 by creating an answer file and optionally install the WDS office in Windows Server 2008 R2.
4. Install MDT 2010 on the file server along with additional components as required, including the User Land Migration Tool.
5. Create a distribution share that contains operating systems, applications, drivers, and updates.
6. In MDT 2010, create and customize a job sequence for each configuration y'all volition be deploying. In one case consummate, create and update a deployment betoken.
7. Create a device to start the Windows PE prototype past preparing a removable storage device with the images created by MDT 2010 when you update a deployment point. Optionally, you can add the Windows PE image to WDS to brand starting the image a fleck easier during deployment.
8. Finally, start each client computer by using the Windows PE image you created, and follow the instructions to connect to the shared resource, choose a task sequence, and install Windows 7.

Learn more near this type of deployment on TechNet: Lite-Impact, Loftier-Volume

Null-Touch, High-Volume Deployment

The zero-impact, loftier-book deployment strategy is fully automated and generally only meant for large organizations with over 500 computer systems, and an It professional with deployment and Configuration Manager 2007 R2 expertise. Using standardized images with network access using push automation, the deployment becomes completely automated. No interaction with customer computers is necessary during the installation process.

The zero-touch strategy takes advantage of:

• A server configured with the Windows Deployment Services role
• Volume-licensed (VL) media
• Windows Automated Installation Kit (AIK)
• Microsoft Deployment Toolkit (MDT) 2010
• Application Compatibility Toolkit (Act)
• Microsoft Assessment and Planning Toolkit (MAPT)
• Windows Deployment Services (WDS)
• Configuration Managing director 2007 R2

You should follow this path when using this deployment method (Note: items in quotes are direct references to the Microsoft TechCenter guidelines):

1. Review the Planning and Process guide for deploying Windows 7 using the nada-touch strategy.
2. Apply the Microsoft Assessment and Planning Toolkit to figure out if your organization is ready for Windows 7.
3. Use the Application Compatibility Toolkit (ACT) to prioritize applications, determine any compatibility bug that you might face, and consolidate applications.
4. Fix your organizations infrastructure with MDT 2010, "including installing and configuring Configuration Manager 2007 R2 and its prerequisites, creating the required user and service accounts, and configuring Agile Directory Domain Services."
5. "Install MDT 2010, and configure the Configuration Manager 2007 R2 integration. This process includes configuring how to define new computers in the site database and creating additional packages that Configuration Director 2007 R2 requires during deployment (USMT package, Custom Settings packet, and and so on)."
6. "Optionally, create a custom master image by using Configuration Manager 2007 R2 to deploy Windows 7 to a master figurer, customize the configuration, and then capture the custom image."

Learn more than about this blazon of deployment on TechNet: Zero-Affect, Loftier-Volume Deployment

Windows 7 Deployment Resource

Here's a couple of handy resources that will help you learn more than well-nigh Windows vii deployment:

• Windows 7 Deployment FAQ
• Deploying Windows 7 Essential Guidance
• Windows 7 Deployment Learning Portal
• Microsoft Deployment Toolkit (MDT) Overview
• Application Compatibility Toolkit (ACT) Overview -- coming soon
• Microsoft Cess and Planning (MAP) Toolkit Overview -- coming soon

I hope this guide helped you to better empathize the Windows seven deployment procedure, and to figure out which deployment method is right for y'all and your organization. If you have any questions about the deployment procedure, feel free to exit a comment below. Be certain to keep an eye on more than articles on Windows vii deployment. Thanks for reading!

The Ultimate Windows seven Deployment Training

Master Windows seven deployment with the help from Microsoft'south Setup and Deployment MVP, Rhonda Layfield. Rhonda's new Windows 7 deployment training covers everything you need to know to plan and implement a successful deployment, whether y'all're deploying to v or 5,000 PCs. See every deployment tool and technique that is bachelor to yous in action and prepare for the lxx-681 MCTS exam to validate your Windows 7 deployment cognition.

Larn more: Windows 7 Deployment Preparation

wayandonellove1988.blogspot.com

Source: https://www.pluralsight.com/blog/it-ops/windows-7-deployment-strategy

Share this post