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

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

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

Similar Messages

  • OSD Task Sequence Applications Fail to Install

    Hello,
    In my task sequence, any application that i add fails to install with Error Code 0x87d00215. Outside of the task sequence the
    applications install with no problems. 
    A couple things that i have verified already
    DP is set to allow clients to connect anonymously
    Network Access Account is set and verified
    Setting on the application for Allow
    this application to be installed from the Install Application task sequence action instead of deploying it manually is set
    Boundaries are set correctly as software installs correctly outside of the TS 
    Logs that do not show errors
    IIS logs - Check out just fine
    Location Services - Does not show any errors and finds the AD Forest/Site and MP successfully 
    CAS Log - Does not show any errors with the correct date
    Data Transfer Log - Does not show any error with the correct date
    Any ideas would be greatly appreciated.
    Thanks 

    The AppEnforce log is empty and below are some bits from the AppDiscovery log and the AppIntentEval log which I did not see anything unusual.
    AppDiscovery.log
        Performing detection of app deployment type VMware Tools x32(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, revision 2) for system.
    +++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, Revision: 2]
    +++ Did not detect app deployment type VMware Tools x32(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, revision 2) for system.
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f" AND Revision = 2)"
        Performing detection of app deployment type Adobe AIR - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, revision 2) for system. 
    +++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, Revision: 2]
    +++ Did not detect app deployment type Adobe AIR - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, revision 2) for system.
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255" AND Revision = 1)"
        Performing detection of app deployment type Adobe Reader X MUI - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255, revision 1) for system.
    +++ MSI application not discovered [MSI Product Code: {AC76BA86-7AD7-FFFF-7B44-AA0000000001}, MSI Product version: ]
    +++ Did not detect app deployment type Adobe Reader X MUI - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255, revision 1) for system.
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2" AND Revision = 2)"
        Performing detection of app deployment type Adobe Shockwave Player 11.6 - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, revision 2) for system.
    +++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, Revision: 2]
    +++ Did not detect app deployment type Adobe Shockwave Player 11.6 - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, revision 2) for system.
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4" AND Revision = 6)"
        Performing detection of app deployment type Flash(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, revision 6) for system.
    +++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, Revision: 6]
    +++ Did not detect app deployment type Flash(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, revision 6) for system.
    Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038" AND Revision = 2)" AppDiscovery 5/23/2012 3:10:56 PM 3520
    (0x0DC0)
        Performing detection of app deployment type VMware Tools x64(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, revision 2) for system
    +++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, Revision: 2]
    +++ Did not detect app deployment type VMware Tools x64(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, revision 2) for system.
    AppIntectEval.log
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_01c75763-a985-4a58-99fc-35e5b5380106/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Project 2010 Pro - Silent AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_4680375d-efcf-411b-8901-233d7a9694aa/1 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, Title = Autodesk 2012 64bit AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_5f72c7c1-b695-4f8d-b754-f8f6d1aa4046/9 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Autodesk 2012 32bit AppIntentEval 5/23/2012 3:10:56
    PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Shockwave Player 11.6 - Windows Installer (Native) AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9365b2e3-d0a3-4486-88bb-a7071d9b047b/4 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = LogMeIn - Windows Installer (Native) AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe AIR - Windows Installer (Native) AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = VMware Tools x32 AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4/6 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Flash AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038/2 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, Title = VMware Tools x64 AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f8a1de4d-ffa9-4ba6-b51b-7e9a6810cfda/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Silent Install AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255/1 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Reader X MUI - Windows Installer (Native) AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_07eed4d3-7acf-4717-93f9-74f717a191b4/5 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = LogMeIn Client AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_0bce5378-1b95-45ea-b210-e72cb65b2b37/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Project 2010 Pro AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_808fe5d5-5b90-48aa-83cb-f5497d534691/6 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = VMware Tools AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_b1a04314-2a3a-47e2-98a0-ff09fc8e3948/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe AIR AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_b614de9b-5133-4788-a013-71c7de98a233/11 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = AutoCAD 2012 AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_c4ccbd68-7c0f-4b79-9437-eba3cb46e90c/5 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Shockwave Player 11.6 AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_dec4acbc-b968-41d9-82e6-3f7767467c8e/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Reader X AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_e4048d56-cfa1-43e0-b4df-f30b6a834828/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Application Virtualization Client with SP1 and HF4 AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_ee3b1dcf-e401-44fe-8283-a6e5721dac11/10 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Flash Player AppIntentEval 5/23/2012 3:10:56 PM 1912
    (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_07eed4d3-7acf-4717-93f9-74f717a191b4/5 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_0bce5378-1b95-45ea-b210-e72cb65b2b37/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_808fe5d5-5b90-48aa-83cb-f5497d534691/6 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_b1a04314-2a3a-47e2-98a0-ff09fc8e3948/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_b614de9b-5133-4788-a013-71c7de98a233/11 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_c4ccbd68-7c0f-4b79-9437-eba3cb46e90c/5 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_dec4acbc-b968-41d9-82e6-3f7767467c8e/2 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)
    ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_ee3b1dcf-e401-44fe-8283-a6e5721dac11/10 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
    3:10:56 PM 1912 (0x0778)

  • Task Sequence has failed with error code: 0x80070570

    I've created task sequence for Windows XP OS Deployment. WinPE boot image loads successfully, Partitions are formatted successfully too. But during "Applying image 1 from volume C:\" I receive following error:
    Task Sequence: My_task_sequence_name has failed with error code: 0x80070570.
    What I need to do? Any ideas? (My computer has following details: ASUS P5KSE motherboard, Core 2 Duo, SATA HDD, Atheros L1 adapter)

    No, a build and capture task sequence automates the build of the image removing any and all human intervention so that rebuilding or refreshing an image becomes a simple matter. Building images by actually manually installing Windows is anti-IT.
    File corruption can be caused by many, many things; e.g., anti-virus, physical disk errors, network transmit errors, etc.
    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

  • 11g start fails with no error

    Hi all.  I have inherited an OEM 11gR1 installation running on Solaris 10.
    It has been running fine until recently.  We had to restart the server due to an issue unrelated to OEM.  When the server was back up the listener and database started fine, but I cannot get the OMS to start.
    When I run emctl it just shows the version information and returns to a prompt with no error (see below).  None of the log files are touched.  Start, stop, and status commands all act the same.  However, i *can* start the agent without issue.  I'm guessing it is just an environmental configuration problem, but I've tried setting ORACLE_HOME, OMS_HOME, ORACLE_SID, and various others with no success.
    Does anyone have any ideas?  I'm all out at this point.
    Thanks,
    Jeremy
    -bash-3.00$ ./emctl stop oms -force -all
    Oracle Enterprise Manager 11g Release 1 Grid Control
    Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
    -bash-3.00$ ./emctl start oms
    Oracle Enterprise Manager 11g Release 1 Grid Control
    Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
    -bash-3.00$ ./emctl status oms
    Oracle Enterprise Manager 11g Release 1 Grid Control
    Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.

    Hi Silviu,
    long time no see
    Try SAP Note 883859. The last paragraph may seem to be related to your problem.
    Regards,
    Chris

  • Bare metal restore of full server backup fails with RPC error 0x800706BA (server 2012)

    With Windows Server 2012, after creating a successful windows server backup (full server), I am unable to do a bare metal restore of the system.
    EFI System Partition, C:, D: are the volumes on a single array (Raid 5).
    Loading WinRE and launching re-image, the full server restore stops after completing the C: restore just after beginning the D: drive restore (data volume) with the error with the message about RPC error 0x800706BA, unavailable.
    The system will not boot as a result of the failure. 
    What may be causing this?
    [edit]
    I think I have two things working against me here... one, Volume Shadow Copy service wasn't running in WinPE and two.. the D: volume contains data deduplication.
    I think this is causing some of my problems.
    Is there an additional service that I need to start in WinPE to get a volume that was deduplicated restored perhaps using wbadmin?

    Hi,
    Thanks for the reply Shaon.
    The hardware system is identical; however, I am increasing storage capacity from 12TB to 16TB.  Basically, the system is the same, just new hard drives (4x4TB versus 4x3TB).  Drives are all identical enterprise class drives and I am actually using
    the same system (backup, swap drives then restore).
    I tried both using the WinRE restore (re-image) with the backup set, and tried using wbadmin.  Both produce same RPC unavailable messages (although using the GUI based tool via WinRE provides the additional error code #).
    I do not have any idea what to look at to try to figure this one out.
    [edit]
    I was just informed of this posting:
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/147efccc-e0e9-4458-852e-c3a44ae5cb64/the-system-image-restore-failed-error-details-he-rpc-server-is-unavailable-0x800706ba?forum=windowsbackup
    and in my case, this lab server does in fact act also as a DC as well as a file server...  do I need to spin up a secondary controller (perhaps in a VM on another machine) to do this restore?

  • Known issue: BackgroundTransfer sample fails with 0x80070002 error when using Windows Phone Emulator (Windows 10 Insider Preview SDK and tools, April 2015 release)

    When running the Universal Windows Platform (UWP) BackgroundTansfer sample (C# or C++) in a phone emulator (i.e., Debug Target is Emulator 10.0.1.0) the sample builds and deploys successfully, but clicking any button in "Scenario 1 File Download",
    "Scenario 3 Completion Notifications" or "Scenario 4 Completion Groups" will result in the following exception:
    An exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.ni.dll but was not handled in user code. Additional information: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
    This posting is provided "AS IS" with no warranties, and confers no rights.

    I am getting the same error even with the references recommended here. This is my code
       using (var stream = await Windows.Storage.ApplicationData.Current.LocalFolder.OpenStreamForWriteAsync(
                        JSONFILENAME,
                         CreationCollisionOption.OpenIfExists ))           
                serializer.WriteObject(stream, myCars);
    I can read it back as long as I don't stop the app/emulator. When I run the emulator again the file is gone. I tried loading the app to my Windows Phone and the same thing still happens.

  • Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager

    Dear All,
    I need your Help, as I am getting below mention error in deployment of OS through MDT 2013.
    Expand a string: WinPEandFullOS    TSManager    6/5/2014 11:40:50 AM    1464 (0x05B8)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"    TSManager    6/5/2014 11:40:50 AM    1464 (0x05B8)
    Process completed with exit code 5627    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    !--------------------------------------------------------------------------------------------!    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Failed to run the action: Install Operating System.
    Unknown error (Error: 000015FB; Source: Unknown)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Sending status message . . .    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Set a global environment variable _SMSTSLastActionRetCode=5627    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Clear local default environment    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Let the parent group (Install) decides whether to continue execution    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015FB; Source: Unknown)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Sending status message . . .    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Task Sequence Engine failed! Code: enExecutionFail    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    ****************************************************************************    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Task sequence execution failed with error code 80004005    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Cleaning Up. Removing Authenticator    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Cleaning up task sequence folder    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Command line for extension .exe is "%1" %*    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Set command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Executing command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    ==========[ TsProgressUI started in process 320 ]==========    TsProgressUI    6/5/2014 11:51:18 AM    552 (0x0228)
    Command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister    TsProgressUI    6/5/2014 11:51:18 AM    552 (0x0228)
    Unregistering COM classes    TsProgressUI    6/5/2014 11:51:18 AM    552 (0x0228)
    Unregistering class objects    TsProgressUI    6/5/2014 11:51:18 AM    552 (0x0228)
    Shutdown complete.    TsProgressUI    6/5/2014 11:51:18 AM    552 (0x0228)
    Process completed with exit code 0    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Successfully unregistered TS Progress UI.    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,657)    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Sending error status message    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Finalizing logging from process 1456    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Finalizing logs to root of first available drive    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Successfully finalized logs to C:\SMSTSLog    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Cleaning up task sequencing logging configuration.    TSManager    6/5/2014 11:51:18 AM    1464 (0x05B8)
    Deployment is going failed.
    Regards
    Sachi

    Note:Only mass storage device drivers and network adapter device drivers should be added to boot images because other types of
    drivers are not needed and will increase the size of the boot image:
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • PXE OSD Task Sequence fails to run on new laptop

    We are trying to run a working PXE OSD task sequence on a new HP laptop.  It's a Elitebook 840 G2.  We've downloaded the provided driver package & created a new driver package in SCCM.  We inserted the driver into the boot image &
    updated the DPs.  When we PXE boot the laptop it flashes the splash screen & reboots.  Other laptops & desktops boot properly.  This looks like a driver issue but we wanted to run it past the forum to see if anyone had any other suggestions.
     The SMSTS log file is copied below.
    LOGGING: Finalize process ID set to 728
    TSBootShell
    4/23/2015 4:20:40 PM
    732 (0x02DC)
    ==============================[ TSBootShell.exe ]==============================
    TSBootShell 4/23/2015 4:20:40 PM
    732 (0x02DC)
    Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'
    TSBootShell 4/23/2015 4:20:40 PM
    732 (0x02DC)
    Debug shell is enabled TSBootShell
    4/23/2015 4:20:40 PM 732 (0x02DC)
    Waiting for PNP initialization... TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    RAM Disk Boot Path: NET(0)\SMSIMAGES\ALN00001\BOOT.ALN00001.WIM
    TSBootShell 4/23/2015 4:20:40 PM
    736 (0x02E0)
    Booted from network (PXE) TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    Network(PXE) path: X:\sms\data\ TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    Found config path X:\sms\data\ TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    Booting from removable media, not restoring bootloaders on hard drive
    TSBootShell 4/23/2015 4:20:40 PM
    736 (0x02E0)
    X:\sms\data\WinPE does not exist. TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    X:\_SmsTsWinPE\WinPE does not exist. TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    Executing command line: wpeinit.exe -winpe TSBootShell
    4/23/2015 4:20:40 PM 736 (0x02E0)
    Executing command line: X:\WINDOWS\system32\cmd.exe /k
    TSBootShell 4/23/2015 4:20:40 PM
    732 (0x02DC)
    The command completed successfully. TSBootShell
    4/23/2015 4:20:40 PM 732 (0x02DC)
    Successfully launched command shell. TSBootShell
    4/23/2015 4:20:40 PM 732 (0x02DC)
    Executing command line: X:\WINDOWS\system32\cmd.exe /k
    TSBootShell 4/23/2015 4:20:41 PM
    732 (0x02DC)
    The command completed successfully. TSBootShell
    4/23/2015 4:20:41 PM 732 (0x02DC)
    Successfully launched command shell. TSBootShell
    4/23/2015 4:20:41 PM 732 (0x02DC)
    Executing command line: X:\WINDOWS\system32\cmd.exe /k
    TSBootShell 4/23/2015 4:20:41 PM
    732 (0x02DC)
    The command completed successfully. TSBootShell
    4/23/2015 4:20:41 PM 732 (0x02DC)
    Successfully launched command shell. TSBootShell
    4/23/2015 4:20:41 PM 732 (0x02DC)
    The command completed successfully. TSBootShell
    4/23/2015 4:20:43 PM 736 (0x02E0)
    Starting DNS client service. TSBootShell
    4/23/2015 4:20:43 PM 736 (0x02E0)
    Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\
    TSBootShell 4/23/2015 4:20:44 PM
    736 (0x02E0)
    The command completed successfully. TSBootShell
    4/23/2015 4:20:44 PM 736 (0x02E0)
    ==============================[ TSMBootStrap.exe ]==============================
    TSMBootstrap 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\
    TSMBootstrap 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'
    TSMBootstrap 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL'
    TSMBootstrap 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Current OS version is 6.2.9200.0 TSMBootstrap
    4/23/2015 4:20:44 PM 1124 (0x0464)
    Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH
    TSMBootstrap 4/23/2015 4:20:44 PM
    1124 (0x0464)
    PXE Boot with Root = X:\ TSMBootstrap
    4/23/2015 4:20:44 PM 1124 (0x0464)
    Executing from PXE in WinPE TSMBootstrap
    4/23/2015 4:20:44 PM 1124 (0x0464)
    Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll
    TSMBootstrap 4/23/2015 4:20:44 PM
    1124 (0x0464)
    TsPxe.dll loaded TSPxe
    4/23/2015 4:20:44 PM 1124 (0x0464)
    Device has PXE booted TSPxe
    4/23/2015 4:20:44 PM 1124 (0x0464)
    Variable Path: \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var
    TSPxe 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Succesfully added firewall rule for Tftp TSPxe
    4/23/2015 4:20:44 PM 1124 (0x0464)
    Executing: X:\sms\bin\i386\smstftp.exe -i 172.20.100.51 get \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var X:\sms\data\variables.dat
    TSPxe 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Command line for extension .exe is "%1" %*
    TSPxe 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Set command line: "X:\sms\bin\i386\smstftp.exe" -i 172.20.100.51 get \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var X:\sms\data\variables.dat
    TSPxe 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Executing command line: "X:\sms\bin\i386\smstftp.exe" -i 172.20.100.51 get \SMSTemp\2015.04.22.16.21.10.0001.{8EBA05A2-1AB7-4CBB-9DDD-497DFE8E5E07}.boot.var X:\sms\data\variables.dat
    TSPxe 4/23/2015 4:20:44 PM
    1124 (0x0464)
    Process completed with exit code 1 TSPxe
    4/23/2015 4:21:31 PM 1124 (0x0464)
    Succesfully removed firewall rule for Tftp TSPxe
    4/23/2015 4:21:31 PM 1124 (0x0464)
    uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,185)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    Failed to download pxe variable file. Code(0x00000001)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    PxeGetPxeData failed with 0x80004005
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1459)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2667)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1078)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1226)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    Exiting with return code 0x80004005 TSPxe
    4/23/2015 4:21:31 PM 1124 (0x0464)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)
    TSPxe 4/23/2015 4:21:31 PM
    1124 (0x0464)
    Execution complete. TSBootShell
    4/23/2015 4:21:31 PM 736 (0x02E0)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    ::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,809)
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    GetTsRegValue() is unsuccessful. 0x80070002.
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    End program: TSBootShell
    4/23/2015 4:21:31 PM 736 (0x02E0)
    Finalizing logging from process 728 TSBootShell
    4/23/2015 4:21:31 PM 736 (0x02E0)
    Finalizing logs to root of first available drive
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)
    LOGGING: Setting log directory to "D:\SMSTSLog".
    TSBootShell 4/23/2015 4:21:31 PM
    736 (0x02E0)

    Press F8 in order to get a cmd window and see if the client got an IP address.
    Torsten Meringer | 
    There's no IP Address when trying to the command prompt. It doesn't even show a MAC Address.

  • OSD Task Sequence fails to install SCCM client

    Hello,
    Our OSD task sequence fails to install the SCCM client with certain images.
    The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the
    task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
    The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence
    If we change the image specified under "Apply Operating System" step, everything works ok.
    It appears there is something wrong with this particular image. Any ideas?
    Logs show no errors. Let me know which logs you'd like me to post (and from which location)
    There is no ccm folder under c:\windows

    Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You
    can mount the Image and check those settings.
    RunOnce Key Reference :
    https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
    If the above key is present in the Image, TS Engine won't resume after the reboot.
    You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
    The above variable is applicable in CM 2012 SP1 and R2.
    Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This
    can be beneficial to other community members reading the thread.

  • Install Software Updates fails (timeouts) during OSD Task Sequence

    Hi
    As one of the lasts steps in our OSD Task Sequence we have an "Install Software Update" step where "Mandatory Software Updates" is choosen. It worked a week ago, but now the step fails with error code 0x800705B4
    (This operation returned because the timeout period expired.)
    When examining the WindowsUpdate.log I see an error followed by several minutes without log activity:
    2014-02-18 10:39:13:874
    416 b74
    Report CWERReporter finishing event handling. (00000000)
    2014-02-18 10:39:13:874
    416 b74
    Report CWERReporter finishing event handling. (00000000)
    2014-02-18 10:39:13:874
    416 b74
    Report CWERReporter finishing event handling. (00000000)
    2014-02-18 10:39:13:999
    1632 4e4
    COMAPI  - Updates found = 260
    2014-02-18 10:39:13:999
    1632 4e4
    COMAPI ---------
    2014-02-18 10:39:13:999
    1632 4e4
    COMAPI --  END  --  COMAPI: Search [ClientId = CcmExec]
    2014-02-18 10:39:13:999
    1632 4e4
    COMAPI -------------
    2014-02-18 10:39:18:835
    416 b74
    Report CWERReporter finishing event handling. (00000000)
    2014-02-18 11:08:12:225
    416 4dc
    AU AU received policy change subscription event
    2014-02-18 11:08:12:334
    416 4dc
    AU AU Options changed from policy.
    2014-02-18 11:08:12:334
    416 4dc
    AU Successfully wrote event for AU health state:0
    2014-02-18 11:08:12:334
    416 4dc
    AU ###########  AU: Policy change processed  ###########
    When examining the WUAHadler.log - again there is no log activity during the Software Update step.
    Its a WSUS Update Source type ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}), adding it.
    WUAHandler 18-02-2014 10:39:05
    2016 (0x07E0)
    Existing WUA Managed server was already set (http://<servername>:8530), skipping Group Policy registration.
    WUAHandler 18-02-2014 10:39:05
    2016 (0x07E0)
    Added Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
    WUAHandler 18-02-2014 10:39:05
    2016 (0x07E0)
    Scan results will include all superseded updates.
    WUAHandler 18-02-2014 10:39:05
    2016 (0x07E0)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
    WUAHandler 18-02-2014 10:39:05
    2016 (0x07E0)
    Async searching of updates using WUAgent started.
    WUAHandler 18-02-2014 10:39:05
    2016 (0x07E0)
    Async searching completed. WUAHandler
    18-02-2014 10:39:13 1108 (0x0454)
    Successfully completed scan. WUAHandler
    18-02-2014 10:39:15 2016 (0x07E0)
    Removed Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
    WUAHandler 18-02-2014 11:06:25
    1160 (0x0488)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
    for bundles WUAHandler
    18-02-2014 11:09:25 2232 (0x08B8)
    The Software Update Step started at 10:27 and the timeout came at 11:05.
    Any ideas why the step times out? Or which logs I should look at?
    Regards,
    FC

    PolicyEvaluator.log:
    No errors. The last event is:
    Received notification that Local policy has changed.
    PolicyAgent_PolicyEvaluator 19-02-2014 10:51:11
    1692 (0x069C)
    Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
    DateTime = "20140219095123.565000+000";
    PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
    ProcessID = 1748;
    ThreadID = 1768;
    PolicyAgent_PolicyEvaluator
    19-02-2014 10:51:23 1768 (0x06E8)
    Forcing settings update for local policy change.
    PolicyAgent_PolicyEvaluator 19-02-2014 10:51:23
    2900 (0x0B54)
    Updating settings in \\.\root\ccm\policy\machine\actualconfig
    PolicyAgent_PolicyEvaluator 19-02-2014 10:51:33
    2900 (0x0B54)
    Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
    DateTime = "20140219095144.641000+000";
    PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
    ProcessID = 1748;
    ThreadID = 2900;
    PolicyAgent_PolicyEvaluator
    19-02-2014 10:51:44 2900 (0x0B54)
    UpdatesHandler.log:
    No errors. A couple of lines:
    Successfully initiated scan. UpdatesHandler
    19-02-2014 10:54:10 1768 (0x06E8)
    Updates scan completion received, result = 0x0.
    UpdatesHandler 19-02-2014 10:55:23
    3572 (0x0DF4)
    UpdatesStore.log
    No errors. Just quering updates, and the last line:
    Querying update status completed successfully.
    UpdatesStore 19-02-2014 10:56:27
    3300 (0x0CE4)
    In the smsts.log I found an interesting thing:
    Successfully initiated RefreshUpdates operation
    InstallSWUpdate 19-02-2014 10:51:37
    3424 (0x0D60)
    Waiting for RefreshUpdates complete notification from Updates Deployment Agent
    InstallSWUpdate 19-02-2014 10:51:37
    3424 (0x0D60)
    FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273)
    InstallSWUpdate 19-02-2014 11:21:37
    3424 (0x0D60)
    Timedout waiting for updates refresh complete notification
    InstallSWUpdate 19-02-2014 11:21:37
    3424 (0x0D60)
    It times out after exactly 30 minutes. Does 2012 have the same "feature" as 2007? (http://support.microsoft.com/kb/2009754/da)
    Still the last event in windowsupdate.log is:
    2014-02-19 10:55:37:251
    324 dd0
    Report CWERReporter finishing event handling. (00000000)
    Regards,
    FC

  • Whats the best way to apply office updates during OSD task sequence with Software Update Agent disabled?

    I am trying to update office via the SCCM 2012 R2 OSD task sequence. I know offline updating only updates the core components in the WIM and I'm trying to figure out how to add office updates as well. I am aware of using powershell to try and kick off
    a WU scan as seen here:
    http://myitforum.com/myitforumwp/2012/01/24/use-powershell-commands-to-assist-with-patching-during-sccm-image-build/
    But the kicker is we don't use SCCM to update the workstations (Solo WSUS install). Is there a way to do this (maybe set the client in the TS to switch on SUP, then off again when it goes off into production) rather than have to build a new image every month?

    You could use the ZTI_WindowsUpdates.wsf script from MDT.
    http://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/
    How does it work?
    The task sequence steps run a script called ZTIWindowsUpdate.wsf. The script uses the
    Windows Update Agent API to manage the downloading and installation of updates. All audit information is written to the
    ZTIWindowsUpdate.log file. If you find any unusual error codes in your log returned from the API (although I never have)  you can compare the codes
    here. The script will also check and update the
    Windows Update Agent(WUA) as needed at the start.
    In its default state, the ZTIWindowsUpdate.wsf script will connect to Microsoft Update then search for and download all available updates including Security Patches, Drivers, Browser Updates and Service Packs. This is essentially the same
    as opening the GUI and selecting check for updates.
    Daniel Ratliff | http://www.PotentEngineer.com

  • SCCM 2012 OSD Task Sequence Fails "An error occurred while retrieving policy for this computer"

    We have SCCM 2012 R2. I amm trying to start OSD task sequence from bootable media.
    Hyper-v client gets DHCP ip and starts MDT bootable media, but could not find policy.
    From F8 I can ping SCCM/DP/MP server.
    What could be the cause?

    Yes, this DHCP client is in the same subnet as other working clients.
    smsts.log from client
    Request was successful. TSPxe
    21.03.2014 14:14:14 324 (0x0144)
    pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1970)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    reply has no message header marker TSPxe
    21.03.2014 14:14:14 324 (0x0144)
    DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    Failed to get client identity (80004005)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1113)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    failed to request for client
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe
    21.03.2014 14:14:14 324 (0x0144)

  • Win 7 x64 OSD Task Sequence BSOD with SSD

    Hello,
    I have recently rebuilt my OSD Task Sequences into ConfigMgr 2012 R2 and consistently experiencing BSODs on machines with SSDs after the machine boots after the "Setup and Windows ConfigMgr" step.  When the machine reboots and starts Windows
    Setup, it Blue Screens immediatley after attempting to Update System Registry with the Stop Code 0x000000f4
    To validate the health of the SSDs, I am able to successfully build the same machines using bootable media from the (still standing) 2007 environment.  Also, replacing the SSD with a standard HDD builds the machine successfully which makes me question
    my driver packages less than when I first saw this.  I am unable to see any steps in the Task Sequence that appear different between the 2 environments.
    I have captured the logs from WinPE as well as the system drive before the crashes have occured - can anyone suggest where I should be looking to help flush out why this is occuring?  For what it's worth, the drives are Crucial m4 SSD 2.5 128GB SATA
    6Gb/s with the most current firmware.
    Thanks
    Scott

    Here is a quick update as I continue to struggle with the same issue on a few different models in our environment.
    I have made attempts with multiple different combinations of drivers in packages and continue to see BSODs when the TS reboots after configuring the ConfigMgr client.  I have deployed the captured Win 7 image using a basic Task Sequence and have also
    brought the Win 7 image from the 2007 environment into 2012 and replaced it in the MDT Task Sequence and the results are all the same. 
    Given that I can build machines using a Task Sequence with SCCM 2007 but not with ConfigMgr 2012 R2 points at this being a Task Sequence and\or Driver issue.  I am appreciative of any suggestions or ideas.
    Thanks
    Scott

  • SCCM 2012 Export Task Sequence fails with generic error message

    We have a complex task sequence comprising of more than 50 applications\packages, 1975 drivers, 18 driver packages etc etc. Its long, it's big and it will not export with it's content.
    We have several environments for development test and live. I am attempting to export the primary task sequence with all it's dependencies from live so that I can port it over to a new development environment.
    I can export the zip file without content and it comes to 92Mb in size. The entire task sequence software set is 50Gb+. When I attempt to export with all dependencies and content the process gets about 60% of the way through and fails with the error
    "Error: The filename, directory name, or volume label syntax is incorrect"
    Googling the error roughly defines the problem as 'the export process cannot access the defined source path for one of the dependant items'
    I wrote a PowerShell script that looks as every application, package, driver, driver package, boot image, os image and software update package in the entire SCCM software library and verifies that each and every package has a valid UNC source directory
    that can be reached using test-path.
    I also wrote another tool that parsed the entire source software library on the server looking for permissions errors (permissions on the structure set at a directory level rather than inherited), directories that were too long, inaccessible or otherwise
    blocked, nothing was found.
    It will take a very long time to go through and check each and every dependency by hand - time I do not have at present.
    I looked in the TaskSequenceProvider.log as that is supposed to contain messages from the export process and found the messages in there far too high a level to use
    =======================
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:00:41.161-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
    <![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.339-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:333">
    <![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:352">
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
    <![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:01:36.036-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="5592" file="wmiprovider.cpp:399">
    <![LOG[[1AFF658 PID:3500] Initializing provider for namespace root\sms\site_P01]LOG]!><time="13:02:36.550-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068"
    file="wmiprovider.cpp:90">
    <![LOG[[1AFF658  PID:3500] Initialization of provider for namespace root\sms\site_P01 succeeded]LOG]!><time="13:02:36.551-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1"
    thread="7068" file="wmiprovider.cpp:107">
    <![LOG[[PID: 3500] Invoking method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.554-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
    <![LOG[[PID: 3500] Done with method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.558-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:02:36.559-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
    <![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.428-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
    <![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
    <![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:03:36.369-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:399">
    ====================
    Is there any way of increasing the log verbosity? I need to see what item is causing the export to fail.
    Is there another log containing the information about the export & what it is doing?
    All out builds that use the task sequence complete successfully, we can edit the sequence fine, make changes etc. so no internal corruption we can find.
    Any ideas?

    Torsten, smsprov.log did indeed prove useful, I could see every package as it was validated. Unfortunately the log was wrapping about every 4 minutes and it takes 3+ hours for the task sequence to reach the fail point so I still cannot see the offending
    package as it wraps before I can get to the log.
    I will increase the size of the log and see if I can maintain some details to investigate.
    There was nothing of note in the event logs, certainly nothing leading me to suspect that WMI might be reaching its limits.
    I will keep looking for the cause and will post here when I find it <= positive thinking :)

  • Lenonvo T440 with Intel SSD SC2BF240A4L - failing to install apps via SCCM 2012 task sequence

    Hi there
    Wondering if anyone else has encountered this issue with a T440 with Intel SSD hard disk.
    Our firm purchased two Lenovo T440 laptops. One has a magnetic hard disk, the other a SSD hard disk. Here are the models:
    SSD hard disk:           Intel SSDSC2BF240A4L
    Magnetic hard disk:   500Gb 7200rpm HTS725050A7E635
    We deploy our Windows 7 build via a SCCM 2012 task sequence.
    Building the T440 with the magnetic hard disk was trouble free. I built it repeatedly, and encountered no errors; our core applications installed successfully every time and the task sequence completed successfully every time.
    All well and good.
    Building the T440 with the Intel SSD hard disk has been frustrating. When I run the task sequence on this machine, 8 times out of 10 the task sequence will fail, either stopping abruplty at installing Oracle Single-Sign On or Appsense agents. When the task sequence fails it is ALWAYS at one of these two apps. 
    Frustratingly, sometimes the task sequence will complete successfully on this T440.
    Given we successfully deploy this task sequence to a variety of different hardware from different vendors, including other Lenovo laptops, I can only guess the Intel SSD hard disk is the culprit. 
    Has anyone encountred anything like this? I've went through the smsts.log file and other SCCM log files and can find nothing obvious. That this ONLY happens on the T440 with the SSD suggests to me the issues lies in that direction.
    I'll swap disks in either T440 to see if the other T440 fails also with the SSD aboard, to see what happens.
    Meantime if anyone has any information about this issue I'd be grateful if you coud share.
    Thanks
    CT

    Does the install provide any logging? Does execmgr.log show any other info?
    Per the readme, it should be setup.exe.
    http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/girc15ww.txt
    Unattended Install
    This is for system administrators' use only.
    1. Refer to the Manual Install section, and download and extract the file.
    2. In the step 11 of the Installing files section, uncheck the checkbox next
    to "Install ..... now", and then select Finish to cancel installation.
    3. At the command line, execute Setup.exe with the -s option.
    Example: [Path where the files were extracted]\Setup -s
    Daniel Ratliff | http://www.PotentEngineer.com

Maybe you are looking for