Windows 8.1 Sysprep & Unattend.xml

Hi All

I am currently working on a deployment image for Windows 8.1.  I intend to use a WinPE disk (automated) to deploy the sysprep image, but I'm having some difficulties with the unattend.xml file.

Currently, I use a custom, automated WinPE boot disk to deploy our sysprepped Win 7 images, and works a charm!  I have invested a lot of time in developing this, and we are fairly happy with the process. We have three domains under our control and have to deploy devices to either domain.  To create the Win 7 image, I used MySysprep (www.tsaysoft.com/mysysprep2/) with the answer file.  This package provided the ability to prompt for the device name during the OOBE stage, as well as prompted for the domain to join, in form of a drop down list.  Thus, we had the choice to join one of three domains at the OOBE stage depending which department\domain the device would be located.

As the time came to venture into the latest Windows OS (win8.1 and possibly Win10 once released), I revisited MySysprep and hope that it would run without any issues.  Unfortunately, this is not the case, and the device produce an error during the OOBE stage:

Windows could not parse or process the unattend answer file for pass [specialize]. The setting specified in the answer file cannot be applied....

Thus opted to use the standard Sysprep command.  I am currently using Win8.1 ADK.

Ok, so I edited the file to only join to one domain instead of trying to prompt for three domains, but still the same issue.  Obviously, if I remove this section (unattendedjoin) from the XML file, the OOBE stage proceeds and all appears to be fine.

I guess my main question would be:  Are there any way to configure the XML file to prompt for which domain to join, and autologin with a domain account once the OOBE stage has completed?

I know some would say I should look into MDT or SCCM, but unfortunately this is not possible at this stage (I will discuss this with management in the near future).

Regards

Leon

June 25th, 2015 7:22am

Hi,

About this problem, in my opinion, firstly, you'd better to check the log file where the specific problem it is:

setupact.log file in following path should be helpful:

C:\Windows\Panther\UnattendGC

Free Windows Admin Tool Kit Click here and download it now
June 26th, 2015 3:04am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics