User Profiles - Create and Move During Windows 7 Installation

Sorry, my mistake. coming from DOS era I often forget that those old commands are not clear to everyone

CD is short from Change Directory (directory = the name we used to use for Folder).

That command you referred to simply changes the default working directory (folder) to \Windows\System32\Sysprep.

\Windows = C:\Windows, you can mark drive root simply by typing a backslash, no drive letter needed if you jump to another directory (folder) on the current drive.

So, to speak "puters": That command translates to "Change working folder to C:\Windows\System32\Sysprep".

OK thank you, I speak DOS as well as I do Finnish or German.
It make sense now.

How can I move the ProgramData folder back to C:?
I have installed some programs to C:\Program Files (x86) and C:\Program Files which don't appear in my start menu while others do. I don't know if the data file is at fault or not. I even installed two programs to K: (data drive) which do appear in the start menu.

Should write caching remain enabled on the SSD?
Thanks.

First, location of ProgramData has most definitely nothing to do with your issue. Relocating ProgramData with sysprep even leaves the original ProgramData to system drive C: to be used by those apps that use absolute location C:\ProgramData instead of Windows environment variable %ProgramData% when installing. See this post for more information.

That being said, this post shows how to revert to original location.

About write caching on SSD I have no idea. Sorry.

Kari

Thanks, I will leave as is since I don't know how to boot to audit mode nor "run the script" other than during install as in your tutorial. That particular script appears to be for both Users and ProgramData.

Sorry Britton, forgot to mention how to boot to Audit Mode.

• Close all programs
• Run Command Prompt as administrator
• Type or copy / paste this to command prompt:
  
  • C:\Windows\System32\Sysprep\Sysprep.exe /audit /reboot
• hit Enter

Or

• Close all programs
• Browse to C:\Windows\System32\Sysprep\
• Right click Sysprep.exe, select Run as administrator
• Select Clean Up and Boot options as in this screenshot, click OK:
  .
  

Windows reboots now to Audit Mode.

Kari

that was a mistake, I can't leave audit mode, Windows is preparing your desktop on each restart. I chose enter OOBE and created a new account and the original account is an option to log into.
However about a half dozen installed prgrams are now missing. I didn't know how to run the script so I tried nothing.
Looks like a complete secure erase and clean reinstall...again.

Don't panic yet!

First, that's normal that when leaving Audit and rebooting to Oobe, it asks a new accountname and computer name, and does not accept your old username because that already exists in the system. You need to create a temporary user, then in Welcome screen select your old account, and finally in Windows delete the temporary account. All this is explained in post number 22 earlier in this thread.

Audit Mode and SysPrep do not delete or uninstall your installed programs. That is one thousand percent sure! Of course, if you did not read this thread before starting, you did not know that you should login to your old account instead of the temporary one Oobe boot makes you to create, and logged in to that temporary account and noticed that the Start Menu did not show all your apps. Naturally. As you certainly know, not all apps install to all users automatically. They are there but not visible in the Start Menu.

This NOT LOGGING IN to temporary account when sysprepping existing system and returning to Oobe is important. At the very beginning of this tutorial is information box telling to read post 22 if sysprepping existing Windows installation. This quoted infromation box can be found at very beginning of the post 1 in this thread:

   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.

To summarize this:

• Sysprepping in Audit Mode does not cause installed apps not showing in Start Menu. Absolutely not. The reason must be found elsewhere in your SW and / or HW setup and / or working methods
• Sysprepping in Audit Mode does not unistall your apps. Again, this is absolutely sure
• Running the answer file (script) given in this tutorial does nothing else than changes values of two of the environment variables of Windows 7. It does not touch, it simply can not touch, any of your installed applications

Kari

Somehow I lost 1.8GB on the C: drive however, my program seem to be intact. All the taskbar shortcuts were missing and I simply restored them.
I think the problem here is that while you are very fluent in xml and Audit Mode, I am not. I have no clue how it works other than the info in the tutorial. I think you infer more intelligence on me than I deserve and I can't fill in the blanks you think I should know.
In THIS for example, is that the entire script to convert to a xml file or a modification of the larger one from the tutorial?

Kari,

Very well done regarding your posts............very clear, and very easy to understand!

Background:
My nothing unusual basic setup as delivered:
New Laptop - HP Pavilion G6 running W7 Home Premium 64 bit, pre-installed by OEM on 1 TB SATA drive:

System 199 MB NTFS (System, Active, Primary Partition)
(C) 912.66 GB NTFS (Boot, Page File, Crash Dump, Primary Partition)
Recovery (D) 14.70 GB NTFS (Primary Partition)
HP_TOOLS (E) 3.97 GB FAT32 (Primary Partition)

My initial alterations:
Straight out of the box, cleaned (de-bloated), no other software whatsoever installed yet, not connected to internet. Drive re., partitioned very smoothly with Partition Wizard (nice little tool):

System 199 MB NTFS (System, Active, Primary Partition)
(C) 100.00 GB NTFS (Boot, Page File, Crash Dump, Logical Drive)
Data (G) 406.33 GB NTFS (Logical Drive)
Multimedia (H 406.33 GB NTFS (Logical Drive)
Recovery (D) 14.70 GB NTFS (Primary Partition)
HP_TOOLS (E) 3.97 GB FAT32 (Primary Partition)

All now backed up and cloned.

Current Position:
Chose to move only the location of "Users" to Data (G), leaving ProgramData on (C), and therefore deleted the appropriate line re., ProgramData from the XML-script. Edited the other parts of the script as per Tutorial to suit my particular circumstances. Followed all of your instructions to the letter using all of your posts and the Tutorial (page 4 onwards).............all apparently went to plan.............no errors, correct boots etc., etc., etc., except...................."Users" still remain stubbornly on (C). Tried four times now, and each time with the same result.

With all of the above in mind, I very much suspect that this has absolutely nothing to do with any re-partitioning, and everything to do with the fact that it is an OEM pre-installed OS without any OS installation disks supplied (as is usual in such circumstances). I have made the usual 'one-off' set of recovery disks (4 disks in total) for future reinstallation if necessary, and I have therefore had to use those in lieu of an original OS disk.

Checking this through, I cannot locate "install.wim" anywhere at all on any of the recovery disks, or on any of the hard drive partitions, which would appear to make the "offlineImage cpi:source" part of the XML-script useless. Windows Explorer does not allow a detailed analysis of the contents of the recovery disks, or the Recovery (D) partition, only displaying the headline icons for the file contents...........don't know if I've explained that well enough, but anyway, you'll know exactly what I mean if you've ever explored a typical recovery disk set created via an OEM installation.

Any thoughts and / or ideas?
What can I do to make this a success?
Have you or anyone else experienced this problem and then successfully resolved it?

Bearing in mind the vast number of OEM pre-installed OS laptops being sold, there is probably an equally vast number of other owners out there with exactly the same problem, tearing their hair out wondering how to make your method work for them.

H E L P pleeeease!

Thanks,

Amicus