id=973289 However this process does have a drawback.It does not propagate all settings to Default User and there is no known documentation as to what will and will not be propagated.There are three main methods that have been used to configure the Default User profile.

It also can be difficult to determine if a setting did not carry over to a new user because it was considered inappropriate (i.e.

not copied to Default User by design) or is being reset by Minisetup/Specialize or first logon processes.

One final important point to remember is the difference in behavior between Windows XP/Windows Server 2003 and Windows Vista and higher with respect to when the answer file setting must be present for the automated profile copy to occur.

On Windows XP and Windows Server 2003, if you want to change the behavior of the automated profile copy, the Update Server Profile Directory entry must be present in when Sysprep is run.

To prevent this, Windows 7 and Windows Server 2008 R2 now block this scenario by having the Control Panel System applet gray out the option to overwrite the Default User profile.

At this time the only supported way to configure the the Default User profile using a copy of a configured profile is to use the next method described here, the automated profile copy associated with using Sysprep. id=887816), Minisetup was modified so that it will copy customizations from the local administrator account to the default user profile.

This is because the profile copy for Windows Vista and higher happens only during the Specialize phase.

So if you are using a deployment tool like Config Mgr or MDT that may modify/replace the Unattend.xml, make sure that Copy Profile is configured in the answer file used for deployment.

The traditional solution for this (developed during the Windows NT Workstation days) was to configure the Administrator account (or another designated account) with the settings, then copy the Administrator (or designated account) user profile over the Default User profile.