XistEnCe Posted January 20, 2011 Report post Posted January 20, 2011 Hi! I've just installed SCCM2007R3 with FEP2010. I'm trying to configure everything and get this show on the road - but..... When booting, the clients just wait for DHCP from the PXE server, and times out. Does the PXE boot, require the WDS service? Or is this optional? The server running SCCM is also a DHCP server, and I have defined a boundary which contains the net in the DHCP scope. Do I have to advertise anything for it to PXE boot? Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 When trying to run the commands on the page you linked me - I get the error: >WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption 60:Yes Windows Deployment Services Management Utility [Version 6.1.7600.16385] Copyright (C) Microsoft Corporation. All rights reserved. An error occurred while trying to execute the command. Error Code: 0xC1030104 Error Description: The Deployment Server role service for Windows Deployment Ser vices has not been configured on the server. This is after a fresh install of WDS and PXE Role in SCCM. Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 21, 2011 Report post Posted January 21, 2011 Then it first needs WDS Configured.... you could use this commandline for that: WDSUTIL /initialize-server /REMINST:"<DriveLetter>:\RemoteInstall" Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 Ran the above command, and now the previous one worked! I booted up a client and tried to PXE boot it, but its taking forever to fetch DHCP (and it fails at the end). With: PXE-E55 Proxy DHCP Service did not reply to request on port 4011. I haven't defined the #67 rule, in DHCP - could this be the problem? (As no files exists on the shares..) Quote Share this post Link to post Share on other sites More sharing options...
0 Eswar Koneti Posted January 21, 2011 Report post Posted January 21, 2011 Ran the above command, and now the previous one worked! I booted up a client and tried to PXE boot it, but its taking forever to fetch DHCP (and it fails at the end). With: PXE-E55 Proxy DHCP Service did not reply to request on port 4011. I haven't defined the #67 rule, in DHCP - could this be the problem? (As no files exists on the shares..) If Microsoft DHCP is installed on the same physical computer as Windows Deployment Services, the WDS configuration wizard does the following (if you configure Windows Deployment Services by using WDSUTIL, you have to manually make these changes): Adds DHCP option tag 60, with the PXE client setting selected, to all DHCP scopes (as a DHCP global option). This is necessary so that a booting PXE client can be notified that there is a listening PXE server on the network. Selects the Do Not Listen on port 67 option. This is necessary so that booting clients can find the DHCP server on the network. [*]If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you must use your DHCP tools to add Option 60 to their DHCP scopes.[*]If DHCP is installed on a server that is located in a different sub-net, then you must do one of the following: Recommended: configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts). Add DHCP options 66 and 67. For more information, see the PXE Boot chapter at http://go.microsoft.com/fwlink/?LinkId=88439 Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 21, 2011 Report post Posted January 21, 2011 If Microsoft DHCP is installed on the same physical computer as Windows Deployment Services, the WDS configuration wizard does the following (if you configure Windows Deployment Services by using WDSUTIL, you have to manually make these changes):Adds DHCP option tag 60, with the PXE client setting selected, to all DHCP scopes (as a DHCP global option). This is necessary so that a booting PXE client can be notified that there is a listening PXE server on the network. Selects the Do Not Listen on port 67 option. This is necessary so that booting clients can find the DHCP server on the network. [*]If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you must use your DHCP tools to add Option 60 to their DHCP scopes.[*]If DHCP is installed on a server that is located in a different sub-net, then you must do one of the following: Recommended: configure your IP Helper tables. All DHCP broadcasts on UDP port 67 by client computers should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server. Also, all traffic to UDP port 4011 from the client computers to the Windows Deployment Services PXE server should be routed appropriately (these requests direct traffic to the server, not broadcasts). Add DHCP options 66 and 67. For more information, see the PXE Boot chapter at http://go.microsoft.com/fwlink/?LinkId=88439 Thanks for the reply! I've done the above - except the #67, as my shared folders do not contain any linkable files. If I have to put the files there myself, where would I get them from? The microsoft link you put up, doesn't go anywhere (even without the trailing . ). Still no luck in getting the clients to PXE boot.. Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 21, 2011 Report post Posted January 21, 2011 Did you now already got the 060 option fixed? Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 22, 2011 Report post Posted January 22, 2011 Did you now already got the 060 option fixed? Yeah! That option came when I configured the WDS Role. 060 is set to "PXEClient" now. 066 is set to the IP of the server and 067 is set to blank for now. Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 22, 2011 Report post Posted January 22, 2011 Ok, only the 060 option is enough. Now make sure you advertise a Task Sequence to a collection with your computer in it and make sure the Bootimages etc. exist on the DP(s). Quote Share this post Link to post Share on other sites More sharing options...
0 XistEnCe Posted January 22, 2011 Report post Posted January 22, 2011 Ok, only the 060 option is enough. Now make sure you advertise a Task Sequence to a collection with your computer in it and make sure the Bootimages etc. exist on the DP(s). I don't get any other reply from the PXE other than the PXE-E53. I should be able to connect to it, and it should load without the advertisment - yes? As it does so with a boot-cd or usb stick, but then gives me the error that it doesn't have a TS-advertisement. Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted January 23, 2011 Report post Posted January 23, 2011 AFAIK I would say that you have to advertise a Task Sequence to a collection with the machine in it. Quote Share this post Link to post Share on other sites More sharing options...
Hi!
I've just installed SCCM2007R3 with FEP2010.
I'm trying to configure everything and get this show on the road - but.....
When booting, the clients just wait for DHCP from the PXE server, and times out.
Does the PXE boot, require the WDS service?
Or is this optional?
The server running SCCM is also a DHCP server, and I have defined a boundary which contains the net in the DHCP scope.
Do I have to advertise anything for it to PXE boot?
Share this post
Link to post
Share on other sites