Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

ConfigMgr Basics - What are the differences between UDA and TopConsoleUser0 in v_GS_SYSTEM_CONSOLE_USAGE ?

$
0
0

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



Viewing all articles
Browse latest Browse all 4762

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>