Scripting Driver and Powershell Versions

It appears that the latest version of Powershell supported by the Scripting Driver running in Windows is Powershell 4 with IDM 4.7.2, but it is contradictory when looking at it as a whole. The statement is "All PowerShell versions up to 4.0 are supported; the latest version of PowerShell supported by your Windows version is recommended." Windows Server 2016, which is supported has a base level of 5.1.

So, what are other people using for version of Powershell if they are running the powershell service piece?

Thanks
  • On 04/29/2019 08:04 AM, schwoerb wrote:
    >
    > It appears that the latest version of Powershell supported by the
    > Scripting Driver running in Windows is Powershell 4 with IDM 4.7.2, but
    > it is contradictory when looking at it as a whole. The statement is
    > "All PowerShell versions up to 4.0 are supported; the latest version of
    > PowerShell supported by your Windows version is recommended." Windows
    > Server 2016, which is supported has a base level of 5.1.


    I would guess, as usual, that the "latest version" bit is correct, and
    that either the testing is only up through 4.0 (whatever version of
    windows that is on) or, more likely, the documentation is out of sync with
    the code and testing, because documentation often is (somebody needs to
    realize it needs to change, then submit the change, etc.).

    > So, what are other people using for version of Powershell if they are
    > running the powershell service piece?


    I setup an Azure driver earlier this year with a fully patched windows
    2016-something-or-another box, so whatever it had all squeaky new was what
    was working. Unless PowerShell deprecates something, I can't imagine why
    that would matter much.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
  • Aaron is correct--the documentation is simply out-of-date in that section. You should have no trouble on PS 5.1.

    Sam (Scripting Driver Developer)
  • Zygomax;2499044 wrote:
    Aaron is correct--the documentation is simply out-of-date in that section. You should have no trouble on PS 5.1.

    Sam (Scripting Driver Developer)


    You can validate version of your installed PS:

    PS C:\> $PSVersionTable

    Name Value
    ---- -----
    PSVersion 5.1.15063.674
    PSEdition Desktop
    PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
    BuildVersion 10.0.15063.674
    CLRVersion 4.0.30319.42000
    WSManStackVersion 3.0
    PSRemotingProtocolVersion 2.3
    SerializationVersion 1.1.0.1


    PS C:\>


    Windows Server 2016 has "default" PS v5.1, but after "upgrade" you can get PowerShell Core 6.0 or 6.1.
  • Are either of you running Powershell from the script service? If so, please run $PSVersionTable from within their to see if you see the same values. My understanding is that the Script Service runs differently as they are creating a remote session within the service which is dependent on the compiled .Net version.
  • I haven't gotten around to trying out what you suggest. In any case, without the Script Service, the Driver Shim service simply runs PowerShell.exe. The Script Service loads the system's .NET "Automation" object in order to run scripts. I wouldn't call it a remote session. Some customers' implementations may use preloaded modules / commands in scriptservice.conf (see docs) to make a remote connection though.

    Is there an issue you are having that you believe is based on which PS version is in use?

    -- Sam
  • I've now tried out your example. The same PS version (5.1) is reported whether I use powershell.exe or the Script Service. The .NET version is 4.6.

    -- Sam