5

On a Windows Server 2003 rig (which already has .NET 4 but no 4.5 on it) that is to be expired before the end of the year, I'd like to run a few PowerShell 3 scripts on a scheduled base as the scripts depend on functionality introduced in PowerShell 3.

There are not many useful hits in the search I tried as they give mixed information: Some indicate it is possible but others indicate impossible and it certainly is not in the official downloads.

So:

  1. Are there workarounds to install PowerShell 3 on Windows Server 2003?
  2. If not, where should I look for replacement Cmdlets that are unique to PowerShell 3 like Invoke-RestMethod, ConvertTo-Json, ConvertFrom-Json or Invoke-WebRequest?
Jeroen Wiert Pluimers
  • 2,853
  • 10
  • 41
  • 55

1 Answers1

4
  1. No.
  2. I would use Poshcode/ Jaykul modules:
BartekB
  • 676
  • 4
  • 11
  • Thanks. 1 wasn't what I hoped for, but the Poshcode looks promising (well, the ones not requiring too many assemblies). I might go for the built-in .NET Object though. Need to give this some thinking, as depending on the amount of time, I might migrate the server to a more modern Window as well. – Jeroen Wiert Pluimers Jul 15 '14 at 18:39
  • I've investigating how much work it will be to migrate the machine, as opposed to adapting the scripts with Poshcode/Jaykul modules (of which many have external dependencies that I'd need to check first). It's about the same order of magnitude, so I'll be migrating the machine earlier. In the mean time, a different machine will run the scripts and access the required data over a network share. – Jeroen Wiert Pluimers Jul 21 '14 at 07:00