Powershell version directive in script?

Question: looking for a way within a Powershell script to direct which Powershell version to use.

Background:

Solarwinds system running on a Windows 2019 server (note this is a test "non-prod" system)
Windows 2019 server comes with Powershell 5.1 by default
I'm testing a Powershell script monitor which uses Invoke-WebRequest
For this purpose I need to use the -SkipCertificateCheck switch of Invoke-WebRequest. Note: this switch became available in Powershell 6.x; -SkipCertificateCheck does not exist in Powershell 5.x
I installed Powershell 7.3 on the server. Note that by default 7.3 will run in tandem with the default 5.1
Executing from a 7.3 shell my script works as expected and returns data
However, when I create a script monitor in Solarwinds script does not return any data (note: I run a lot of script monitors in Solarwinds - I know how to set up the message and statistic constructs to return data).

I am still troubleshooting my script in Solarwinds. However, I suspect that the script invokes Powershell 5.1 which will error out on the -SkipCertificateCheck switch.

Does anyone know of a way to direct a script to execute with Powershell 7.x verses 5.x?

Thanks in advance for any input from the community.

Find more posts tagged with

invoke-webrequest

version

powershell script monitor

Accepted answers

mesverrum

The work around I've used is to create the component as a "Windows Script Monitor" and in the section where it asks you what script engine to use you ca type in pwsh and it will work, assuming pwsh is installed on the polling engine. The big complication there is that those components dont have the option to do remote polling, so its always go to be written from the perspective of the SAM server.

adam.beedell

$results = pwsh testscript_writefile.ps1 -args $args

I think you actually just want to use New-PSSession -ComputerName

soheilamiri

yes, my TEMP.ps1 retune result as shown below

adam.beedell

You misunderstand, I'm referring to specific functions so that it's parsed correctly

Write-output = Bad
Write-host = Good

All comments

planglois

AFAIK, SolarWinds indeed always triggers PoSh 5.x. As a workaround, you can invoke PS7 from a PS5 script. To also help, you can use the #requires statement at the beginning of your script.

https://superuser.com/questions/1555730/how-to-execute-powershell-script-as-powershell-7-from-command-prompt

https://www.reddit.com/r/PowerShell/comments/13ooso1/launch_powershell_7_script_section_from/

adam.beedell

I did this once having failed to find the 64bit toggle, it's not worth it

Use this block instead

if (-not ([System.Management.Automation.PSTypeName]’ServerCertificateValidationCallback’).Type)
{
$certCallback = @"
using System;
using System.Net;
using System.Net.Security;
using System.Security.Cryptography.X509Certificates;
public class ServerCertificateValidationCallback
{
public static void Ignore()
{
if(ServicePointManager.ServerCertificateValidationCallback ==null)
{
ServicePointManager.ServerCertificateValidationCallback +=
delegate
(
Object obj,
X509Certificate certificate,
X509Chain chain,
SslPolicyErrors errors
)
{
return true;
};
}
}
}

Add-Type $certCallback
}
[ServerCertificateValidationCallback]::Ignore()

mesverrum

robert777

Thank you. All responses are very helpful.

As a first step, my endpoint owner and I plan to import the chain of trust from the http endpoint server (openshift/prometheus - thanos endpoint) into our Solarwinds test system. This should enable the Solarwinds http script monitor to accept the CA from the http endpoint as valid.

Hopefully that will work out Ok.

Much appreciate the info about about workarounds to make Solarwinds use Powershell 7.x. Cheers.

soheilamiri

I attempted to write a PowerShell script to monitor my remote Linux machine, but unfortunately, my script using "New-PSSession -Hostname" which does not function with SolarWinds SAM monitoring because it defaults to PowerShell 5.1. I have not found a way to execute my script, and SolarWinds does not provide an option to change the PowerShell version for executing my module.

adam.beedell

You can use PS5.1 to open PS7 if you need to. Most of the functions available in PS7 have equivalents in 5.1 unless you're trying to run on linux or something.