Wousje

i had the same error a few days ago. can't remember exactly when it occures. i can be wrong since im also pretty new to sccm but it seems like the communication isn't going as it should be. Do you use HTTPS or HTTP to let the client communicate with the DP? if it use HTTPS, try HTTP. Select HTTP in the MP and reinstall the dp and select the HTTP option and distribute the packages again. you could also try adding option 006 to the dhcp scope with the ip of the DNS server if the client can't ping to your FQDN. You can check it by enabling the Windows PE-Scratch, and press f8 when booting the client and type nslookup. If it doesn't find the dns server than try adding option 006 to the scope. and once again, im also pretty new so correct me if im wrong. I hope it helps. with kind Regards

hello again So i forgot to add the ip of the server with the DNS role to the scope. After i added option 006 with the ip adres of the DNS server, it went passed "Preparing network connection" i was able to choose a task sequence. When i choose one, it loads for a very short time, like 1 seconde,and after that i get this message: This task sequence cannot be run becouse the program files for (package id) cannot be located on a distribution point. For more information, contact your system administrator or helpdesk operator. So i tought hmmkay lets distribute that package and get the stuff working. but the distribution of the package keeps going. it has been on yellow for like 2/3 hours instead of red or green. what could be this problem? the package is called: Configuration Manager-clientpackage ( i use a dutch version of SCCM so the name can be a bit different). when i watch the status it says: content is being distributed to the distribution point. Can someone help me? Thanks in Advance

WOOHOO! I had some settings wrong on my dp. My dp was configured to let the clients comunicate with HTTPS. So the Clients probably couldn't respond. I reïnstalled the dp again with the HTTP option. And when i boot the client now, i get the SCCM background and stuff but after the "Windows is starting now" screen it suddenly reboots. going to search for some info now. thnx everyone

i have uninstalled the wds service and dp again. after a reboot i installed the dp with the pxe services. after a while my wds service started and made the remoteinstall folder. I distrubuted the images again and when i boot the client i get the following: Downloaded WDSNBP from (my wds&SCCM server ip) WDSNBP started using DHCP Referal. Contacting server: (my wds&sccm server ip) (Gateway: 0.0.0.0).. No response from Windows Deployment Services server. Launching pxeboot.com... Press F12 for network service boot.

Thanks for responding! Does that also work for SCCM 2012?

I uninstalled the DP and WDS service again, removed the Remoteinstall folder, and deleted the content in %windir%\temp . After a reboot i installed the PXE service in the DP. And when i reboot now, i get the message: PXE-E32: TFTP open timeout i've read somewhere that SCCM would make the Remoteinstall folder if you install the PXE service on the DP. But this folder hasn't be made yet. Does anyone know where this folder should be located? the previous Remoteinstall folder was located on my E: drive [Edit] The WDS Service doesn't start, becouse i got errors asking for images.

Hey everyone, I'm new to SCCM and i want to install a client with SCCM PXE. I've already installed SCCM. this is my setup: Server 1: WDS, SCCM, IIS, WSUS. (virtual server)Server 2: DHCP, DNS, AD DS And i want to install a client in Hyper-V. The problem is: Every time when i boot the client, it keeps asking me for a boot image in wds. When i add a boot image in WDS , it works. But i want it to use SCCM. i've tried a couple of things such as: - enable option 66 en 67 (ip adres of the wds server and the bootfile name: SMSBoot\x86\wdsnbp.com) - enable PXE in the DP - added images etc. - uninstalled wds and the DP, and after a reboot installed PXE in the DP Im searching for a solution pretty long now but i can't get it fixed. Does anyone know how to fix this problem?