Windows Deployment Services - Error when adding Unattend.xml

[thatley]

Hi all,

 

Not sure if anyone has had this error before. We've installed 2016 in about 4 schools so far, 2 have been fresh installs with new domains and 2 have been migrations from Server 2008 R2. The new installs have been pretty smooth with just a few minor issues; the migrations however have been a real pain in the backside with these issues:

 

- NLA not selecting "domain network" after reboots (fixed this by restarting the NLA service as a scheduled task 1 min after reboot)

- 5 Sophos Services not starting after reboot - fixed this by setting those services with a "delayed start"

- WSUS won't install - fixed this by adding "NT SERVICE\ALL SERVICES" to the Default Domain Controller Policy

 

This one with WDS is a strange one. Installs fine, can add boot and install images fine, however, when attaching an unattend.xml to an install image - I get this error:

"the process cannot access the file because it is being used by another process"

Once you get this error, you can only cancel out of the message. However, when you go back in to the install image properties, it has actually added the file in and it does work when you build the machines!!!

 

So to sum up, it does actually work, but you get that error regardless.

 

Anyone else had this, or any other issues with migrations that you've had to make workarounds/fixes? Would be good to know.

 

Thanks.

[woreilly]

We have found that with ADK 10 - 1703, you have to disable secure boot on your MDT/WDS server before you can update your deployment share and generate a boot image.

[thatley]

Hi woreilly,

 

Really? In the bios? I know that we're definitely not using a UEFI bios, just standard/legacy, so not sure this the problem.

 

As mentioned in my post, I can generate boot and install images, it's just attaching the unattend files to the install image that throws up the error.

 

Can you clarify?

 

Thanks.

[woreilly]

Hi woreilly,

 

Really? In the bios? I know that we're definitely not using a UEFI bios, just standard/legacy, so not sure this the problem.

 

As mentioned in my post, I can generate boot and install images, it's just attaching the unattend files to the install image that throws up the error.

 

Can you clarify?

 

Thanks.

 

My Apologies. We run Hyper-V Generation 2 VMs. We had to disable secure boot in the VM settings. It is something to do with Digital Driver signing.

 

https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/

 

Although looking at this article, there seems to be a fix for that.

[Arthur]

there seems to be a fix for that.

There's also a script to patch the ADK quickly.

 

https://gist.github.com/keithga/6a64abb048d885ea7c5f096c319f38b8

 

.\Patch-MyADK.ps1 -verbose

[Arthur]

it's just attaching the unattend files to the install image that throws up the error.

Do the unattend files successfully validate in WSIM?

[thatley]

Thanks, I'll have a look at that.

 

Yes Arthur, they do work strangely enough. It's just a weird misleading error that only seems to happen on a server migration from 2008 r2 to 2016, but is fine on a fresh install new domain.