Software Deployment

I'd make a substantial wager that you are coming from a scenario where you used to deploy software via Group Policy, which is typically set up so that when users or machines are removed from an AD group, the software associated with the GPO is uninstalled. Well, forget that in SCCM. That would be too logical!

We do this with some success. We have a group in AD for Acrobat Users. In SCCM I create two user collections. One is Acrobat Users and equals all users from the AD group for Acrobat Users (Membership rule query AD). We have a second user collection in SCCM for Adobe Reader users and we populate this group by including the All Users collection from SCCM and excluding the Acrobat Users collection.

For Acrobat, we deploy an Install to Acrobat Users and and Uninstall to Reader users. Reader is the opposite. This allows us to move a user back and forth and they should ultimately get the proper software based on the group they are in.

You can do something similar by deploying an uninstall to the All Users collection and an install to the group including your specific users for that software.

This is all assuming user accounts and user deployments. If you are deploying based on devices this won't work.

Some of the pains with this are that users roam and it's hard to limit it to one device. I put logic in to specifically only target their primary machine, but our IT staff often trigger as primary users based on the login logic so we get software installed incorrectly. When this happens, the slow cycles of SCCM can cause software to disappear and it may not return automatically for days or even weeks.

So it's not perfect, but it definitely is possible if I'm understanding your scenario.