Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, June 14, 2016 8:47 PM
Hi Community,
So I've been putting together some reports to map primary users to devices in my organization. In doing so, I've been spending some time with the following view : v_GS_SYSTEM_CONSOLE_USAGE and I noticed that I have duplicate ResourceID records with differing TotalConsoleTime0 values. So, my first question should anyone be able to answer it is :
1) Why would there be duplicate records for a ResourceID with differing TotalConsoleTime0 values? Is it due to profile deletion or re-creation on the actual workstation?
2) As it pertains to UDA I find myself wondering what the actual distinctions are between trying to draft a report based on TopConsoleUser0 values vs. whatever underlying database values UDA leverages?
3) Does UDA leverage the TopConsoleUser0 column in the aforementioned view?
My understanding of UDA is that it is a mechanism developed to focus software deployments to a user's primary device which could be a tablet, mobile phone, or workstation. Thus UDA creates a relationship between a user and a device. In my mind this may not have anything to do with the TopConsoleUser0 column in the aforementioned view, particularly in a scenario where a user manually defines a UDA relationship. But, what about if your Client Agent settings are set to auto populate this data?
4) What does this mean when we are trying to draft reports for a device -> primary user? Is it more accurate to leverage UDA data for such a report (assuming enabling UDA in the client agent settings) produces additional views to aggregate this information from the various tables in the ConfigMgr DB?
As always I appreciate your input and guidance!
Gabe | @ConfigMgrGeek
All replies (5)
Wednesday, June 15, 2016 3:21 PM âś…Answered | 1 vote
Yes there is another SQL view it is called, v_GS_SYSTEM_CONSOLE_USAGE_MAXGROUP. This view will give you the user with the MOST usage. BUT it will also have more NULLs too.
v_GS_SYSTEM_CONSOLE_USAGE gives you all user that have logon to a computer, therefore you should expect to see many computers with two or more users listed.
Use v_GS_SYSTEM_CONSOLE_USAGE_MAXGROUP for the CMDB then I would user last logon user for any NULLs, something like this.
isnull(SCUM.TopConsoleUser0, isnull(RV.User_Domain0 +'\+RV.User_Name0,'n/a')) AS 'UserName',
Garth Jones
Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx
Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased
Wednesday, June 15, 2016 2:34 AM
Dear Sir,
1) It should not be with user profile, but some left over in the WMI class as these information were collected from WMI Classes during hardware inventory.
2) The TopConsoleUser property, which is the user who has been logged in the most on the device. UDA is just a method of associating a user with one or more specified devices. Administrators have to manage the user device affinity so that they know the information is accurate then make use of these information.
3)Correct. Administrators need to decide if the 'Automatically configure user device affinity...' fits the environment that's what I said in 2) that administrators have to manage.
4)It bases on what you need to report.
Related Links:
how to manage user device affinity in Configuration Manager:
https://technet.microsoft.com/en-sg/library/gg699365.aspx
Best regards
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Wednesday, June 15, 2016 9:45 AM | 1 vote
- this view list all that have logon on to the computer is the last 90 days.the is a different view for top console user.
- If you are using the auto-populated UDA when there is no difference. If you have used manual UDA then there is big difference.
- UDA can use top console user. (TPC)
- I personally, don't use UDA in my reports, instead, I use TCU and last logon user, for user details.
Garth Jones
Blog: http://www.enhansoft.com/blog Old Blog: http://smsug.ca/blogs/garth_jones/default.aspx
Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleased
Wednesday, June 15, 2016 1:28 PM
Hi Garth,
I appreciate your response. In your first point, I think you mention there is a separate view for TCU. Is this a different view from v_GS_SYSTEM_CONSOLE_USAGE? If so, what view should I be using to pull TCU data?
Also - Any thoughts on why I'd see duplicate ResourceID and UserName with different values for TopConsoleTime0, GroupID, TimeStamp, SecurityLogStartDate0? An example of what I am referring to is below:
The reason why I am focusing on this is some folks which manage the CMDB at my organization feel this data is inaccurate due to the duplicity seen above. My personal thought is a sub-select query filtering out the value with the lowest TotalConsoleTime0 value will be sufficient to give them a clear picture of the primary user of a given device. But, I thought I'd get your input on it first.
I look forward to your thoughts.
Gabe | @ConfigMgrGeek
Wednesday, June 15, 2016 3:49 PM
Thanks Garth!
Gabe | @ConfigMgrGeek