PXE boot Issue, SCCM 2012sp1 cu2

Hi Everyone,

I have 2 secondary sites which won't PXE boot machines. SMSPXE.log shows errors like the following...


reply has no message header marker      SMSPXE            4772 (0x12A4)
PXE::MP_LookupDevice failed; 0x80004005      SMSPXE            4772 (0x12A4)
reply has no message header marker      SMSPXE            4824 (0x12D8)
PXE::MP_LookupDevice failed; 0x80004005      SMSPXE            4824 (0x12D8)
reply has no message header marker      SMSPXE            4772 (0x12A4)
Failed to send status message (80004005)      SMSPXE            4772 (0x12A4)
Failed to send the status message      SMSPXE            4772 (0x12A4)
PXE::MP_ReportStatus failed; 0x80004005      SMSPXE            4772 (0x12A4)
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows)      SMSPXE            4772 (0x12A4)
B4:B5:2F:BF:BE:B1, E17D0700-0E0C-11E2-8362-B4B52FBFBEB1: Not serviced.      SMSPXE            4772 (0x12A4)

I've rebuilt the entire secondary site server and still this error persists... all other secondary sites are working correctly and are configured the same... any ideas what could be going wrong?


Cheers!
WGE_ENRBAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sumeshbnrCommented:
Have you created a DHCP relay on your network ?
0
WGE_ENRBAuthor Commented:
SCCM should have configured the WDS role on the site server to be authorized automatically... they're on the same subnet so it shouldn't need any helpers or anything should it? it looks to me like the client is contacting the sccm server without a problem... otherwise it wouldn't appear in the LOG as the PXE service not being able to query the MP for the computer details right?
0
vivigattCommented:
What can you see on the client side? Any error?

Error 0x80004005  usually relates to access permissions denied. Check permissions on the RemoteInstall folder.  The SMS Admin account  (or any account the SCCM/PXE/WDS Service runs with) should be able to access this folder. Give that account full access (you may have to actually take ownership to do it). AT first, you can give all users read permission to it.

Also, check this link:
http://www.windows-noob.com/forums/index.php?/topic/7281-management-point-pxe-boot-error-80004005-after-sp1-upgrade/
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

WGE_ENRBAuthor Commented:
Client Side error was PXE-E53. I ended up coming across the following info about the SQL database.

http://www.windows-noob.com/forums/index.php?/topic/9281-pxe-0x80004005/

what i did was, remove secondary sites with the issue, remove all traces of SCCM and WDS on them, then go into the primary site database and remove the machine account permissions completely and then re added the secondary sites, re-add the PXE role and reflow all the content... VOILA!

Seems that SQL permissions and accounts aren't recreated or removed properly when you install secondary sites.

Hope this helps someone!
0
WGE_ENRBAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for WGE_ENRB's comment #a39586932

for the following reason:

Because it was the solution...
0
vivigattCommented:
It was an access permission then?
I think I gave you the lead in my coment http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_28269281.html#a39579450, didn't I ?
I am pretty sure that if you followed my advices you also would have resolved your issue.

I am objecting the closing of this question, just to give you the chance to retribute my help, if you think it was useful (I won't object if you don't...)
0
WGE_ENRBAuthor Commented:
In my question I mentioned that I rebuilt the entire site already before posting on here which what basically what that link you posted suggested, so I know that following your advice wouldn't have resolved it as i'd already done it.

The issue was that the MP couldn't talk to the primary site server database due to SCCM seemingly not cleaning up SQL when you uninstall a site, nothing to do with the folder permissions.

I rebuilt the entire site because i didn't want to run into any more issues, and i wanted the install to recreate all the SQL permissions that i'd removed correctly.

Choosing your answer as a solution would confuse people who come here with the same issue. sorry mate, thanks for the help though!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WGE_ENRBAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for WGE_ENRB's comment #a39586932

for the following reason:

correct solution.
0
vivigattCommented:
No problem...
Yet it was a permission issue, which 0x80004005 usually suggests (this will NOT confuse readers...)
0
vivigattCommented:
Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.