Whether you are re-using or replacing hardware, Vista computers should be set up with a standard Vista image. Deploying standard images is the fastest and most consistent way to migrate to a new operating system.
What you need
- A standard computer model to use as the source computer. The operating system on this computer is deleted then re-installed, so select a system without important data.
- Source installation CD. Windows Vista Business is used as an example in this article.
- Windows Volume License and corresponding license key.
- Any mass storage and plug-and-play drivers required by Vista computers that are not included in the Windows Vista installation.
- A working understanding of Sysprep and Altiris® Deployment Solution™ software.
Getting Ready to Image
Before imaging, there are a few things you need to do.
- Selecting Imaging Format
- Selecting Core Software
- Booting to Automation
Selecting Imaging Format
Vista introduces a new computer imaging format called a Windows Image File (WIM, also called imageX in reference to the Microsoft tool used to deploy these images).
While comparing the advantages and disadvantages of WIM versus traditional imaging formats is beyond the scope of this document, Deployment Solution supports deploying traditional and WIM images.
This guide uses Altiris® RapiDeploy® software to perform Vista imaging because of its native support of multicasting.
Selecting Core Software
While selecting core software can become a point of philosophy, there are evaluations you can make to see which core software might fit your environment better.
First, how many applications are common across your company? These core applications are good candidates for inclusion in your image.
Second, what are your internal change control process and the tools you have available for patching and software deployment? Is it easier to update your image on a regular basis, or is it easier to manage software separately and make fewer updates to your image?
If you have a rigorous change control process, you might not want to be responsible for keeping images up-to-date with the latest security patches.
Booting to Automation
To capture or deploy an image, computers must boot into a managed preboot operating system. We recommend using WinPE 2005 or the Linux environment provided with Deployment Solution.
This section walks you through creating a CD to boot computers to automation. This CD contains a pre-boot automation operating system and additional files required to contact your Deployment Server.
When you are ready to perform broad migrations, we suggest using PXE to perform zero-touch migrations. PXE and other boot methods are discussed in article 27534 “Deployment Solution 6.8 Preboot Automation Environment” on the Altiris Knowledgebase at https://kb.altiris.com/article.asp?article=27534&p=1.
If you plan on setting up your source computer using a scripted installation, create WinPE boot CD. Otherwise, you can use a Linux boot CD.
To create a WinPE boot CD, you need:
- WinPE 2005 CD
- Windows 2003 Server SP1 CD
To create a Linux boot CD, you need:
- BDCgpl*.frm (Available on the Deployment Solution download page on altiris.com.
Click the Linux and FreeDOS Automation Environment for Deployment Solution 6.8 SP1 link.)
In the Deployment Console:
- Click Tools > Boot Disk Creator.
- Click Tools > Install Pre-Boot Operating Systems.
- Click Install next to the version of WinPE or Linux automation you are installing (this example uses x86).
- Complete the prompts.
Create a Boot Configuration
In Boot Disk Creator:
- Click File > New Configuration.
- Provide a Configuration Name and Select WindowsPE or Linux.
- Complete the remaining prompts, accepting the default options.
- When the Create Boot Disk Wizard starts, select Create automation boot disk.
- Complete the remaining prompts, accepting the default options.
Burn the CD Image to Disk
Use CD writing software to burn the ISO CD image you created to a disk. By default, the image file is located in the Bootwiz/iso-imgs folder on the Deployment Share.
Capturing a Vista Image
This section walks you through capturing a Vista image. The basic imaging process is as follows:
- A source computer is configured with a clean installation of Windows Vista.
- Before capturing an image, Sysprep is executed on this computer to clear it of SIDs, hardware drivers, and other system-specific settings.
- When Sysprep completes, an image of this computer is captured. When this image is restored on another computer, Sysprep runs as if it is configuring this computer for the first time. Sysprep searches for plug-and-play drivers, generates SIDs, and performs other initial configuration tasks.
Capturing a Vista image is divided into the following steps:
| Step 1: Configure a Source Computer (page 4) | The source computer is used to capture the standard image you deploy across your organization. |
| Step 2: Patching and Optimizing the Source Computer (page 6) | The configuration settings and software on this computer are placed on each computer receiving this image. |
| Step 3: Gather and Prepare Device Drivers (page 7) | If you have hardware that isn’t supported by the base driver set in Vista, you need to gather and provide these drivers. |
| Step 4: Capture an Image From the Source Computer (page 7) | After capture, this image can be distributed to computers across your organization. |
Step 1: Configure a Source Computer
For previous versions of Windows, we recommended using a scripted installation to ensure the source computer is set up consistently in case it needs to be restored.
With Vista, a scripted installation is not required since answer files can be used with normal disk-based installations, and the WIM format ensures consistent setup.
Setting up a scripted installation through Deployment Solution can automate up the process, though it requires WinPE.
Selecting a Source Computer
The source computer should be a standard model with no unique or custom configurations. If your organization uses a set of standard hardware models, one if these is a good choice.
If you are using a scripted installation, this computer must have a 30 GB or larger hard drive.
Creating a Base Answer File
Microsoft provides a tool, called the Windows System Image Manager, to create unattend answer files. To download this tool, search microsoft.com for “WAIK” and download the Windows Automated Installation Kit.
The goal of an answer file is to implement a consistent, easily repeatable process for future efforts. Answer files can be created from scratch using the Windows System Image Manager, and an example tokenized answer file is included on the Deployment Share in the Samples folder.
Before using this sample unattend file, make the following changes:
- Manually replace the %PROCTYPE% token with the processor type of the computer you are deploying (for example, x86). This token must be replaced or the file does not validate.
- Add your volume license key to the <Key>Mention Product Key Here</Key> section.
- The default Administrator password is altiris. We recommend changing this to something unique.
- As an example, a new user is added in this unattend file. For most migrations, users are added when the personality is restored so this section can usually be removed.
Open this answer file in the Windows System Image Manager to make additional changes.
Building the Scripted Install Job
If you are not using a scripted installation, follow the instructions provided by Microsoft to perform a disk-based installation using an answer file.
In the Deployment Console:
- Create a new job and add a Scripted OS Install task.
- Select Windows, then on the following screen, select Windows Vista and the OS language.
- Click Next.
- Select the OS profile. If you have not performed a scripted install of the selected operating system, select add new and provide the path to the source files on the installation CD.
- Click Next.
- Leave the default partition and format options selected and click Next.
- Review the selected options then click Next.
- Browse to your unattend.xml file and then click Finish.
Assigning the Scripted Installation Job
- Insert the automation CD you created in Booting to Automation (page 2) into the CD drive of the source computer, and configure the BIOS to boot to CD.
- Restart the computer.
- When the computer restarts, the Deployment Agent enters wait mode:
- In the Deployment Console, the computer appears in the New Computers folder:
- Assign the Scripted Installation job to the computer using a drag-and-drop.
The scripted install can take some time, and you might notice the source computer performing several reboots. Wait for the status in the Deployment Console to indicate that the job is complete before you continue.
Step 2: Patching and Optimizing the Source Computer
If required, use a USB drive or CD to install the network adapter. This is the only additional driver we recommend installing.
When the computer has network connectivity, the Deployment Agent connects and appears in the Deployment Console. (If you performed a disk-based installation, the Deployment Agent can be installed manually by running dagent.msi located in the agents/aclient folder on your Deployment Share.)
Do not add this computer to your corporate domain. You can use Sysprep to add computers to your domain when they are deployed, but for initial creation leave the source computer off the domain.
Patch the Operating System
Patch the operating system to include the latest security fixes. Run Windows Update until no new critical patches are identified restarting as necessary.
Install Base Software
Install any software applications you want to include in your image.
Final Configuration
Make any final configurations or modifications to the operating system or installed applications. Some companies add a global administrator user account or apply other settings that need to be enabled system-wide.
After you have completed all changes, reboot the computer one additional time and make sure everything is installed correctly.
Step 3: Gather and Prepare Device Drivers
In this step, you gather required OEM drivers.
Vista is advertised as being hardware independent; this is true in the sense that all Vista installations use the same hardware abstraction layer (HAL), but you still need to provide the correct mass storage and plug-and-play drivers for each computer.
Any additional OEM drivers you wish to include in your standard image should be copied to a folder on your Deployment Share. Deployment Solution can include these drivers in your standard image.
Step 4: Capture an Image From the Source Computer
After you have prepared your source computer and gathered OEM drivers, the next step is capturing a sysprep-enabled image. The Sysprep files are included in Vista by default, so they do not need to be copied to each computer as with previous Windows versions.
Create the Image Capture Job
In the Deployment Console:
- Create a new Job and add a Create Disk Image task.
- Provide a name and location to store the image on your Deployment Share.
- Select Prepare using Sysprep, select the Windows Vista, and then provide a Product Key.
- Click Advanced and provide the path to the OEM drivers you collected in Step 3:
Gather and Prepare Device Drivers (page 7). If you want to include all of the drivers you installed on the source computer select Persist all PnP devices installed: - Click OK and then Finish.
Assign the Image Capture Job
- Configure the BIOS to boot from CD. Do not insert the automation CD at this time.
- Start the source computer normally and let Vista finish loading.
- Insert the automation CD you created in Booting to Automation (page 2) into the CD drive of the source computer.
- Assign the Image Capture Job to the source computer. Before rebooting, the bcdedit utility and Sysprep execute in Vista on the source computer to prepare the computer for imaging.
- The computer restarts automatically when Sysprep completes. When the computer restarts, automation loads and the image capture job is processed. This image is now ready to be deployed.
355
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
