Hello,

When staging a machine with standalone media (usb) applications are not installed, when staging via PXE with the same Task Sequence all applications are installed during the staging.

I checked the setting "allow this application to be installed from the install application task sequence action..."

Errors I find in smsts.log are:

<![LOG[spCIStore->StoreCIFromDisk(pInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2237)]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="cisdkclass.cpp:2237">
<![LOG[StoreCIFromDisk: Unable to store CI: 0x80004005]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="cisdkclass.cpp:2243">
<![LOG[spAppSDK->StoreCIFromDisk (&PathInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,912)]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:912">
<![LOG[StoreCIFromDisk failed]LOG]!><time="13:24:24.675-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:912">
<![LOG[StoreAppDocuments failed; 0x80004005]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:948">
<![LOG[TS::Utility::StoreAppDocuments (sAppDocs.c_str()), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,880)]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="installapplication.cpp:880">
<![LOG[StoreAppDocuments failed]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:880">
<![LOG[Step 3 out of 5 complete]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="daprogress.cpp:226">
<![LOG[Install application action failed: 'Adobe Reader XI (11.0.0.3 ) - Franais'. Error Code 0x80004005]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:798">
<![LOG[Sending error status message]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="installapplication.cpp:802">
<![LOG[sClientGUID.empty()==false, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5699)]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:5699">
<![LOG[The client GUID must be set in an environment variable]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:5699">
<![LOG[Non fatal error 0x80004005 in sending task sequence execution status message to MP]LOG]!><time="13:24:24.691-120" date="08-28-2013" component="InstallApplication" context="" type="2" thread="2644" file="utils.cpp:5811">

Any idea ?

Thanks

What SCCM version are you using?

Also can you copy paste the logs before StoreCIFromDisk: Unable to store CI: 0x80004005

Moiz

I'm using SCCM 2012 SP1 (no CU)

Hereunder what gets logged in smsts.log for each application, in this example 7-zip

<![LOG[Installing application '7-Zip 9.20']LOG]!><time="13:24:25.313-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="installapplication.cpp:782">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000001.xml]LOG]!><time="13:24:25.438-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000002.xml]LOG]!><time="13:24:25.438-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000003.xml]LOG]!><time="13:24:25.438-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000004.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000005.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000006.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000007.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000008.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000009.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000000a.xml]LOG]!><time="13:24:25.453-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000000b.xml]LOG]!><time="13:24:25.640-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000000c.xml]LOG]!><time="13:24:25.640-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000000d.xml]LOG]!><time="13:24:25.640-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000000e.xml]LOG]!><time="13:24:25.655-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000000f.xml]LOG]!><time="13:24:25.655-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000010.xml]LOG]!><time="13:24:25.655-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000011.xml]LOG]!><time="13:24:25.671-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000012.xml]LOG]!><time="13:24:25.671-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000013.xml]LOG]!><time="13:24:25.671-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000014.xml]LOG]!><time="13:24:25.702-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000015.xml]LOG]!><time="13:24:25.702-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000016.xml]LOG]!><time="13:24:25.702-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000017.xml]LOG]!><time="13:24:25.702-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000018.xml]LOG]!><time="13:24:25.702-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000019.xml]LOG]!><time="13:24:25.702-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000001a.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000001b.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000001c.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000001d.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000001e.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000001f.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000020.xml]LOG]!><time="13:24:25.718-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000021.xml]LOG]!><time="13:24:25.827-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000022.xml]LOG]!><time="13:24:25.827-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000023.xml]LOG]!><time="13:24:25.827-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000024.xml]LOG]!><time="13:24:25.951-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000025.xml]LOG]!><time="13:24:25.951-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000026.xml]LOG]!><time="13:24:25.951-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000027.xml]LOG]!><time="13:24:25.967-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000028.xml]LOG]!><time="13:24:25.967-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000029.xml]LOG]!><time="13:24:25.967-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000002a.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000002b.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000002c.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000002d.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000002e.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\0000002f.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000030.xml]LOG]!><time="13:24:25.982-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000031.xml]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000032.xml]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[Created temp document: C:\WINDOWS\TEMP\\a54-0\00000033.xml]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="utils.cpp:873">
<![LOG[spCIStore->StoreCIFromDisk(pInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2237)]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="cisdkclass.cpp:2237">
<![LOG[StoreCIFromDisk: Unable to store CI: 0x80004005]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="cisdkclass.cpp:2243">
<![LOG[spAppSDK->StoreCIFromDisk (&PathInfo), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,912)]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:912">
<![LOG[StoreCIFromDisk failed]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:912">
<![LOG[StoreAppDocuments failed; 0x80004005]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:948">
<![LOG[TS::Utility::StoreAppDocuments (sAppDocs.c_str()), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,880)]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="installapplication.cpp:880">
<![LOG[StoreAppDocuments failed]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:880">
<![LOG[Step 5 out of 5 complete]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="daprogress.cpp:226">
<![LOG[Install application action failed: '7-Zip 9.20'. Error Code 0x80004005]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="installapplication.cpp:798">
<![LOG[Sending error status message]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="1" thread="2644" file="installapplication.cpp:802">
<![LOG[sClientGUID.empty()==false, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,5699)]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="0" thread="2644" file="utils.cpp:5699">
<![LOG[The client GUID must be set in an environment variable]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="3" thread="2644" file="utils.cpp:5699">
<![LOG[Non fatal error 0x80004005 in sending task sequence execution status message to MP]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="InstallApplication" context="" type="2" thread="2644" file="utils.cpp:5811">
<![LOG[Process completed with exit code 0]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="TSManager" context="" type="1" thread="2072" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:24:25.998-120" date="08-28-2013" component="TSManager" context="" type="1" thread="2072" file="instruction.cxx:3012">

• Edited by Iske12 Thursday, August 29, 2013 6:16 AM

I believe this is a known issue which happens when application documents for a given app, for example PowerShell script which is used in application detection or some other app document contain some extended (non-ASCII) characters.

The problem has been fixed in the coming R2 release of Configuration Manger 2012 .

Workaround: do not use extended characters in app documents if you plan to use them in the deployment using stand-alone media.

• Proposed as answer by Vladimir Sorokin Thursday, August 29, 2013 7:29 PM
• Edited by Vladimir Sorokin Thursday, August 29, 2013 7:33 PM

I believe this is a known issue which happens when application documents for a given app, for example PowerShell script which is used in application detection or some other app document contain some extended (non-ASCII) characters.

The problem has been fixed in the coming R2 release of Configuration Manger 2012 .

Workaround: do not use extended characters in app documents if you plan to use them in the deployment using stand-alone media.

This is correct, however it's not always the case that the special characters are being added to the app or deployment type properties by the administrator. This issue can also occur if you enable multiple languages when you install your primary site and then add requirement rules to applications.

The applications will install during network based deployment but will fail with this error during standalone media. The root cause is the same, the app document XML which contains the global conditions includes translation to the languages you have installed. This translation can include characters which cause the install process to fail. Hopefully it will be fixed in R2, but something to be careful about in the meantime.

Mark.

• Edited by Mark_Thomas Wednesday, September 25, 2013 8:00 PM
• Marked as answer by Iske12 Thursday, September 26, 2013 5:48 AM

Thanks Mark, this clarified it because even after removing the characters like "" from comments in some scripts I still ended with the error

We installed the French language on the PS server, I'll remove it until we're on R2 :-)

• Edited by Iske12 Thursday, September 26, 2013 5:50 AM

Thanks Mark, this clarified it because even after removing the characters like "" from comments in some scripts I still ended with the error

We installed the French language on the PS server, I'll remove it until we're on R2 :-)

It's not the Windows OS language pack, it's the language support you enable during the ConfigMgr install process. I don't think you can change those after install. Mark.

I think you can, see http://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_ManageLangPacks

• Edited by Iske12 Thursday, September 26, 2013 6:22 AM

That's OK then, that should resolve it.  Not sure if you will need to remove and re-add the requirement rule afterwards to make sure that the language support is fully removed from the app document XML.  Guess you will find out soon enough... :-).

Mark.

I'll test this today and let you know

Cheers

Glad to find a recent post regarding this issue!
I myself am just starting to test a UDI setup with CM 2012 SP1 CU1. Everything works flawlessly from a PXE installation but I did notice that the applications in my first deployment via standalone media were failing. To be clear these are applications selected during the UDI wizard.
I'm still learning UDI. Would you mine clarifying exactly how to remedy this issue? It sounds like a potential special character in my application documents - but I'm not clear on where to look or what exactly needs to be changed.

• Edited by ImageGuy Monday, October 07, 2013 3:10 AM

In my case it were some scripts used as detection methods of applications.

Those scripts contained the "" character in comments (I'm at a French speaking customer), after removing those characters, updating DP's and recreating the USB media the issue went away.

BUT, also check the properties of the applications, deployment types and make sure no extended characters are in there. As Mark said it can also be due to multiple languages being installed on the site server.

Hope it helps !

Iliass

Glad to find a recent post regarding this issue!
I myself am just starting to test a UDI setup with CM 2012 SP1 CU1. Everything works flawlessly from a PXE installation but I did notice that the applications in my first deployment via standalone media were failing. To be clear these are applications selected during the UDI wizard.
I'm still learning UDI. Would you mine clarifying exactly how to remedy this issue? It sounds like a potential special character in my application documents - but I'm not clear on where to look or what exactly needs to be changed.

I am not sure that you are suffering with the same issue.  Although it is similar in that your application installs work during PXE deployment and then fail in standalone media, the big difference is that you are using UDI.  Applications selected during UDI deployment are installed using dynamic variable lists.  The UDI wizard configures the list of variables and then there is an action in the task sequence to process the list and install the apps.  This makes the deployment process very dynamic and enables application selection to be made at runtime, rather than hardcoded into the TS.

The problem is that this approach is at odds with standalone media.  When you create standalone media from a task sequence that uses dynamic variable lists for application installs you will notice that your applications are not included in the media.  This is because they are not directly referenced by the task sequence.  The task sequence is unaware of the applications that will be installed and therefore the standalone media wizard cannot get the application content and include it in the ISO/USB.  The only way to get the app content in the media is to configure the task sequence to install specific applications/packages rather than using the dynamic variables.

I have not tested this with 2012 but with 2007 the install using dynamic variable action did work during standalone media deployment.  The issue with it is that it would try and get the application content from a DP.  Therefore it relied on network connectivity etc.

We do use UDI but we have developed our own pages using the SDK and it's a completely different solution.  It should be possible to achieve what you want but not with the out-of-box configuration.  You will need to make some significant changes to both the UDI wizard configuration and task sequence to get this to work. Perhaps someone who is using the standard UDI setup might be able to advise if this is achievable.

Mark.

We are just starting our standalone task sequence media development (we call it OSD To Go), and we also use UDI in our environment.

When we started to create our standalone media, we noticed it didn't detect all of the packages configured in UDI. I just had a thought that I haven't tested yet.

My thought is to create a New Group in the Task Sequence we're using to create the standalone media. Then in the options of that new group, create a bogus task sequence variable condition. That way, it skips over the group when the task sequence runs. Then under the group, add all of the packages\applications you're calling in UDI.

Like I said, I haven't tried it yet, but hopefully that will work.

Any other ideas?

Also keep in mind that if you use Auto Apply Drivers, that won't work with Standalone Media. We are including the NIC driver in our task sequences and installing Lenovo System Update or Dell System Update utilities so the imager can download the remaining drivers\software after the process is completed.

• Edited by Joshua.Luke Thursday, December 05, 2013 6:02 PM

What I suggested above worked at putting the applications/packages on the standalone media, but they didn't install.

To me, that would mean that the "Install software packages according to dynamic variable list" option isn't using the same package source as the "Install a single software package" option.

We have steps that are set to Install a single software package and those install just fine.

Also I see in the registry (HKLM\SOFTWARE\Microsoft\MPSD\OSD) that our package selections in UDI were correctly written to the dynamic PACKAGES variable.

Seems like a bug to me.

What I suggested above worked at putting the applications/packages on the standalone media, but they didn't install.

To me, that would mean that the "Install software packages according to dynamic variable list" option isn't using the same package source as the "Install a single software package" option.

We have steps that are set to Install a single software package and those install just fine.

Also I see in the registry (HKLM\SOFTWARE\Microsoft\MPSD\OSD) that our package selections in UDI were correctly written to the dynamic PACKAGES variable.

Seems like a bug to me.

It's not a bug, it's by design. Install apps using dynamic variables is not supported in standalone media deployment. The standard UDI template uses dynamic variable lists as the apps are selected at runtime and therefore the install actions have to be dynamic. Adding dummy install application steps to the task sequence will ensure that the application content is included in the media but it would never be used.

As I mentioned in a post above the out-of-box solution will not allow you to use UDI to select apps during standalone media deployment. We have built our own UDI pages and standalone media support using the UDI and ConfigMgr SDKs which has enabled us to build this functionality. However it's a lot of work but was viable for us as we have 160,000 seat environment. It would be nice if MDT/ConfigMgr provided this functionality out of the box, but it doesn't.

Mark.

• Edited by Mark_Thomas Saturday, December 21, 2013 10:35 PM

We are seeing the same exact issue as the original posted now that we have upgraded to ConfigMgr 2012 R2 and MDT 2013 in our images.  In our case, the issue seems to be related to the number of applications linked in a task sequence and a certain combination of security patches.  Here is our scenario:

- We capture a new "base" image with all of the latest patches and the ConfigMgr 2012 R2 client.  We generate quarterly patched "base" images.  The "base" image is basically the DVD image from SA that is patched up to the current quarter.  This is done as a means to speed up deployment of our "thin" image.

- We create an MDT 2013 task sequence that has 11 (or more) applications to be installed during the "thin" imaging process.

- Delivering the image via the network/PXE works fine - Everything installs great.

- Delivering the image via USB FAILS - When combing through the logs, we see the same "StoreCIFromDisk: Unable to store CI: 0x80004005" error referenced by the original poster.

- If we reduce the number of applications linked in the task sequence down below 10 (any combination), the USB image works fine.

This has been pretty maddening to track down and seems to be related to a security patch or multiple security patches.  We have gone through and tried combinations of applicable security patches from 2009 to 2013, getting down to about a list of 50 possible patches being the issue.  Each time, we have to capture a new image with the set of security patches we want to test, generate a new USB image, and test in a virtual machine - It's very time consuming. 

Does anyone have any ideas on this one? 

Do you install updates for different languages ?

I'd check the applications also, check all the content (we had to open every file :-/) and also the application definitions and make sure you have no special characters like and so on.

We identified 3 apps like this that we excluded from the USB standalone media and now works fine.

Although you have the R2 version which should have solved this special characters issue...

I'm using 2012 R2, with only the English Lang Pack Installed for Config Man.

I've just had this error as per the OP:

StoreCIFromDisk: Unable to store CI: 0x80004005
StoreCIFromDisk failed
StoreAppDocuments failed; 0x80004005
StoreAppDocuments failed
Install Static Applications failed, hr=0x80004005

Strangely, before the application (that fails) tries to install, I get a load of these lines:

Created temp document: C:\WINDOWS\TEMP\\a9c-0\00000001.xml

It seems to be the only application that does this.

But, when we rebuilt the machine a 3rd time from the same USB stick it worked fine.

I may try grouping the applications in the Task Sequence into application lists, as the poster above suggested it appears when you install over 10 applications.

Try putting a sleep just before the install apllication step. Randomly, I had the same issue on some deployments. MS support suggested putting a 30 seconds sleep (ping 127.0.0.1 -n 30 or Powershell) and the issue didn't reoccur since.

Hope it helps

Iliass