Sltrace file

The time stamps in an SLTrace are only in the HTML file and not included in Data Collection\Reporting. What are you trying to report on maybe there is another way we can get you the information you are looking for?

It appears DA is only running on some computers. We would like to get a report of all computers and the last time DA was ran. The only way I know is to look at the time stamp of the SLTrace file. Is there a way to gather this information?

you have an interesting dilemma - trying to use Desktop Authority to figure out where Desktop Authority is not working correctly.

your request for all computers and the last time DA was run depends on what you mean by "DA was run" - you can use DA reporting to get a list of all computers in the database and the last time they reported a heartbeat, or the last time they reported a login (and who logged in.) But if the computer has never installed DA or reported in to the database it won't be on the list. In that case you would have to run a discovery in a 3rd party tool to get a list of all devices that are online and compare that list to the desktop authority report. You could also write a script that goes out to each computer in an OU and pulls the file-creation date from all the SLTRACE files in the user folders but that would be a bit of work ;-)

But lets step back and look at this from a bit higher up. Are these computers in Active Directory? Do you have a GPO that pushes the DA agent to all of them? Pick a computer that you know is not working correctly on and do a policy modeling on it. Or open a admin window and type: gpresult /scope:computer /r
and verify it says the GPO is supposed to be installing the agent.

When you say it is only "running on some computers" does that mean it fails to install properly when a person logs in or its installed and when they log in it is not running. Many times when people report DA not running its because they failed to put in SLTRACE into the logon script field of the user.

I hope that helps more than it befuddles. Post some more details and hopefully someone will be able to help!

butlerm is correct. You could use Reporting to get a list of machines that have ran Desktop Authority in the last 72 hours. Which will not tell you why DA didn’t report back on some machines but it would at least be a good place to start. With the list you can visit any machine missing from the report and investigate further.

The report that will show machines that have ran DA in the last 72 hours is Pre-Defined Reports | Licensing | Licensing – Managed Seats Inventory

 

Don't forget that the DA reporting requires a unique GUID on each machine. If you are using a standard file to image your computers which has the GUID embedded in it you may not be accurate in the inventory.

We have a job that we run once a year (set for run-once) to delete all GUID's and let them rebuild just in case we have mistakenly left the GUID on one of our images. You have to be careful with reporting as everything will double-report for a little while (old GUID and new GUID)