Hello

I have a problem with an ApplicationCatalog site. Applications takes over 1 hour to become available for users. The contents for the application is available on all distribution points. I have checked all the logs and I cannot find any hints to why it is slow. The applications have been created with an automatic script. I have tried setting the deployment time earlier with no luck. Suspecting stuck in the flow somewhere. How can I track what applications become available in ApplicationCatalog?

Any help appreciated 

Regards yvind

• Edited by Øyvind Nernæs Thursday, November 27, 2014 10:36 AM

Hi,

The content of the Application Calatog is enumerated when you log on to the application catalog, are there any collections that need updating in the backend before it is visible?

It sounds like an issue with something else then the catalog itself..

Regards,
Jrgen

It really should be almost instant. Are you using direct memberships in the targeted collection(s)? Are you using AD security groups or users? Are the users refreshing the app catalog, closing it and reopening it, and/or locking the system?

Sorry for a very late reply. Right now testing with a user collection with user objects in it. The first time it happened it took 30-40 minutes before a deployment was available. Now it takes a working day. If deployed to computer objects it works fine.

As Jason asked, are the user objects direct members of the collection(s) or are you using queries? Also, is AD Group Discovery enabled and configured for delta discovery?

Jeff

The collection members are based on a query. Running everyday at nighttime. Not using ad group here so should not be applicable with the AD Group Discovery? Refresh of the appcatalog in any way shape or form does not change anything. Restart,CTRL +F5, Reinstall of the SCCM Client. This is a serverside problem as far as I know.

Can you please post your query?

select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueUserName,SMS_R_USER.WindowsNTDomain from SMS_R_User where SMS_R_User.FullDomainName = "my.domain" order by SMS_R_User.WindowsNTDomain

Try narrowing the scope of your query from your entire domain to a single OU. . .see if that makes a difference.

You can also check the colleval.log to see if there are errors evaluating collection membership.

Jeff

Changing the query didn't make any difference. What seems to have helped is to have the collection update more often. Why I cant explain. The collection have members and the software is published to the collection. A collection update should not be needed unless you have member change?

Very st

The solution is to kick of a collection update after deployment. Not always but sometimes.