Archive

Archive for February, 2012

SCCM 2007: PXE-E32: TFTP Open timeout

February 27, 2012 Leave a comment

The setup of my ConfigMgr PXE Service Point was for me not a straight forward process. I faced some serious issues with the WDS service on my SCCM server. After my initial setup of WDS & PXE Service point + DCHP config I ran into an TFP Open timeout error.

PXE-E32: TFTP Open timeout

I found that the Windows deployment Service was not started properly. Event viewer generated unusual WDS errors like below:

EventID: 1811
an error occured while checking for exsitence or creation of service control point for BINLSVC provider
error information 0X5

EventID: 261
an error occured while trying to inisalize provider BINLSVC loaded from C:\windows\system32\binlsvc.dll. if the provider is maked as critical the windows deployment services server will be shutdown.
error information 0x5

EventID: 265
An error occured while trying to initalize provider BINSVC. since the provider is makerd as
critical the windows deployment services server will be shutdown.
error information 0x5

EventID: 513
an error occured while trying to initalize provider WDSPXE from c:\windows\system32\wdspxe.dll. windows seployment server will be shutdown.
error information 0x5

EventID: 257
an error occured while trying to start the windows seployment services server.
error information: 0x5

After a lot of searching I found a Technet threat with exact the same issue which provided me the solution which was apparently a security issue of the built-in SELF group object on my SCCM Computer object.



Solution:

  1. Open Active Directory Users and Computers
  2. Enable “Advanced Features” View ->  “Advanced Features”
  3. Find your SCCM/WDS Server object and open the Security tab
  4. Verify that the SELF group has the following permissions:
  • Create All Child Objects
  • Delete All Child Objects
  • Validated write to DNS host name
  • Validated write to service principal name
  • Read Personal Information
  • Write Personal Information

I don’t know why this is required but it’s worth to verify these security settings if you have WDS issues: Technet Threat

Advertisements
Categories: SCCM 2007 / 2012