New
#310
Download ISO from Tech Bench. The MCT ISO has esd not .wim. Alternatively you can convert the MCT esd to a wim using the tool from here.
Last edited by lx07; 10 Dec 2015 at 11:29. Reason: had written ISO instead of .wim
Download ISO from Tech Bench. The MCT ISO has esd not .wim. Alternatively you can convert the MCT esd to a wim using the tool from here.
Last edited by lx07; 10 Dec 2015 at 11:29. Reason: had written ISO instead of .wim
I'm a little unclear about this. I am currently on Windows 7 and I just got a new computer. It currently has Windows 7 installed. I am tempted to upgrade to Windows 10, but I have a smallish SSD C: drive. After reading this tutorial I'm thinking it really not worth it to upgrade if I have to spend a half a day just to move my new user profile to another drive. I'm pretty nervous about upgrading then hacking the registry just to "trick it" in to thinking it's not an upgrade.
I guess my question is is this really what I have to go though just to move one profile that hasn't even been created yet?
All I really want to do is configure any new use profiles to another drive. Is it really necessary to go though all of this? It was a simple registry change in Win 7. I would use the relocation features of Win 10 if it wasn't for the fact that the app data file in the past has been incapable of ridding itself of useless data. My experience with sysprep and answer files in the past is not good at all. Way to much overhead unless I'm imaging a 100 + machines.
I'm not sure what exactly you are referring to. If you have a new machine, then the best option might be a clean install. Duiring a clean install the sysprep relocation procedure (Method One) takes just a few minutes.
(Note that the stage where you are supposed to take a snapshot of the system is completely optional. You don't have to do that.) All you have to do is interrupt the install (Ctrl+Shift+F3), check drive letter assignment, prepare/copy 'relocate.xml' file to one of the drives and reboot using sysprep.
Hello,
I have a brand new Asus M32CD desktop for my mom that I'm trying to move the user directory off C:\ and onto D:\.
When I run sysrep with relocate.xml (modified to match my setup, i.e. drives and windows version), it reboots, walks through the set up and account creation process, but creates the new account in C:\Users.
The computer came pre-installed with Windows 10 Home and the software key is embedded in the BIOS somewhere. I burned a dvd of the latest ISO downloaded from the MS website, but it doesn't seem like the install process is using it, because the drive is quiet after booting up.
Any thoughts as to what I'm doing wrong? Thanks!
Here's my relocate.xml, saved on the root of d:\
<?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>D:\Users</ProfilesDirectory>
</FolderLocations>
</component>
</settings>
<cpifflineImage cpi:source="wim:E:\sources\install.wim#Windows 10 Home" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
... and the Windows 10 DVD is done from original Windows 10 ISO image which contains the install.wim file in Sources folder?
Just one more question: Is this the sysprep command you used:
Code:sysprep.exe /oobe /reboot /unattend:D:\relocate.xml