I have an Application defined for Office 2010 Pro Plus.  I have tested it through a running client OS on my desk and the content downloads and installs fine.  I have configured my boundary groups to contain boundaries for my environment.  I have a network access account configured within the Software Distribution component.  I want to install this application during OSD of a reference build, workgroup joined system.  I have SMSMP=server.domain.com defined in my task sequence "Setup Windows and ConfigMgr" step.

"Installation of Application Office 2010 Pro Plus failed - 0x8000405"

I look at the CAS.log and I see that the system is failing to download the content, however it DOES show successful location of content on the local DP.  I notice that the CAS.log shows the "context" of the download is SYSTEM - shouldn't this be using the network access account?  Is there a problem here in that the Application Install mechanism isn't trying to use the Client Network access account?

Installation of "Legacy" packages works fine, I even created a "Legacy" Office 2010 package and this downloads and installs fine.  Has anyone else managed to build a workgroup joined reference PC using ConfigMgr 2012 with additional "Applications"?

I have tried, to no avail, using both Subnet and IP Range boundaries.

Andy

• Edited by Andrew Lukaszewski Thursday, April 26, 2012 6:29 PM

Hi Andrew,

I failed to add the boundaries to a boundary group. Application installs would not work before I did that.

Hi Andrew,

I failed to add the boundaries to a boundary group. Application installs would not work before I did that.

Have you enabled Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting on your Office 2010 app?

Panu

Have you enabled Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting on your Office 2010 app?

Panu

• Edited by Andrew Lukaszewski Tuesday, May 01, 2012 4:16 PM

Have you entered a valid network access account?

I'll give it a shot. Do you have an AppEnforce.log file? If yes, what does it say? You should also check the IIS logs on the DP if you see any 401 access denied not followed by a 200 OK message. The SCCM agent will first try to access the DP with it's computer account, if it fails it will try again with the Network Access Account. In my experience it will not try anything if the CI is not evaluated to be applicable for your system, and the installation is detected (AppEnforce.log). In my situation the CI was applicable but the installation method was not detected because of my failure to add the subnet range to a boundary group. Therefore the next step might be to check any App*.log files for errors. This is what I experienced when I was struggeling with this very issue, please correct me if I'm wrong.

 In my situation the CI was applicable but the installation method was not detected because of my failure to add the subnet range to a boundary group. 

This applied to me, too. We have a number of VLANs, and during OSD the clients were assigned to a 'build' or similar range to segregate them during deployment. 

Strange to see that it presented as a straight 0x8000405, though.

Hi Andrew,

Confirming I have observed this same behaviour during builds, and have had to revert to the package model for now (I also got a 0x8000405 error if the "detectoid" for an application install was invalid...)

Sounds like something for SP1?

:)

I think I have figured out what the problem was in my case - it would seem that if you want to install "Applications" to a workgroup joined system during an OSD Task Sequence, then you must specify the SMSMP=servername.yourdomain.com in the "Setup Windows and ConfigMgr" step.  This all smells familiar; like Software Updates during OSD for ConfigMgr 2007!  It is odd how installing "Packages" does not require this, I guess this is just a requirement to satisfy the added complexities of the application install mechanism. 

Thanks for your contributions guys.  If I find out anything else, I'll update this post - but for now, I'll mark this as the answer to my problem and hopefully it will help others.

I have SMSMP=server.domain.com defined in my task sequence "Setup Windows and ConfigMgr" step.

I have SMSMP=server.domain.com defined in my task sequence "Setup Windows and ConfigMgr" step.

But you already mentioned in your very first posting that this parameter was already added 

What are your settings for site and MP/ DP are these in HTTPS mode or HTTP?

They are both set as just HTTP - as my live and lab environments do not have a PKI infrastructure. yet.  The Allow Anonymous acccess checkbox on the DP role did not have any effect on the issue I had, this toggle essentially just changes the IIS DP share to allow anonymous access or to require credentials (like the network access account.)  If I do not allow anonymous access to my DP, my workgroup systems still download applications from the DP using the Network Access account.  I needed the SMSMP=server.domain.com in the Setup Windows and ConfigMgr step and that was all that seems to be missing.

Andy

Dear Andrew,

I have SCCM 2012 R2 and i have create one work group TS with application (adobe reader, Office 2010 ,firefox mozilla etc. ) for windows 7 also i add SMSMP in "setup windows and configmgr" but TS not deployed successful, could you help me.

Regards,

D.Chouhan