Welcome to Sign in | Join | Help
in
Home Blog Forums

Windows Deployment Services and Toolkit

Last post 10-08-2008, 1:51 PM by joec212000. 1 replies.

Sort Posts: Previous Next
  •  10-02-2008, 4:37 PM 2210

    Windows Deployment Services and Toolkit

    Hello all,

     

    I have a WDS server here that is setup in Mixed Mode. It currently pushes out both XP images that were conceived with RIS and a Vista Vanilla image. I have now loaded a new image using the deployment workbench which worked very well. I was able to add all of my applications and Hotfixes as well as all my drivers. All of this went pretty smooth and that is something to say when dealing with MS!!

    Anyhow this is where I am currently stuck. I PXE boot (F12) and all of my RIS and WDS images show up as they should (basically verifying that it (NIC) is going out to my WDS server to get image information). I then pick my new Vista image and wait for it to load.... wait for the new WDS wizard to start which it does. I then get the deployment screen. All is going according to plan at this point.... I check "Run deployment Wizard" which is checked by default and click the next button. Screen pops “Specify credentials for connecting to network share" with UserName\Password\Domain. I enter all the necessary info and get "invalid credentials, network path not found". I am using the domain admin account credentials. If I cancel out of that I get a "connection to \\server\distribution$ could not be made error" At his point I have checked the server logs...nothing. I have also tried to ping the server from the command prompt within the wizard and I don’t get a reply. The thing I don’t understand is how does it go off to the server and get the install files using the NIC card installed and then suddenly lose the connection and\or the drivers. I am certain that the drivers are installed and they are correct. ANY ideas would help at this point.

  •  10-08-2008, 1:51 PM 2228 in reply to 2210

    Re: Windows Deployment Services and Toolkit

    I've had this happen in my test lab.  Check the IP settings and make sure that the DHCP is sending the correct address, meaning that the IP address is in the correct subnet.  I had this exact problem and when i looked at the IP address issued it was for some reason picking up the wrong IP, I manually changed it to an IP address in the correct subnet and my credentials worked.  Sounds strange but may be worth looking into. Big Smile
    Joe G.
View as RSS news feed in XML


All postings are provided "AS IS" with no warranties, and confer no rights.
Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.