Hi folks, I'm experiencing a really bonkers problem where I've created my usual CS.ini file on a brand new MDT deployment and it all works fine on VM's but NOT on physicals, where it seems to read some odd hybrid of the CS and the Boot.ini file. So all the automated sections of the CS.ini are ignored (the name just reverts to minint variable etc.. and for example the domain join screen is NOT skipped but in the greyed out section of the "Join a Domain" screen, I can that the account specified in the boot.ini file (for connection to the deployment share is being specified). If you progress through all the screens, the 21H1 image is deployed but it's not correctly named, domain joined etc..
I'm trying to rationalise what is happening here because in none of my previous MDT deployments, with other companies, have I witnessed such an odd issue. My understanding is that when the PXE boot is established with the MDT / WDS server, it is presented with the TS screen and when the desired image deployment TS is chosen, it reads the boot.ini to connect to the MDT share and find all it's scripts, including the CS.ini file in the Control folder ?
[1]: /answers/storage/attachments/120132-image.png