How to customize the default local user profile when you prepare an image of Windows XP or Windows Server 2003

 

How to customize the default local user profile in Windows XP or in Windows Server 2003

In Windows XP and in Windows Server 2003, updates that you have installed may change the method that you use to customize the default local user profile. For more information, see the following sections.

Windows XP Service Pack 2 (SP2)

The default behavior is to automatically copy customizations from the administrator profile to the default user profile. Therefore, no additional steps are required to customize the profile.

Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 SP2

The default behavior is to automatically copy customizations from the administrator profile to the default user profile. Therefore, no additional steps are required to customize the profile. You can disable this functionality by setting a parameter in the Sysprep.inf file. This parameter prevents the Minisetup process from copying customizations from the administrator profile. To do this, set the parameter in the "UNATTENDED" section of the Sysprep.inf file as follows:

[UNATTENDED]
UpdateServerProfileDirectory=0 

Windows XP Service Pack 3 (SP3) or hofix 887816 is applied

Hotfix 887816 disables the automatic copying of customizations. Therefore, you must configure a parameter in the Sysprep.inf file to enable the Minisetup process to copy the customizations from the administrator profile. To do this, set the parameter in the "UNATTENDED" section, as follows:

[UNATTENDED]
UpdateServerProfileDirectory=1 

Note Windows XP SP3 includes hotfix 887816.

Windows XP or Windows Server 2003

To use this CopyProfile setting in Windows XP SP2 together with hotfix 887816, in Windows XP SP3, or in Windows Server 2003 SP1, the UpdateServerProfileDirectory setting must be present in the Sysprep.inf file when you run the Sysprep tool. Therefore, when you use automated image build and deployment tools, such as the Microsoft Deployment Toolkit or System Center Configuration Manager, the UpdateServerProfileDirectory setting must be included during the reference image build and capture process.

The procedure that is described in this article supersedes all previously published procedures for customizing default local user profiles when you prepare images. This behavior applies to the following operating systems:

• Windows Server 2003
• Windows XP

Previously published procedures relied on a file copy mechanism. These procedures caused information to be left behind in the default user profile that caused the Windows shell to behave incorrectly. This led to problems with application compatibility and with the user experience. Therefore, do not advise customers to copy profiles over the default user profile. This method is no longer supported.

How to configure the default network profile

Install the version of Windows for which you want to use the profile. Follow the procedures in this article to configure the local default user profile. Restart the computer after you run the Sysprep command. When the operating system finishes the Minisetup/Specialize process, log on as the local administrator. Use the newly configured local default user profile as the source for the default network profile.

How to configure default user settings for already deployed desktops

Implement the required new or changed settings as a logon script and configure it to run one time. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

284193 How to run a logon script one time when a new user logs on

You can automate the procedure in Knowledge Base article 284193 by using the Reg.exe command. For an alternative solution, see the “Targeted changes to the Default User Registry hive and profile folders” section on the following Microsoft website: