Hi all, still kinda new to SCCM, i'm learning the tricks of it during my internship. I need to implement OSD deployment into the production SCCM here in the company. I installed some driver packages and deployed them with the OSD, everything was working great. Now i return after the weekend and nothing works. I want to reboot the laptop that needs to receive the deployment, press F12 and choose network boot. I receive this msg: DHCP.... (getting ip, gateway is correct, etc) TFTP . PXE-M0F: Exiting Intel Boot Agent So i have handled some errors already like: open timeout or access violation things. But here i don't receive anything.. he just starts rebooting out of the blue. My PXESetup.log tells me pxe is installed correctly... Not sure where to start looking. Thanks in advance for your reply's!

Check the PXE Service Point and make sure that the extracted boot binaries from the boot image are resident (for either x86 or x64 boot images or both). These should be under the RemoteInstall\SMSImages\SMSPKG folder, I think. If all 5 or 6 files aren't there, you need to refresh the boot image on that PXE Service Point, restart WDS and try F12 again. HTH!

I just now noticed the \SMSBoot\... folders (x86,i64,x64) were empty so i ran this script: NET STOP WDSServer subinacl /subdirectories C:\Windows\Temp\*.* /Setowner=%USERNAME% SetACL.exe -on C:\Windows\Temp -ot file -actn rstchldrn -rst dacl,sacl NET START WDSServer Now the boot works but he instantly goes to loading abortpxe.com. I've done a clear latest pxe advertisement on the collection and it doesn't fix the problem.. Any ideas? This abortpxe.com problem occurs a lot in my opinion... Thanks for your reply!

That script looks like it's changing the permissions on the files in those folders, however, the files you need in those folders seem to be missing. If you refresh the boot images on that PSP and restart WDSServer, they should extract the necessary files to the SMSBoot folders. I'm not sure what causes the files to disappear, but I've seen it happen before many times! Refreshing boot images and restarting WDS always solved it for me.

That script looks like it's changing the permissions on the files in those folders, however, the files you need in those folders seem to be missing. If you refresh the boot images on that PSP and restart WDSServer, they should extract the necessary files to the SMSBoot folders. It seems to work though, i now have the needed folders added in SMSBoot, i've used this script a lot since it's a bug in SCCM 2007, when you reboot the SMSBoot is always empty. I'll try reinstalling WDS (in meanwhile some received a popup about a windows7 install... :/)

I see this message in SMS_PXE_SERVICE_POINT: The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned. Altho there is an advertisement towards the collection with this machine being inside it.

Do the machines that received the pop-up need to start their image in Windows 7? Are you capturing user data? If you're just imaging machines as if they're brand new, there's a way to get around the pop-up. As for the machine not having an advertisement, try updating that collection and refreshing it to see if the machine is still a member. That problem is a little puzzling - you could try creating a new collection with just that machine in it and advertise the TS to it.

It was more of a panic moment.. Since he wanted to distribute the package to every computer in the company, which is not what it should do. I now remade the advertisement to a specific collection, and the members is 1 computer with the mac address of the laptop i'm trying to boot. Isn't there a risk with reinstalling wds? Consequences for the rest of the server? Never uninstalled it before..

I have reinstalled the WDS role on the server, now i cant start it up anymore... I receive this error in my system event log: The Windows Deployment Services Server service terminated with service-specific error 3238199556 :/ Can anyone assist me on this one?

I have found a bit of a solution: - delete WDS - Remove the PXE Service Role (remove distribution points from the images, else you'll get an error saying something about distributed packages) - Reboot - Reinstall WDS (don't configure, just check if it boots! If it doesn't: a) wdsutil.exe /uninitialize-server b) wdsutil.exe /initialize-server /reminst:"x:\RemoteInstall" - Check if WDS is started - Reinstall the PXE role - Add the pxe share as distribution points to the images, remake the task sequence and advertisement Solution to previous problem, now i need to find an answer to my new problem: - error: No response from windows deployment Service Server Launching pxeboot.com... TFTP download failed He is loading WDSNBP but then he sais download failed further in the pxe boot... Anyone has some options?

Sorry for the delay getting back to you! If you're exepriencing an error with the TFTP download, take another look at the SMSImages folder to see if all 5 or 6 files are there in the x86 and x64 folders.

Weird thing now to be honest... I'm back to square.. Again i receive the error: DHCP ... (i get my correct IP's) TFTP . PXE-M0F: Exiting intel boot agent If i look at my RemoteInstall folder i now have an SMSBoot & a Boot.. In my WDS settings the files he's calling are the ones in the Boot folder... I'm really stuck :/