How does the demographic information get into Beacon?
Beacon attempts to pull what it can from the Active Directory. There are other options to get that information into Beacon as well. For more information, see this post: Print User Info
Thanks for the information. How does the connection with AD happen?
Hi Andrew, can you help me understand in more detail what information you would like to get about how it works? For example, are you interested from a security standpoint, from an accuracy standpoint or is there a specific problem that you are dealing with?
My question comes from a situation that I am aware of but is not currently a problem. The situation is that not all users sign into their workstation with AD credentials and not all users are joined to the domain. So if the connection from Beacon comes from the login that is used for the workstation then I could experience issues with identify a user to the usage recorded in Beacon.
Thanks, Andrew. The scout will attempt to look up the user in the domain, using the username they used to login. If an entry can't be found there, Beacon will report the job against the username itself. In this case, you would need to use a data import if you want the extra user information.
For your case, it does look like you would need a manual data import if you wish to have information for those not in the AD.
Hope this helps.
Thanks Carrie! Could there be duplicate usernames?
In Beacon, a user is defined as 'domain+username'. So, users with the same logon but in different domains would be considered different. If there is no domain information, then users with the same logon are considered the same. A user without a domain will match a user already in the system with the same name and a domain if that is the only instance of that username in the database.
I am working with the information in the print scout and noticed a user being included multiple times. The user is sviatosia. I have included a screen shot. Do you know what would cause this?
That's odd! Looking into it, will let you know when we figure out why this is happening!
Hi Andrew, did some research on this... turns out this happens when a user running the Mac scout shares a locally-connected printer via Airprint. When others print to the shared device, it gets registered as the user of the Mac, but the domain of the user doing the printing. Each "sviatosia" is actually a separate device printing to the shared Airprint device.
Question for you and the community at large... do you typically find Mac users are sharing locally connected devices via Airprint? Is that a configuration you would want Print Analytics to specifically alert on?
Retrieving data ...