SCCM 2007 R3 OSD PXE Troubleshooting

I’ve had a heck of a time learning SCCM 2007 R3. There’s a –ton- of little “gotchas” and unintuitive issues with operating system deployment, task sequence advertisement, windows deployment server guid caching, etc. It’s an incredible program but it takes some getting used to. Fortunately, after about 2 weeks of work it’s starting to make sense and come together into something beautiful. Here are some of my relatively unstructured notes on troubleshooting OSD PXE issues.

General OSD Troubleshooting

  • On your boot image, enable the command prompt. After an error, press F8 to bring up the command prompt. Then it’s possible to ‘net use’ a file server share and copy the client logs. Also, the TS usually logs to the server under “System Status” -> “Advertisement Status” ->  AdvertisementName -> Site name. You can right-click the site and select “Show Messages”.
  • The OSD logs are stored on the client system at “X:\Windows\Temp\SMSLogs\smslog.log”
  • When looking through the client logs, searching for “_SMSTSCurrentActionName” will show you the corresponding task sequence steps.

Error – Task Sequence Action Format Drive fails with HRESULT=8004####

  • Deleting the TS advertisements, the TS itself, then recreating the TS and re-advertising cleared this for me.

Error – Multicast fails

I haven’t yet found a workaround.

General PXE Troubleshooting

  • In the SCCM console, check System Status -> Site Components -> PXE.
  • Also, Component Health -> PXE.

Error – PXE Stops Working (no dhcp or proxyDHCP offered)

  • Sometimes this happens while distributions are happening to the site; waiting fixes it.
  • Sometimes this happens if your system was deleted from the SCCM database, in which case you need to target the advertisement to the, “Unknown Computers” collection.
  • Check that the WDS Service is running on your PXE point.
  • Clear the PXE Advertisement list for the collection (right click on the collection -> Clean Last PXE Advertisement…)
  • Restart the WDS Service to clear it’s GUID cache.
  • Check that the machine you’re PXE booting has an advertisement associated with it. (software distribution -> advertisements).
  • If the machine you’re PXE booting is unknown, make sure it’s actually not in a collection already and that unknown computers has an advertised task sequence.
  • If you just deleted the machine from your database to make it unknown, you must clear the advertisement of the collection it was in, and of unknown computers, then restart the WDSServer service. Sometimes letting it sit for 30mins will fix it too (and sometimes not).

Error – System gets AbortPxe.com

  • Check site messages; probably getting, “instructed computer to resume booting because no task sequence is advertised”.
  • Make sure your machine has an advertisement (see Error – PXE Stops Working).
  • Try restarting the WDSServer service

General Weirdness

  • Update your boot images.
  • Check your task sequence for a boot image.
  • Try restarting wdsserver service; it resets the GUID cache.
  • Clear all advertisements and re-advertise
  • Check the logs and component health messages
  • Last resort: de-install the PXE service point, uninitialize the wds server, and reinitialize.
Advertisements

One thought on “SCCM 2007 R3 OSD PXE Troubleshooting

  1. Pingback: Table of Contents | windowsmasher

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s