Getting PowerShell 5 April Preview (5.0.10105) Running Windows 7 and Server 2008 R2 (some assembly required) |
![]() |
![]() |
PowerShell |
Written by Darwin Sanoy |
Thursday, April 30, 2015 9:48pm |
I am very excited that the PowerShell team has just delivered the April Preview that allows version 5 to run on Windows 7 SP1 and Server 2008 R2 (PowerShell Version 5.0.10105). For this preview version there are a few foibles to getting it running on Windows 7. The PowerShell team hopes to sort these out, but in the mean time I have put together a quick config that steps you though everything with one command line.
Windows 7 and Server 2008 R2 are the worst case scenarios and therefore are the focus of the below, however, all of these steps work for Server 2012, 2012 R2 and Windows 8.1 - they take fewer steps because they have more of the prerequisites. Here are the challenges in getting a Windows 7 or Server 2008 R2 machine to PowerShell 5:
The below quick config uses the Chocolatey package for PowerShell that I have updated for the April preview. If you already know your way around Chocolatey, then you can simple keep re-running that package with -force until PowerShell 5 is on your system. Before you start you will need to have SP1 loaded and use "choco install -y dotnet4.5.1" to get the minimum .NET version installed. Then use "choco install -y powershell -pre -force" at least two times. If you've never heard of Chocolatey, no problem. You can run a PowerShell script from a public github file I have created and it will install chocolatey for you. You can just keep running it repeatedly to get PowerShell 5 on your system and then at the end you can optionally install the latest PowerShell dsc resources from PowerShellGallery.com. This quick config is intended for lab and test machines - it installs the Chocolatey package manager and sets your PowerShell execution policy to RemoteSigned. You can see the complete source of the script before running here: https://raw.githubusercontent.com/CSI-Windowscom/Bootstraps/master/QuickConfigPowerShell5.ps1 Here are the quick config steps:
If you find any problems with the quick config - be sure to send me a note. D. The underlying connection was closed: Could not establish tru st relationship for the SSL/TLS secure channel. |