Table of Contents
- Introduction
- System Requirements
- Assign Service Logon As Credentials
- Server Configuration
- Agent-Based Monitoring
- Azure Relay Hybrid Connection
- Account Lockout Monitoring and Reporting
- Data Providers
- Directory Services
- Hosts
- Templates
- Template Properties
- Batch Update Templates
- Log Management Templates
- File and Directory Monitor Templates
- Windows Monitor Templates
- Account Lockout Monitor Template
- Logon Monitor Template
- CPU Monitor Template
- Memory Monitor Template
- Disk Space Monitor Template
- SMART Monitor Template
- Process Monitor Template
- Service Monitor Template
- Performance Counter Monitor Template
- Active Directory User Monitor Template
- Active Directory User Integrity Monitor Template
- Clock Synchronization Template
- Defragment NTFS Disks Template
- Network and Application Monitor Templates
- SSL Certificate Monitor Templates
- Email Monitor Templates
- SNMP Monitor Templates
- Monitor Hierarchy
- Reports
- Auto-Configurators
- Options
- Actions
- Filters
- Schedules
- Shared Views
- General Executable Properties
- Assign Actions
- Assign Directories
- Assign Disks
- Assign Shares
- Assign Files
- Assign Consolidated Logs
- Assign Event Logs
- Assign Active Directory Audit Logs
- Target Files and Sub-Directories
- Define Log Entry Columns
- Define CSV and W3C Log Entry Columns
- Active Directory User and Group Filters
- Explicitly Assigned Logs
- Report Columns
- Report Date/Time Ranges
- Report Security Event Log Filters
- SNMP Browser
- SSH Shell
- Exporting and Importing Configuration Objects
- Command Line Interface
- Troubleshooting
- Terminology
The RPC server is unavailable Errors
The RPC server is unavailable error is typically thrown by the local WMI Service when an attempt is made to access WMI functions from a host that is blocking WMI requests or has a firewall between the hosts.
Verify the error:
- Open a command-prompt and type:Wbemtest
- The Wbemtest application opens.
- Once loaded, click
-
From the Namespace text box, type:\\HOSTNAME\root\cimv2Where HOSTNAME is the name of the remote server throwing the error. If either computer resides on a different domain or within a workgroup, specify administrator credentials that reside on the remote computer or domain.
- Click Connect. You should receive the The RPC server is unavailable error.
NetBIOS issues?
Often hardware manufactures ship Windows computers with names pre-configured that do not meet the NetBIOS specification. Specifically, names longer than 15 characters are often pre-configured. Host names that are not addressable by NetBIOS cause many Windows API calls to fail. When you find a host that has a name longer than 15 characters, rename the host to 15 characters or less then reboot the host.