![]() The server essentially logs nothing about the install so is useless for troubleshooting. I tried using the ISO and a floppy image to test the xml and I found that I get no errors at all unless I use the name autounattend.xml in which case it produces a 0x000005 access violation error code with no useable information. I created a separate partition for the images and the autounattend.xml is in E:\RemoteInstall\WdsClientUnattend\autounattend.xml Here is the XML: (could not post here said it looked like spam) Įach time it runs I get to the point of picking the locale and keyboard input language like the autounattend.xml is being completely ignored. The client (which is booting in UEFI Mode) picks up the lease from dhcp, pulls the initial boot stage files and the Server 2019 install starts, by starts I mean it asks me to pick the locale and keyboard input method despite having linked the autounattend.xml to the install image in WDS as well as in the architecture within WDS (server, properties, clients). ![]() I have spent a good number of hours on this and due to the massive amount of links to Windows 7,8,10 and older server versions essentially crowding the search results I am not able to find my way forward on this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |