Simple powershell script doesnt work

Greetings,

I'm trying to run from the powershell component a simple script (many script from powershell behaving SO WEIRD and even not working due to god knows why)

so I came across a post here which someone offered to check the powershell version running locally and remotely on the target computer, however even this script is running WEIRD!

$version = $psversiontable.PSVersion

$edition = $psversiontable.PSEdition

write-host "Statistic $version"

write-host "Message: $edition"

while running from SW component i get:

Desktop and NaN

when running locally from powershell (which means RDP to the server itself) i get the following:

Desktop & 5.1.17763.1852

why? what seems to be the problem? (there is no typo error in the script, I copied and pasted it on SW itself, maybe there is a typo mistake here on the forum)

Thanks in advance.

Find more posts tagged with

sam

powershell script

PowerShell

Accepted answers

marlief22

Hi, no problem - glad to help!

Unfortunately the version number is actually put through as a string, since it has multiple decimal points in it. If it were, for example, just '5.1' it would likely work perfectly.

You could in that case, depending on the amount of precision required, simply split the version number to only a single decimal point and pull it through as a statistic.

Kind regards,

Marlie Fancourt | SolarWinds Pre-Sales Manager

Prosperon Networks | SolarWinds Partner since 2006

All comments

marlief22

Hello,

Statistic has to be a floating number, rather than a string so it's trying to automatically assign the string to message.

I changed your script to put a dummy statistic for each message:

$version = [string]$psversiontable.PSVersion
$edition = [string]$psversiontable.PSEdition

write-host "Statistic.Version: 1"
write-host "Message.Version: $version"

write-host "Statistic.Edition: 1"
write-host "Message.Edition: $edition"

exit 0

That's working nicely for me, obviously you won't be able to do any sort of threshold based alerting for this though.

Kind regards,

Marlie Fancourt | SolarWinds Pre-Sales Manager

Prosperon Networks | SolarWinds Partner since 2006

TalK

Hello Marlie,

Thank you for taking the time to read and reply to my post.

I've tried to delete the question because i found the solution for that, there are 2 types of "tests" when edit the script and outside, the "edit script test" doesnt work, however outside statistics shows the right number.

also it doesnt make any sense since even on the powershell script example in SW they are showing the following:

Statistics.CPU: 31.08

Message.CPU: svchost.execpu usage

there is no different between CPU number to a version number, they are both holding numbers, to me it seems like a weird bug or fail by design.

Thanks

marlief22

Hi, no problem - glad to help!

Unfortunately the version number is actually put through as a string, since it has multiple decimal points in it. If it were, for example, just '5.1' it would likely work perfectly.

You could in that case, depending on the amount of precision required, simply split the version number to only a single decimal point and pull it through as a statistic.

Kind regards,

Marlie Fancourt | SolarWinds Pre-Sales Manager

Prosperon Networks | SolarWinds Partner since 2006

TalK

On that answer i can agree on because i checked it and i got to the same solution after i did split.

thankss again