Jump to content

How to use <FolderLocations> with WTK?


Alpha_95

Recommended Posts

Hi Alpha_95:

I've done this successfully. I test with VMWare Player with a pair of 30GB.hard disks configured. I have both hard drives formatted NTFS before install. I've attached my Autounattend.xml file for reference.

The last time I tested this was about 6 months ago with the prior version of WinToolkit 1.5.4.4.

Hope this helps,

Clark.

Autounattend.xml

Link to comment
Share on other sites

Hello clarkg888,

hard drive formatted NETFS before install => yeah sure!

your .xml file is similar, i use:

    <cpi:offlineImage cpi:source="wim:E:/sources/install.wim#Windows 7 ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

or .clg is required for that?

edit: try with you .xml file and doesn't work, i need to enter in audit mode or what?

 

<cpi:offlineImage cpi:source="catalog:dvd_pro/sources/install_Windows 7 Revolution.clg"

path to DVD or? can you explain please

Edited by Alpha_95
Link to comment
Share on other sites

I don't think that <cpi:.. line matters. I got that line after editing with Windows System Image Manger (SIM). According to this post , you can delete that line.

Does the install proceed ok, but just doesn't put \Users on the D: drive? Or do you get some error message? Are you installing in a VM?

I've never used audit mode for this. I just add the AutoUnattend.xml to the root of the ISO created with WinToolKit using an ISO editing tool. I use  UltraISO.

Also, if you are adding a OOBE.CMD script to your ISO in path "\sources\$oem$\$$\Setup\scripts", the script gets run TWICE when you have the FolderLocations specified in the AutoUnattend.xml.  It runs once before the \Users folder is moved, then the system reboots and it runs again with the \Users in the new location.

I've attached my OOBE.CMD for your reference. It creates a log file on the first run, so it can detect whether this is the first or second run. It runs an OEM activation script on the first pass. On the second pass, it fixes the junctions "Documents and Settings" and ProgramData on the boot (C:) drive so they point to the new location on the D: drive. And it creates a junction "Users" on the C: drive to point to the D: drive so brain-dead software that assumes Users is on the C: drive goes to the right location. This is just a refinement once you've got \Users being created correctly on your D: drive when you install.

Clark.

 

 

OOBE.CMD

Link to comment
Share on other sites

 

No error and yes i test in a VM.

For OOBE.cmd script, i need to put in C:\MYDVD\sources\$OEM$\$$\Setup\scripts?

edit: OOBE.cmd in "C:\DISMTOOL\DVD_PRO\sources\$OEM$\$$\Setup\scripts"

doesn't work.

 

OOBE1.log:

C:\Windows\System32>IF EXIST "C:\Windows\Setup\scripts\OEMACT.CMD" CALL "C:\Windows\Setup\script\OEMACT.CMD" 1>C:\Windows\Setup\scripts\OEMACT.log 2>&1
C:\Windows\System32>GOTO :EOF

 

Edited by Alpha_95
Link to comment
Share on other sites

Yes, assuming you are burning the contents of C:\MYDVD to DVD or creating the ISO for install in the VM from the contents.

But the OOBE.CMD isn't required to get the Users folder on the D: drive.

Maybe try putting your Autounattend.xml on the root of a virgin untouched Windows 7 SP1 Ultimate DVD or ISO ?

Clark.

Edit: yes, your result with OOBE1.log is expected, since you don't have the OEMACT.CMD file. I'm assuming you are getting no OOBE2.log, so the second pass isn't running.

Edited by clarkg888
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 months later...

OK, I finally got the time to try this. I used your autounattend.xml with the image name changed from "Windows 7 Revolution" to "Windows 7 Ultimate" and the Product key section removed:

                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>XXXX-XXXX-XXXX-XXXX-XXXX</Key>
                </ProductKey>

I used the US English iso X17-59465.iso Windows 7 Ultimate SP1. I think you must use the French one.

I installed in a VMWare VM with 1.5GB RAM and two formatted 30GB drives C: and D: The Users and ProgramData folders ended up on D: as expected.

I don't know what is going wrong for you.

Clark.

Link to comment
Share on other sites

  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...