Windows Monitoring

Hi,

So I was challenged by my leaders to find a "non-intrusive" monitoring system for a company I am working for. I immediately thought of ZenOSS as I used it in the past (V4.2) and setting up WMI monitoring for Windows Servers was a breeze using the WMI WIndowsMonitor ZenPack. Just imported a list of server and gave a privilege user account and we were good to go.

So Today I installed ZenOSS Core 6.1.0, and to my surprise the simplicity in setting up Windows Monitoring is a bit more involved. If I am correct in digesting the information found in the 45 minute video, I have to touch all the end points, which I would call intrusive.

So to meet the challenge given to me by my boss, I have to ask...

Question: Is it possible to remove the new ZenPack and load the old "ZenPacks.zenoss.WindowsMonitor-1.1.1.egg" file with out any problems?

PS: The new ZenPack will cause the need for multiple change requests as we will be touching all the machines to be monitored with a change to their config. Apposed to simply using a Domain User that always has access to the current WMI data points.

"WindowsAuthSetup2"

YouTube		remove preview
WindowsAuthSetup2 This video walks through setting up WinRM on Windows 2003, 2008 and 2012 to support interaction with the Zenoss Window ZenPack. It will cover setting up authentication from Zenoss for Basic and Kerberos authentication. This video is kind of boring to watch all the way through so I recommend you pick a section that fits your needs. View this on YouTube >