Evaluating Operating System and Software Settings

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

You do not usually need to create a separate disk image for each computer or group of computers that has different operating system settings or different software settings. You can configure most operating system and software settings on the master computer before you create the disk image. However, if you need to configure settings that are unique, you can automatically configure the settings during Mini-Setup while the destination computer is being set up, or after Mini-Setup is complete and the destination computer has been restarted.

Examples of operating system and software settings include:

  • Local policy settings, such as Group Policy Administrative Template settings.

  • Control Panel settings, such as power options, sound scheme settings, system startup and recovery options, system performance settings, and accessibility options.

  • Internet Explorer settings, such as the default home page, security and privacy settings, and connection settings.

  • Optional Windows components settings, such as network monitoring tools, Remote Storage, and Services for Macintosh.

  • Services settings, such as startup type, logon accounts, and recovery actions.

  • Desktop settings, such as desktop shortcuts and folder options.

  • Microsoft® Word or Microsoft® Excel settings, such as view, edit, save, and spelling options.

You can record operating system settings in each copy of the worksheet under "Operating System Installed on This Image" and under "Operating System Settings Configured After Disk Copy." Likewise, you can record software configuration settings in each worksheet under "Software Installed on This Image" and under "Software Installed After Disk Copy."

Most operating system settings and software settings can be configured on the master computer before you create the disk image. However, you must configure the following settings after the disk image is copied onto a destination computer.

Domain controller settings   You cannot configure a master computer as a domain controller. You first configure a master computer as a member server, and then configure it as a domain controller after the disk image is copied onto a destination computer. You use Dcpromo.exe (also known as the Install Active Directory Wizard) to configure a server as a domain controller.

Plug and Play hardware settings   You must configure settings for Plug and Play hardware after a disk image is copied onto a destination computer. For example, you cannot configure power management settings for a specific device, such as enabling wake-on-LAN settings for a network adapter, or configuring link speed or duplex settings for a network adapter. Sysprep configures the master computer so that Plug and Play devices are detected, installed, and reconfigured with default settings the first time you start a computer after a disk image is copied onto it.

Static IP address settings   You must configure static IP address settings after a disk image is copied onto a destination computer (by using Sysprep.inf). When a disk image is copied onto a destination computer, all of the network adapters on a destination computer are initialized to the default settings, which include dynamic allocation of IP addresses. For more information about how Sysprep affects network settings, see article Q271369, "Statically-Entered TCP/IP Settings Are Not Present After Sysprep," 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.

Encrypting File System settings   You must configure EFS settings on files and folders after a disk image is copied onto a destination computer. If you run Sysprep on a hard disk that contains encrypted files or folders, the data in those files and folders will become completely unreadable and unrecoverable.

Policy settings   You can configure local Group Policy Administrative Template settings on a master computer. This is because Administrative Template settings are stored in the registry, and Sysprep does not change this part of the registry. Any changes you make to Administrative Template settings will appear on the disk image. You can also configure other local Group Policy settings if the local Group Policy object is not linked to a site, domain, or organizational unit Group Policy object. This is because Sysprep does not change the local Group Policy object as long as local Group Policy settings are not overridden by site, domain, or organization unit Group Policy settings. If Group Policy settings are not overridden by site, domain, or organizational unit Group Policy settings, any changes you make to local Group Policy settings will appear on the disk image. If the local Group Policy settings are overridden by site, domain, or organizational unit Group Policy settings, and you configure these settings on a master computer, the settings will be overridden on each destination computer.

Mini-Setup settings   Several types of operating system settings are configured during Mini-Setup. Examples of these settings include: telephony settings, licensing information, computer name, administrative password, and domain membership settings. You cannot configure Mini-Setup settings on the master computer before you create the disk image. For more information about Mini-Setup settings, see "Designing Automated Setup Tasks" later in this chapter.