Hi Everyone, I have a switched network using CISCO switches and also CISCO CNR(Cisco Network Register 6.1) acting as DHCP on my network. I modified the policies for the scope where my clients are connected using PXE to obtain the SCCM and WDS images and i'm having the following error "PXE error = PXE-E32: TFTP open timeout" The networking guy told me that the clients using DHCP never tries to connect to the TFTP server on my SCCM and WDS server that are running on a different box than the CNR 6.1. Also i set the following parameters on my scope policy at the CNR 6.1 to the network segment where the clients are connected: [011] resource-location-server <ip address of my WDS & SCCM server> [067] boot-file <name of my .WIM image> [066] tftp-server <FDQN of my WDS & SCCM server> If there's more options to set in order to achieve the download of the images from the WDS & SCCM server? Could someone help? I'll appreciate your comments, Cordially, Oscar.

This isn't really a ConfigMgr question, it's really a Cisco question (or WDS question)more or less. (I didn't see where you mentioned using the PXE service point just WDS) I would be willing to bet almost everyone here is using Microsoft DHCP especially if they are using WDS but WDS does support non-microsoft DHCP as non-microsoft DHCP is mentioned in the WDS docs. Personally I would take baby steps here, first of all take as much stuff out of the equation as possible then work your way up. What I mean by that is if you are using PSP don't do that until you first get just WDS where the machine can at least get an IP address during a PXE boot then go back and add the PSP. Known issues with configuring Windows Deployment Services 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 will need to 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 subnet, then you will need to 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. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com.

This could actually be that the FTP Server Role Service was not installed as part of your IIS Installation...

Should not have to enable FTP during IIS configuration. Do you have IP helpers setup to direct your PXE clients to your WDS server? the DHCP Scope options are no longer applicable for WDS and can/should be removed.

the DHCP Scope options are no longer applicable for WDS and can/should be removed. You can use option 66/67 to point a client to the PXE service point (but that's not supported according to a kb article) OR you can use IPhelpers. Moving that thread to the OSD subforum, as it fits better there.

I had the same problem. I did checked on the latest changes i made to the server. I found out I just Installed the Hyper V with only one Physical NIC on my server. The Physical NIC loses the settings and are taken over by the virtual NIC which Windows uses normaly for both connections. If you use WDS and Hyper V make sure the server has more than one nic and that the one of them if not virtualized. It will fix the problem for you