1) How secured is installing SCOM agent on any server
You may use local system account to run agent service and then use action account to gather information about, and run responses on, the managed computer (a managed computer being either a management server or a computer with an agent installed). The MonitoringHost.exe
processes run under the action account or a specific Run As account. There might be more than one MonitoringHost.exe process running on the agent at any given time.
Some of the actions that MonitoringHost.exe performs include:
Monitoring and collecting Windows event log data.
Monitoring and collecting Windows performance counter data.
Monitoring and collecting Windows Management Instrumentation (WMI) data.
Running actions such as scripts or batches.
The separation of the Health Service process from the single and multiple uses of the MonitoringHost process means that if a script running on the managed computer stalls or fails, the functionality of the Operations Manager service or other responses on the
managed computer will not be affected.
2)other monitoring tools provides agentless monitoring. Is agentless monitoring solution is more secured than Agent monitoring.
No i does think so.
3) Impact on servers when SCOM agent runs workflows (CPU/Memory utilization).
4)When heart beat fails, management server tries to ping the target server. What if ping is disabled on target server. Do we get false alarm
yes.
5)When Agents sends data to management servers, will it compress the data (and also will it encrypt the data)
SCOM agents will encrypt data send to management server. If agent and Management server on the same domain, it will use kerberos to encrypt data otherwise certificate should be deploy to both management server and agent.
Roger