none
need help : 2 PXE RRS feed

  • Question

  • Hi,

    before:

    PXE of WDS server 2003 served XP deployments and contained a boot image of MDT server.

    Altiris server provided PXE for Thin client deployments.

    Altiris PXE always took precedence of WDS's PXE. If both WDS and Altiris were up only Altiris was accessible.

    after:

    WDS 2003 was removed. I installed WDS services on Server 2008 DHCP server and place MDT boot image on it.

    PXE works fine and I can access my MDT images.

    The problem:

    after enabling PXE on DHCP server Altiris PXE not responding anymore.

    When I stop WDS service on DHCP server Altiris PXE still not accessible and as reported (I didn't check) DHCP not distributes IPs.

    Looks like DHCP is hardly dependent now on installed WDS.

    I guess there are some settings for detaching WDS (with it's PXE) from DHCP when stop WDS, leaving DHCP as it was before

    installation of WDS.

    Please provide help.

    Thx.


    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Friday, September 26, 2014 10:44 PM

Answers

  • DHCP should not be dependent on WDS. IF you disable WDS, and DHCP stops working, you have some other problem.

    You do not have to put WDS on the same server as DHCP. There are some *special* options required to make these two sevices co-exist, and it's *possible* that these services are conflicting with each other. (option 60 and 67?!?!) Can you separate them into three servers? DHCP/WDS/Altris? Does that work?


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, September 29, 2014 10:24 PM
    Moderator

All replies

  • DHCP should not be dependent on WDS. IF you disable WDS, and DHCP stops working, you have some other problem.

    You do not have to put WDS on the same server as DHCP. There are some *special* options required to make these two sevices co-exist, and it's *possible* that these services are conflicting with each other. (option 60 and 67?!?!) Can you separate them into three servers? DHCP/WDS/Altris? Does that work?


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, September 29, 2014 10:24 PM
    Moderator
  • > Can you separate them into three servers?

    I mentioned that they actually were separated.

    Altiris with it's PXE is usually down and is turned on rarely for couple of reimages.

    WDS was dedicated server for XP deployment. WDS became useless and suddenly it's PXE became not functional.

    So instead of troubleshooting PXE on old WDS I installed WDS service on DHCP server (2008), imported MDT boot image and it made a perfect job from first start. So I just eliminated old WDS with it's PXE.

    DHCP is daily backed up. So I have reliable PXE for MDT.

    What I am missing now is:

     Altiris PXE always took precedence of old WDS. So for WDS use, Altiris supposed to be down/disconnected.

    If you confirm (and I thought about this too) that there is no dependency between DHCP service and WDS on the same server it could be really other issue with DHCP server (I don't manage it but will check it because this situation was e-mailed to me).

    What is weird that now DCHP guy saying that when we stop WDS DHCP not works and sure a workstation cannot get a DHCP address for sending PXE request.

    And looks like that WDS's PXE 2008 takes precedence of Altiris PXE.

    Thanks for confirmation about DHCP and WDS coexistence.


    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Monday, September 29, 2014 10:58 PM
  • Hi there!

    My name is Randall and I am from Symantec. I read through this and see these issues in your environment:

    1. Interdependent DHCP & WDS issue: Not sure what is going on here.
    2. Competing PXE servers : This is known to be the way that PXE works. A machine when PXE booting will take the boot image from the first PXE server that responds to it.

    One things that muddies the waters a bit is this:

    “What is weird that now DCHP guy saying that when we stop WDS DHCP not works and sure a workstation cannot get a DHCP address for sending PXE request.”

    This looks like your are talking about stopping WDS for using the Altiris PXE (which is the right thing to do). Are you talking about the initial DHCP request for connecting with the TFTP server to get the boot image? Or is this about pulling a DHCP address in the automation environment? Does WinPE load, and in automation fail to have a valid IP? Or do we not get to that point? If you get to the automation environment, we may just need a network driver. If not, then you're back to the DHCP issue.

    Thank you,

    Randall Newnham

    Tuesday, October 7, 2014 4:27 PM
  • Randal thanks for answering...

    The question is not valid anymore since we'll not use anymore our Altiris that was used only for old models of THIN client. They are still in production. But in case of failure they will go straight to the recycle.

    WDS on DHCP server does perfect job. We have some complications with DHCP configuration because of weird request, but trying to bring it to clean function.


    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Tuesday, October 7, 2014 8:02 PM