Retrieved Properties: User Name is "<none>"

1

(imported topic written by mkearns)

The “User Name” retrieved property is showing as “” for about 1,400 out of 10,000 endpoints. All computers are bound to AD and the computers are used everyday, so there should be a user name. We have several relays and I’m having difficulty finding a common issue. I’ve tried performing a “refresh” from the console but no change.

I’m not sure where to begin to remedy this issue, please share your suggestions.

2

(imported comment written by Tim.Rice)

The User Name indicates who was logged in when the computer last reported.

If there is nobody logged in at the time it will report .

3

(imported comment written by jfschafer)

This looks like something you may want to download. It’s provided on the bigfix.me community website. It tracks information not only on the last logon, but what user logs in the most so that you can pinpoint a machine to it’s most likely user. You will have to create a free account on the site to download but I highly recommend as this site has great Bigfix content.

http://bigfix.me/fixlet/details/2533

Here’s some details on what this custom task does:

The “Primary User” of an endpoint is the user who has logged on most frequently in a given history window (e.g. the past 10 logins).

This task monitors each login and records the most recent logins. This information is stored in the following registry values:

[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\userstats\LoggedIn]

[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\userstats\LastLoggedInUser]

[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\userstats\LastTime]

[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\userstats\LogonHistory]

[HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\EnterpriseClient\userstats\PrimaryUser]

Note:
This task will not run on domain controllers.

Note:

This task will be set as a policy and will run following each logon.

4

(imported comment written by mkearns)

Thank you both! The policy to track a primary user is exactly what I needed.

I’m still using 8.2 and ran into an import error, see below:

"The content is ‘Track_Primary_User_v2.8.bes’ could not be imported.

XML parsing error:

Error parsing "as boolean database.

The element ‘AllowCancel’ with value " failed to parse.

Line 74, Character 40"

5

(imported comment written by mkearns)

We just upgraded to 9.0 (yeah!) However, I’m still unable to import the BES file and I’m getting the same error above. Anyone know how to fix this? If not, is there an alternative? We would really like to start tracking primary user data and have something other than " currently being reported.