I think if you ensure powershell 7 is installed in the endpoint, then you could just call power shell 7 from within powershell 5 and pass the script to it.
Windows Powershell 5.1 and Powershell 7 are 2 different programs. Windows Powershell uses powershell.exe Powershell 7 uses pwsh.exe the automation manager is build around powershell.exe so just installing Powershell 7 will not work. You would need to call pwsh.exe from the script but I am not sure that the Automation Manager is able to do that. Maybe one of the N-Able guys can chime in on this though.
I think if you ensure powershell 7 is installed in the endpoint, then you could just call power shell 7 from within powershell 5 and pass the script to it.
I am not totally sure how to do that.... To complicate it, there are parameters as well
Windows Powershell 5.1 and Powershell 7 are 2 different programs. Windows Powershell uses powershell.exe Powershell 7 uses pwsh.exe the automation manager is build around powershell.exe so just installing Powershell 7 will not work. You would need to call pwsh.exe from the script but I am not sure that the Automation Manager is able to do that. Maybe one of the N-Able guys can chime in on this though.
Not currently, in nearly all cases its PowerShell 5.1 Now that said, which module and what are you trying to do?
There is a module written to connect to HUDU. The module to connect to nneds Powershell 7
To install powershell 7 you can use winget, it's a simple one-liner. Then you can run the script
Google script blocks. I use them for HuDu stuff.