User-Device Affinity and application deployment

Question

Am trying to use UDA as a requirement within application DeploymentType, but it does not seem to work. Here's my scenario:

1. Set a device as my primary device manually
2. Set the User Primary Device as a requirement for an application
3. Deployed the above application to my user name via user collection (my user name is added as direct membership and not via an user AD group)
4. Application is deployed as Available and not Required deployment

Now, my expectation was that i should be able to see the application under SC of the primary device only mapped against my username.. but i can see the app under SC (Software Center) of other devices also that i logon to.

Am I missing anthing here? Kindly advice.

Thanks!

Answer 1

That's backwards from a use case perspective. You use UDA on app deployments targeted to devices so that only the primary user of a device sees the deployment.

What you have above will probably work to prevent the app from installing, however, requirements for user targeted available apps are not evaluated until the user chooses to install them from software center. Thus, they will still show in software center regardless of the requirement but will fail installation with a requirements not met error.

Answer 2

Ok, so it turns out during my test:

Required Deployment + User Collection + Primary Device Requirement = App respects the requirement and only installs on Primary device. Does not install on any other device

Available Deployment + User Collection + Primary Device Requirement = App follows user on Software center on every device, but installs only on Primary device. If user tries installing it on non-primary device from Software Center, it does not proceed to install with message 'requirement not meant'