User Profiles - Create and Move During Windows 7 Installation

How to Create User Accounts on another Partition or Disk During Windows 7 Installation ​

   Information

There are several methods to move user profiles to another disk or partition after you have installed Windows 7. The easiest way is to use Audit Mode and System Preparation Tool, both built-in Windows 7 features, to permanently move the location of the folder Users.

This tutorial shows how to relocate both Users and ProgramData to another disk or partition when doing a new, fresh and clean install of Windows 7. If you have already installed Seven, and you'd like to move those folders away from their default location in C: drive, please read first post number 22 in this thread. Follow the steps told in that post, and continue then from beginning of the page 4 in this tutorial.

When Windows 7 is installed, 5 or 6 system folders are created depending on chosen bit-version:

• PerfLogs (Performance Logs), where Windows stores performance and reliability logs
• Program Files, where applications and software are installed. Windows x86 (32-bit) stores all applications here, Windows x64 (64-bit) only native 64-bit applications
• Program Files (x86), only in Windows x64. All non-x64 applications are stored here
• Windows, which contains core operating system files and drivers
• ProgramData, where some applications store application and user specific settings and configuration files
• Users. This is the "home" of all user folders. When a new user account is created and this new user logs in first time, Windows creates a set of user specific folders Users\New_User

Moving Windows and Program Files folders is not recommend by Microsoft. However, moving both Users and ProgramData folders is safe and can save a lot of space on system disk. Pictures, mp3’s videos, documents and so on, a user folder with its subfolders can be tens, sometimes hundreds of gigabytes.

For instance, using this laptop of mine as an example, the total size of Users folder and subfolders is at the moment about 240 GB. The size of ProgramData folder is at the moment almost 18 GB. I simply could not have these folders stored in my system C: drive, there’s not enough space.

When installing Windows 7, I recommend using Windows System Preparation Tool (Sysprep) in so called Audit Mode to relocate Users and ProgramData, leaving C: drive only for Windows and applications.

   Warning

An upgraded Windows cannot be sysprepped. As this method is based in sysprepping, this tutorial is valid only for Windows setups which have not been upgraded.

This means that if you have for instance in-place upgraded Vista to Seven, you cannot sysprep. The same applies if you have upgraded from a lesser edition to a better edition, for instance from Windows 7 Home Premium to Professional.

Notice that a repair install is also an upgrade install, so if you have ever done a repair install (= in-place upgrade to same edition), you cannot sysprep.

In other words, when sysprepping an existing Windows setup it only works if the Windows was installed clean and has never been upgraded or repaired using repair install, or if it is the original pre-installed Windows.

Using this method causes Windows 7 to lose activation information, and it needs to be reactivated afterwards. If your Windows 7 is an OEM version, you might not be able to reactivate it, at least not without phone activation option.

   Warning

IE10 Users: Please read this article first: Sysprep Fatal Error With IE 10 (FIX) | System Administration

Complete tutorial as PDF: View attachment Relocate User folders during Windows 7 installation.pdf (1.22 MB)

Kari

Related Tutorials

---

• How to Change the Default Location of a User Profile in Windows 7 and Vista
• How to Change the Default Location of Windows 7 User Folders
• How to Restore the Default Location of Windows 7 User Folders
• How to Free Up and Recover Hard Drive Space in Windows 7
• How to Change the User Folder Name of a User Profile in Windows 7

 

[Kari]

I'm using Notepad++ to edit Kari's script. I keep getting an error message when I check the xml syntax. "XML parsing error at line 11; Extra content at the end of the document"
...

Syntax is correct, if your install media is located on drive R:.

You can use any Windows 7 install media when sysprepping, it does not need to be the one you have used to install. Get an OEM or Retail SP1 ISO, burn or create a USB and use it. Should work.

Kari

 

[Jenac]

Excellent guide!!!

Well done. Super useful. Love it!

 

[BWR]

I am having the same issue as above Xosder in post 144, derryvolge in post 156, and Vict555 in post
I have two new build your own systems with
-New 128GB SSD, C: drive
-New 1 TB SATA drive E:
-DVD drive is D:
-OS Windows 7 x64 PROFESSIONAL

my unattended.xml file contains:

<?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="[URL="http://schemas.microsoft.com/WMIConfig/2002/State"]Error[/URL]" xmlns:xsi="[URL]http://www.w3.org/2001/XMLSchema-instance[/URL]">
<FolderLocations>
<ProfilesDirectory>E:\Users</ProfilesDirectory>
<ProgramData>E:\ProgramData</ProgramData>
</FolderLocations>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:D:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Additionally, I type:

Sysprep.exe /audit /reboot /unattend:Z:\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:

"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.

Has there been a resolution to this?

It seems that this is the one issue that seems to get ignored.


Please help if possible.

 

[dcapit8]

Awesome but a few questions

Kari,

This is simply an outstanding tutorial, I spent a few weeks looking into this. I find this method to be just superb as to doing manual registry edits to get similar results.

I had to use the method twice because I didn't read the full thread about doing system imaging. I have a 100GB SSD and a 2TB HDD. I originally just moved users and program data to the HDD which only had the one partition. I realized in order to make a good image I need all the basic windows folders (user and program data included). I realized that would now require me to image the full HDD. So I decided against that and created a partition and make the move, one more time. The only thing I am noticing is that now in both my C and E drives still contain a ProgramData folder. I am not sure if it is safe to delete those folders all together because it seems redundant. On the E: there is a Microsoft folder that has a search folder and windows folder. The same folder is on C: too. The one on Z: (the partition) has a more extensive Microsoft folder that has just more than Search and Windows. Would it be safe to delete on the other drives, assuming your or anybody else came across something similar.

Edit....I was thinking for imaging and backing up reasons, would it be possible to make a symbolic link on your OS drive to the user and programData folder drive, so therefore when the image is being created it will know where to look for the remaining system folders. This might be a completely dumb question as I am by know means computer savvy, so bare with me.

 

[William Lyders]

Following the PDF instructions, using "new scenario" in Post #22, AFTER Windows is already installed

Basic question 1:
Can all this be done on a re-build computer where the Windows 7 has not yet been RE-ACTIVATED? [ I have yet to "fight" with MS to be able to re-activate this re-built computer which sports a new motherboard, SSD, and HDDs]

Question 2:
Why have I stalled?
All has gone OK up to Kari's instruction (pg 6):
Sysprep.exe /audit /reboot /unattend:\relocate.xml
which I have modified to:
Sysprep.exe /audit /reboot /unattend:E:\RELOCATION TEXT, MODIFIED.XML

When I enter this, I get the following message on a small screen:

<< Usage: sysprep.exe /quiet /generalize /audit | /oobe /reboot | shutdown | /quit /unattend:<FILENAME>
If no command-line arguments are provided, a graphical user interface is used to select the desired mode of sysprep operation >>

When I click "OK", it goes back to the Command Prompt, but does nothing more.

Just what is this message telling me?

 

[dcapit8]

William,

Take my answer with a grain of salt, but I think E:\RELOCATION TEXT, MODIFIED.XML needs to read E:\"RELOCATION TEXT, MODIFIED.XML" if there are spaces in the document title.

I can't remember where I read that, but hopefully it helps.

dcapit8

 

[William Lyders]

Thanks, decapit8,

Will just change the file name to Kari's \relocate.xml, and give it a retry, tomorrow.

 

[Kari]

"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.

Has there been a resolution to this?

It seems that this is the one issue that seems to get ignored.


Please help if possible.

The error message you get is one normally gotten when there's a syntax error in answer file, when answer file or install.wim is not found. This can be the case for instance if the drive letter is changed between Audit Mode and first boot to OOBE. Also, I have seen this error when sysprepping some heavily manipulated OEM Windows versions.

This error message might also occur when sysprepping a Windows version with bootloader. This, of course, I do not believe your case.

Reading your answer file I noticed that it returns an error where there should be a schematic check:

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
xmlns:wcm="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

I need to check if I need to rebuild this answer file again, original was created about two years ago.

I will be back as soon as I find some time to spare.

Kari,

This is simply an outstanding tutorial, I spent a few weeks looking into this. I find this method to be just superb as to doing manual registry edits to get similar results.

I had to use the method twice because I didn't read the full thread about doing system imaging. I have a 100GB SSD and a 2TB HDD. I originally just moved users and program data to the HDD which only had the one partition. I realized in order to make a good image I need all the basic windows folders (user and program data included). I realized that would now require me to image the full HDD. So I decided against that and created a partition and make the move, one more time. The only thing I am noticing is that now in both my C and E drives still contain a ProgramData folder. I am not sure if it is safe to delete those folders all together because it seems redundant. On the E: there is a Microsoft folder that has a search folder and windows folder. The same folder is on C: too. The one on Z: (the partition) has a more extensive Microsoft folder that has just more than Search and Windows. Would it be safe to delete on the other drives, assuming your or anybody else came across something similar.

Edit....I was thinking for imaging and backing up reasons, would it be possible to make a symbolic link on your OS drive to the user and programData folder drive, so therefore when the image is being created it will know where to look for the remaining system folders. This might be a completely dumb question as I am by know means computer savvy, so bare with me.

About duplicate Programdata folders, read this post: http://www.sevenforums.com/tutorial...ing-windows-7-installation-4.html#post1161672

Imaging and how to do it is up to you. I am a bit disappointed in Microsoft for making using built-in imaging tool so difficult when system folders are spread on two or more drives, so I use Macrium Reflect to always create an image containing both system drive (Program Files, Windows) and the Users drive (ProgramData, Users).

Call me coward but I really do not want to give detailed instructions in how to image an SSD / HDD system with system folders spread in between them. So much can (must not!) go wrong and me being not an imaging expert, I would spent rest of my days in explaining my wrong advice

Kari

 

[dcapit8]

Kari, thank you for the quick response.

I don't have a problem leaving the program data folder on C: drive, since that will be one of the drives I use to image. I am trying to avoid having to include the e: drive as that is 1.5TB and for down the road I don't think I will be willing to wait as the system has to image all that, assuming I fill 1TB.

I too am like you and want to include all the system folders when I do an image. I don't think that program data is required to be on e: as you said it is really only there for programs that hard code to c:\programData. I think my dilemma came from doing the sysprep twice (First User and ProgramData went from c: to e: and then from e: to z Therefore if I decide another partition down the road and need to move these folders again there will be a trailing ProgramData folder in each of the previous drives. This is what I am trying to solve. I would like to move the e:\programData over to c:. Since you said you done this many of times, have they all been on the same machine? If so what was your work around for this situation. Again I know in post you referred is that you just left it alone, I am absolutely fine with that for the c drive.

Anybody who has dealt with this please feel free to answer as well.

 

[William Lyders]

An Update:

I took time off to complete the problematic re-activation of my re-built computer, which I was finally able to do successfully using the double-install method.

But that killed the chance to use Kari's re-locate Users folder process, because I now get this message:

"Sysprep cannot run on a computer that has been upgraded to a new version of Windows. You can only run Sysprep on a custom (clean) install version of Windows"

Now what????

I haven't digested the method published by Brink, yet.

 

[jvidamins]

Error Message

Kari, I'm following your instructional to the T. I've tried it 3 times and each time, after I run the script and try to exit Audit mode I get the following Error Message as my machine tries to boot into Windows:

Install Windows

Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing setting for component [Microsoft-Windows-Shell-Setup].

Once I get that error, there's no way for me to boot into windows, and I'm forced to reinstall again.

Is there a fix for this? Or is it something I'm doing wrong? Please help!

 

[Positronic]

Hi Kari,

I'm stuck, tried your method of moving the USER folder over but no love. In the past I've been able to move a user folder following your guide but am having problems with this system.

My setup includes a C: drive (SSD) on Intel controller, two mirrored 3TB drives partitioned as GPT. The Intel controller is set to RAID so the SSD is on this as well. Does it matter as to the controller, i.e. Intel or Marvell? Does it matter if controller set to RAID? I've disabled the onboard Marvell controller.

Earlier you mentioned not formating drive D: prior to running the xml script in reply to another post. I hadn't tried that but well now. I've been going into Audit mode and partitioning Drive D: and formating it prior to running the xml code. Is the D: drive supposed to be unpartitioned when running the xml code? I'm guessing not as your example copied the xml file to the D: drive root directory prior to running.

Another thing I tried was disabling all the RAID drives and set the controller to AHCI and hooked up a single drive for the D: drive. I install Win 7 to the SSD and in AUDIT mode I create a partition on the single drive and assign drive letter D:. I make sure the DVD drive letter matches the XML code, the OS is "PROFESSIONAL" which is correct and it is a 64 bit OS so AMD64 is being used. I copied the source code to the root of drive D: and run the sysprep command. It closes out fine without error and reboots. Upon the second reboot the user files are created in the C: drive, and, newly created users are in the C: drive.

I am using Windows 7 Professional SP1 OEM 64 bit. Now, this is a copy provided by the computer maker, which I think is a stock OEM DVD. Is it possible something on the install from that DVD is keeping it from working?

Thanks for your help!

 

[Positronic]

Also, am wondering if there is a way after running the sysprep.exe command when it boots the 2nd time in to audit mode to check some way to see if it will actually create the User folder on the target drive? It'd be nice so you wouldn't have to boot into Out-of-box to see if it worked.

Btw - I redid the Win 7 install from scratch again without creating a partition on the D: drive and upon booting into normal mode the USER was on the C: drive and the 2nd harddrive wasn't partitioned or formatted so I answered part of my question in that the D: drive needs to be partitioned, if not formatted.

 

[Positronic]

Btw - here is the script I'm using which I just checked again and seems to match up. Note - the Win 7 DVD is in drive F:.

<?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="Error"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<FolderLocations>
<ProfilesDirectory>d:\Users</ProfilesDirectory>
<ProgramData>d:\ProgramData</ProgramData>
</FolderLocations>
</component>
</settings>
<cpifflineImage cpi:source="wim:F:/sources/install.wim#Windows 7 PROFESSIONAL"
xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Also, this is the command I used to execute the xml file...

sysprep.exe /audit /reboot /unattend:c:\relocatepro.xml

I called it relocatepro.xml for Win 7 Professional. I'll make a separate one for Win 7 Home later.

OK - success! Apparently the included Windows 7 PRO DVD from the computer manufacturer is the cause of this not working. When I used a new OEM Windows 7 PRO SP1 DVD the USER folder transferred fine!!!!

Might want to include this little caveat with your guide.

 

[ibmattg]

Freaking out! I just built this cpu had win7ultimate x64 on SSD and Formatted WD 2TB HD All working and installed Anti-virus...then tried this but first time was not sure if you ment to make Folders called Users and program data on D first(and am not sure if I deleted before script ran), got distracted came back an ran script but I deleted Users and Program folder without even testing if.....well it seemed easy so I thought I would do a fresh install and do it again to make sure and got error script is already running (this may have had to do with the fact I forgot to take out usb drive with script an note pad commands?) Then forgot with SSD I was suppose to start at forums #22 So reinstalled for like the fourth time and ran it... what I had not knowticed is that my CD drive was D and Data drive was E tried to swich drive letters and run again then swich drive letters reinstall 7 and they come back the same and when I run cd \Windows\Sysprep32\sysprep I get cannot find sysprep or something how do I proceed...How do I Wipe SSD back to factory settings and then can I put in mother board cd and get main drivers on and start again?

 

[twitters99]

Specifying target drive

Thank you Kari for a very thorough set of notes. Sorry if my question is basic - I am a complete novice when it comes to xml scripts, audit mode etc. As far as I can see the target drive - D: in your case - is not specified in the script, so is the target drive determined by where you place the xml file? So, I have a logical drive / partition "S:" which I want to house my user profile. Do I simply, load the xml file in the root of "S:" ? (I am aware of changes to the script to state my version of Windows. It is just the target drive I am trying to pin down). Tony

 

[xps15]

Thanks for the tutorial.

 

[piikea]

Should you end up having to reactivate Windows at the end of all this?? It asked for Product Key at some point when I created the temporary account thinking once I was back to my real or actual user account things would be back as they were (i.e., already activated).

 

[Kari]

This procedure is as any other Windows installation procedure, you need a valid product key.

 

[Britton30]

I have just finished up another install using your method Kari and the answer file worked fine. Of course Windows decided to give different drive letters than what I had in the answer file so I had to change them, but all went well, thanks one more time!

Should you end up having to reactivate Windows at the end of all this?? It asked for Product Key at some point when I created the temporary account thinking once I was back to my real or actual user account things would be back as they were (i.e., already activated).

Anytime you do a repair install or clean install or upgrade, you will have to "reactivate" Windows.
I recommend skipping the key entry during installs and uncheck the box to Activate when I'm Online so you can verify all is working well.
Using a Dell OEM installer is one exception to this.