[ruudboek]

I already have a working autounattend.xml available for Vista, which changes the profilesdirectory from C:\users to D:\users .
It does this by setting <ProfilesDirectory>D:\Users</ProfilesDirectory> during the oobeSystem pass.
I'm having a hard time to get this to work in windows 7.
Apparently the command "sysprep.exe /quiet /audit" to get into audit mode no longer works in windows 7.
I've found out that you now have to change the mode from OOBE to Audit in Microsoft-Windows-Deployment\Reseal, but i just don't know where to then put that Windows-Deployment\Reseal. Should it be in audit System or in audit User?

Basically what i want is this:

1. Change the profiles directory to D:\users.
2. Add a few registry settings to the default user, so that those registry will be valid for every newly created user.

If anyone has a working autounattend.xml that can do that, i would really appreciate it if they would be so kind to post it here.

[Sponsor]

[MrJinje]

From the unattend.chm

Quote

<FolderLocations>
<ProfilesDirectory>%SYSTEMDRIVE%\Profiles</ProfilesDirectory>
<ProgramData>%SYSTEMDRIVE%\ProgramData</ProgramData>
</FolderLocations>

There is the syntax. Doing so may bork you image slightly. Has big red warning at the top.

Quote

Caution:
This setting should be used only in a test environment. If you change the default location of the user-profile directories or program-data folders to a volume other than the system volume, you cannot service your image. Any updates, fixes, or service packs will not be applied to the installation.
For a list of known issues with this setting, see Description of known issues with the FolderLocation settings..

Using this setting to redirect folders to a drive other than the system volume blocks upgrades. Using ProfilesDirectory to point to a directory that is not the system volume will block SKU edition upgrades and upgrades to future versions of Windows®. For example, if you use Windows 7 Home Premium with ProfilesDirectory set to D:\, you will not be able to upgrade to Windows 7 Ultimate or to the next version of Windows. The servicing stack does not handle cross-volume transactions, and it blocks upgrades.

This means you won't be able to DISM /ADD-PACKAGES to your offline images anymore, not sure if that matters to you.

This post has been edited by MrJinje: 18 November 2009 - 02:03 PM

[ruudboek]

@MrJinje, thx so much for your reply, i really appreciate it.

I don't think i need to be able to "DISM /ADD-PACKAGE".
However, i thought about this, maybe it would be better to simply change almost all the User Shell Folders in the registry to point D:\users\%username%.
So that will mean that ntuser.dat will remain in C:\users\%username% and My Documents, My pictures, etc. will point to D:\Users\%username%\My Documents, etc.

I would like that those registry entries will be set for every newly created user in windows 7.

Can you provide me with a working autounattend.xml that will add Current User registry settings to the default user, so that those registry will be valid for every newly created user?

[MrJinje]

ruudboek, on Nov 19 2009, 02:40 PM, said:

Can you provide me with a working autounattend.xml that will add Current User registry settings to the default user, so that those registry will be valid for every newly created user?

Use <CopyProfile>true</CopyProfile> during the Specialize Pass.

Detailed Info

Untested by me, report back if it works.

For actually pushing the reg settings, use setupcomplete.cmd

REGEDIT /S CUSTOM_SETTINGS.reg

If that doesn't work, it might be a little harder, but this looks promising.