I know this has probably come up before but does anyone know if there is an alternative Windows client to BBWin that actually works. I've got problems with both 0.12 and 0.13 versions of the client.
0.12 doesn't seem to work on Windows Server 2008 and 0.13 has a memory leak. This issue has been recently raised on the BBWin sourceforge big list and the reply was, 0.13 is mostly just a port from VS 2008 to VS2010. I don't have the time to spend on improving it and to be honest it's probably not worth spending the time. We really need a client developed on C# so that it can take advantage of .NET's capabilities of hooking into the OS much more cleanly.
I appreciate that this is open source software and as such I don't expect people to jump on it and fix it, however 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 I wouldn't really be comfortable attempting something like this even though I have started to look at learning C#.
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the
Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any
information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the
information for any purpose other than that indicated and upon request will destroy the information and remove it from their records.
Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not
the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing,
or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this
e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor
all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT
helpdesk on +44(0) 1254 303030
I agree, BBWin is not ideal, but it is surprisingly resilient considering it is alpha code and with all the changes in Windows...
One way would be to put up some funding - maybe someone is willing to put in the work. I'd be happy to contribute (monetarily that is - I, too, am no programmer). We have a big 'investment' in xymon and it would be great if the windows side was strengthened.
BTW, I have been using BBWin 0.13 on both 2008R2 and 2012, a dozen systems so far, for a month or two in production. I think there was a problem once (on a system with *huge* logging) where we have to restart BBWin but otherwise it has been stable. It just takes (at times considerable) patience to work out the foibles.
From: Xymon on behalf of Neil Simmonds Sent: Monday, 22 July 2013 10:50 PM To: Phil Crooker; xymon at xymon.com Subject: [Xymon] Windows Client
I know this has probably come up before but does anyone know if there is an alternative Windows client to BBWin that actually works. I've got problems with both 0.12 and 0.13 versions of the client.
0.12 doesn't seem to work on Windows Server 2008 and 0.13 has a memory leak. This issue has been recently raised on the BBWin sourceforge big list and the reply was, 0.13 is mostly just a port from VS 2008 to VS2010. I don't have the time to spend on improving it and to be honest it's probably not worth spending the time. We really need a client developed on C# so that it can take advantage of .NET's capabilities of hooking into the OS much more cleanly.
I appreciate that this is open source software and as such I don't expect people to jump on it and fix it, however 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 (1/4) 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 I wouldn't really be comfortable attempting something like this even though I have started to look at learning C#.
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Conduct Authority
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the information for any purpose other than that indicated and upon request will destroy the information and remove it from their records. Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT helpdesk on +44(0) 1254 303030
Please consider the environment before printing this e-mail
This message from ORIX Australia may contain confidential and/or privileged information. If you are not the intended recipient, any use, disclosure or copying of this message (or of any attachments to it) is not authorised. If you have received this message in error, please notify the sender immediately and delete the message and any attachments from your system. Please inform the sender if you do not wish to receive further communications by email. ORIX handles personal information according to a Privacy Policy that is consistent with the National Privacy Principles. Please let us know if you would like a copy.
It is also available at www.orix.com.au<http://www.orix.com.au>
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
I'm a fan of WinPSClient and would like to see that become more widely utilized. The chief drawback I have is no great way to run external scripts.
Been working a lot with PowerShell lately so I might dive in one of these days....
Cheers. Darin
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner Sent: Tuesday, July 23, 2013 10: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
Unfortunately we use quite a lot of External scripts and we also can't use Powershell. We have scripting disabled on all servers and while we might be able to get signed scripting allowed, we would require to run the client as a service which would have to run under the Local System account. Experience has shown us that this causes significant problems when trying to run signed scripts.
The last time we had a requirement to run a Powershell script as an external on BBWin, I ended up having to rewrite it in VBScript as we couldn't get the PS script to work as a signed script under the Local System account.
Unfortunately I don't make the rules under which I have to work, I just have to make the best of them and work within those rules for monitoring.
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Dugan, Darin D [ITSYS] Sent: 23 July 2013 17:06 To: xymon at xymon.com Subject: Re: [Xymon] Windows Client
I'm a fan of WinPSClient and would like to see that become more widely utilized. The chief drawback I have is no great way to run external scripts.
Been working a lot with PowerShell lately so I might dive in one of these days....
Cheers. Darin
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner Sent: Tuesday, July 23, 2013 10: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
Name & Registered Office: EXPRESS GIFTS LIMITED, 2 GREGORY ST, HYDE, CHESHIRE, ENGLAND, SK14 4TH, Company No. 00718151. Express Gifts Limited is authorised and regulated by the Financial Services Authority
NOTE: This email and any information contained within or attached in a separate file is confidential and intended solely for the
Individual to whom it is addressed. The information or data included is solely for the purpose indicated or previously agreed. Any
information or data included with this e-mail remains the property of Findel PLC and the recipient will refrain from utilising the
information for any purpose other than that indicated and upon request will destroy the information and remove it from their records.
Any views or opinions presented are solely those of the author and do not necessarily represent those of Findel PLC. If you are not
the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing,
or copying of this email is strictly prohibited. No warranties or assurances are made in relation to the safety and content of this
e-mail and any attachments. No liability is accepted for any consequences arising from it. Findel Plc reserves the right to monitor
all e-mail communications through its internal and external networks. If you have received this email in error please notify our IT
helpdesk on +44(0) 1254 303030
Apologies for not responding on this one earlier.
My thoughts on WinPSClient (which I built up from the first cut Henrik wrote, and was a great way of learning powershell):
- it needs a bit of work still
- it does have some functions not in the BBWin client
- it can be a resource hog - some apparently builtin powershell cmdlets end up calling some dodgy underlying mechanisms, and it's not obvious what without a bit of work. Most are OK however, and the most recent versions are pretty aggressive about garbage collection. I'm not sure how many persistent processes are written in powershell - memory leaks aren't much of an issue for a short run process.
- it doesn't run external scripts - I started looking at Start-Job and the .Net process management classes but there are so many corner cases to handle on process termination, overlapping runs, etc.
- the service runner is very crude - start process and ignore it until sent a stop service signal at which point go looking for it to kill. Service restart options are irrelevant. Not sure if anything has changed around running powershell as a service directly.
- because the service runner used is 32-bit, it uses the 32-bit version of Powershell. There may be a workaround for this, but I couldn't find one.
- it may be better to update BBWin to C#, 64-bit, etc and include the option of calling Powershell scripts as part of the core client and as external scripts. I gather this isn't too hard to do from .Net, but not sure if there are any limitations on requiring code signing of scripts to do that, or whether system execution policy can be overridden (which would be a bad thing in some respects).
David.
I'm a fan of WinPSClient and would like to see that become more widely utilized. The chief drawback I have is no great way to run external scripts.
Been working a lot with PowerShell lately so I might dive in one of these days....
Cheers. Darin
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner Sent: Tuesday, July 23, 2013 10: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
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
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.
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
Couldn't tell you what version of PS I was running, but it was the current one of the time. I never saw anything but a small spike reported back to Xymon, so if you're looking there you won't see them. I only saw them when I was watching the task manager on the server itself. The servers were sitting between 10-15% usage generally, and would only spike when the WinPSClient ran. This was on 2008R2 VM's on ESX4 at the time.
Scot
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Dugan, Darin D [ITSYS] Sent: Tuesday, July 30, 2013 9:16 AM To: xymon at xymon.com Subject: Re: [Xymon] Windows Client
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
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.
On 30-07-2013 16:32, Scot Kreienkamp wrote:
Couldn't tell you what version of PS I was running, but it was the current one of the time. I never saw anything but a small spike reported back to Xymon, so if you're looking there you won't see them. I only saw them when I was watching the task manager on the server itself. The servers were sitting between 10-15% usage generally, and would only spike when the WinPSClient ran. This was on 2008R2 VM's on ESX4 at the time.
My "gut feeling" is that it is the eventlog-scanning that causes many of these spikes - it certainly was/is with the old BBWin client, and I would suspect that WinPSClient has the same problem.
Could be wrong - it's been quite some time since I delved into it.
Regards, Henrik
Might be with polling the services and processes as well. Just remembered that was part of the instability I saw. Sometimes the services or the processes lists would be incomplete or missing altogether.
Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Incorporated 1284 N. Telegraph Rd. | Monroe, MI 48162 | scot.kreienkamp at la-z-boy.com | www.la-z-boy.com
-----Original Message----- From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner Sent: Tuesday, July 30, 2013 11:17 AM To: xymon at xymon.com Subject: Re: [Xymon] Windows Client
On 30-07-2013 16:32, Scot Kreienkamp wrote:
Couldn't tell you what version of PS I was running, but it was the current one of the time. I never saw anything but a small spike reported back to Xymon, so if you're looking there you won't see them. I only saw them when I was watching the task manager on the server itself. The servers were sitting between 10-15% usage generally, and would only spike when the WinPSClient ran. This was on 2008R2 VM's on ESX4 at the time.
My "gut feeling" is that it is the eventlog-scanning that causes many of these spikes - it certainly was/is with the old BBWin client, and I would suspect that WinPSClient has the same problem.
Could be wrong - it's been quite some time since I delved into it.
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.
On 31/07/13 1:17 AM, Henrik Størner wrote:
On 30-07-2013 16:32, Scot Kreienkamp wrote:
Couldn't tell you what version of PS I was running, but it was the current one of the time. I never saw anything but a small spike reported back to Xymon, so if you're looking there you won't see them. I only saw them when I was watching the task manager on the server itself. The servers were sitting between 10-15% usage generally, and would only spike when the WinPSClient ran. This was on 2008R2 VM's on ESX4 at the time.
My "gut feeling" is that it is the eventlog-scanning that causes many of these spikes - it certainly was/is with the old BBWin client, and I would suspect that WinPSClient has the same problem.
Could be wrong - it's been quite some time since I delved into it.
The eventlog scanning was unfinished business. The Get-EventLog cmdlet is very basic - from memory, despite it having options like -After it would in fact scan the entire event log every time. Get-WinEvent is the updated version - not sure if that was available on 2003. I'd started looking at the .Net eventlog stuff as a workaround and that was more promising, but since I log ship everything to a central server with syslog and process it there, eventlog stuff was not a high priority with me.
David.
-- David Baldwin - Senior Systems Administrator (Datacentres + Networks) Information and Communication Technology Services Australian Sports Commission http://ausport.gov.au Tel 02 62147830 Fax 02 62141830 PO Box 176 Belconnen ACT 2616 david.baldwin at ausport.gov.au Leverrier Street Bruce ACT 2617
Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au
This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.
participants (6)
-
david.baldwin＠ausport.gov.au
-
dddugan＠iastate.edu
-
henrik＠hswn.dk
-
Neil.Simmonds＠express-gifts.co.uk
-
Phil.Crooker＠orix.com.au
-
SKreien＠la-z-boy.com