WDS वास्तव में काफी एक अमित्र प्रणाली है. भद्दा, बारीकियों, बिना उपयोगी त्रुटि जानकारी और प्रवण OT विफलता. मेरी पहुंच से बाहर फ़ाइलों में से कुछ अद्यतन करने के बाद मैं अब पहुंच से बाहर प्रतिष्ठानों बाहर ले जाने में सक्षम था, लेकिन अंत में भ्रामक त्रुटियों की श्रृंखला समाधान कर लिया है
मैं कम से कम था 3 different errors, जिनमें से सभी संबंधित होने लगते हैं. I am using my WDS server without a domain, but as I want to use multiple images (जीत Dows 7 और खिड़कियां 10) and I want them to be unattended, I need multiple unattend files.
There is an unattend file for the PXE boot stage which sets things like partitions, और जहां मैं चयन जो छवि मैं स्थापित करना चाहते हैं. This is linked to the WDS server to make it work with the PXE boot. There have been no problems with this part. इस फ़ाइल में autounattend.xml नामित हो जाता है के बाद आप इसे सर्वर से लिंक कर लिया है
Then each image has an unattend file which gets renamed to ImageUnattend.xml and gets put inside the appropriate image folder. यह वह जगह है जहाँ मैं समस्याओं मारा.
Several key things before you start which will help reduce problems.
1. Do not edit the files in the locations the server puts them. keep a copy somewhere else, कि प्रतिलिपि संपादित, and then relink them to the server through the WDS interface
2. Restart the WDS server after relinking the unattend files
3. Think about the permissions on the RemoteInstall share — by default these may not work for non-domain systems. मैं मेरा बदलना पड़ा
Despite having done all of these things I still got a couple of errors. The first was that my second unattend file just seemed to be completely ignored! मैं लॉग फ़ाइलों में देखा और एक त्रुटि पाया Failed to process client unattend variables. Error code [0x8007000D]
. I assumed this was caused by a misconfiguration somewhere, but after generating a new unattend file with Windows Answer File Generator (an online service) I then got a new error that setup couldn’t continue due to a problem with the answer file. So despite the error logs indicating that my unattend file couldn’t be accessed at all, यह वास्तव में पहुँचा जा सकता है, so the fault must have been with the contents of the file.
इसलिए मैं अब था 2 फाइलें, न तो काम किया, but both had different errors!
I went back to my original file and remove some of the content and tried again. इसने काम कर दिया! A copy of that file is at the bottom of this post.
I now had to figure out what the problem was with my original 2 files…
The easiest of the 2 was the file generated by the online service. यह एक उत्पाद कुंजी शामिल, but the product key must be a trial key for a retail or oem version of windows 7, and the version I have uses a MAK key. आप ऑनलाइन जनरेटर से एक जवाब फाइल का प्रयोग करता है, तो सुनिश्चित करें कि आप उत्पाद कुंजी परिवर्तन करना
The issue with my original file were some comments that had been put in it. I don’t know how or when they got there but once removed it worked as expected so make sure you don’t have any comments in your file.
“Hi James I realise it has been a long while, but I just checked this on windows 11 (build 23H2)…”