It could be, the defining factor is if the user account is actually listed in the collection. If it is, its just user policy not updating on the machine. If its not in the collection, it could be when the user was added to the group, AD user discovery interval, or the collection update interval. All of this comes into play.
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Dwayne Sent: Tuesday, February 04, 2014 10:01 AM To: [email protected] Cc: Lala, Jeremy; [email protected] Subject: RE: [mssms] Some Application Content not showing up in Software Center After OSD WIN 7 Upgrade Rollout Daniel, Thanks for the reply, I wasn't involved with setting up the Collections, but I'm looking at one now, It appears to be a Query Based from a User Group, example: SMS_R_User.UserGroupName=" OURAPPLICATIONCONSOLEUSERS" Could this be the bottle neck as it were? Dwayne Hebert [MCTS(rgb)_1424] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, February 04, 2014 8:51 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Some Application Content not showing up in Software Center After OSD WIN 7 Upgrade Rollout How are the collections populated for the software that's not showing in software center? Are you querying off software inventory or hardware inventory? There were some changes in 2012 where SINV is now a low priority process and all inventory actions run consecutive not parallel. In our environment SINV can take up to 4 days to finish, so hardware inventory populated shortly after. This causes any collections that are based off these inventories to not populate until the client reports back its full inventory. Daniel Ratliff ________________________________ [http://static.avast.com/emails/avast-mail-stamp.png]<http://www.avast.com/> This email is free from viruses and malware because avast! Antivirus<http://www.avast.com/> protection is active. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
<<inline: image001.gif>>
