Share via


Application Installs Fail During OSD

Question

Wednesday, August 29, 2012 3:52 PM

I am trying to deploy a list of applications during my OSD TS for Win7 SP1 x64.  Everything runs as expected except the application installations, which error out with 0x80004005.  Each of the applications deploys successfully from the Application Catalog, but fail during OSD.  The machine is within the IP boundary of the site, SMSMP=<server_name>.<domain_name>.com is specified in the Setup Windows and ConfigMgr TS step, and the machine reboots right after that step, before trying to install any applications.

Here is an excerpt from the TS report:

Setting Server Certificates.
Setting Authenticator.
Set authenticator in transport
Sending StatusMessage
Default CSP is Microsoft Enhanced RSA and AES
Cryptographic Provider
Default CSP Type is 24
Setting message signatures.
Setting the authenticator.
Policy Evaluation failed, hr=0x80004005
Install application action failed: 'AnyConnect Posture
Module - (Deploy)'. Error Code 0x80004005
CLibSMSMessageWinHttpTransport::Send: URL:
<server_name>.<domain_name>.com:443 CCM_POST
/ccm_system_AltAuth/request
In SSL, but with no client cert
In SSL, but with no media cert
Request was succesful.
hrInstallation, HRESULT=80004005 (e:\nts_sccm_release
\sms\client\osdeployment\installapplication
\installapplication.cpp,799)
pInstall->InstallApplications(saAppNames,
sContinueOnError), HRESULT=80004005 (e:
\nts_sccm_release\sms\client\osdeployment
\installapplication\main.cpp,277)
Install application action cannot continue.
ContinueOnErrorFlag is set to false.
Install Static Applications failed, hr=0x80004005

Does anyone know how to fix this?  I've seen several things in various searches online, but nothing with a solution that's worked.

All replies (22)

Thursday, September 13, 2012 6:32 PM ✅Answered

After digging through more logs and paying close attention to timestamps, it turned out the client was not assigned to the correct site yet, because it was trying to assign itself to a different site based on GPO.  This is despite the fact that the GPO is no longer in place and the registry entries that the GPO implements were removed from the image.  I was able to get the applications to install by removing the GPO-created registry entries by using F8 and opening regedit while the TS was running and before it got to the Install Applications step.

What's left is to figure out where the GPO-based registry entries come from during the TS if the GPO is gone and the registry entries were removed from the WIM.


Monday, September 17, 2012 2:09 PM ✅Answered

Re-creating the image to incorporate the updated GPO did the trick.  I'll have to create a new image from scratch in the near future.


Wednesday, August 29, 2012 4:45 PM

Try the hotfix described in this kb: http://support.microsoft.com/kb/2522623 . It is a Win 7 hotfix that you can apply in the TS using a classic package/program (along with a reboot) before you try to install any Applications.

Jason | http://blog.configmgrftw.com


Wednesday, August 29, 2012 6:45 PM

I set the hotfix to install and reboot just before any applications installed, but it didn't change anything.  I did verify that the hotfix was installed once the OS loaded, but like I said, no change.


Wednesday, August 29, 2012 7:03 PM

Is it failing with the same error?

Note, you should be using smsts.log from the client to troubleshoot issues. Can you please review it for better information?

Jason | http://blog.configmgrftw.com


Wednesday, August 29, 2012 7:10 PM

The reports show the same error, but the smsts log doesn't show any errors.  Here's the piece of the log that references one of the applications.

<![LOG[
Parsing step node: Install Secure Mobility Client]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:474">
<![LOG[A condition is associated with the step found]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:659">
<![LOG[Found and operator.]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:737">
<![LOG[There are 1 operands]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:772">
<![LOG[**Processing expression node]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:781">
<![LOG[Found SMS_TaskSequence_VariableConditionExpression expression.]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:806">
<![LOG[**In ProcessBuiltInCondition node: expression]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:898">
<![LOG[There are 3 operands in the built in action]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:915">
<![LOG[Operand Operator=equals]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:929">
<![LOG[Operand Value=TRUE]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:929">
<![LOG[Operand Variable=ISLaptop]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:929">
<![LOG[Successfully added 3 condition parameters]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="0" thread="2284" file="tsxml.cpp:994">
<![LOG[Disable: ]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_6AD9F4C7-068B-4259-A8A6-42864A1E6272/Application_a7f41e39-a78d-4b7a-ae83-f32cca219586 /basevar: /continueOnError:False]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:522">
<![LOG[Adding instruction at 67]LOG]!><time="13:30:07.255+300" date="08-29-2012" component="TSManager" context="" type="1" thread="2284" file="tsxml.cpp:524">


Wednesday, August 29, 2012 7:17 PM

Where are you looking for the smsts.log? It always has all of the information from a task sequence in it.

Jason | http://blog.configmgrftw.com


Wednesday, August 29, 2012 7:23 PM

The excerpt above was taken from C:\Windows\CCM\Logs\smsts-20120829-133016.log.


Wednesday, August 29, 2012 7:31 PM

What about smsts.log? The one with the time and date (above) is the older log.

Jason | http://blog.configmgrftw.com


Wednesday, August 29, 2012 7:35 PM

I checked that first, but all it has is one line that says "Successfully finalized logs to SMS client log directory..."


Thursday, August 30, 2012 12:20 AM

It may have already wrapped and thus may not be available anymore.

Have you added the SMSMP public property to the Setup Windows and ConfigMgr task?

Jason | http://blog.configmgrftw.com


Thursday, August 30, 2012 12:38 AM

Yes, I have added that.


Wednesday, September 5, 2012 12:51 AM

Can you please check the CIAgent.log and CIDownloader.log files for any errors around the time this failure occured?

Thanks,

Moiz


Tuesday, September 11, 2012 2:32 PM

I see several 0x80004005 errors in both logs.  DownloadPackages failed (0x80004005) and StartDownload failed (0x80004005) show in CIDownloader.log; InitiateCIDownload failed (0x80004005) and HandleEvent failed (0x80004005) show in CIAgent.log.  It looks like there is one set of each error for each piece of software I'm trying to install.  Why would the machine be unable to download the content from the DP even though it's within the boundary and on the domain?


Thursday, September 13, 2012 6:39 PM

Your image.

Did you join the domain when creating your image? If so, bad joo-joos.

Jason | http://blog.configmgrftw.com


Thursday, September 13, 2012 6:42 PM

Yes, I did and haven't had any problems thus far.  I don't get where the assignment registry entries would be coming from though, since I removed from the registry in the WIM.  I mounted the WIM file, loaded the HKLM\SOFTWARE hive, removed the required entries, unloaded the hive, and committed the WIM.  I've even re-mounted it to verify the entries are gone.  Do I need to re-make the image again since the GPO for site assignment has been removed so that the GPO in the image doesn't re-populate the entries?


Thursday, September 13, 2012 7:01 PM

Did you check HKLM\Software\Wow6432Node (assuming this is a 64-bit OS)?

As mentioned, joining a reference system to the domain is asking for trouble and is generally discouraged. So yes, I would recreate your image (using a build and capture task sequence) and not join the domain. There is no reason to join a domain to create a reference image.

Jason | http://blog.configmgrftw.com


Thursday, September 13, 2012 7:03 PM

Yes, I did check Wow6432Node.  I haven't re-built the image from the ground up because I don't know all of the customizations that went into the original image in the first place.  The task sequence I have now simply loads the existing image, applies updates, and captures.  I'm in the process of doing that now to see what happens, but I may just have to suck it up and re-create the image from scratch.


Thursday, September 13, 2012 7:10 PM

Just to get on my soapbox, this is perfect validation for using a build and capture task sequence. The fact that there's any question over what went into an image is scary.

Jason | http://blog.configmgrftw.com


Wednesday, June 26, 2013 4:40 PM

Hello,

seems to have the same troubles !

Can you point the gpo registry key deleted  ?

Thanks in advance !


Wednesday, June 26, 2013 5:00 PM

HKLM\Software\Microsoft\Sms\Mobile Client -> GPAssigned ... (typed from memory, so it might be slightly different)

Torsten Meringer | http://www.mssccmfaq.de


Thursday, June 27, 2013 4:10 PM

Thanks for reply !