Hi,

We are using SCCM 2012 for publishing applications on VDI.

There are some users not able to view the applications in Software Center. The applications published are In User collection context. However, the application published to per-machine in Device collection context are visible to them.

What could be the issue?

I believe SCCM Client is working fine on that system, because Device collection published applications are working fine.

-Regards

Sumit Soni

• Edited by theone.sumit Tuesday, June 30, 2015 6:44 PM

It`s because they are seeing the computer deployment and not the users one. probably those 2 users are connected to a computer who as the deployment. Can you log on with 1 of those user on a computer where the other user see the deployment?

Here you will see a rundown for application:

Object type	Collection resources	Deployment	Application Catalog	Software Center
Application	Users or groups	Available deployment,  does not require approval	Yes	After installation is initiated successfully from the Application Catalog
	Users or groups	Available deployment,  requires approval	Yes	After the application is approved
	Users or groups	Required deployment	No	Yes
	Computers	Available or required deployment	No	Yes

Taken from:http://blogs.technet.com/b/configmgrteam/archive/2012/03/31/introducing-the-application-catalog-and-software-center-in-system-center-2012-configuration-manager.aspx

Hope this help

• Edited by Frederick Dicaire Tuesday, June 30, 2015 2:33 PM

No it is not i checked. I published an application on my account to check. It was visible in Software Center and got installed properly. This is because we are publishing it with Required option not available.

• Edited by theone.sumit Tuesday, June 30, 2015 2:46 PM

I checked multiple logs. Out of those i found below useful information:

CCM Eval.log:

Failed to get SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Real-Time Protection\DisableIntrusionPreventionSystem

ClientIDManagerSetup.log:

Unable to find PKI Certificate matching SCCM certificate selection criteria. 0x87d00280

StatusAgent.log:

Successfully sent location services on HTTP failure switching to success message for MP 'KBJER8002.ci.kbroot.net'.

Those lines are taken out of context and are useless then. You can also download ConfigMgr (R2) toolkit and use Deployment Monitoring Tool to check what's going on on the client. 

Under monitoring , Content Status is showing success for both users. However, the users are still unknown in deployment status tab.

Hi Torsten,

I found the below information in ccmmessaging.log

Request to <Server name> failed with 400

Successfully sent location services HTTP failure message.

Post using <UserName> security context failed due to Integrated Windows Authentication failure

Post to <Server name> failed with 0x80070005.

OutgoingMessage(Queue='mp_[http]mp_policymanager', ID={B067792A-D927-4ECE-AF71-BA7F4C2042B9}): Will be discarded (0x80070005).

Is this related to user authentication or certificates ?

• Edited by theone.sumit 20 hours 40 minutes ago

That snippet only shows http (not https) so I assume that no certs are involved. 

I checked multiple logs. Out of those i found below useful information:

CCM Eval.log:

Failed to get SOFTWARE\Policies\Microsoft\Microsoft Antimalware\Real-Time Protection\DisableIntrusionPreventionSystem

ClientIDManagerSetup.log:

Unable to find PKI Certificate matching SCCM certificate selection criteria. 0x87d00280

StatusAgent.log:

Successfully sent location services on HTTP failure switching to success message for MP '<ServerNAME>'.

• Edited by theone.sumit Friday, July 03, 2015 9:56 AM

Hi Torsten,

I found the below information in ccmmessaging.log

Request to <Server name> failed with 400

Successfully sent location services HTTP failure message.

Post using <UserName> security context failed due to Integrated Windows Authentication failure

Post to <Server name> failed with 0x80070005.

OutgoingMessage(Queue='mp_[http]mp_policymanager', ID={B067792A-D927-4ECE-AF71-BA7F4C2042B9}): Will be discarded (0x80070005).

Is this related to user authentication or certificates ?

• Edited by theone.sumit Wednesday, July 01, 2015 11:06 AM

I resolved it myself. It was token bloating issue. the token size was too big so that it was creating barrier in communication.

this was happening because user was associated with multiple AD groups.

thanks all for your time and suggestions.

• Marked as answer by theone.sumit 45 minutes ago

I resolved it myself. It was token bloating issue. the token size was too big so that it was creating barrier in communication.

this was happening because user was associated with multiple AD groups.

thanks all for your time and suggestions.

• Marked as answer by theone.sumit Monday, July 06, 2015 7:01 AM