The majority of desktop monitoring I have seen is specific role machines 
running a desktop OS.  Such as embedded/full OS POS machines, ATM, Kiosk, and 
those get monitored just like servers or critical services.

I have also seen a fair amount of desktop monitoring that is done just to be 
proactive... such as VERY lightweight monitoring of event logs for disk 
errors/bad blocks/NTFS issues, lightweight performance reporting, inventory 
correlation.  The agent queues this data and then sends it in to a MS whenever 
the laptop is online.  Our client monitoring MP's are very light, and we don't 
monitor up/down/HB failure by default on client OS.

It works quite well, you just don't treat them like critical 24x7 services.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Thompson, Joseph W (Joe)
Sent: Thursday, August 29, 2013 8:36 AM
To: [email protected]
Subject: RE: [msmom] SCOM to monitor Desktops

We have some field automation desktops that couldn't run a server os, so we use 
client monitoring for those. I couldn't imagine monitoring a standard users 
desktop

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of JRIT
Sent: Thursday, August 29, 2013 8:20 AM
To: [email protected]<mailto:[email protected]>
Subject: [msmom] SCOM to monitor Desktops

Folks,

What is the good, the bad, and the ugly when we think use SCOM to monitor 
Desktops?
Tnx


________________________________
THIS E-MAIL AND ANY MATERIALS TRANSMITTED WITH IT MAY CONTAIN CONFIDENTIAL OR 
PROPRIETARY MATERIAL FOR THE SOLE USE OF THE INTENDED RECIPIENT. ANY REVIEW, 
USE, DISTRIBUTION OR DISCLOSURE BY OTHERS IS STRICTLY PROHIBITED. IF YOU ARE 
NOT THE INTENDED RECIPIENT, OR AUTHORIZED TO RECEIVE THE INFORMATION FROM THE 
RECIPIENT, PLEASE NOTIFY THE SENDER BY REPLY E-MAIL AND DELETE ALL COPIES OF 
THIS MESSAGE.




Reply via email to