Thanks for the feedback Chris. No one should have been accessing WDS at the time we updated WDS with the new boot WIMs. I was working with the site administrator helping him add an older model laptop (a Lenovo) to MDT so he can image it. It would not load the WinPE boot image. It gave a TFTP time out error. I have seen this twice before. When I went to remove the WDS server and then re-add it, that is when I got the windows Deployment Service is corrupt message.
I have searched the internet and found lots of documents, blogs, and videos on what to do, but quite frankly, a lot of them seem incomplete or they contradict each other. Which brings me to you guys and gals. So if I am understanding this right, I am doing this correctly and not missing a step? Thanks in advance, Dave Landry From: [email protected] [mailto:[email protected]] On Behalf Of Chris Catlett Sent: Tuesday, February 17, 2015 7:08 PM To: [email protected] Subject: Re: [MDT-OSD] WDS getting corrupt if someone was booting to that wim during the replace, it could do bad things. ________________________________ Hi Everyone, I am new to administrating to MDT and have encountered a problem 3 times. I am curious if I am doing something wrong. The problem is, is when I add drivers to the Out-of-Box Drivers folder, WinPE, I update the deployment share to generate new boot WIMS. I then import then into WDS > Server>Boot folder by choosing the replace option for each x86 and x64 wim. I am not shutting the WDS service down … or anything else. I am supporting servers worldwide and on 3 occasions we could no longer boot into MDT even though 5 mins earlier we could. I then get an error saying Windows Deployment Service is corrupt and I am not able to recover from it even after running the commands to uninitialized and initialize the server. Is this just bad luck or am I not doing something correctly and breaking WDS? I am left having to remove WDS from the server, reboot and reinstall WDS to get it to work. Regards, Dave Landry
