Both problem and resolution contained within. I'll blog about this later, but figured I'd throw it out there for you all now... Problem: After migrating from SCCM 2007 to SCCM 2012, only a few applications are appearing in the Application Catalog. Expect to see 100+. All are user-based deployments, and everything as far as the package and program and deployment look fine. User collections contain a single AD group which contains the users of that are allowed to receive the application. Environment: CAS and three primaries. AD Forest Discovery is enabled on the CAS, and and all other AD discoveries (other than Forest Discovery) is enabled on one of the primaries. Troubleshooting: After looking high and low for days, the only thing that stood out was that for those applications that appeared in the Application Catalog, the properties of the User in the form of DomainName\AD_Application_Group contained the following:Agent Name: "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT"Agent Site: "PR1"Those applications that were not appearing in the Application Catalog had either the User properties above and the User properties shown below, or just the one below:Agent Name: "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT", "SMS_MIGRATION_MANAGER"Agent Site: "PR1", "CAS" Resolution:Remove all Users in the form of DomainName\AD_Application_Group for which the Agent Site had both the primary and the CAS site codes listed. Then run a full Active Directory Group Discovery. Once that is complete, update collection membership on all affected User collections. All the removed Users are rediscovered and no longer contain SMS_MIGRATION_MANAGER in the Agent Name, nor CAS in the Agent Site. Review the Application Catalog and notice all of the expected application now appear available. Root Cause: ??? - I suspect it's because one of the collection migrations was ran on the CAS as opposed to the Primary? Anyone know for sure? Cheers!
