The Windows® Automated Installation Kit (AIK) for Windows® 7
Overview
The Windows® Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and deployment of Windows® operating systems. By using Windows AIK, you can automate Windows installations, capture Windows images with ImageX, configure and modify images using Deployment Imaging Servicing and Management (DISM), create Windows PE images, and migrate user profiles and data with the User State Migration Tool (USMT). Windows AIK also includes the Volume Activation Management Tool (VAMT), which enables IT professionals to automate and centrally manage the volume activation process using a Multiple Activation Key (MAK).Top of page
System requirements
Supported operating systems: Windows 7 Service Pack 1, Windows Server 2008 R2 SP1• Windows Server 2003 with Service Pack 2• Windows Vista SP1• Windows Server 2008 family• Windows 7 family• Windows Server 2008 R2 familyTop of page
Instructions
To install the Windows AIK, you must first download the ISO, Write the ISO file to a DVD using a third party tool, and then install the Windows AIK from the DVD. For installation on Windows prior to Windows 7, this download requires that you run genuine Microsoft Windows. Click the Continue button in the Validation Required section to begin the validation process. After validation is complete, you will return to this page to continue the download. For the latest issues and known workarounds, see the Windows AIK Readme file (http://go.microsoft.com/fwlink/?LinkId=139690).Top of page
http://www.microsoft.com/en-us/download/details.aspx?id=5753
ad CenterSign inProductsCategoriesSecuritySupport
Windows Automated Installation Kit for Windows 7 documentation (May 2010 Update)
Overview
The Windows Automated Installation Kit (Windows AIK) is a set of tools and documentation that support the configuration and the deployment of Microsoft® Windows® operating systems. This guide describes the current methods, tools, and requirements for deploying Windows. This release includes updates to the Windows AIK documentation as of May 2010. Updates include many corrections that were previously documented in the readme file.Top of page
System requirements
Supported operating systems: Windows 7, Windows Server 2008, Windows Vista Service Pack 1Supported Operating Systems You can install the Windows AIK to the following operating systems: Windows® 7, Windows Server® 2008 R2, Windows Server® 2008, Windows Vista®, Windows Server® 2003.Top of page
Instructions
To download the Windows AIK documentation:1. Start the download by clicking the Download button on this page.2. Click Save to save the .zip file to your computer.3. Open the .zip file and drag the .chm and other files to a folder on your computer.4. Open the .chm file or .rtf file to ensure that you can open the files.If you experience problems opening the .chm file, use the following workaround.1. Right-click the .chm file, and then click Properties.2. Click Unblock.3. Double-click the .chm file to open the file.For more information, see the following Microsoft Knowledge-Base article: http://support.microsoft.com/kb/902225/Top of page
sysprep Overview
Applies To: Windows 8, Windows Server 2012The System Preparation (Sysprep) tool is used to change Windows® images from a generalized state to a specialized state, and then back to a generalized state. A generalized image can be deployed on any computer.
A specialized image is targeted to a specific computer. You must reseal, or generalize, a Windows image before you capture and deploy the image. For example, when you use the Sysprep tool to generalize an image, Sysprep removes all system-specific information and resets the computer. The next time that the computer restarts, your customers can add user-specific information through the Out-Of-Box Experience (OOBE) and accept the Microsoft® Software License Terms.
You can run Sysprep as either a command-line tool or a graphical user interface (GUI) tool.If you intend to create an image of an installation for deployment to a different computer, you must run the Sysprep command together with the /generalize option, even if the other computer has the same hardware configuration. The Sysprep /generalize command removes unique information from your Windows installation so that you can safely reuse that image on a different computer. For more information, see How to Capture an Image for Deployment (Generalize).In this topic:Common Sysprep Scenarios Benefits of Sysprep Sysprep Dependencies Unsupported Scenarios in Sysprep Sysprep Limitations Common Sysprep Scenarios
The Sysprep tool is typically used in the following scenarios:Create a reference imageIn this scenario, you create a single Windows reference image by installing Windows, customizing the image, and adding additional drivers and applications. You then capture the reference image and install it on computers that use the same hardware configuration.
Sysprep makes no additional modifications to this image.This scenario includes the following steps:Install Windows on a reference computer.After the installation is complete, boot the computer into Windows PE.
Customize the image by installing boot-critical drivers, optional components, and language packs.Install any additional device drivers or applications.After updating the Windows reference installation, run the Sysprep /oobe /generalize /shutdown command.
The /generalize option instructs Sysprep to remove system-specific data from the Windows installation, such as event logs and unique security IDs (SIDs). After Sysprep removes unique system information, the computer shuts down.NoteInclude the /oobe option in the Sysprep command, if you do not plan to use the reference image as the basis for a model-specific reference image.
The /oobe option instructs the Windows installation to run OOBE the next time that the computer boots.After the computer shuts down, reboot Windows PE.Capture the Windows installation by using the Dism /capture-imagecommand.
You now have a reference image that you can use to install Windows on computers that have the same hardware configuration, or use as the basis for a model-specific reference image.Create a model-specific reference imageIn this scenario, you start with a single reference image. After you install the reference image on a model-specific reference computer, you make additional updates that are unique to the computer that you are using. These could be customer-requested applications or other updates.
By booting to audit mode, you can install additional devices and applications that are specific to the computer model that will be shipped. You can repeat this process and create a new model-specific reference image for each additional line of computers that you are shipping.This scenario includes the following steps:Install the reference image on a computer representative of the model that is to be shipped to the customer.
After installation is complete, run the Sysprep /audit /generalize /shutdown command to configure Windows to boot the computer to audit mode.
You can then capture the Windows image by booting to another partition or by using Windows PE.This image becomes your model-specific reference image to install on computer models that share the same configuration.Install the model-specific reference image on a new computer. The Windows image is applied to the computer, and Windows boots to audit mode.(Optional) Install additional applications and other updates based on a customer's order.
You can also test the computer to verify that all components are working correctly.After you update the Windows installation, run the Sysprep /oobe /shutdown command.NoteIf you install Windows images by using the Sysprep /generalize /oobecommand, the user experience will not be ideal.
On the next reboot after you run the Sysprep /generalize /oobe command, Windows runs the specialize configuration pass, Plug and Play, and other Setup tasks before Windows starts OOBE.
This process can take additional time and can delay a customer's first logon.Package the computer and deliver it to the customer.The next time that the computer starts, OOBE runs.
Booting to Audit ModeAudit mode enables you to quickly customize a Windows installation. In audit mode, you can install applications, add device drivers, run scripts, and test the validity of a Windows installation. Audit mode does not require that you apply settings in OOBE.
Typically, Windows starts OOBE immediately after installation. However, by booting to audit mode, you can bypass OOBE and boot the computer immediately to the desktop. This enables you to start your customization process as quickly as possible.Audit mode enables you to verify that a computer is functional before you deliver the computer to a customer.
You can verify that the end user's first boot experience will run as expected and that any customizations and information about your company's support options is present. After you configure the Windows installation, you can prepare that computer for delivery to a customer by running the Sysprep /oobe command.
NOTE----
The /oobe option instructs Windows to run OOBE the next time that the computer boots. Windows processes any settings in the oobeSystem configuration pass in an answer file immediately before OOBE starts.For more information about audit mode, see the following topics:Audit Mode
How to Boot to Audit Mode or OOBEHow to Enable and Disable the Built-in Administrator AccountHow to Add a Driver Online in Audit ModeBenefits of SysprepSysprep provides the following benefits:Removes system-specific data from Windows.
Sysprep can remove all system-specific information from an installed Windows image. This includes the computer security identifier (SID). You can then capture the Windows installation and install that image throughout an organization.Configures Windows to boot to audit mode.
Audit mode is a built-in administrator account that enables you to install third-party applications and device drivers, and to test the integrity of the Windows image.
Configures Windows to boot to OOBE. Sysprep configures a Windows installation to boot to OOBE the next time that the computer starts. Typically, you configure a system to boot to OOBE immediately before you deliver the computer to a customer.
Sysprep DependenciesSysprep has the following dependencies:You must run Windows Setup before you use Sysprep.You need an imaging tool to capture an image of the installation.
Deployment Image Servicing and Management (DISM) image-capturing tool, third-party disk-imaging software, or disk-duplicating hardware devices are required for image-based setup. These products create binary images of a computer's hard disk. These products either duplicate the image to another hard disk or store the image in a file on a separate disk.
NoteWhen you copy Windows images between computers, the reference and destination computers may not have to have compatible hardware abstraction layers (HALs). The /detecthal option in the Boot Configuration Data (BCD) enables a system that has already run Sysprep to install the correct HAL.
Unsupported Scenarios in Sysprep
The following scenarios are not supported:Moving or copying a Windows image to a different computer without running the Sysprep /generalize command is not supported. You must prepare any method of moving a Windows image to a new computer by using the /generalize option together with the Sysprep command. These methods include imaging, hard disk duplication, and all other methods.Using a different version of the Sysprep tool to configure an image is not supported. You must use only the version of the Sysprep tool that is installed with the Windows image that you intend to configure. Sysprep is installed with every version of Windows.
You must always run Sysprep from the %WINDIR%\system32\sysprep directory.Using the Sysprep tool on upgrade installation types, or to reconfigure an existing installation of Windows that has already been deployed is not supported. Sysprep must be used only to configure new installations of Windows.
You can run Sysprep an unlimited number of times to build and configure your installation of Windows. Automating Sysprep by using a Microsoft-Windows-Deployment | RunSynchronous command in an auditUser configuration pass is not supported.
However, you can use the Microsoft-Windows-Deployment |generalize setting to automatically prepare the computer for imaging after installation. The Sysprep VM mode is new for Windows 8. Running VM mode outside a virtual machine (VM) is unsupported. You cannot use VM mode to prepare a VHD for deployment to any computer.Sysprep
Sysprep has the following limitations:The computer security identifier (SID) is only replaced on the operating system volume when you execute Sysprep. When Sysprep generalizes an image, Sysprep only generalizes the general partition.
Therefore, if a single computer has multiple operating systems, you must run Sysprep on each image individually.If you apply multiple partitions, you can use the BCDBoot tool to copy boot configuration data to the system partition. For more information, see BCDboot Command-Line Options.
In some cases, customized applications that you install before you recapture the Windows image may require a consistent drive letter. Some applications store paths that include the system's drive letter.
Uninstallation, servicing, and repair scenarios may not function correctly if the system's drive letter does not match the drive letter that the application specifies.The Plug and Play devices on the reference and destination computers do not have to be from the same manufacturer.
These devices include modems, sound cards, network adapters, and video cards. However, the installation must include the drivers for these devices.Not all server roles support Sysprep.
If you run the Sysprep /generalizecommand against a Windows Server® 2012 installation that has specific server roles configured, those server roles may not continue to function after the imaging and deployment process.
For more information, see Sysprep Support for Server Roles.
-------NOTE----
If you run Sysprep on an NTFS file system partition that contains encrypted files or folders, the data in those folders becomes completely unreadable and unrecoverable.
The Sysprep tool runs only if the computer is a member of a workgroup, not a domain.
If the computer is joined to a domain, Sysprep removes the computer from the domain.
If a computer is joined to a domain, and the Group Policy of that domain assigns a strong account password policy to the computer, all user accounts will require strong passwords.
Running Sysprep or OOBE does not remove the strong password policy.
WarningIf you do not assign a strong password to a user account before you run Sysprep or OOBE, you may not be able to log on to the computer. We recommend that you always use strong passwords for your user accounts.
See Also
Tasks
How to Capture an Image for Deployment (Generalize)
Reference
Sysprep Command-Line Options
Concepts
Work with Produ
Add a Driver Online in Audit Mode
1 out of 1 rated this helpful - Rate this topicPublished: February 29, 2012Updated: May 31, 2012Applies To: Windows 8, Windows Server 2008 R2, Windows Server 2012You can use an answer file to automate the installation of device drivers when the computer is booted in audit mode.Adding a Device DriverThe auditSystem configuration pass processes unattended Setup settings while Windows® is running in system context, before a user logs on to the computer in audit mode. The auditSystem configuration pass runs only if the computer is booted in audit mode. To add device drivers during the auditSystem configuration pass, add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the auditSystem configuration pass, and specify the path for each device driver. After you run Setup, boot Windows in audit mode. You can run the Sysprep command with the /audit option to configure the computer to start in audit mode the next time that it boots. Or, in the answer file, you can configure the Microsoft-Windows-Deployment\Reseal\Mode setting to audit. For more information, see Unattended Windows Setup Reference Guide.To add a device driver during the auditSystem configuration passLocate the .inf files that you want to install during audit mode for the device driver.On your technician computer, open Windows System Image Manager (Windows SIM). Click Start, type Windows System Image Manager, and then select Windows System Image Manager.Open your answer file and expand the Components node to display available settings.Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the auditSystem configuration pass.Expand the Microsoft-Windows-PnpCustomizationsNonWinPE node in the answer file. Right-click DevicePaths, and then click Insert New PathAndCredentials.A new PathAndCredentials list item appears.For each location that you access, add a separate PathAndCredentialslist item.In the Microsoft-Windows-PnpCustomizationsNonWinPE component, specify the path of the device driver and the credentials that are used to access the file if the file is on a network share.NoteYou can include multiple device-driver paths by adding multiple PathAndCredentials list items. If you add multiple list items, you must increment the value of Key for each path. For example, if you add two separate driver paths, the first path uses the Key value of 1, and the second path uses the Key value of 2.Save the answer file and close Windows SIM. The answer file must resemble this example:<?xml version="1.0" encoding="utf-8" ?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="auditSystem"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:keyValue="1" wcm:action="add"> <Credentials> <Domain>Fabrikam</Domain> <Password>MyPassword</Password> <Username>MyUserName</Username> </Credentials> <Path>\\networkshare\share\drivers</Path> </PathAndCredentials> </DriverPaths> </component> </settings> </unattend>
Boot in Windows® Preinstallation Environment (Windows PE), run Windows Setup, and specify the name of the answer file. For example:Setup /unattend:C:\unattend.xml The specified answer file is cached to the system so that when you run audit mode, the computer applies settings in the answer file.Setup finishes.Run the Sysprep command with the /audit option to configure the computer to start in audit mode the next time that it boots. For example:Sysprep /audit /reboot When Windows reboots in audit mode, device drivers that you specified in the answer file are added.You can use the PNPUtil tool to add, remove, and enumerate drivers on a running operating system. For more information about how to use PNPUtil to add or remove Plug and Play drivers, see Install a Plug and Play Device.
See Also
Tasks
How to Add Device Drivers by Using Windows Setup How to Add and Remove Drivers Offline How to Boot to Audit Mode or OOBE
Reference
Driver Servicing Command-Line Options
Concepts
Device Drivers and Deployment Overview Audit Mode Overview http://technet.microsoft.com/en-us/library/hh825685.aspx
1
2
3
No comments:
Post a Comment