Tim, does starting powershell.exe with the command line parameter of "-Version 2.0" help at all?
-----Original Message-----
Date: Thu, 18 Oct 2018 12:24:10 -0400
From: Timothy Williams <user-1a5482fb085e@xymon.invalid>
To: user-aada0fa38bf8@xymon.invalid
Cc: xymon at xymon.com
Subject: Re: [Xymon] [External] PS client enhancement of ServiceCheck
Message-ID:
<user-18f326ac85ba@xymon.invalid>
Content-Type: text/plain; charset="utf-8"
Zak, all
I pushed my revised script out to a few servers. Most all have upgraded powershell, but a few 2008 & 2008R2 still have PS v2. Script will not start, but no clear error about why. It runs fine on the '08 servers with PS v3, v4, or v5. The ones with v2 seem to be running the script in a v1 instance. Error: Program C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe for service XymonPSClient exited with return code 4294770688. Any way to force it to run in v2? Or do you see anything in the new function that would choke v1?
On Tue, Oct 9, 2018 at 9:28 AM Timothy Williams <user-1a5482fb085e@xymon.invalid> wrote:
Sounds good to me. I've only been powershell coding a year, so I'm
sure there are more elegant and efficient ways than what I've devised.
Tim
CONFIDENTIALITY NOTICE: This email and any attachments are for the
exclusive and confidential use of the intended recipient. If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.