How to customize the default local user profile when you prepare an image of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2
This article discusses how to customize the default local user profile settings when you create an image on a computer that is running one of the following operating systems:
- Windows Vista
- Windows 7
- Windows Server 2008
- Windows Server 2008 R2
Note: If you are having issues logging on to a user profile, click the following links to view the article on the Microsoft website:
After you deploy the image, these settings are applied to all new users who log on to the computer.
Note: This article supersedes all previously published procedures for customizing default local user profiles when you prepare images.
For more information about the steps to customize the default local user profile when you prepare an image for Windows XP and Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
959753 How to customize the default local user profile when you prepare an image of Windows XP or Windows Server 2003
To customize a default user profile or a mandatory user profile, you must first customize the default user profile. Then, the default user profile can be copied to the appropriate shared folder to make that user profile either the default user profile or a mandatory user profile.
When the default user profile is customized in the manner that is described in this article, it reconstructs the source profile in a format that is appropriate for use by multiple users. This is the only supported method of customizing the default user profile for the Windows operating system. If you try to use other methods to customize the default user profile, it may result in extraneous information being included in this new default user profile. Such extraneous information could lead to serious problems with applications and system stability.
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB973289.