Hoping that someone can offer me some advice on an intermitant issue we are having when deploying Windows 7 to various devices using a Zero Touch approach. The Task Sequences had been completing successfully each time until one day they just started throwing up errors. They seemed limited to either 0x80070002, 0x80004005 or HTTP 401 and pointed toward the Network Access Account. We ensured the account had share and NTFS permissions, was unlocked in AD and that the password was correct. This, to us anyway, kinda ruled out permissions as the issue especially because it was intermitant. We are experiencing problems with Windows 7 client PCs dropping out of DNS and wondered if this was perhaps an issue. We enabled command prompt in our Boot Images and the PC is picking up a valid IP address and can communicate with the SCCM box no problem (and vice versa from SCCM - once the WinPE firewall is disabled). Even at the point of failure the IP config of the client seems okay. The problem is also intermitant. We can run a complete OSD TS one minute then it will fail running the same TS on the same client PC moments later with the same issues - unable to connect to the DP for package X. We are running ConfigMgr 2007 R3 with Advanced Client 4.00.6487.2000. Thanks in advance for any feedback : )

It sounds like DNS problems... can you ping fqdn when it happens ?Could you supply the smsts.log on a machine that is failing??Michael Petersen | My blogs: blog.coretech.dk/mip and SCUG.dk/ | Twitter: @OSDeploy | Linkedin: Michael Petersen

I concur with Michael. Quick note also: - 0x80070002 = "File not found". This is often seen when the DP can't be reached. - 0x80004005 = generic error message that means something went wrong.Jason | http://myitforum.com/myitforumwp/community/members/jasonsandys/ | Twitter @JasonSandys

I had 0x80004005 error recently while re-doing OSD setup and it turned out to be a DNS issue. Make sure MP is reachable with FQDN after you boot with boot image.

Appreciate the quick responses guys. I am pretty sure I tried the FQDN from the client after it had failed with the 70002 error and it could resolve it okay - will need to double check. I have not tried reaching the MP after boot however - will try that tomorrow. In the meantime here is the SMSTS log file from a client I tried to deploy to this afternoon: https://skydrive.live.com/redir.aspx?cid=66b37a0bc806ca43&resid=66B37A0BC806CA43!110&parid=66B37A0BC806CA43!109

Thanks for all the responses. In the end we never got to the bottom of the issue - as per the posts we above we still suspect DNS but we cannot be certain. Our OSD Task Sequences are now running to completion without failure. Wish I had the answer to share with the community - perhaps as our usage of SCCM takes off we will encounter this again, but this time establish the root cause.