|
|
#1 (permalink) |
|
Guest
Posts: n/a
|
We are now in pre=production testing of SCCM 2007. This is our third
deployment of SCCM. So far we have never been able to get PXE to work in any of the environments. We use a centralized DHCP appliance. It gives out the correct IP and path for the PXE SP. When booting a system we get PXE-T04: Access violation. PXE-E36: Error received from TFTP server PXE-M0F: Exiting Intel PXE ROM I have done the WDS and PXE role remove/reinstall routine a number of times. It has not helped in any of the three deployments we tested. The above errors occur when we use the path smsboot\x86 or smsboot\x64 However if we move the files from x86 or x64 into smsboot then point at it with via DHCP the systems will boot, but never complete the OS install. Very curious, huh? It seems that something is missing, but I cannot figure out what. I am able to GET files from the directories via tftp so it is not a permissions issue. Suggestions anyone? Steve |
|
|
|
#2 (permalink) |
|
Guest
Posts: n/a
|
Hi,
To use osd in SCCM 2007 you need If DHCP and WDS are hosted on the same server you have to configure these options in DHCP Server : option 60 = PXEClient in WDS Server : disable listen on port 67 in mmc WDS console IF DHCP and WDS role are hosted on differents servers you have to configure this option in DHCP Server : option 66 = <Name of WDS server> |
|