ALTE DOCUMENTE
|
|||||||||
You can use Dynamic Update to update installation files and
device drivers that are used by Setup during an unattended installation.
Dynamic Update does not replace Windows Update;
it downloads only a small subset of Windows Update files and device driver
files that prevent critical errors from occurring during the setup process. The
files that Dynamic Update
downloads include:
Updated installation files. This can include system files, in-box device drivers, Setup information (.inf) files required during upgrades, DLL files used by the Winnt32.exe Setup program, and file assemblies (.asm files). Dynamic Update downloads only replacements for existing installation files. It does not add new installation files to the setup process.
New device drivers. This can include new device drivers that are critical to the setup 19219c221t process and are not on the operating system CD. New device driver files are not replacements for in-box device drivers. Replacements for in-box device drivers are considered updated installation files.
You can use Dynamic Update only if you are installing on
destination computers that have an existing connection to your network or the
Internet. For example, you can use Dynamic Update
if your destination computer is running Windows 2000 and it is connected to
your network when you run Windows Setup. In addition, you can use Dynamic
Update only with Winnt32.exe; you cannot use Dynamic Update with Winnt.exe. By
default, Dynamic Update is disabled during an unattended installation of
Windows Server 2003 and Windows XP Professional.
In addition, if you are upgrading a computer that is running Windows 95 with Internet Explorer 4.01, you need to upgrade to Internet Explorer 5.0 or a higher version of Internet Explorer. The version of Secure Sockets Layer (SSL) in Internet Explorer 4.01 is not compatible with Dynamic Update, and will cause Dynamic Update to fail.
You can deliver Dynamic Update files to destination computers two ways: you can download Dynamic Update files across the Internet from the Windows Update Web site, or you can download Dynamic Update files across your corporate network from a shared folder that you create on a server in your organization. The latter method is better suited for large-scale corporate deployments because it ensures consistency among your destination computers.
When you download Dynamic Update files from a server in your organization, you can guarantee that the same set of Dynamic Update files are downloaded onto each of your destination computers because you have full control of the Dynamic Update files that are on the server. When you download Dynamic Update files across the Internet from the Windows Update Web site, you might introduce inconsistencies among your destination computers because the Windows Update Web site is periodically updated, and you cannot control when this occurs. In addition, downloading Dynamic Update files from a server in your organization eliminates many security issues that can arise when destination computers are connected to the Internet.
|
|
|
Note This book assumes you are delivering Dynamic Update files across your corporate network from a server in your organization. This book does not describe how to configure an unattended installation so that Dynamic Update files are delivered across the Internet. |
To use Dynamic Update, you need to determine the following:
Which files to deliver to your destination computers.
How to prepare the files for delivery.
How to configure answer files settings or Winnt32.exe settings.
For a worksheet to help you record information about your Dynamic Update design, see "Dynamic Update Worksheet" (ACIUI_4.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Dynamic Update Worksheet" on the Web at https://www.microsoft.com/reskit).
You need to download two types of files to prepare for Dynamic Update: Dynamic Update packages, which contain updated installation files; and device driver .cab files, which contain new device driver files that are not present on the operating system CD. Device driver files must be downloaded individually; they are not assembled in packages.
You can download Dynamic Update packages from the Microsoft Download Center. To do this, go to the Microsoft Download Center, specify the operating system that you are deploying, and then search for the keywords "dynamic update." Download the most current Dynamic Update package (the Dynamic Update package with the highest version number). To use the Microsoft Download Center, see the Microsoft Download Center link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources.
For information about downloading the most recent Dynamic
Update package for
Windows XP Professional, see article Q311220, "Description
of the Dynamic Update
Feature in Windows XP Setup," in the Microsoft
Knowledge Base. To find this article,
see the Microsoft Knowledge Base link on the Web Resources page at
https://www.microsoft.com/windows/reskits/webresources. For information about
downloading the most recent Dynamic Update package for Windows
Server 2003, search the Microsoft Knowledge Base using the keywords "dynamic update."
You can download new device driver .cab files from the
Windows Update corporate Web site. Before you do this, you need to identify all
of the devices on your destination computers for which there are no device
drivers on the operating system CD. To identify these devices,
use an operating system CD to manually install the operating systems you are
deploying on a representative sampling of your destination computers. You can
then use Device Manager to check the device status for each device. Devices
that do not have device drivers are denoted with a yellow question mark and a
yellow exclamation mark in Device Manager. To download device driver .cab
files, see the Windows Update link on the Web Resources page at
https://www.microsoft.com/windows/reskits/webresources.
|
|
|
Important Use Dynamic Update to install missing device drivers only for devices that are critical for Setup, such as hard disk controllers, mice, display adapters, and keyboards. Do not use Dynamic Update to install missing device drivers for peripheral devices, such as scanners, cameras, and printers. To install missing device drivers for peripheral devices, or devices that are not critical for Setup, use the OemPnPDriversPath entry in the [Unattended] section of your answer file. |
After you download the Dynamic Update packages and the device driver .cab files, you need to prepare these files for delivery to your destination computers. Perform the following tasks to prepare Dynamic Update files.
Run the executable Dynamic Update package to extract the
Dynamic Update files. This creates separate folders for each operating system.
For example, if you run the executable Dynamic Update package for
Windows XP, this creates two folders: a Windows XP Professional
folder named IP, and a Windows XP Home Edition folder named IC. If you run
the executable Dynamic Update package for Windows Server 2003, this
creates three folders in your new folder: a Windows Server 2003, Standard
Edition folder named Standard; a Windows Server 2003, Enterprise Edition
folder named
Copy the .cab files for each operating system, and each of the new device driver .cab files for each operating system, to a new folder. For example, copy the .cab files in the IP folder to a folder named DU_XPPro, and copy any new device driver files you downloaded for Windows XP Professional to the DU_XPPro folder.
Run Winnt32.exe with the /duprepare parameter on each of the new folders. This prepares each folder for Dynamic Update. During the preparation process, Winnt32.exe creates one or more of the following subfolders: Duasms, Dudrvs, Updates, Upginfs, and Winnt32. Winnt32.exe also copies the contents of the .cab files to one or more of these subfolders.
For more information about preparing files for Dynamic Update, see article Q312110, "How to Deploy the Windows XP Dynamic Update Package," in the Microsoft Knowledge Base. To find this article, see the Microsoft Knowledge Base link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources.
To distribute Dynamic Update files across your corporate network, you need to create a shared folder on a server. The shared folder must be available to all of your destination computers. For example, do not create the shared folder on a server that is in a restricted subnet. Typically, you create the shared folder on the same server that contains your distribution shares.
In addition, you need to assign permissions to the shared
folder. If you create the shared folder on the same server that contains your
distribution shares, the shared folder should have the same permissions as your
distribution shares. Permissions ensure that only authorized users can access
the shared folder. If the shared folder is not secure, a malicious user could
tamper with the Dynamic Update files. For example, a malicious user could
replace the .cab files in the shared folder with .cab files that contain a
virus. For more information about permissions, see "Best
practices for permissions and user rights" in Help
and
After you create the shared folder on a server, copy each of the prepared Dynamic Update folders to it. The "Dynamic Update Worksheet" (ACIUI_4.doc) shows the structure of the shared folder, and provides spaces for you to record the names of the folders containing your Dynamic Update files. See "Dynamic Update Worksheet" (ACIUI_4.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Dynamic Update Worksheet" on the Web at https://www.microsoft.com/reskit).You will need the names of these folders to design your answer file settings and Setup program settings later in this chapter.
Dynamic Update is disabled by default when you perform an unattended installation with an answer file. Dynamic Update is enabled by default when you perform an unattended upgrade installation by running Winnt32.exe /unattend.
To use Dynamic Update during an unattended installation with an answer file, you need to add the following entry to the [Unattended] section of your answer file:
DUDisable=No
This entry tells Setup to enable Dynamic Update. By default, this entry is set to Yes, which means Dynamic Update is disabled.
|
|
|
Important Do not use the /dudisable parameter with Winnt32.exe if you enable Dynamic Update in your answer file. The /dudisable parameter takes precedence over the DUDisable entry in your answer file: that is, using the /dudisable parameter disables Dynamic Update regardless of how you configure your answer file. |
In addition, you need to specify the location of the shared folder that contains the prepared Dynamic Update files. You can do this by creating the following entry in the [Unattended] section of your answer file:
DUShare = path_to_prepared_dynamic_update_files
You can also do this by using the following command-line parameter with Winnt32.exe:
/DUShare:path_to_prepared_dynamic_update_files
In both cases, path_to_prepared_dynamic_update_files is the path to the folder containing the Dynamic Update files that you downloaded, prepared, and saved on a secure shared folder in your organization. This path is different for each operating system you are installing.
In addition, when you perform an unattended installation, you can change the way Setup responds to Dynamic Update errors by using the DuStopOnError parameter in the [Unattended] section of your answer file. Dynamic Update errors include any failure to process Dynamic Update files, or the inability to connect to Windows Update. By default, the Dynamic Update process stops when an error is detected. You can change this by adding the following entry to your answer file:
DuStopOnError=No
For a worksheet to help you record answer file information, see "Answer File Settings Worksheet" (ACIUI_5.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Answer File Settings Worksheet" on the Web at https://www.microsoft.com/reskit). For more information about answer file settings and Winnt32.exe parameters, see Microsoft Windows Corporate Deployment Tools User's Guide (Deploy.chm). Deploy.chm is included in the Deploy.cab file in the Support folder on the Windows Server 2003 operating system CD.
|
