1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Windows Deployment Services - Cannot get to boot menu

Discussion in 'Windows Home Server' started by Luke Chalmers, Aug 25, 2009.

  1. Hello,

    I have been trying to setup Windows Deployment Services and I have hit a
    wall and wondering if you can help.

    I have setup WDS on the W2K8 server. I have copied the boot.wim files and
    install files from a Vista SP1 DVD to get things going. To test the network
    boot to make sure that a client machine can connect to the WDS server, I took
    a XP machine, booted up via the network and it was able to contact the server
    and after I approved the connection from the WDS console, I was then able to
    get into the boot menu asking me to choose my language etc and select the
    install image.

    I then cancelled this, knowing that I was happy that this then worked and
    was then ready to sysprep my first image to be captured.

    The issue is, is now that I have approved the computer, I cannot get the
    client machine to get back into the boot menu again to allow me to choose my
    install image like I did before. This happens on another machine as well,
    boots up fine, can get into boot menu, cancel it, reboot and then nothing.

    I get the following error.

    ProxyDCHP did not reply to port 4011

    One reboot earlier it was fine, now it is not.

    I assume that now the machine has been approved that I cannot get back into
    the boot menu which I find strange. I not sure if this related to something
    being stored in some form of database in the remoteinstall folder.

    Has anyone else had this problem? I notice that WDS has an option to remove
    rejected objects, but it seems that I kind of need to same option for
    approved objects as well if this makes sense.

    Many thanks,

    Luke
     
  2. Tim Judd

    Tim Judd Guest

    Luke Chalmers wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hello,
    >
    > I have been trying to setup Windows Deployment Services and I have hit a
    > wall and wondering if you can help.
    >
    > I have setup WDS on the W2K8 server. I have copied the boot.wim files and
    > install files from a Vista SP1 DVD to get things going. To test the network
    > boot to make sure that a client machine can connect to the WDS server, I took
    > a XP machine, booted up via the network and it was able to contact the server
    > and after I approved the connection from the WDS console, I was then able to
    > get into the boot menu asking me to choose my language etc and select the
    > install image.
    >
    > I then cancelled this, knowing that I was happy that this then worked and
    > was then ready to sysprep my first image to be captured.
    >
    > The issue is, is now that I have approved the computer, I cannot get the
    > client machine to get back into the boot menu again to allow me to choose my
    > install image like I did before. This happens on another machine as well,
    > boots up fine, can get into boot menu, cancel it, reboot and then nothing.
    >
    > I get the following error.
    >
    > ProxyDCHP did not reply to port 4011
    >
    > One reboot earlier it was fine, now it is not.
    >
    > I assume that now the machine has been approved that I cannot get back into
    > the boot menu which I find strange. I not sure if this related to something
    > being stored in some form of database in the remoteinstall folder.
    >
    > Has anyone else had this problem? I notice that WDS has an option to remove
    > rejected objects, but it seems that I kind of need to same option for
    > approved objects as well if this makes sense.
    >
    > Many thanks,
    >
    > Luke<!--colorc--><!--/colorc-->

    Luke,

    Only thing I'm familiar with that uses ProxyDHCP is Dell's reimaging
    console for some of their PowerVaults. Do you use any of those devices?

    It kind of seems you have battling DHCP servers, and neither are
    authoritative. an Authoritative DHCP server will forcefully offer a
    lease, weather it belongs on that network or not.

    You might need to check to make sure you have no other workstations,
    servers, or NAS boxes in whatever shape offering DHCP when it's not
    supposed to.


    Good luck.
    --Tim


    --
    This posting is provided for you, from a fellow community member. Use
    at your own risk.
     

Share This Page