User Profiles - Create and Move During Windows 7 Installation

@Ibex

Yes, the old ProgramData stays on C:. Read post #30 in this thread for better explanation: User Profiles - Create and Move During Windows 7 Installation

Would you like to tell how did you resolve your update / reboot issue as told in your previous post?

Kari

Thanks for the info, Ibex. That is really interesting.

Kari

Hi Martin, welcome to the Seven Forums.

The folders are not moved before the computer is booted in OOBE (Out Of the Box Experience) mode. As long as you stay in Audit Mode or reboot to Audit Mode, nothing is done except some preparations; sysprep runs the script preparing computer to be started normally in Welcome / OOBE mode, and only then are the folders created / moved to the new address.

So, after running the script and when computer has booted back to Audit Mode, exit Audit Mode rebooting normally to OOBE as told in tutorial. You should select the SysPrep options as in this screenshot:



When you then log in first time to Windows normal mode, you should see the new folders on location you selected.

Kari

Hi Kari,

Thanks for the advice about the folders not moving till I boot into normal mode. That saves me looking unnecessarily.

Unfortunately the folders do not appear on D drive even after I boot normally. I have tried the routine several times doing a new install of Windows 7 each time. For the latest attempts I have been following your routine for when W7 is already installed. I will paste the commands and .xml script I have used.

Before doing that I would just add that everything seems to run as expected - eg a progress box saying Sysprep is doing something appears for a few seconds and the laptop reboots. There are no error messages. The only difference to what you describe is that when I set up windows as if a "new install", I am asked to provide a user name and password. I am then taken directly into the new account with no chance to choose my original login. When I reboot again, I am then offered the choice of original or old. Anyway, the main concern is that the User folder(s) have not moved from C to D.

These are the command prompts and the xml script I have used. F is the drive letter for the USB memory stick but I had similar results placing the xml on D drive. The Windows 7 install dvd is in the E drive

1) During install I used cd \Windows\System32\Sysprep

if booting into audit from already installed I used command prompt as administrator and C:\Windows\System32\Sysprep\Sysprep.exe /audit /reboot then I used cd \Windows\System32\Sysprep

2) Next I used Sysprep.exe /audit /reboot /unattend:F:\relocate.xml

3) This is the "relocate.xml" script (saved with word wrap off) -

Code:

 
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<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>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:E:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

I would be very grateful if you can spot any stupid mistakes I am making or have any ideas, I am playing with this first W7 install to check which of my XP programmes work on W7 before doing a final install "for keeps"

Thanks,
Martin

Hi Brink,
Thanks for the edit and sorry I didn't know about keeping smileys at bay with code boxes!
Martin

Hey all, I am having the same issue as above Xosder in post 144. and derryvolge in post 156

-I installed the OS on my new SSD, C: drive
-my old hard drive, 1 TB with Windows 7 pro 32 bit still installed on it is F:
-my DVD drive is E:

my unattended.xml file contains:

Code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64"
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>f:\Users</ProfilesDirectory> <ProgramData>f:\ProgramData</ProgramData>
</FolderLocations> </component>
</settings>
<cpi:offlineImage cpi:source="wim:E:/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

In bold are the changes I made to the script on the tutorial to math my drives

Additionally, I type:

Code:

Sysprep.exe /audit /reboot /unattend:F:\relocate.xml

After running script, computer reboots in Audit mode, then when I exit Audit mode (by clicking OK on OOBE popup) and reboot occurs, I get:

Xosder said:

"Windows could not parse or process unattend answer file C:\Windows\Panther\unattend.xml for pass oobeSystem"

This only shows up once and then I'm back to the "Windows could not complete the installation. To intall Windows on this computer, please restart the installation" over the "Setup is preparing your computer for first use" screen.

I have looked all over the internet but have not found any solution, any tips will be greatly appreciated!

Thanks

Sorry geeks, I have been a bit busy and only occasionally checked in here. Now I had some time and checked your scripts.

First, Martin and Vict555, I find no typos or other mistakes in your scripts. If the Windows installation DVD is on drive E: as you both seem to have, if the install media is valid and includes original install.wim on Sources folder, if the destination drive exists, and if the bit version is correct (x86 for Martin and x64 for Vict), then those scripts are as far as I can tell correct.

I am very sorry but I can not explain this. As I have told earlier on this thread, sometimes it just wont work. My saldo at the moment is 16 out of 18 rigs I have done did work, 2 did not. I have done an enormous amount of Googling, Binging, Yahooing, you name it , and I have found no explanation. I suspect it is some Windows service that causes this. I am going to do some extensive testing next weekend trying to find out more.

Kari