Difference between revisions of "Windows Remote Management (WinRM)"

From Zenoss Wiki
Jump to: navigation, search
(Created outline for article)
Line 3: Line 3:
 
|Author=Hydruid
 
|Author=Hydruid
 
|Abstract=If you've fought and lost the battle with WMI, never fear WinRM is here!
 
|Abstract=If you've fought and lost the battle with WMI, never fear WinRM is here!
|Cover image=Newsletter5-winrm-poewrshell.png
+
|Cover image=Newsletter3-command-data-plugin.jpeg
 
}}
 
}}
 
== Introduction ==
 
== Introduction ==
Line 29: Line 29:
 
echo "EPIC CODE INPUT"
 
echo "EPIC CODE INPUT"
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
 
{{ArticleFooter}}
 
{{ArticleFooter}}

Revision as of 16:14, 6 June 2014

Windows Remote Management (WinRM)

If you've fought and lost the battle with WMI, never fear WinRM is here!
Newsletter3-command-data-plugin.jpeg

Introduction

For years and many Zenoss versions, the default tool for monitoring Windows Servers was with WMI. WMI is awesome but has a tendency to stop working and cause gaps in graphs and monitoring. Luckily Microsoft released a different tool and now Zenoss can fully utilize it for more monitoring flexibility and reliability!

Problem

Unreliable metrics using WMI as the method for monitoring window servers performance counters. WMI seems to die without any reason or warning, but at least it does usually start working again.

Approach

Implement the new 'Microsoft Windows' ZenPack, which uses WinRM, with a simple configuration.

Goal

Reliable metrics using WinRM.

Results

Insert graph pictures

Summary and Future Work

This article covers a very simple configuration of WinRM to get you started. It is highly recommended to convert to using HTTPS so that the data is encrypted and not plain-text!

Acknowledgements

Lets give a big hand to the Zenoss engineers for making this change and making Zenoss a better product on a day to day basis!

echo "EPIC CODE INPUT"