Issues with agent based Client Monitoring
Hi, I've tried implementing agent based Client monitoring to attempt to gather information on Client health of our PC estate - we have a number of 'problem areas' where users have varoius complaints of poor logon performance, application issues etc so I was hoping a combination of aggregate client monitoring and business critical monitoring would give an insight into potential issues which support desk could follow up. I've followed the MP guide but am finding little useful info coming back. My main observation if I'm following the guide correctly, most of the information gathered using aggregate client monitoring is viewed only through the client reports that the MP installs. However when I try and run them, most of them are bombing out with execution failure errors for dataset 'Data_Warehouse_Main', TimeByMachineType etc. I know Data warehouse maine is a dataset reference by many reports so am weary renameing my Mata Warehouse Main if it affects running of other reports which are currently OK. also on aggregate monitoring, does the 'sample PC's' actively gather states from other PCs or does how does it come up with the aggregated data - I cant find this in the documentation. Finally the MP guide also recomments installing the Information Worker MP for greater detail on application level issues in Word,excel Outlook etc. I would be keen to use this but looks like that MP is for office 2007, but we are on Office 2010. Do nt see any updated MP for 2010 - will the 2007 one work for 2010, I'm guessing not as this 2010 was a big change in underlying code... Any help much appreciated...
September 14th, 2012 5:43am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics