Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.4 Administrator Guide > Troubleshooting SAM > Configure Distributed Component Object Model (DCOM) and User Account Control (UAC) issue in SAM

Configure Distributed Component Object Model (DCOM) and User Account Control (UAC) issue in SAM

Table of contents
No headers

Updated: 3-9-2017

If the target computer is running Windows Vista or Windows Server 2008, you may be required to make settings changes to allow remote WMI requests (https://support.microsoft.com/en-us/help/951016/description-of-user-account-control-and-remote-restrictions-in-windows-vista).

Item Need

DCOM

  • Default and Limits permissions edited to allow the following actions:
  • Local launch (default permission)
  • Remote launch (default permission)
  • Local activation (limits permission)
  • Remote activation (limits permission)

WMI Namespaces

  • Modify the CIMV2 security to enable and remote enable the account used to access the server or workstation through WMI. You must ensure the security change applies to the current namespace and sub-namespaces.

User Account Control

  • Remote UAC access token filtering must be disabled when monitoring within a workgroup environment.
 
Last modified
15:28, 20 Mar 2017

Tags

Classifications

Public