How To Create A Windows 7 Image For Deployment

The simple answer : Use MDT 2012 Update 1, WAIK and WDS (John and Josh are Both right.)

MDT is free and information technology will build, capture, and deploy Windows seven images. More than that though, it volition update the systems at deploy time, name the systems, inject drivers, bring together to the domain, add together local admin groups, you name information technology, MDT can do it.

Use WDS for PXE boot and multicasting if you have Server 2008 or above. Don't effort to build and capture with WDS alone. WDS by itself is non a deployment solution. AIK past itself is not a deployment solution.

The beauty of MDT is that it uses task sequences to automate everything dynamically. Use it build your images, and so use it to deploy those same images. Build a share for both, one for builds, and one deploys.

Employ a VM to build your reference, and you lot can build a "hardware independent" image that'll run on everything, laptops, desktops, Dell, HP, Lenovo, whatever. MDT tin do the drivers later at deploy time. When combined w/ WDS, it's the only deployment solution yous'll always want to use again. Every bit far every bit pitfalls are concerned, you should make certain you build a good image that has just the bones core applications, almost everything else can come later.

The MDT Deployment Workbench. Notation that Win7 & WinPE drivers are segregated.

Download and Install:

1. Download & Install MDT 2012 http://www.microsoft.com/en-united states of america/download/details.aspx?id=25175

2. Download & Install Win7 AIK http://www.microsoft.com/en-us/download/details.aspx?id=5753

3. Download Win7 AIK Supplement http://www.microsoft.com/en-us/download/details.aspx?id=5188

4. Download Win7SP1 digital river SP1 ISOs are listed on super user'due south FAQ

Overview of what to do in the MDT workbench:

1. Create Deployment Share http://www.youtube.com/lookout?five=ciT_YqLdcgk

2. Import Drivers http://www.youtube.com/watch?v=bWdGBVyD1pM

3. Import a .wim file from your Windows install CD or a custom .wim file

4. Create a chore sequence and point it your .wim file

5. Yous would then launch the Windows System Image Director from the Chore Sequence Properties Os Info Tab. to edit your unattended.xml file.

6. Update the deployment share

7. Burn the boot iso, boot to ISO (employ this iso to upload and download images)

Optional Steps for WDS Integration: (For PXE Booting & Multicast)

1. Install WDS Role on Server

2. Upload Boot.wim from MDT Share

3. Configure PXE Boot

4. Enable multicast in MDT

Accept Control of Drivers

Once more, to ensure a reference paradigm can run on both Laptops and Desktops, and across vendors, build it in a Virtual Environment. This way your reference image is truly hardware independent. Don't worry about drivers in your reference build, MDT can be configured to inject drivers dynamically into the epitome file at deploy time.

Look into a Driver Injection model known as "total control". The idea is uncomplicated, by segregating the drivers used in the workbench, you can ensure that only the correct drivers are injected to the right systems. This is achieved past first creating a strictly organized set of folders within the workbench. At the very peak of this we have the root folder Out of box Drivers. Inside this folder we accept a binder for each OS we will exist supporting. Next we sort in nonetheless another pair of folders by Architecture, x86 vs. x64.

In the case of this example, nosotros accept ii folders in the root of out of box drivers in the workbench, One for Windows seven, and another for Windows PE. Within both of these folders nosotros will accept a folder named after the Manufacturer equally it would appear in WMI or organization information. Then, finally within those folders we want to have folders named equally the Model info, again exactly equally it appears within system information.

For case, ane would find the 64 fleck Win7 drivers for the HP 8300 in: Windows 7\x64\Hewlett-Packard\HP Compaq Elite 8300 SFF. This may seem like overkill at first, but information technology pays off in dividends when we set the driver grouping variable in the customsettings.ini file.

DriverGroup Settings in MDT

Learning MDT is highly rewarding, even though it takes some time, but it really pays off. Once you lot really understand the system, y'all can have one baseline image, and apply all the apps and drivers dynamically on the wing. A well tuned MDT lite touch can install the OS, name the PC, inject drivers, join to the domain, install all needed apps, actuate office, and reboot in less than an hour with almost no interaction required from the tech who is running the deployments.

Deployment Soup Video

http://technet.microsoft.com/en-the states/windows/hh215959

Deploying Windows A - Z

http://www.microsoft.com/en-us/download/details.aspx?id=6157

Learning to use MDT litetouch

http://www.deploymentresearch.com/Videos/MDT2010LiteTouchUnleashedVideos.aspx

Source: https://superuser.com/questions/77821/what-tool-can-i-use-to-create-and-deploy-windows-7-images

Posted by: medranogoomects.blogspot.com

Share this post