It all started when the service stopped auto naming new clients. I found I could do accept and name, throw a gibberish name at it and click through the options. it would still error out, but the client would boot.
then I had to update drivers for a new client. At first it went through all the steps and appeared to work, but the client would not load the network drivers. finally i assumed my boot image was corrupt as I had had that happen a few times in the past. I build a new image and tried again. same results. I made a few other changes and then suddenly it began to error out during the driver add process telling me that "the system could not find the path specified". So now it will not even try.
We have tried removing the role, rebooting and re-adding the role. I wanted to create a new share but when i went to create the new folder on the existing E: it told me that share was already in use. yet when I pointed it back at the original folder it loaded and pulled all the default settings.
What are the proper steps for rebuilding WDS with a new share. did we miss a step the first time we tried to fix it? I think my "sever" with in the console is corrupt and needs to be done away with.
when i did the upgrade on this box from 2008 r2 to 2012 it allowed me to create a new folder with in the E: and then i brought all my images and drivers across. I am OK with rebuilding my driver pool at this point but of course I need to retain my images. Should i clear the E: drive off and reformat it? all that is on there is WDS stuff.