Hi,
This an host terminal. We're are talking about a medical center in our national healthcare system. So, we've multiple machines in medical rooms that are used by multiple users, not at the same time, but one at a time. The end users, let say multiple doctors, they may or may not end their windows sessions. So, when the next doctor comes up to the end machine, they could have another user account logged in. So, this doctor will use the "Switch User Account" option on Windows to login in his session. From the Administrator point of view, we will have multiple sessions in the state of "Disconnected" and one session as in "Active" state. How will the Identity collector handle this? Will he use only the last logged in user, with the active session? That, at least, is what I expect.
We've excluded all the service accounts from the Identity collectors. Regarding software running with specific user accounts, let's say that a Domain admin goes to one of these machines to install a new software. Instead of disconnect the session on the end user, the domain admin click the right button and uses the "Run as Administrator" feature to install the software. The Identity collector will send te new IP/user mapping to the gateways. The problem is that this is not a real new login event. So, these kind of events should be ignored. If they don't, we will have multiple access roles that are not properly applied. With that, we will have users with permissions to use some Apps or to access to some URLS that they shouldn't.
Regards