Windows 10: WDS: unattend.xml does not work for boot image

Hi everyone, since i read some goof topics in this forum while i am working with wds i decided to join too because of my problem

Atm i am working with WDS for rolling out custom images at work. The main goal is to get it as automated as it could. While the captured/install images it selfes works perfect with its unattend.xml (lets call it installunattend.xml), the boot image does not work with the unattend.xml (lets call it bootunattend.xml) at all. I created both XML files with WSIM and run a WSIM error test over it, no errors at all.

I mounted the BootUnattend.xml under WDS > Right Click on the Server > Proberties > Client > activate the checkbox for the unattend instalation > and selected the bootunattend.xml

The bootunattend.xml itselfe is places directly in W:\RemoteInstall

Because the file contains alot of options i also created a second file wich only contains the domain credentials (SmallBootUnattend.xml) to check if its the file itsselfe but this file is also not working.

Sidefacts:

- Server: Server 2019 (1809)
- Image to roll out: custom Win10 pro 64 bit (10.0.19041) (made in audit mode with sysprep)
- Boot Image: Win 10 pro 64 bit (10.0.19041)
- WDS is connected to the active directory of the company
- Windows ADK 10.1.18362.1 is installed on the server

Things i tried:
- use a different user (ActiveDirectory-Admin)
- google but most people have problems with the unattend.xml + install images
- using different / new XML Files for WIN PE
- got all rights from the domaine admin
- read alot of tutorials, i can't find what they do different to me

If you have any more questions, feel free to ask, thanks for your help.

Code of bootunattend.xml
Code:

Code of SmallBootUnattend.xml
Code:

:)

 

Is there a way to make unattend.xml actually work in W10 1903?

I have built a valid answer file "unattend.xml" in WSIM and set it to skip Eula etc, create two users and pull drivers from a network path. I validated the file before saving. I placed the file in c:\windows\panther. It appears to get overwritten before
the oobe pass. So I put a registry entry into HKLM\System\setup called "UnattendFile" and gave it a path to my unattend.xml file. Then I sysprepped the image with c:\windows\system32\sysprep\sysprep /generalize /oobe /shutdown /unattend:c:\build\copyprofile.xml.
I take an image with winpe and then apply the image to my target device and boot. Windows still doesn't use the answer file. In fact, this was the second time imaging this machine and somehow, it didn't overwrite the user account that I put in the previous
imaging attempt.

How do you get unattend.xml to actually be used? None of the documentation seems to be correct.

When imaging windows 10 with winpe, do you have to format the drive first to actually lay down a fresh copy?

 

Operating System Dialog is empty when I use unattend.xml file

Hi guys,

Something weird happened to me when I was using the unattend.xml that I make it. To build this I use the ADK in version 1809. That file works normally when I run in a clean image windows 10 1809 with command setup.exe /unattend.xml. But when I customize
a image using sysprep, building the install.wim and make others settings, so when I run setup.exe /unattend.xml, the process stopped in this screen below. Just to make sure if the image is working, I runned without the unattend and that works fine.



Does anyone know or have any idea about this problem?

Thank you so much.

 

Getting WD My Book to work on Ubuntu?

I am not booting from the WD drive. I am booting from my internal drive. But when I plug the WD drive into one of my USB slots, the disk does not mount. I visited "My computer" where the disks at least show up in the list. The WD drive shows up here, seems fine. But if I try to mount it (as a secondary disk), it refuses to. Thanks for responding. I appreciate it.