Example from my x86 install disc (method applies to x64 also), Key component is "FolderLocations".
<FolderLocations> <ProfilesDirectory>D:\Users</ProfilesDirectory> <ProgramData>D:\ProgramData</ProgramData> </FolderLocations>
Basically it has do be done before users are creted, to avoid issues.
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<FolderLocations>
<ProfilesDirectory>D:\Users</ProfilesDirectory>
<ProgramData>D:\ProgramData</ProgramData>
</FolderLocations>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Name>NipiTiri</Name>
<Group>Administrators</Group>
<Password>
<PlainText>true</PlainText>
<Value>XXXXX</Value>
</Password>
</LocalAccount>
<LocalAccount wcm:action="add">
<Name>Konn</Name>
<Group>Users</Group>
<Password>
<PlainText>true</PlainText>
<Value>YYYYY</Value>
</Password>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
Has a small caveat though... legacy or applications that have hardcoded paths (I have none fortunately), will create duplicate folders to "old" default locations and will use them. Basically cosmetic issue...
Edited by HapuKurk, 19 August 2011 - 09:10 PM.












