I want to be able to deploy an Application to a user account as optional, and that same Application to a computer account as mandatory. So I created a single Active Directory group that contains both users and computers. Then I created two collections, one for computers (populated by that AD group), and one for users (populated by the same AD group). I made a mandatory deployment to the computer collection, and an optional deployment to the user collection.
It works fine, in most cases. The problem is... the users I deploy it to I trust to be aware of what program they are installing, and to be sure not to have that program open and running the moment they click the Install button (which would break the install). These are typically IT staff. But the computers I deploy it to, I do not. These are usually end users who are too distracted to pay attention. So to avoid problems with the mandatory deployment, I like to deploy itOnly when no user is logged on.
So there's the problem. I can't have one application deployed to two different collections when one deployment is designed to be run manually by a user (obviously while they are logged on) when the deployment type is defined to runonly when no user is logged on. Is there a way I can configure my application to allow for both scenarios? Maybe create two different deployment types, one designed to be run manually, and one designed to be pushed out as mandatory?