User Device Affinity: Temporary Assignments
We manage our systems using only usage based UDA. User defined and admin defined were not being updated regularly enough and our data got stale quickly.
We have since change to usage only UDA. Our challenge here is new devices or loaner devices do not have the applications available to the users until they meet the usage threshold.
A work-around that we have done is create a PS script to force a usage based UDA releationship between the user and the device. We assigned it to only our support staff, so users can't go installing apps on neighboring devices. This will only work until the client is restarted such as in a reboot.
I am suggesting a UDA type that can be assigned for x number of days and then go away.
After the temporary UDA falls away, the usage based UDA rule will have taken over if the user still has that device, or fall away if they no longer have the loaner.
As my experience, configmngr client is not aware of administrative UDA assignments,it is only aware, and creates a UDA entry in CCM_useraffinity based on the automatic UDA assignment based on usage in client settings.
As a consequence the requirement in DT for Primary DEvice/User only will be true based on usage. I will be nice to create new entries at the client based on administrative assignment at the server, I think the best method should be a machine/user policy update where those policy include a check and create/remove Instances with updated info