DHCP and PXE on same Windows 2003 Server
I'm try hard to get DHCP and PXE to paly nice on the same box. I tried the registry change but it didn't seem to work. I tried to run " WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes " But I get an error: C:\Documents and Settings\jenkindladmin>WDSUTIL /Set-Server /UseDHCPPorts:No /DH CPOption60:Yes Windows Deployment Services Management Utility [Version 6.0.6000.16386] Copyright (C) Microsoft Corporation. All rights reserved. An error occurred while trying to execute the command. Error Code: 0xC1030104 Error Description: The Windows Deployment Services server role has not been conf igured on the server. I've tried removing PXE but that does not seem to have worked. Can someone direct me to what I'm doing wrong? I've read tons of posts all pointing to this article: http://technet.microsoft.com/en-us/library/bb680753.aspx
July 21st, 2010 8:39pm

does the following help ? http://www.windows-noob.com/forums/index.php?/topic/93-windows-deployment-services-wds/ My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2010 10:37pm

no it doesn't unfortunatly.
July 21st, 2010 10:58pm

I figured out the problem. The instructions appear to be for Windows 2008 maybe. On Windows 2003 I had to add option 60. It's confusing because option 60 isn't available in the GUI. Apparently disappeared around Windows 2000. I used the netsh commands and everything started working. C:\WINDOWS\system32>netsh netsh>dhcp netsh>dhcp>server \\<server_machine_name> netsh dhcp>add optiondef 60 PXEClient String 0 comment=PXE support netsh dhcp>set optionvalue 60 STRING PXEClient netsh dhcp>exit I applied the registry cahnge: I'm not sure if the registry setting for PXE was necessary. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE Set the registry value to: UseDHCPPorts = 0
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2010 11:07pm

hi, In My SCCM i was trying to enable OSD .but unfortunatly i am facing some issue in PXE BOOT in the DHCP server option . so that i reffed so many articles for finally i got your reply it was quite confusing in the 3 step kindly please specify the step 3 (server \\<server_machine_name>) what should i give first entry 1)C:\WINDOWS\system32>netsh 2)netsh>dhcp 3)netsh>dhcp>server \\<server_machine_name> 4)netsh dhcp>add optiondef 60 PXEClient String 0 comment=PXE support 5)netsh dhcp>set optionvalue 60 STRING PXEClient 6)netsh dhcp>exit i tried this much C:\Documents and Settings\Administrator>netsh netsh>dhcp netsh dhcp>server\\drdo-qqluvgdi0p The following command was not found: server\\drdo-qqluvgdi0p. netsh dhcp>cabsint\\drdo-qqluvgdi0p The following command was not found: cabsint\\drdo-qqluvgdi0p netsh dhcp>cabsint\\drdo-qqluvgdi0p The following command was not found: cabsint\\drdo-qqluvgdi0p netsh dhcp>server\\192.168.1.65 The following command was not found: server\\192.168.1.65. netsh dhcp>server\\192.168.1.65 The following command was not found: server\\192.168.1.65. netsh dhcp>\\192.168.1.65 The following command was not found: \\192.168.1.65. netsh dhcp>
May 18th, 2011 5:48am

Sounds like the server isn't found. What happens when you ping drdo-qqluvgdi0p? Just to verify did you put a space between the server and the \\? "netsh dhcp>server \\drdo...."David Jenkins
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 9:34am

Sounds like the server isn't found. What happens when you ping drdo-qqluvgdi0p? Just to verify did you put a space between the server and the \\? "netsh dhcp>server \\drdo...."David Jenkins
May 18th, 2011 9:34am

hi, In My SCCM i was trying to enable OSD .but unfortunatly i am facing some issue in PXE BOOT in the DHCP server option . so that i reffed so many articles for finally i got your reply it was quite confusing in the 3 step kindly please specify the step 3 (server \\<server_machine_name>) what should i give first entry 1)C:\WINDOWS\system32>netsh 2)netsh>dhcp 3)netsh>dhcp>server \\<server_machine_name> 4)netsh dhcp>add optiondef 60 PXEClient String 0 comment=PXE support 5)netsh dhcp>set optionvalue 60 STRING PXEClient 6)netsh dhcp>exit i tried this much C:\Documents and Settings\Administrator>netsh netsh>dhcp netsh dhcp>server\\drdo-qqluvgdi0p The following command was not found: server\\drdo-qqluvgdi0p. netsh dhcp>cabsint\\drdo-qqluvgdi0p The following command was not found: cabsint\\drdo-qqluvgdi0p netsh dhcp>cabsint\\drdo-qqluvgdi0p The following command was not found: cabsint\\drdo-qqluvgdi0p netsh dhcp>server\\192.168.1.65 The following command was not found: server\\192.168.1.65. netsh dhcp>server\\192.168.1.65 The following command was not found: server\\192.168.1.65. netsh dhcp>\\192.168.1.65 The following command was not found: \\192.168.1.65. netsh dhcp>
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 12:42pm

hi, In My SCCM i was trying to enable OSD .but unfortunatly i am facing some issue in PXE BOOT in the DHCP server option . so that i reffed so many articles for finally i got your reply it was quite confusing in the 3 step kindly please specify the step 3 (server \\<server_machine_name>) what should i give first entry 1)C:\WINDOWS\system32>netsh 2)netsh>dhcp 3)netsh>dhcp>server \\<server_machine_name> 4)netsh dhcp>add optiondef 60 PXEClient String 0 comment=PXE support 5)netsh dhcp>set optionvalue 60 STRING PXEClient 6)netsh dhcp>exit i tried this much C:\Documents and Settings\Administrator>netsh netsh>dhcp netsh dhcp>server\\drdo-qqluvgdi0p The following command was not found: server\\drdo-qqluvgdi0p. netsh dhcp>cabsint\\drdo-qqluvgdi0p The following command was not found: cabsint\\drdo-qqluvgdi0p netsh dhcp>cabsint\\drdo-qqluvgdi0p The following command was not found: cabsint\\drdo-qqluvgdi0p netsh dhcp>server\\192.168.1.65 The following command was not found: server\\192.168.1.65. netsh dhcp>server\\192.168.1.65 The following command was not found: server\\192.168.1.65. netsh dhcp>\\192.168.1.65 The following command was not found: \\192.168.1.65. netsh dhcp>
May 18th, 2011 12:42pm

Thanks for your reply, problem solved with server ip instead of trying server name
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2011 1:17am

Thanks for your reply, problem solved with server ip instead of trying server name
May 19th, 2011 8:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics