I have seen this a few times but seems to be intermittent. I created a query based user collection. My test user account was part of that collection. I deployed an app to the collection. The user was able to see it in the app catalog
and install it successfully. The user then uninstalled the app successfully. The app stills shows in Software Center as available (which appears to be normal although I wish the behavior would be that it would disappear). But that's not the
issue. So I no longer wanted the user to be able to deploy this application that they previously installed and uninstalled. Since it is a query based collection which the user should be in, I added an exclude collection that just had the user account
in it which seemed to work fine. The exclusion collection caused my test user account to drop out of the collection. After a few minutes, the app dropped out of the app catalog which is good and what I expected. The problem here is
that the app still remains in Software Center and shows as available and the user can still continue to install and uninstall this app. I have forced user policy several times with no change and let it sit for a few hours with still no change. As
a test I then removed all membership from the collection so that it was completely empty. Still no change. I then deleted the collection and the deployment and still no change. I have also forced machine policy and application deployment
evaluation cycles and still no change. I have ensured that there are no other deployments of this app, it is not a dependent app of any other app either. So I am left with an app that I can still install/uninstall from software center with no existing
deployments of that app. Other times I have done similar and the app does disappear from Software Center after updating user policy. But definitely once or twice in the past I have seen this behavior as well. In the past I believe I removed
and re-installed the configmgr client to get rid of the orphaned apps. I have not done that yet this time in the hopes of troubleshooting further. Has anyone ran into anything like this?
↧