Jump to content

Recommended Posts

Posted

This is just a little FYI in case anyone has encountered it. I'm not sure this is even documented. I installed a Windows 7 Pro on a machine yesterday using an AUTOUNATTEND.XML file that is on a USB key. After it was all done, instead of seeing the machine in Audit Mode like it should, it had gone through system, had a user created and all that.

Scratching my head I ended up reloading it 2 more times before I found out what the problem was. I also had another file in the root of the key called UNATTEND.XML which was a file I used in a project for SYSPREP!

So be careful. Interesting to know, that after the Setup uses the AUTOUNATTEND.XML, during the reboot phase the OS will look for other XML files for the OOBE phase info in it, even if it is not in the main XML file it just used.

:D


Posted

This is just a little FYI in case anyone has encountered it. I'm not sure this is even documented.

Documented

Waik.chm - Methods for Running Windows Setup > Implicit Answer File Search Order

Thats why I name my sysprep xml different if doing audit and just point at it in a cmd file

sysprep.exe /oobe /reboot /quiet /unattend:%DVDroot%\OOBEAudit.xml

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...