locked
UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    This is kind of long, but here goes...

    We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images.  We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002  during what appears to be the "Use Toolkit Package" step.  This is after the OS image has already been laid down and after the ConfigMgr client has been installed/configured.  The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence.  Error code 0x8007002"  Among other errors...I will post the entire log below...

    After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain, but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure. 

    Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment.  We have a few OSD task sequences built without UDI and those all still work just fine.  So, I am at a loss for where the root problem lies.  Any suggestions or assistance would be greatly appreciated.

    Here is the entire SMSTS.log and BDD.log...

    https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc

    Thanks

    Richie Tenhet

    Monday, December 31, 2012 6:53 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Just found my issue.... the UDI task sequences had a step called "Auto Apply Drivers" in the Post Install section.  It was configured to "Install only best matched compatible drivers" and to "Consider drivers from all categories".  It seems that another Admin had done some significant changes/reorganization to our driver packages.  These driver changes caused the UDI seqs to fail when attempting to run the Auto Apply Drivers step and apparently overwrote some of the NIC drivers for Win7.  Anyway, I disabled this Auto Apply Drivers step and the task sequences are completing as expected now. 
    • Marked as answer by Richie Tenhet Monday, January 7, 2013 11:15 PM
    Monday, January 7, 2013 11:15 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the Use Toolkit Package step...

    "Starting Task Sequence Engine . . . "

    "Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"

    "Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"

    "unknown host (gethostbyname failed)"

    "sending with winhttp failed; 80072ee7"

    "Tried all the available http based locations. SMB based locations will be attempted now."

    "Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"

    "Failed to run the action: Use Toolkit Package.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)"

    that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity around the time of the failure.


    Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I'm on Twitter > ncbrady

    Wednesday, January 2, 2013 8:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the detailed response, Niall.  I verified that the toolkit package exists and even redistributed it to Dist Point.  Just ran the TS again, and you are correct about network.  At F8 shell, I couldnt ping MP...IPCONFIG reveals machine doesnt even have IP address at that point!  Assuming because of no NIC driver at the time.  This is where I get confused...machine obviously booted with DHCP and PXE into WinPE, contacted MP and copied down needed packages and WIM for the image deployment.  I suppose after these steps and once the WIM is layed down, the Win7 OS actually boots...maybe this is where driver is missing from Win7?  I find that odd since I am using HyperV VM with legacy NIC and havent had to manually insert that driver in the past.  Also, this Win7 customized WIM works in other task sequences.  I am sure Im overlooking something obvious here...

    Wednesday, January 2, 2013 5:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Wanted to add some additional troubleshooting steps.  I have setup a completely new UDI MDT task sequence in SCCM as well as created new MDT Settings and Toolkit packages for this TS.  I am also using a different Win7 WIM than I was originally.  Even after all this, I am still losing my network driver after the first boot in Windows 7 and receiving the 80070002 error during deployment.  I am at a complete loss as to why this is happening.  If anyone could offer assistance, I would greatly appreciate it.

    Monday, January 7, 2013 9:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just found my issue.... the UDI task sequences had a step called "Auto Apply Drivers" in the Post Install section.  It was configured to "Install only best matched compatible drivers" and to "Consider drivers from all categories".  It seems that another Admin had done some significant changes/reorganization to our driver packages.  These driver changes caused the UDI seqs to fail when attempting to run the Auto Apply Drivers step and apparently overwrote some of the NIC drivers for Win7.  Anyway, I disabled this Auto Apply Drivers step and the task sequences are completing as expected now. 
    • Marked as answer by Richie Tenhet Monday, January 7, 2013 11:15 PM
    Monday, January 7, 2013 11:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had the same issue yesterday, and it didn't help adding SMSTSDownloadRetryCount = 5 and SMSTSDownloadRetryDelay = 15 to the task sequence, as it still gave me hash mismatch errors. This is probably due to some informational events in smsts.log, saying that it didn't have permissions to delete some files and folders belonging to MDT Toolkit on the system drive.

    After testing with another machine that actually worked, I started diskpart on the client that failed and deleted the primary disk partition. The task sequence was forced to create a new partition, and this solved the issue.

    • Proposed as answer by Stian Myhre Tuesday, September 9, 2014 8:34 AM
    Tuesday, September 9, 2014 8:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    it didn't help adding SMSTSDownloadRetryCount = 5 and SMSTSDownloadRetryDelay = 15 to the task sequence, as it still gave me hash mismatch errors.


    Just wanted to add, that in my case with similar error codes, adding those values seemed to help. Earlier, Computers crashed randomly on first downloading phase in OSPhase. I updated MDT from 2012 and 2013 and re-newed MDT Files package (same as Toolkit Package), and after this the problem arised. Before adding those values, I tried to republish and refresh the Package, but eventually it still did crash installations.
    Monday, November 17, 2014 12:05 PM