Upgrading or using a different Powershell version on the SMP Server
Article ID: 249839
Updated On:
Products
Issue/Introduction
The customer asked the following:
We would like to get information on upgrading the backend of the SMP server to support Powershell 7. There are scripts we run via Altiris that cannot call specific commands due to powershell being an old version.
Is it possible to update powershell on the backend meaning on SMP Server?
Also the customer sent more details on it:
We would like to have "powershell core" (Powershell 7) installed so Altiris can call the appropriate version of powershell when running jobs/tasks.
We are currently working on Windows Toast notifications. Toast notifications require powershell 7 to function properly. When running the exact same script locally on an endpoint, it functions properly. When we push the task using Altiris, it errors out as it would with powershell 3 or 5.
Microsoft is moving in the direction where it requires scripts to use the latest versions of powershell. This hampers our ability to run specific scripts that would normally work locally on the machine.
Below is an example of a deferred reboot using toast.
Environment
ITMS 8.6 RU2, RU3
Cause
This is a feature request (the ability to choose a different version of powershell)
Resolution
Powershell can be upgraded on the SMP Server or client machines as needed. As of ITMS 8.6 RU3, we don't provide a way to select a different version of Powershell.
After initial research, we weren't able to force using or switching to PowerShell 7.2.6 Core even if it is set as default program for file extensions like .ps, .ps1, .ps1xml, .psc1
Assume that we always using native Powershell and will not use "pwsh" even if it is the default shell for ps1 files on the Windows client.
There is an enhancement request so we can provide an additional option in the "Run Script" task to allow the customer to choose to use native Windows OS PowerShell or installed PowerShell 7.x (pwsh.exe)
Feedback
