Jump to content


Phylum

Download Failed During OSD TS

Recommended Posts

After dropping the WIM on the workstation I'm running Windows Updates (a few times) and manually rebooting for good measure before moving onto application installations.

When the machine comes back up & begins the Application Installation section, it fails on the first application installation which happens to be .NET 4.5.2. The error presented is a not-very-helpful 0x80004005.

 

Selection from smsts.log

CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
Passed in version 8 for ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
DCMAgentJob({41A895F7-27AD-4D46-9EFA-DF72832C735F}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Success) DCMAgent 7/2/2014 6:55:24 PM 2528 (0x09E0)
DCMAgentJob({41A895F7-27AD-4D46-9EFA-DF72832C735F}): CDCMAgentJob::HandleEvent(Event=NotifyProgress, CurrentState=Success) DCMAgent 7/2/2014 6:55:24 PM 2172 (0x087C)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74.8 = DownloadFailed DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
GetAppMgmtSDKInterface successful InstallApplication 7/2/2014 6:55:24 PM 1644 (0x066C)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
Passed in version 8 for ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74.8 = DownloadFailed DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
GetAppMgmtSDKInterface successful InstallApplication 7/2/2014 6:55:24 PM 1644 (0x066C)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
Passed in version 8 for ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
CIAgentJob({9476DA7D-7E0E-4BEC-99F0-DC734671E08B}): Client requesting CIAgentJob context info for key: StateMessagePriority CIAgent 7/2/2014 6:55:24 PM 2772 (0x0AD4)
DCMAgentJob({41A895F7-27AD-4D46-9EFA-DF72832C735F}): CDCMAgentJob::HandleEvent(Event=Transition, CurrentState=Success) DCMAgent 7/2/2014 6:55:24 PM 2772 (0x0AD4)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74.8 = DownloadFailed DCMAgent 7/2/2014 6:55:24 PM 1644 (0x066C)
NotifyComplete received InstallApplication 7/2/2014 6:55:24 PM 1644 (0x066C)
NotifyComplete processed InstallApplication 7/2/2014 6:55:24 PM 1644 (0x066C)
Received job completion notification from DCM Agent InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
GetAppMgmtSDKInterface successful InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 2116 (0x0844)
GetAllInstances - 866 instance(s) of 'CCM_StateMsg' found StateMessageProvider 7/2/2014 6:55:24 PM 2756 (0x0AC4)
State message(State ID : 2) with TopicType 1703 and TopicId DEP-AP220054-ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/Application_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 has been recorded for SYSTEM StateMessage 7/2/2014 6:55:24 PM 2772 (0x0AD4)
Passed in version 8 for ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 DCMAgent 7/2/2014 6:55:24 PM 2116 (0x0844)
CDCMAgentJobMgr::DeleteJob - Request to delete DCM Agent job {41A895F7-27AD-4D46-9EFA-DF72832C735F} DCMAgent 7/2/2014 6:55:24 PM 2772 (0x0AD4)
CAppMgmtSDK::GetEvaluationState ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74.8 = DownloadFailed DCMAgent 7/2/2014 6:55:24 PM 2116 (0x0844)
Installation job completed with exit code 0x00000000 InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Execution status received: 24 (Application download failed ) InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
App install failed. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting TSEnv variable '_TSAppInstallStatus'='Error' InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting TSEnv variable 'SMSTSInstallApplicationJobID__ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/Application_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74'='' InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Completed installation job. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Step 2 out of 2 complete InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Install application action failed: '.NET Framework 4.5.2'. Error Code 0x80004005 InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Sending error status message InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting URL = http://dpmpfsp.F.Q.D.N, Ports = 80,443, CRL = false InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting Server Certificates. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting Authenticator. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Set authenticator in transport InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting Media Certificate. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Sending StatusMessage InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting message signatures. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Setting the authenticator. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
CLibSMSMessageWinHttpTransport::Send: URL: dpmpfsp.F.Q.D.N:80 CCM_POST /ccm_system/request InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Request was successful. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Install application action cannot continue. ContinueOnErrorFlag is set to false. InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
hrInstallation, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\installapplication\installapplication.cpp,914) InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\installapplication\main.cpp,277) InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Install Static Applications failed, hr=0x80004005 InstallApplication 7/2/2014 6:55:24 PM 2116 (0x0844)
Process completed with exit code 2147500037 TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
!--------------------------------------------------------------------------------------------! TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Failed to run the action: Install .NET 4.5.2.
Unspecified error (Error: 80004005; Source: Windows) TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
MP server http://dpmpfsp.F.Q.D.N. Ports 80,443. CRL=false. TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Setting authenticator TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Set authenticator in transport TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Sending StatusMessage TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Setting message signatures. TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Setting the authenticator. TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
CLibSMSMessageWinHttpTransport::Send: URL: dpmpfsp.F.Q.D.N:80 CCM_POST /ccm_system/request TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Request was successful. TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Let the parent group (Build the Reference Machine) decide whether to continue execution TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Clear local default environment TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Let the parent group (Install Applications - Update) decides whether to continue execution TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
The execution of the group (Build the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)
Failed to run the last action: Install .NET 4.5.2. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows) TSManager 7/2/2014 6:55:24 PM 2136 (0x0858)

 

 

I opened a bunch of other logs (see attached) and found some alarming errors like:

 

Unable to read Associations Policy for ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/Application_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74 : 0x0 CIDownloader 7/2/2014 6:55:21 PM 2628 (0x0A44)

...
CCIDownloader::StartJob CIDownloader 7/2/2014 6:55:21 PM 2628 (0x0A44)
CIDownloader job empty. CIDownloader 7/2/2014 6:55:21 PM 2628 (0x0A44)
CCIDownloader::DeleteJob for job {01A18AE2-A596-42D3-AC7C-27BB102FAB63} CIDownloader 7/2/2014 6:55:21 PM 2628 (0x0A44)
...
Failed to get the display name of the CI. Status messages will be based on the CI ID. CIAgent 7/2/2014 6:55:21 PM 2628 (0x0A44)
...
Conformant Rule:5fed7d11_23e5_46ef_9648_ec05eb82e271__ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8_Configuration_PolicyDocument not found DCMReporting 7/2/2014 6:55:21 PM 2172 (0x087C)
No ConfigPoints found for rule:System Center Configuration Manager.ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8_Platform_PolicyDocument.8.Platform_Rule_ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8 DCMReporting 7/2/2014 6:55:21 PM 2172 (0x087C)
In policy:ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8_Platform_PolicyDocument, rule:Platform_Rule_ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8 status is:Conformant DCMReporting 7/2/2014 6:55:21 PM 2172 (0x087C)
No ConfigPoints found for rule:System Center Configuration Manager.ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8_Platform_PolicyDocument.8.5fed7d11_23e5_46ef_9648_ec05eb82e271__ScopeId_900CC2BB_3300_42BE_8F1B_14256C0D511D_Application_1ddbba79_a3f8_4f17_9afd_bb75b3e7fe74_8_Platform_PolicyDocument DCMReporting 7/2/2014 6:55:21 PM 2172 (0x087C)
...
GetLogonUserSid failed at GetTokenSids 0x800703f0 ContentAccess 7/2/2014 6:55:23 PM 2628 (0x0A44)
Requesting locations synchronously for content Content_b921ce6f-c9d8-4f08-97d5-28546e85340b.1 with priority Foreground ContentAccess 7/2/2014 6:55:23 PM 2628 (0x0A44)
Unable to retrieve AD site membership LocationServices 7/2/2014 6:55:23 PM 2628 (0x0A44)
Failed to send Location Request Message ContentAccess 7/2/2014 6:55:23 PM 2628 (0x0A44)
Failed to create Location Request Message body ContentAccess 7/2/2014 6:55:23 PM 2628 (0x0A44)
GetLocationSyncEx failed with error 0x8000000a ContentAccess 7/2/2014 6:55:23 PM 2628 (0x0A44)
...
Unable to get locations, no need to continue with download CITaskMgr 7/2/2014 6:55:23 PM 2628 (0x0A44)
CheckLocations failed. Error = 0x87d00607 CITaskMgr 7/2/2014 6:55:23 PM 2628 (0x0A44)
No location available : CTaskConsumer(ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/DeploymentType_11dfcd87-93ca-4d9c-b31d-47e3bb8462d2.6.{9476DA7D-7E0E-4BEC-99F0-DC734671E08B}) CITaskMgr 7/2/2014 6:55:23 PM 2628 (0x0A44)
State transition to (Failure), Param(-2016410105) : CTaskConsumer(ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/DeploymentType_11dfcd87-93ca-4d9c-b31d-47e3bb8462d2.6.{9476DA7D-7E0E-4BEC-99F0-DC734671E08B}) CITaskMgr 7/2/2014 6:55:23 PM 2628 (0x0A44)
...
Job({9476DA7D-7E0E-4BEC-99F0-DC734671E08B}): Handling dependency failure : Task(ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/RequiredApplication_1ddbba79-a3f8-4f17-9afd-bb75b3e7fe74.8.ContentDownload) CIAgent 7/2/2014 6:55:23 PM 2628 (0x0A44)
...
Remove failed. Error 0x80041002 : CITask(ScopeId_900CC2BB-3300-42BE-8F1B-14256C0D511D/DeploymentType_11dfcd87-93ca-4d9c-b31d-47e3bb8462d2.6..Install.ContentDownload) CITaskMgr 7/2/2014 6:55:24 PM 2772 (0x0AD4)

Note: I just selected a handful of errors via cmtrace & copied so there's a bunch of extra stuff in between these lines hence the ...'s

 

When booting from media:

  • it finds the right TS' exposed to that device collection
  • it drops the image
  • downloads the offline updates all of which are packages
  • downloads & executes other scripts which are also packages

I'm concerned this may be an indication of a configuration issue versus a problem with the TS itself or the steps within the TS. Perhaps its a configuration item that's not set [correctly] that manifests itself this way.

 

 

Some details:

  • SCCM 2012 R2 CU1 on Server 2008 R2
  • Servers (Site & DP/MP/FSP) and clients are physically in the same site
  • Deploying Windows 7 Enterprise with SP1
  • This is a Build & Capture TS so the machine isn't joined to the domain
  • Verified MP was published in AD in DNS & via nslookup -type=srv _mssms_mp_ap2._tcp.F.Q.D.N
  • Boundary Groups
    • enabled "use this boundary group for site assignment"
    • specified correct assigned site (only one)
    • added the correct site system server under content location (only one)
    • added all the boundaries for this location
  • Boundaries
    • have been defined by IP Address Range and Active Directory Site
    • have been added to the Boundary Group (always many boundaries to one boundary group; not many to many)
    • site systems tab shows correct site system (just the one)
    • boundary groups shows correct boundary group (just the one)
    • checked a handful of boundaries for this specific office - they're all the same.
    • while several IP ranges have been explicitly defined for this and other offices, its not an exhaustive list; for instance my specific range (10.1.37.0-255) hasn't been specified. however, an over-arching IP address range does exist (10.1.0.1-10.1.255.254) which should catch everything, right? If no, then how does anything work on this vlan?
  • Client Installation Settings > Client Push Installation Properties:
    • Client Push Installation Account specified
    • Installation Properties: SMSSITECODE=AP2 FSP=dpmpfsp.f.q.d.n SMSMP=dpmpfsp.f.q.d.n DNSSUFFIX=f.q.d.n
  • Setup Windows and Configuration Manager TS step properties:
    • SMSMP=dpmpfsp.f.q.d.n FSP=dpmpfsp.f.q.d.n DNSSUFFIX=f.q.d.n PATCH="%_SMSTSMDataPath%\Packages\AP200003\hotfix\KB2938441\Client\x64\configmgr2012ac-r2-kb2938441-x64.msp"
  • Offline Updates are applied via DISM right after the WIM is applied
    • Enterprise roll up and 3 regression hotfixes
    • Windows 7 updates that are known to require multiple reboots (See: http://support.microsoft.com/kb/2894518)
    • Some other known required hotfixes (prevent BSOD's after resuming from sleep, slow login time fix etc.)
  • .NET Package is sound:
    • Manual installation by running the batch/command line is successful
    • Push of .NET 4.5.2 to existing clients is successful
    • Installing .NET 4.5.2 via OSD TS without doing Windows Updates & reboots is successful

 

Could it be because I have both IP Address Ranges and AD Sites boundaries specified? I would like to think that if it was a site assignment/boundary/boundary group issue, nothing would work (i.e.: it wouldn't locate TS' so the process would fail from the very beginning) and it would fail all the time, regardless of whether or not windows updates & reboots are in the mix; Right?

 

What have I missed?

smsts.log

CAS.log

CIAgent.log

CIDownloader.log

CIStateStore.log

LocationServices.log

CITaskMgr.log

Share this post


Link to post
Share on other sites

It's an app and not old package, correct? I've long since abandoned using apps in OSD. It's just too error prone. I use apps when pushing software to existing clients but during OSD i only use packages. Haven't had a problem since.

 

In your case it seems like software updates are messing up the .net installation, correct? What updates are you installing? Is .net already in one of your software update groups perhaps, and maybe already installed when the app installation commences?

Share this post


Link to post
Share on other sites

Also attach the appenforce log file, if app, or execmgr log file if package. 8004005 is just a generic error like "something went wrong". The real error code is always listed earlier in smsts.log or in this case in appenforce/execmgr.

Share this post


Link to post
Share on other sites

It's an app and not old package, correct? I've long since abandoned using apps in OSD. It's just too error prone. I use apps when pushing software to existing clients but during OSD i only use packages. Haven't had a problem since.

 

In your case it seems like software updates are messing up the .net installation, correct? What updates are you installing? Is .net already in one of your software update groups perhaps, and maybe already installed when the app installation commences?

Correct, .NET is an app.

Software updates seems to break the installation of any application. If I skip the .NET install and go to IE11 or Office 2010 it fails the same way.

 

What updates am I installing? That's good & somewhat difficult question to answer.

I imported a fresh Windows 7 SP1 Enterprise WIM, performed Schedule Updates which installed 93 successfully. I went back to Schedule updates it again, only this time it said 71 were needed. However, whether I do all 71, half or even just 2, all the updates fail with the same errors:

Processing image at index 1	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:02:32 PM	10352 (0x2870)
Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\12300119\updated-install.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\12300119\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:02:32 PM	10352 (0x2870)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 18015	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:25:03 PM	10352 (0x2870)
Checking if update (1 of 71) with ID 16811634 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:25:04 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\fc38fd35-1f4f-4c53-ba73-090c80368750\windows6.1-kb2835364-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:11 PM	10352 (0x2870)
Applying update with ID 16811634 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:11 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:33 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:33 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:26:33.398 2014 ISTR0="16811634" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:33 PM	10352 (0x2870)
Failed to install update with ID 16811634 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:33 PM	10352 (0x2870)
Checking if update (2 of 71) with ID 16811689 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:33 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\28ed6c22-0b13-4202-a27a-17618cc6728e\windows6.1-kb2840631-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:40 PM	10352 (0x2870)
Applying update with ID 16811689 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:40 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:48 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:48 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:26:48.430 2014 ISTR0="16811689" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:48 PM	10352 (0x2870)
Failed to install update with ID 16811689 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:48 PM	10352 (0x2870)
Checking if update (3 of 71) with ID 16812324 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:48 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\62ad16de-b149-43c7-83ff-5e68fad8de26\windows6.1-kb2847927-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:55 PM	10352 (0x2870)
Applying update with ID 16812324 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:26:55 PM	10352 (0x2870)
Failed to install update with ID 16812324 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:03 PM	10352 (0x2870)
Checking if update (4 of 71) with ID 16815183 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:03 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\5096a2f8-d460-4cc9-9b84-5bb1c4a22255\windows6.1-kb2862966-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:10 PM	10352 (0x2870)
Applying update with ID 16815183 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:10 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:17 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:17 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:17.208 2014 ISTR0="16815183" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:17 PM	10352 (0x2870)
Failed to install update with ID 16815183 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:17 PM	10352 (0x2870)
Checking if update (5 of 71) with ID 16815205 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:17 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\bea7d7ae-09fe-486a-8a84-6190970c7779\windows6.1-kb2861855-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:24 PM	10352 (0x2870)
Applying update with ID 16815205 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:24 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:31 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:31 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:31.452 2014 ISTR0="16815205" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:31 PM	10352 (0x2870)
Failed to install update with ID 16815205 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:31 PM	10352 (0x2870)
Checking if update (6 of 71) with ID 16815279 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:31 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\88cc81ec-b8b5-4c60-8dfa-ce430024142d\windows6.1-kb2849470-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:38 PM	10352 (0x2870)
Applying update with ID 16815279 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:38 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:46 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:46 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:27:46.081 2014 ISTR0="16815279" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:46 PM	10352 (0x2870)
Failed to install update with ID 16815279 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:46 PM	10352 (0x2870)
Checking if update (7 of 71) with ID 16815432 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:46 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\f3497d26-7995-4f66-8b3e-fdb692093111\windows6.1-kb2844286-v2-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:54 PM	10352 (0x2870)
Applying update with ID 16815432 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:27:54 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:01 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:01 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:01.719 2014 ISTR0="16815432" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:01 PM	10352 (0x2870)
Failed to install update with ID 16815432 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:01 PM	10352 (0x2870)
Checking if update (8 of 71) with ID 16815924 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:01 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\1287f24a-6df3-4845-9181-451e37873202\windows6.1-kb2803821-v2-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:08 PM	10352 (0x2870)
Applying update with ID 16815924 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:08 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:15 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:15 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:15.544 2014 ISTR0="16815924" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:15 PM	10352 (0x2870)
Failed to install update with ID 16815924 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:15 PM	10352 (0x2870)
Checking if update (9 of 71) with ID 16816368 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:15 PM	10352 (0x2870)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\46953317-9ed4-49b3-9d2e-0463dffec251\windows6.1-kb2853952-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:22 PM	10352 (0x2870)
Applying update with ID 16816368 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:22 PM	10352 (0x2870)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:29 PM	10352 (0x2870)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:29 PM	10352 (0x2870)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMSERVER.F.Q.D.N SITE-123 PID=15324 TID=10352 GMTDATE=Fri Jun 27 19:28:29.568 2014 ISTR0="16816368" ISTR1="12300119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:29 PM	10352 (0x2870)
Failed to install update with ID 16816368 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:29 PM	10352 (0x2870)
Checking if update (10 of 71) with ID 16816380 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	6/27/2014 3:28:30 PM	10352 (0x2870) 

I tried again today just to see, but its still failing even with just 2 updates, so its not a quantity issue.

Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 18015	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:27 PM	2920 (0x0B68)
Checking if update (1 of 2) with ID 16811634 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:27 PM	2920 (0x0B68)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\fc38fd35-1f4f-4c53-ba73-090c80368750\windows6.1-kb2835364-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:41 PM	2920 (0x0B68)
Applying update with ID 16811634 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:41 PM	2920 (0x0B68)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:47 PM	2920 (0x0B68)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:47 PM	2920 (0x0B68)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=siteserver.f.q.d.n SITE=AP2 PID=6300 TID=2920 GMTDATE=Sat Jul 05 16:07:47.367 2014 ISTR0="16811634" ISTR1="AP200119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:47 PM	2920 (0x0B68)
Failed to install update with ID 16811634 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:47 PM	2920 (0x0B68)
Checking if update (2 of 2) with ID 16811689 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:47 PM	2920 (0x0B68)
Applicability State = APPLICABLE, Update Binary = D:\ConfigMgr_OfflineImageServicing\28ed6c22-0b13-4202-a27a-17618cc6728e\windows6.1-kb2840631-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:52 PM	2920 (0x0B68)
Applying update with ID 16811689 on image at index 1.	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:52 PM	2920 (0x0B68)
Failed to install update with error code -2146498512	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:56 PM	2920 (0x0B68)
InstallUpdate returned code 0x800f0830	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:56 PM	2920 (0x0B68)
STATMSG: ID=7911 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=siteserver.f.q.d.n SITE=AP2 PID=6300 TID=2920 GMTDATE=Sat Jul 05 16:07:56.409 2014 ISTR0="16811689" ISTR1="AP200119" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:56 PM	2920 (0x0B68)
Failed to install update with ID 16811689 on the image. ErrorCode = 2096	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:56 PM	2920 (0x0B68)
UnMounting Image (Commit Changes = 0) ...	SMS_OFFLINE_SERVICING_MANAGER	7/5/2014 12:07:56 PM	2920 (0x0B68)

So to workaround that specific Schedule Update problem, I created a Build & Capture TS that will

  1. apply the WIM that has the 93 updates already
  2. Opt-in to Microsoft Updates
  3. scan for updates via 'WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE'
  4. Install updates
  5. Reboot
  6. Repeat steps 3,4 & 5 three more times to be sure its fully up to date
  7. Install other things that should be 'baked in' like .NET 4.5.2 & IE11
  8. Run steps 3,4 & 5 to be sure those packages are up to date
  9. Capture image

At Step 4 it shows 157 updates are needed (!) so I don't have an exact list. However, everything works fine until I get down to step 7.

 

 

Also attach the appenforce log file, if app, or execmgr log file if package. 8004005 is just a generic error like "something went wrong". The real error code is always listed earlier in smsts.log or in this case in appenforce/execmgr.

 

The AppEnforce.log doesn't exist, and the execmgr.log only contains these lines:

Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
If the client is not yet registered, this is expected behavior.	execmgr	7/2/2014 6:28:00 PM	2256 (0x08D0)
Software distribution agent was enabled	execmgr	7/2/2014 6:28:01 PM	2372 (0x0944)
Service startup.	execmgr	7/2/2014 6:46:12 PM	2940 (0x0B7C)
Service startup.	execmgr	7/2/2014 6:47:59 PM	2748 (0x0ABC)
Service startup.	execmgr	7/2/2014 6:50:19 PM	2752 (0x0AC0)
Service startup.	execmgr	7/2/2014 6:52:45 PM	2752 (0x0AC0)
Service startup.	execmgr	7/2/2014 6:55:10 PM	2772 (0x0AD4)

Being very new to SCCM, I'm open to the possibility that I've done or am doing something wrong.

I'm curious, when SCCM admins prepare for a new OS deployment (specifically Windows 7 but it I'm sure it would also apply to Windows 8+, Server 2008+ etc.):

How are people keeping their WIM's up to date with Windows (OS/CBS) and Microsoft (other Microsoft products like Office) updates?

How are people creating that 'gold' WIM that's used throughout the organization?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.