Hi everyone, I have one physical server running SCCM, WDS and DHCP. When server start DHCP is not working because it cannot bind to NIC which is used by WDS. The workarround for that is to stop DHCP, thenstop WDS. Start DHCP and start WDS. DHCP and PXE start working but I'm getting loads of WDSServer 769 errors in event log. The WDSUTIL /set-server /UseDHCPPorts:No /DHCPOption60:yes does not work because WDS is not configured. Can anyone give me a hint how to solve this ? Thank you

Hello When you setup your sever did you read the document at the following location: http://technet.microsoft.com/en-us/library/bb680753.aspx Please let me know if you followed these steps. Thanks, Dan

This problem is RUINING my life right now. Directions have been followed. The document says the following: You must have a functioning DHCP server with an active scope. WDS will utilize PXE which requires a DHCP server. Whether you plan to co-host WDS and DHCP on the same server or use two different servers you must configure WDS to listen on a specific port. DHCP and WDS both require port number 67. If you have co-hosted WDS and DHCP you can move DHCP or the PXE site role to a separate server or use the procedure below to configure the WDS server to listen on a different port. Modify the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE Set the registry value to: UseDHCPPorts = 0 For the new configuration to take effect run the following command on the co-located DHCP and WDS server: WDSUTIL /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes So, you try and run the command line and you can't because your WDS server is not configured. According to the SCCM docs, you are not supposed to configure WDS, so how is that ever supposed to work? An explanation would be lovely...

any solution for this already?

wdsutil /initialize-server /reminst:G:\RemoteInstall Run that before the other wdsutil command line, fixes everything. Here is a good reference: http://netsaber.wordpress.com/category/sccm-2007/

[Hax Paul, SMS\SCCM consultant Hax70738@aol.com] SCCM V2 and WDS\PXE If you have Pixie service points set up then delete them. If you have WDS installed then delete it. Delete the Remoteinstall directory which WDS creates. On your DHCP server, if your WDS server is on your DHCP server setup option 60,66 and 67. If your WDS is not or it is on your SCCM server, only setup up option 66. [Client will be directed to WDS server with option 66, no other option is needed if WDS is on your SCCM server. WDS runs wdsnbp.com from SMSboot\x86/x64\wdsnbp.com and validates DHCP response and downloads PXEboot.com. PXEboot, tell client to press F12. F12, Bootmgr read the BCD and downloads Boot.sdi and WinPE.wim.] Follow these steps to install SCCM V2 and WDS\PXE Install WDS and reboot as requested by install. Open WDS and you will see an amber icon on it. This is to show that the WDS service has not started and it has not been configured. Many people will say DO NOT configure WDS and SCCM will do it all, this is completely wrong. You MUST configure it, because when it is configured it starts the WDS service and put the RemoteInstall directory on the server. Configure WDS and set the drive for the RemoteInstall directory and set the clients to respond to all Pixie requests. Check that the Remote Install directory is there. When you finish the WDS configuration there will be an end point error, you can ignore this. You will now find the WDS server service started and a green icon on the WDS console. In SCCM setup go to Site Systems and set up new component roles for your SCCM, setup the Pixie service point roles. When this is finished you will find it will populate the Remoteinstall directory with items such as SMSBOOT etc. This is the most important and where everyone gets it wrong. Your TFTP, wdsnbp.com and PIXIE boot files all need to be added by SCCM, the standard WDS ones will not do. Go back into WDS configuration and setup you boot configuration. Direct your x86 and x64 default boot programs at SMSboot\x86\wdsnbp.com. You must direct x64 at the same x86\wdsnbp.com file also. On SCCM you will have new pixie distribution points setup for pixie, send your boot images to these pixie distribution points, x64 and x86. For new machines set up a mandatory advert for All Unknown Computers. Check the Mac address of the machine you want to test in a MAC query to make sure it has never been seen by SCCM. If it has delete the object with that MAC address. Pixie boot the machine and you will have SCCM, bare metal machines working a treat on SCCM V2. Hax Paul

silly question on my part. when you change the registry value does it have to be 0 (zero) in order to use port 67.Thanks

Hey Everybody, I thought I'd help the community 'cause i had enough of troubleshooting OS Deployment in SCCM. That being said it's really easy once you know how. Hax Paul, great post man learned a lot from your post there is however a small error which i thought i'd point out for your benefit and the benefit of others. Error: "Many people will say DO NOT configure WDS and SCCM will do it all, this is completely wrong. You MUST configure it, because when it is configured it starts the WDS service and put the RemoteInstall directory on the server." You dont' have to configure it but there is no harm done configuring it the way you've mentioned after all sccm was made to make things easy. But there is a particular order you need to follow if your not planning on configuring WDS. WDS should be in a different server other than the DHCP server (If not you will have to configure it slightly) Order : 1. Install WDS and do nothing to it. 2. Configure PXE Service Point in SCCM Server 3. Give it 5 -10 mins and it will start Windows Deployment Service as well as create the very important folder RemoteInstall. If followed correctly, You don't need to configure anything on DHCP. You don't need to configure anything on WDS. If WDS is on the same server as DHCP you will have to configure it just a little bit. Namely, Tick Both DHCP Tab Do not listen on port 67 Configure DHCP option 60 to PXE Client ( This will add the DHCP Configuration needed automatically) Pxe Response Settings Tab -Respond to all known an unknown clients Response Delay to 0 Thats it if my memory Serves me right but before doing any of this do the follwing. 1. Create a Collection in SCCM 2. Create an Association and give it the new machines Mac Address (Double CHeck the mac v.important) 3. Add Network Drivers to Boot images enable command line support for trouble shooting and Distribute both Boot images (x64 and x86) to both distribution shares (Package and PXE) 4. Operating System need not be sent to the pxe distribution share the standard distribution share would do. 5. Make sure SCCM Client is also properly distributed the share if using in the task sequence 6. Advertise Task Sequence to pxe and show correct collection say immediately ( Note No matter what you do the OS deployment advertisement will only run once so if you ruin it the first time re advertise it) 7. After booting onto pxe you might still run into issues den press f8 and go to the following and see the log (smsts.log) to do this you will need to open it through notepad x:\Windows\Temp\SMSTSLog\notepad smsts 8. When in pxe the first thing you should check is network connectivity do this by typing ipconfig /all and if you have an IP u're ok if not download correct drivers and apply it to the boot images. 9. If they say wdi.dll is missing check the boot images and remove all other drivers other than the network drivers and redistribute and if it still doesn't work follow steps in http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/5cc6c8a0-2aa9-4929-9722-7480f343dd21/ your network driver might be causing issues 10.If its an issue with access check the distribution folder permissions and check network access account if all is ok redistribut the packages and you could also check the boundary is set correctly. I Hope this helps someone, if i've made a mistake please do correct me and thanks again to Hax Paul for that wonderful article.

I have a cisco call manager using DHCP option 66, I was wondering if I could enter in multiple ip's in the same field.

i think this problem is because of wds and dhcp being on the same system....wds & dhcp both try to use the same port which is port 67 .... 1> go to WDS properties. 2>then to dhcp tab. 3>check the option to "do not listen to port 67" in the dhcp tab of WDS. now restart the dhcp and wds services.

Never configure WDS just use registy to force WDS PXE Service NOT to use same ports as DHCP... Leave SCCM PXE Service intact and also I had to manually add PXE option 60 to DHCP server options using netsh command (you can Google this easily). After that, just restart the server... You'll se that WDS service is now starting without problems and that it has also change the startup type to Auto. Hope this explains... P.S.: Yes! Do not touch, initialize, or configure WDS in ANY way when using SCCM.I've seen things you people wouldn't believe...