[Xymon] Windows Client

[Dugan, Darin D [ITSYS]]

FWIW, I've never seen the extreme resource hog behavior some have described with WinPSClient. Now it's entirely possible there were small spikes that I didn't notice, but definitely nothing in the 30+ second range. The systems where I ran this (at a previous job) were mostly Windows Server 2008 R2 and Windows Server 2012 VMs on ESX. Generally speaking the underlying hosts were not overtaxed. For those seeing issues are you running older versions of PowerShell or Windows? Are the machines already operating at a fairly high utilization?

Cheers.

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Scot Kreienkamp
Sent: Monday, July 29, 2013 1:21 PM
To: Henrik Størner; xymon at xymon.com
Subject: Re: [Xymon] Windows Client

Henrik,

I would not advise anyone to go with the PS client especially in a production setting.  I had it deployed on about 20 servers and ended up going back and removing it.  It is VERY much a resource hog when it runs, pegging my servers at 100% processor for 30-60 seconds, and in my plain vanilla environment was unstable to boot.  It was some time ago so the details are a bit fuzzy but it caused some major problems for me.

Sorry for the late response.... been on vacation to San Francisco with the family.

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner
Sent: Tuesday, July 23, 2013 11:53 AM
To: xymon at xymon.com
Subject: Re: [Xymon] Windows Client

On 22-07-2013 15:20, Neil Simmonds wrote:

> it appears that BBWin
> may not be fit for purpose in the near future. I've looked at MrBig 
> and WinPSClient but MrBig seems to have no one maintaining the code 
> and WinPSClient hasn't been changed in 2 ¼ years.
>
> Is anyone aware of any other options or has anyone considered perhaps 
> writing something? I'd look into it myself but I'm not a programmer so 
> although my VBScript and Shell script abilities are reasonable

If you are not too scared to delve into Powershell, then I would really like you to dig into the WinPSClient.

It does work - despite not having been changed for quite some time. The main problem with it appears to be that it is a bit ressource-consuming; Powershell is not the most effective scripting language.

But it is one that is supported on all current versions of Windows ...
and it does provide you with hooks into all of the Microsoft monitoring interfaces. As I understand, getting data with Powershell is just as "easy" as doing it in C#.


Regards,
Henrik

_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon



This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon