ConfigMgr 2007: Task Sequence may fail to run with error code 0x80072ee7

Here's another neat tip from Clifton Hughes in our Irving, Texas site.  If you're PXE booting machines and they're throwing 0x80072ee7 errors along with getting APIPA addresses then you might try turning on portfast if you're using a Cisco Spanning Tree Protocol (STP) enabled switch to see if that helps:


Issue: When attempting to PXE Boot and install an Operating System Image with System Center Configuration Manager 2007, the Task Sequence may error out and reboot the machine. The SMSTS.LOG files may show error code 0x80072ee7 that points to a name resolution and/or networking issue. Additionally, you may notice that WINPE boots and gets an IP address from the DHCP server initially, however, once it gets to the Graphical User Interface portion of WINPE and try and run the Task Sequence it reverts to an Automatic Private IP Address (APIPA)  of 169.354.x.x.

Note: If you use Task Sequence Boot Media and manually configure a static IP address and subnet mask, etc. then the Task Sequence runs as expected.

Cause: This can occur if portfast is not enabled on your SPT enable Cisco switch.  If portfast is not enabled then the port using STP may remain in blocking mode long enough to prevent the client computer from communicating over the network.

Resolution: To resolve this issue you can turn on "spanning tree portfast enable" on the Cisco switch.  For more information on this feature contact your switch manufacturer or see the following article on's website:


Thanks Clifton!  Personally I've only seen this feature on Cisco switches but I image there are others out there using SPT that have a similar feature as well.  I guess the ultimate takeaway is that if you're seeing problems that may be networking related and you're using Spanning Tree on a directly connected switch you might investigate the options to force that port online immediately.

J.C. Hornbeck | Manageability Knowledge Engineer