0विंडोज़ 8 प्रतीक चिन्हअधिक WDS त्रुटियों हल

WDS वास्तव में काफी एक अमित्र प्रणाली है. भद्दा, बारीकियों, बिना उपयोगी त्रुटि जानकारी और प्रवण OT विफलता. मेरी पहुंच से बाहर फ़ाइलों में से कुछ अद्यतन करने के बाद मैं अब पहुंच से बाहर प्रतिष्ठानों बाहर ले जाने में सक्षम था, लेकिन अंत में भ्रामक त्रुटियों की श्रृंखला समाधान कर लिया है

मैं कम से कम था 3 dif­fer­ent errors, जिनमें से सभी संबंधित होने लगते हैं. I am using my WDS serv­er without a domain, but as I want to use mul­tiple images (जीत Dows 7 और खिड़कियां 10) and I want them to be unat­ten­ded, I need mul­tiple unat­tend files.

There is an unat­tend file for the PXE boot stage which sets things like par­ti­tions, और जहां मैं चयन जो छवि मैं स्थापित करना चाहते हैं. This is linked to the WDS serv­er to make it work with the PXE boot. There have been no prob­lems with this part. This file gets named autounattend.xml after you have linked it to the serv­er

Then each image has an unat­tend file which gets renamed to ImageUnattend.xml and gets put inside the appro­pri­ate image folder. This is where I hit prob­lems.

Sev­er­al key things before you start which will help reduce prob­lems.

1. Do not edit the files in the loc­a­tions the serv­er puts them. keep a copy some­where else, कि प्रतिलिपि संपादित, and then relink them to the serv­er through the WDS inter­face
2. Restart the WDS serv­er after relink­ing the unat­tend files
3. Think about the per­mis­sions on the RemoteIn­stall share — by default these may not work for non-domain sys­tems. मैं मेरा बदलना पड़ा

Des­pite hav­ing done all of these things I still got a couple of errors. The first was that my second unat­tend file just seemed to be com­pletely ignored! मैं लॉग फ़ाइलों में देखा और एक त्रुटि पाया Failed to process client unattend variables. Error code [0x8007000D]. I assumed this was caused by a mis­con­fig­ur­a­tion some­where, but after gen­er­at­ing a new unat­tend file with Win­dows Answer File Gen­er­at­or (an online ser­vice) I then got a new error that setup could­n’t con­tin­ue due to a prob­lem with the answer file. So des­pite the error logs indic­at­ing that my unat­tend file could­n’t be accessed at all, यह वास्तव में पहुँचा जा सकता है, so the fault must have been with the con­tents of the file.

इसलिए मैं अब था 2 फाइलें, न तो काम किया, but both had dif­fer­ent errors!

I went back to my ori­gin­al file and remove some of the con­tent and tried again. इसने काम कर दिया! A copy of that file is at the bot­tom of this post.

I now had to fig­ure out what the prob­lem was with my ori­gin­al 2 files…

The easi­est of the 2 was the file gen­er­ated by the online ser­vice. यह एक उत्पाद कुंजी शामिल, but the product key must be a tri­al key for a retail or oem ver­sion of win­dows 7, and the ver­sion I have uses a MAK key. Make sure you change the product key if you use an answer file from the online gen­er­at­or

The issue with my ori­gin­al file were some com­ments that had been put in it. I don’t know how or when they got there but once removed it worked as expec­ted so make sure you don’t have any com­ments in your file.

तुम क्या सोचते हो? हमें एक टिप्पणी के नीचे छोड़! आप सदस्यता के लिए चाहते हैं, तो ऊपर दाईं ओर मेनू पर लिंक का उपयोग करें सदस्यता लें. आप भी नीचे सामाजिक लिंक का उपयोग करके अपने दोस्तों के साथ इस साझा कर सकते हैं. चियर्स.

उत्तर छोड़ दें