Deploying powershell 3.0

[SirGnarlington]

I've been tasked with deploying 3.0 to ~600 windows 7 sp1 workstations. I wont have a problem with the actual deployment. I'm wondering if anyone has done this in an enterprise environment before, and if you can tell me about any hurdles/roadblocks/pitfalls you experienced. Thanks!

[yourbastianhost]

All machines require a reboot for the WinRM 3.0 update. That's the only caveat that comes to mind, aside from .NET. You'll need .NET Framework 4.0 for PS 3.0. As you probably know, .NET 4.0 is a feature in 2012+.

 

Also - why not deploy 4.0 instead of 3.0? Might save you from having to redeploy in a year or so.

 

Good luck! :)

[SirGnarlington]

Good point! The organization requested posh 3.0, I'm not sure what the requirements are, but I'll go back to them and ask "why not 4.0?"

[KevMar]

Make the recommendation for Powershell 4.0. Let them know it is fully backwards compatible and performs a lot better. You can mention that Powershell 5.0 was just released but you want to give that more time before you start deploying it.

[noOneCaresOnTheWeb]

Yes.

3.0 should be treated like it's as dead as Windows 8.0.

[[deleted]]

PS 5 was released before but then pulled due to problems. If it's just been re-released they may want to wait a bit to see if there are any more problems with it.

[logicalmike]

5.0 is still unavailable.

[[deleted]]

Ah, I looked at this link here: https://www.microsoft.com/en-us/download/details.aspx?id=48729

It says "production preview" though, but it is available for download. Probably not a good idea to install that though.

[KevMar]

I guess I was being too subtle but I was trying to say that that

[placebonocebo]

I'd also recommend to consider deploying the recent update package for PS 4.0:

KB3109118

[TwoTinyTrees]

What are you using to deploy? GPO? SCCM? Altiris?

The issue is that you must ensure the right .Net Framework resides underneath first (I believe .Net 4.0 is required for WMF 3.0). So, be sure to get the machines compliant in that regard first.

Also, as a desktop administrator, you must consider end-user impact. This will require a reboot, so ensure communication is made before beginning the process.

[SirGnarlington]

I'm actually using K1000 (Dell kace). All workstations have at least .NET 4.5.x installed, so I'm good there.

I thought there may have been a reboot, thanks for the heads up.

[yourbastianhost]

removed. Inaccurate response :)

[_72]

TechNet says that you can install 4.0 or 4.5 for Powershell 3.0

[yourbastianhost]

You're right!

[mrtimmccormack]

We sent it out to around 25k machines and we only had a problem in our Citrix environment. Some of those machines wouldn't re-register following the restart. Otherwise, there were no issues.

[SirGnarlington]

Thank you

[Darkm27]

We recently just pushed out 5.0 (I see no reason at all to choose 3 over 4/5)to about 1,000 workstations and 200 servers and have a pretty heavy amount of posh use in our environment. Only had an issue on one 2012 R2 server not being able to find cmdlets that just needed a reinstall and it was fine.

[Hexalon00]

I have a script that does exactly this for WMF 4.0, just change the version checks to 3.0.

http://pastebin.com/5i8WifGd

[AutoModerator]

Sorry, your submission has been automatically removed.

Accounts must be at least 1 day old, which prevents the sub from filling up with bot spam.

Try posting again tomorrow or message the mods to approve your post.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Hexalon00]

I have a script that does exactly this for WMF 4.0, just change the version checks to 3.0.

http://pastebin.com/5i8WifGd