- This topic is empty.
-
Posts
-
We have a WDM server installed and plan to implement the XPe V90L thin clients.
I understand that in order to image the thin clients they must PXE boot which is initiated from WDM.
I have the SP2 image for the V90L installed on the WDM server and is available to be deployed.
Our dhcp server currently has basic default options such as domain name, gateway options etc.Are there any DHCP options that I need to add to tell the clients where to PXE boot from?
The documentation is quite confusing as some docs state that options 186, 190 and 192 are required, others say option 66.
Can anybody tell me the exact DHCP options that are required on a microsoft 2003 dhcp server?
The WDM server has the DHCP proxy option selected, is this correct or should it be disabled?
Many thanks!
Andy
In the first step you do NOT need any DHCP option tags. WDM and its DHCP Proxy will take care of this.
186 is very useful for letting the units know where the WDM server is located. But this is only working with latest XPe WDM agents of 4.7.1 version.Don’t configure 66 at all.
CG
I have S90’s running XPE and am running into a similar problem with not knowing what I need…
I am seeing devices populate but PXE capable is showing as no.
If I right click and choose “refresh device information” I see PXE cable show as yes for about 10 seconds.
I have installed a new WDM here in my test lab and have been able to “replicate” the problem but cannot find the solution… I have old images from 2005 (2.20355, 3.04096) on the devices in the field and a new 5.010607 image in our test lab.
It happens for both the contract deployed WDM and the one in here in my test lab.
I am not hosting DHCP from the WDM in the test lab or onsite.
I configured Option Tags 186 and 192 here in the test lab.
Please help!
When the clients start, do you see a PXE response at the beginning? Is this 100% from the WDM server or is there a different PXE server in your LAN?
CG
It doesn’t receive a response during boot, it just says booting from localboot.
We have no other PXE servers on our network.
@ConfGen wrote:
In the first step you do NOT need any DHCP option tags. WDM and its DHCP Proxy will take care of this.
186 is very useful for letting the units know where the WDM server is located. But this is only working with latest XPe WDM agents of 4.7.1 version.Don’t configure 66 at all.
CG
I have a follow-up question to this. If there is more than one PXE-capable solution in an Enterprise environment, would the DHCP Option Tag 186 be preferable than multiple IP Helper statements?
OT 186 will not help at all in a multi PXE environment.
WDM will always only answer units that are known to WDM. So it will not interfer with any other PXE solution. But other PXE solutions are answering every PXE request and therefore stop WDM from working. Try to make an exclusion list in the PXE servers to prevent this.If the client just says “Localboot” at teh beginning it actually gets a response from the WDM server. But this answer means that there is no package for that client.
Can you clean out every job in the schedulded packages list and try with a brand new job?CG
- You must be logged in to reply to this topic.