Just so happned I was reviewing Ch5 in our upcoming Microsoft Windows Server 2008 R2 Remote Desktop Services Resource Kit. Chapter 5 is our profiles chapter so the timing was perfect to post this answer:
Short story is, Copy To on a user profile has never actually been supported. For many reasons. Because of this, In 2008 R2 Microsoft did away with the functionality.
Copying a user profile over another could lead to problems if the copied profile had been used at all, because the profile being copied would be “tattooed” with inappropriate settings and naming, such as the following:
• A list of that user’s frequently run programs.
• The user’s documents folders will be incorrectly called Administrator’s Documents.
• The user may have access to Administrative Tools (this is incorrect for regular users).
• Windows 7 libraries will be broken.
Now the only profile you can copy is the default profile, which is not tatooed.
If you must make a customized mandatory profile, then you have to overwrite the default profile with another profile by running sysprep with an answer file that tells it to overwrite the default profile with the profile of the user that is logged in that runs sysprep. This is described here:http://support.microsoft.com/kb/973289
Here are the steps:
1. Log on as an administrator and customize the profile as needed. This is the profile that will be copied over the default user profile.
2. Create an Unattend.xml file and add a line of code to it to tell it to copy the profile of the user logged on over the default profile when the system reboots. The line you add is
The unattend file should look like this for 64 bit:
3. Save this Unattend.xml file to : C:/Windows/System32/Sysprep.
4. Once you have the Unattend.xml file in place, open a command prompt and type the following command:
sysprep.exe /oobe /reboot /generalize /unattend:unattend.xml
This will copy the user profile over the default user profile, with which you can then use the Copy To button.
But be warned, sysprepping a production machine will do things like:
• The sysprep command resets the computer SID as well as eliminating system-specific data like the computer name and the domain affiliation.
• It can also remove unique hardware drivers and can reset the Windows activation key.
If you are using VMs, then one workaround is to take a snapshot of the VM before sysprepping. After you are done running sysprep, rebooting, and copying the default profile to another location, apply the snapshot and the VM will be rolled back to its prior state.
People are circumventing this and posting their workarounds, such as using windows enabler to turn on the Copy To button and doing things the old way, but again this is unsupported.
You can also stand up a 2008 VM and then get a profile using the win2k8 server. Again, not supported.
Really the best way to do this is to NOT customize the mandatory profile but use the default profile as it is, and layer in your changes via GPO and GPP and scripting. That way you never have to deal with a customized mandatory profile.
More reading for you: http://blogs.technet.com/b/deploymentguys/archive/2009/10/29/configuring-default-user-settings-full-update-for-windows-7-and-windows-server-2008-r2.aspx