Join over , other people just like you! Forums New posts Search forums. What's new New posts Unanswered threads Latest activity. Members Current visitors. Log in Sign up. Search titles only. Search Advanced search…. New posts. Search forums. Log in. Change the size or format of the system partition before you perform an unattended installation. Use Dynamic Update to download updated installation files and device drivers with your unattended installation.
User data includes such things as documents, e-mail messages, spreadsheets, and databases. User settings, such as desktop settings, shortcuts, and Internet Explorer Favorites. Application settings such as application-specific keyboard shortcuts, spell-checking options, and default file locations. Identify the data you want to migrate, including user data, user settings, and application settings. Describe how to collect and restore the data. Determine where to store the data while you perform the unattended installation.
Create a schedule for migrating the data on each of your destination computers. At a minimum, your user state migration plan must do the following: u u u u Microsoft provides two tools for migrating user data and settings. The tool you use depends on your environment: u Files and Settings Transfer Wizard. Designed for home users and small office users, the wizard is also useful in a corporate network environment for employees who get a new computer and need to migrate their own files and settings without the support of an IT department or Helpdesk.
User State Migration Tool. Designed for IT administrators who perform large deployments of Windows XP Professional in a corporate environment, the User State Migration Tool provides the same functionality as the wizard, but on a large scale targeted at migrating multiple users. The User State Migration Tool gives administrators command-line precision for customizing specific settings, such as unique modifications to the registry. Repartition and reformat the system partition on your destination computers, and you are not using an operating system CD to start your destination computers.
Create and format extra partitions on your destination computers. You want to extend the system partition, create and format extra partitions during or after the installation, or convert an existing system partition to NTFS. These tasks do not require substantial analysis and planning, and are relatively easy to perform by configuring answer file settings or running commands or scripts from the answer file.
You are using an operating system CD to perform an unattended installation, and you want to repartition and format the system partition on destination computers. In this case, you can use the Repartition entry in the [Unattended] section of the unattended installation answer file to repartition and format the system partition before the unattended installation begins. You do not need to create a disk configuration plan in the following situations: u Configuring Disk Settings Begin your disk configuration plan by choosing the tool that most suits your needs: MS-DOS or Windows 98 disk configuration tools You can start a destination computer by using an MS-DOS or a Windows 98 boot disk, and then use the fdisk and format commands to partition and format the hard disk before you perform an unattended installation.
If you want your hard disks formatted with NTFS, you will have to use the convert command to convert the FAT or FAT32 file system to NTFS after you have installed the operating system onto the destination computer, or you will have to use the oformat command. Designing Preinstallation Tasks for Unattended Installations 49 Third-party disk configuration tools Some third-party disk management programs provide a bootable floppy disk or CD that allows you to partition and format hard disks.
If you use a third-party program to partition or format a disk, be sure that the third-party program creates partitions that are compatible with NTFS 3. Windows PE is a bootable operating system that provides limited operating system functionality for performing preinstallation tasks. Windows PE is available only if you have purchased Enterprise Agreement 6.
Each method of configuring disk settings has advantages and disadvantages. You need to determine which method is better suited to your organization and your deployment needs.
Components of a Disk Configuration Plan After you determine which method to use to configure disk settings, you need to create your disk configuration plan. At a minimum, your disk configuration plan must identify: u Disk configuration settings. Disk configuration settings include the number of partitions, partition sizes, and file system formats for the destination computer.
Disk configuration settings are based on several factors, including disk sizes, disk types, backup capabilities, and user needs. Analyze these factors in your disk configuration plan to determine the right disk configuration for your organization. Procedures for configuring disk settings. Your disk configuration plan must describe every step of the disk configuration process, including how to start a destination computer and how to run the partitioning or formatting tools.
Tools that you use to configure disk settings. Disk configuration tools include the format, fdisk, and diskpart commands. Your disk configuration plan must describe all the tools you will use to configure disk settings, including the tools you will use to start a destination computer and to partition, format, and check a disk.
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: u Updated installation files. This can include system files, in-box device drivers, Setup information. 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 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. For example, you can use Dynamic Update if your destination computer is running Windows and it is connected to your network when you run Windows Setup.
In addition, you can use Dynamic Update only with Winnt In addition, if you are upgrading a computer that is running Windows 95 with Internet Explorer 4. Delivering Dynamic Update files to destination computers 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. Designing Preinstallation Tasks for Unattended Installations 51 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. Preparing to use Dynamic Update To use Dynamic Update, you need to determine the following: u u u Which files to deliver to your destination computers.
How to prepare the files for delivery. How to configure answer files settings or Winnt Identifying and Downloading Dynamic Update Files You need to download two types of files to prepare for Dynamic Update: Dynamic Update packages, which contain updated installation files; and device driver.
Device driver files must be downloaded individually; they are not assembled in packages. 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. 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.
Perform the following tasks to prepare Dynamic Update files. This creates separate folders for each operating system. Each folder can contain one or more of the following files: Winnt Delete the folders for any operating systems that you are not installing. For example, copy the. This prepares each folder for Dynamic Update. During the preparation process, Winnt Configure a Shared Folder for Dynamic Update files 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. Copy the prepared Dynamic Update Files to the shared folder After you create the shared folder on a server, copy each of the prepared Dynamic Update folders to it. 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 enabled by default when you perform an unattended upgrade installation by running Winnt By default, this entry is set to Yes, which means Dynamic Update is disabled. In addition, you need to specify the location of the shared folder that contains the prepared Dynamic Update files.
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. For more information about answer file settings and Winnt Designing Answer File and Setup Settings for Unattended Installations By creating an answer file and by using Setup command line parameters, you can automate the following tasks that occur during and after an unattended installation: u Software installation and configuration. You can automatically install and configure client and server applications. You also can install and configure Windows components, services, and applications.
Hardware installation and configuration. You can automatically update device drivers and configure device settings. Computer configuration. You can automatically configure computer settings, such as domain membership, computer name, network protocols, display settings, and system services. You also can configure server roles, such as installing Active Directory. By automating installation and post-installation tasks, you can: u u u u Reduce the number of errors caused by technicians, administrators, and end users during your deployment.
Ensure consistency throughout your organization, which reduces support costs after deployment. Increase productivity by requiring little or no end-user interaction during your deployment. Update or modify your installation process without having to educate or retrain end users, technicians, or administrators.
In addition, you need to choose which command line parameters to use when you start the Setup program. However, if you start a destination computer from an operating system CD and the answer file is on a floppy disk, you must name the answer file Winnt. Setup will then detect the answer file on the disk without user input. The answer file supplies Setup with answers to all the questions that you are asked during a standard, interactive installation. The answer file also contains information about your installation and configuration requirements.
In addition, an answer file tells Setup how to interact with the distribution shares and files that you have created or the installation files on the operating system CD, if that is what you are using to install the product.
An answer file contains multiple sections — some mandatory and some optional — that you can modify. Section names are delineated by brackets for example, [Unattended]. Every section has one or more entries that contain installation and configuration information. The entry name represents a specific computer setting or action; the value represents the unique way you want the setting configured or the action performed.
Setup parameters are specified at the command line when you run Winnt. Some installation and configuration tasks can be performed by configuring either Setup parameters or answer file settings. For example, you can implement Dynamic Update by configuring answer file settings or by configuring Setup parameters when you run Winnt In both cases, the functionality is the same. The settings you need to configure for the answer file.
Installation tasks are usually described in your component design or your client and server configuration design. For example, your network topology should provide information about the network protocol settings you need to configure during an installation. Likewise, your file server design should provide information about the disk settings you need to configure during an installation. Answer file settings correspond to the installation tasks you need to perform.
For example, if one of your installation tasks involves configuring network adapter settings, you need to identify the answer file sections and entries that configure network adapter settings, and then determine the proper values to assign to the answer file entries. Try to automate as many installation tasks as possible with the answer file. This includes partitioning and formatting hard disks prior to setup, and configuring Setup options that are usually configured by end users during GUI mode and text mode stage of Setup.
This also includes configuring upgrade options, uninstall options, and other settings that affect the way Setup runs. This includes configuring power management, telephony, and display settings, and regional options.
This also includes configuring error reporting, Windows file protection, remote assistance, system restore, licensing, and shell settings. This includes configuring Internet Explorer options, such as favorites, proxy server settings, branding, and default Home and Search pages.
This also includes installation and configuration of protocols, network adapters, and networking services and components. This also includes installing and configuring a domain controller by using Active Directory. This includes all Windows components listed in Add or Remove Programs in Control Panel, such as accessories, games, media services, and Indexing Service. This includes Windows Installer.
Software installation must run in quiet mode, which means the installation must be fully automated and cannot rely on user interaction. Usually, when you run an installation program in quiet mode, you must provide an answer file. Programs, scripts, and batch files must be fully automated and cannot rely on user interaction, which means you must provide an answer file for any programs, scripts, or batch files you are running, and you must be able to run the programs, scripts, or batch files in quiet mode.
For more information about answer file settings related to Internet Explorer Enhanced Security Configuration, see the Readme. If you do not provide values for these entries in your answer file, Setup will prompt the end user or whoever is performing the unattended installation for the values: [GuiUnattended] You must specify values for AdminPassword and TimeZone.
Using a password that begins with an asterisk can cause the password to be set to a null value. Designing Answer File and Setup Settings for Unattended Installations 63 Designing Automated Post-Installation Tasks Post-installation tasks include any installation and configuration tasks that need to be performed after the operating system is installed. Post-installation tasks are usually described in your component design or your client and server configuration design.
You usually perform these tasks by running a command, program, script, or batch file after Setup is finished running. For example, your client networking design might include information about network settings that need to be configured with the Netset.
Likewise, your client configuration design might include information about mapped network drive settings that need to be configured with the net use command or printers that need to be installed with the Rundll You can automate these types of tasks after the operating system is installed by using a Cmdlines. Both methods allow you to run commands, programs, scripts, and batch files. To design automated post-installation tasks for an unattended installation, you must: u u Identify the tasks you want to perform after the operating system is installed.
Design a method for automating the tasks you want to perform. Identifying Automated Post-Installation Tasks You can use an answer file to automate only a limited number of installation and configuration tasks during installation.
Many installation and configuration tasks must be performed after the operating system is installed and configured. Testing your unattended installations is the best way to determine whether an installation or configuration task must be performed after the operating system is installed. However, the following installation and configuration tasks always must be performed after the operating system is installed: u Tasks that cannot be performed by setting an answer file entry.
You cannot add any other sections or entries to an answer file that is used to perform an unattended installation. Tasks that rely on Active Directory directory service. For example, if a software installation program registers information in Active Directory or requires information from Active Directory, you must run the installation program after the operating system is installed and the computer is joined to a domain.
Tasks that can be performed only while a user is logged on. For example, some software installation programs create shortcuts on the Start menu and the desktop. If you want these shortcuts applied to a specific user profile, then you need to run the installation program after the operating system is installed and the user is logged on. Likewise, if you install Microsoft Word after you install the operating system, you need to create a Setup. Choosing a Method for Automating Post-Installation Tasks You can perform automated post-installation tasks two ways: you can use a Cmdlines.
Use the following guidelines to determine which method to use. Using Cmdlines. You want to install applications or perform configuration tasks during GUI mode stage of Setup. You want to install applications or perform configuration tasks under the Local System security account. You do not need network connectivity to perform the installation or configuration task.
You are not using Windows Installer packages. You want to install applications or perform configuration tasks while no user is logged on. You want to install applications or perform configuration tasks under a specific user account. You need network connectivity to perform an installation or configuration task.
You need to control the order in which programs, scripts, or batch files run. Important You cannot use Cmdlines. You can use Cmdlines. For information about configuring Cmdlines. Configuring Cmdlines. You can configure Cmdlines. The commands, programs, scripts, and batch files run synchronously; for example, a command waits for the previous command to finish running before it starts.
This means that you can control the order in which commands, programs, scripts, and batch files run. By default, Cmdlines. The syntax for Cmdlines. Note that all commands must be enclosed in quotation marks. Also, if you are using the command line Cmd.
Copy all of the programs, scripts, and batch files that are listed in your Cmdlines. For a worksheet to assist you in recording the commands, programs, scripts, and batch files that you want to run by using Cmdlines.
Configuring [GuiRunOnce] to Perform Tasks The [GuiRunOnce] section of an answer file contains a list of commands, programs, scripts, or batch files that run the first time a user logs on to the computer after the operating system is installed. You can configure [GuiRunOnce] to run multiple commands, programs, scripts, or batch files.
The commands, programs, scripts, and batch files run synchronously, which means each command, program, script, or batch file runs to completion before the next one starts running.
This lets you control the order in which tasks are performed. If you use the [GuiRunOnce] section to install software, you need to adhere to the following guidelines: You cannot run installation programs that require a restart You can automate installation tasks only if you can prevent the installation program from restarting the computer. When a computer restarts, all remaining entries in the [GuiRunOnce] section are lost.
If the system restarts before completing entries listed in the [GuiRunOnce] section, the remaining items will not run. Therefore, you need to suppress restarts. If you cannot suppress a restart within the installation program, you can try to repackage the application into a Windows Installer package. You cannot run installation programs that rely on the Windows Explorer shell The Windows Explorer shell is not loaded when the operating system starts running commands, programs, scripts, or batch files that are listed in the [GuiRunOnce] section of an answer file.
In some cases, you can get an updated installer program from the application vendor that does not rely on the Windows Explorer shell. If you cannot, you might be able to repackage the application as a Windows Installer package.
In some cases, when you are installing multiple applications, this can inadvertently cause the next installation program listed in the [GuiRunOnce] section to start before the previous installation program is finished running. When this occurs, the second installation program usually fails. This forces each installation program to run to completion before the next command listed in [GuiRunOnce] runs.
You can run Winnt. You can run Winnt Choosing Winnt. The default is the current folder. Because it guarantees cost savings, fast deployment, scalability, performance, security and fast recoverability. Think "mainframe," but updated, pretty, shiny, and effective! Server based computing is the mainframe with a vengeance. Terminal Server and Citrix MetaFrame offer the advantages of the old mainframe coupled with the benefits, gadgets, and appeal of the personal computer.
Manage applications from a central location and access them from anywhere Build scalable, flexible, and secure access solutions that reduce computing costs and increase the utility of your network The first book that covers Citrix MetaFrame Presentation Server 3.
Includes a tear-out "Cram Sheet" for last-minute test preparation, two complete practice exams and answer keys with key explanations, and the PrepLogic test engine to simulate the testing environment. Author : Brian S. You have not selected any file s to download. A download manager is recommended for downloading multiple files.
Would you like to install the Microsoft Download Manager? Generally, a download manager enables downloading of large files or multiples files in one session. Many web browsers, such as Internet Explorer 9, include a download manager.
Stand-alone download managers also are available, including the Microsoft Download Manager. The Microsoft Download Manager solves these potential problems. It gives you the ability to download multiple files at one time and download large files quickly and reliably.
It also allows you to suspend active downloads and resume downloads that have failed. Microsoft Download Manager is free and available for download now.
0コメント