We have 2 versions of an application that need to be deployed. The newer version (6.0) is deployed to a collection that includes All Users, but excludes an exception collection. The users that are in the exception collection do not show in this application collection.
We then deployed the older version (5.0) to the exception collection.
The issue is that the users in the exception collection can install both 5.0 and 6.0 from the Application Catalog. They should be excluded from the 6.0 deployment since they aren't in the collection, but they are still seeing it as available. I thought maybe SCCM would recognize that they are not supposed to get the deployment when the user tried to install, but that wasn't the case...they could still follow through with either install.
We use this same process for machine-based deployments and it works fine. I am wondering if I am missing something, or if user deployments don't work quite the same as machine deployments...in this type of scenario.
Thanks for your help!