Has anyone been able to raise the WDS server normally and put the computer into the domain?

Question

Windows

Hello.
I raised a WDS server in the organization, and the question arose of automatically installing Windows 10 Pro 21H1 on computers without human intervention. I created an install.wim image with the necessary software. And it all turned into a whole epic with jambs.

With the help of Windows ADK, I made an answer file, compiled the ISO, put it in virtualbox, the disk itself is marked up, everything is fine, but in the end it still pops up setting up all sorts of tracking, privacy, account, entering the domain.

As a result, I generated a response file on a third-party site , during installation, Windows only asked for disk layout, although I already marked partitions in the generator. The installer didn't ask anything else.

I did this: I opened the downloaded autounattend.xml file, and opened it in the Windows ADK, and made the disk layout myself.

At the same time, Windows ADK cursed at the very lines that are responsible for ensuring that privacy settings do not open, and even though ADK cursed for extra parameters, they successfully worked, and no extra windows appeared.

It turned out such a hybrid file-Frankenstein. I tested the installation on a regular ISO MSDN image. I was already delighted, but when I connect the same file to the WDS server, Windows still asks about disk partitions during installation, and other garbage. Although the answer file is the same pancake.

Some kind of idiocy!

In the WDS snap-in itself, it is possible to generate an answer file, but it is clearly indicated there that this generator is for Windows 7/8 but not 10, and using this autounattend.xml creation wizard, of course, nothing is applied.

Figs with him, with the answer file. Tried a clean install.wmi MSDN distribution - same story. In the WDS server, I specify the response file, and the server seems to either ignore it, or only accept commands by half.

Okay, I think. The main thing is that the computers enter the domain themselves, I will install the software with politicians. Aha - shchaz.

In the WDS functionality, there is a domain entry function. I enter, specify a user with input rights to the domain - and when installing Windows at the initial stage, it asks which user we will enter the computer into the domain - I specify (for some reason) the user. What for then I indicated it in the WDS settings, if you still need to enter it during installation? All the same, it offers to enter the domain manually at the final stage.

I shoveled the Internet - I see that people get out as best they can, write powershell scripts, and assign them to the scheduler.

Is everything really that bad? Or am I doing everything wrong? I used the instruction both from IT sites and from the official Microsoft one. This is taking into account the fact that there are more typos in the tutorials on the Microsoft site than I had in the second grade.

We need a working version of how to make a normal answer file for WDS and how to enter a computer into the domain.

At the weekend, many computers will have to be entered into the domain remotely, and I can smell that it will be kabzdets.

Answer 1

If I remember correctly, the algorithm is as follows:
1. Install a clean OS
2. Roll everything, configure the minimum necessary, the drivers are there.
3. Seal the sys pep image
4. Restart and upload the image to WDS
5. Answer questions,
6. Publish the image to WDS.
7. Configure DNS, DHCP, Auto provisioning to work only with a couple of Mac addresses
8. Check it all on machines with poppies from step 7.
9. Enable for everyone.
I did this last time on XP, so I could forget something (