Windows Server 2012 – Monitor and maintain servers

Monitor Servers

Server Manager

Server Manager allows you to pull event log data, service status information, management and accessibility information, performance counter data and best practice information from servers on your local LAN, private cloud and public cloud into one management console.

The thumbnails show manageability: i.e is the server online, is it accessible, is it reporting information back to Server Manager etc. NOTE: for Server 2003 Server Manager can only query for online or offline status. Other down-level operating systems such as Server 2008 SP2 / 2008 R2 require the Windows Management Framework 3.0 components and a hotfix for performance data capture.


The data is retained for one day but can configured as you wish.


Filtering information in the dashboard


Configure Data Collector Sets (DCS)

The data collection set configuration is the same as 2008; see here for review.

Configure alerts

Alert configuration is the same as 2008; see here for review. Alerts can be configured within Server Manager too.


Monitor real-time performance

Resource monitor still exists as it did in 2008, task manager has had a overhaul, process tab now displays applications and processes and a number of tabs have links to respective tools which allow you to dig deeper.


Monitor virtual machines (VMs)

Virtual machine monitoring is a feature of failover clustering. The administrator running failover clustering must be an administrator of the guest virtual machine and the guest must have the ‘Virtual Machine Monitoring’ firewall rule enabled. PowerShell: Set-NetFirewallRule -DisplayGroup “Virtual Machine Monitoring” -Enabled True.

Monitoring is configured from within the failover clustering manager and works by monitoring services selected by the administrator. If the service fails then the cluster agent honours the settings defined within the recovery tab of the monitored service. If the service recovery action is ‘Take No Action’ then the cluster agent will raise a Event ID of 1250 from the FailoverClustering source within the system log; this can be picked up by a SCOM monitor which has diagnostic and recovery configurations.

By default Failover Clustering will restart the guest on the same host using a forced but graceful shutdown, if that does not fix the issue then the guest is restarted on another Hyper-V server.

More information here.

Monitor events

Event monitoring is still the same as 2008; see here for review.

Event logs are now integrated into Server Manager and can be aggregated to your workstation for quick analysis and remediation where necessary. The events shown in server manager are context sensitive to the role or selected servers.


Configure event subscriptions

Event subscription configuration is the same as 2008; see here for review.

Configure network monitoring

Network monitoring configuration is the same as 2008; see here for review.

One comment

  1. Pingback: Windows Server 2012 – Configure server for remote management | Notes from stuff I'm working on

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.