Well, I am still learning patience, so I went ahead and copied my application. Then I deployed that new (really the same) app as available to the same collection. The copied app now shows up in the app catalog. . . . I have no idea why that worked. . .any ideas on what logs or where I can look to see what went wrong with the original app/deployment? Thanks, Jeff From: [email protected] Date: Thu, 20 Nov 2014 14:04:30 -0600 Subject: Re: [mssms] Application Not in App Catalog To: [email protected]
I have seen that before, assuming you've validated that your account is actually in the collection it is deployed to. :) I've waited for hours for one to show up only to finally give up and go home and then it was there in the morning. Sometimes it seems like you just have to go out an recreate the application. You can try running 'exec usp_BuildCatalogPropertyTable' from SQL If there is an DB issue rebuildling the catalog that will let you see it. But I think under heavy load it can just take a while.----- Dwayne Allen [email protected] (479) 310-0027 On Thu, Nov 20, 2014 at 1:14 PM, Jeff Poling <[email protected]> wrote: Feeling a little dumb here. . .I have an application in ConfigMgr 2012 R2. Single deployment type, user experience is set to install for system whether or not a user is logged in. I deployed it to a user collection. The application is not showing in the application catalog after at least an hour. I can't find any reference to the application in the app*.log files. . . Has anyone seen this before? What am I missing? Thanks, Jeff
