PowerShell 3.0 for Win 7 now available

[karlsnooks]

Download: WMF 3.0 - Microsoft Download Center - Download Details

You will notice in the requirements that Service Pack 1 must be installed.

You will be downloading:
Windows Management Framework 3.0

which includes:
PowerShell 3.0, WMI & WinRM



I suspect that in the future this will be available via the normal Win 7 update.


You will want to download either:

• 64-bit versions: WINDOWS6.1-KB2506143-x64.MSU
• 32-bit versions: WINDOWS6.1-KB2506143-x86.MSU

 

[lehnerus2000]

Thanks karlsnooks

Thanks for the link.

 

[Layback Bear]

Karl have you tried it out yet. If so, what are the changes.

 

[karlsnooks]

Numerous changes.

Google Hey! Scripting Guy.

Here's a link:
Discover Windows PowerShell 3.0 Cmdlets - Hey, Scripting Guy! Blog - Site Home - TechNet Blogs

 

[Layback Bear]

Thanks Karl. That site will take some time to go through but I will.

 

[karlsnooks]

If I find a better write-up than his, I'll let you know.

 

[karlsnooks]

Here is a more complete list of ps 3.0 articles

Not sorted by importance,but rather alphabetically.

PS 3.0


Device Management PowerShell Cmdlets
Discover Windows PowerShell 3
Inside PowerShell 3.0 Parameter Value completion
My Five Favorite PowerShell 3.0 Tips and Tricks
PowerShell 3.0 Overview - Part 1 Krishna Kumar
PowerShell 3.0 Overview - Part 2 Krishna Kumar
Understanding and Using Updatable PowerShell Help
Use PowerShell 3.0 to Rename Network Adapters
What's New In PowerShell v3

 

[karlsnooks]

LaybackBear,

This may be one of the items that you wanted. ( I know that I did).

This shows the new cmdlets. This does not show the improvements, except for indirectly for the Where cmdlet which has been simplified (no more of that $_. notation).

Get-Command -CommandType cmdlet | Foreach-Object { get-help $_ } | select name, description |
where description -match "This cmdlet is introduced in Windows PowerShell 3.0" |
Format-Table -property name -AutoSize –Wrap

Name
----
Add-JobTrigger
Connect-PSSession
ConvertFrom-Json
ConvertTo-Json
Disable-JobTrigger
Disable-ScheduledJob
Disconnect-PSSession
Enable-JobTrigger
Enable-ScheduledJob
Get-JobTrigger
Get-ScheduledJob
Get-ScheduledJobOption
Get-TypeData
Invoke-RestMethod
New-JobTrigger
New-PSSessionConfigurationFile
New-PSTransportOption
New-PSWorkflowExecutionOption
New-ScheduledJobOption
Receive-PSSession
Register-ScheduledJob
Remove-JobTrigger
Remove-TypeData
Rename-Computer
Save-Help
Set-JobTrigger
Set-ScheduledJob
Set-ScheduledJobOption
Show-Command
Suspend-Job
Test-PSSessionConfigurationFile
Unblock-File
Unregister-ScheduledJob
Update-Help

Be sure and run the Update-Help.

That little script is, with only a slight modification present in:
Weekend Scripter: Exploring New and Improved PowerShell 3.0 Cmdlets - Hey, Scripting Guy! Blog - Site Home - TechNet Blogs

 

[karlsnooks]

LaybackBear,
And from that same link:

Here is a list of commands with modifications.

C:\Windows\system32 100% > Get-Command -CommandType cmdlet | Foreach-Object { get-help $_ } |
select name, description |
where description -match "Beginning in Windows PowerShell 3.0" |
format-table -property name -AutoSize –Wrap

Name
----
Add-Member
Add-PSSnapin
Disable-PSSessionConfiguration
Enable-PSRemoting
Enable-PSSessionConfiguration
ForEach-Object
Get-Acl
Get-Command
Get-Content
Get-Credential
Get-Help
Get-History
Get-Job
Get-Module
Get-PSDrive
Get-PSSession
Get-PSSessionConfiguration
Get-PSSnapin
Get-WmiObject
Import-Csv
Import-Module
Import-PSSession
New-PSDrive
Receive-Job
Register-PSSessionConfiguration
Remove-Computer
Remove-Job
Remove-PSDrive
Restart-Computer
Select-Object
Set-PSSessionConfiguration
Start-Job
Stop-Job
Update-TypeData
Wait-Job
Where-Object


For both of these two little scripts, then just delete the "-property name" and you will get both the name and the description.

You will notice that there have been improvements made in some of the very important cmdlets.

I'd start using them in some of my scripts here, but not until PS 3.0 is available thru the normal Win 7 updates.

 

[Layback Bear]

Karl I put you to work. I didn't intend to do that. Thanks. Would it be a good idea for a beginner just to remove 2.0 and start learning again just using 3.0.

 

[karlsnooks]

You won't need to remove PS 2.0. The installer for 3.0 is intelligent. Showed one peculiarity but install ran perfectly.

Probably be easier learning with 3.0.

 

[Layback Bear]

Well I downloaded 64-bit versions: WINDOWS6.1-KB2506143-x64.MSU
It said not allocatable for my system or something like that. I did a search for it and found it. When opened


Is their a script to make sure it is the correct one?

 

[karlsnooks]

did you use the link I provided in post #1?

In any case, if you now have powershell installed, then run powershell and enter:
$host.version

You should see:

Major  Minor  Build  Revision
-----  -----  -----  --------
3       0       -1     -1

 

[Layback Bear]

Yes I did use the site from your post #1.
I get 2-0-1-1
I will remove it and start over.
This is what I used.
Windows6.1-KB2506143-x64.msu 15.8 MB Download

 

[karlsnooks]

All appears correct. I went here:
Download: WMF 3.0 - Microsoft Download Center - Download Details

and clicked on the download button for the x64 6.1 version.

I did not uninstall previous version and 3.0 install correctly detected my profile changes that I had been using.

 

[lkgriffith]

Gee. It looks like it is a return to the dark ages when all we had was a blinking cursor and a command line interface: CPM, MSDOS, DRDOS, UNIX et.al... As far as I am concerned a power shell is the next step after the windows 8 trend. It will be a complete obliteration of a graphical user interface. Might as well have stayed with UNIX and been done with it. None of this easy to use graphical stuff. Only cryptic commands with incomprehensible argument strings. Then for a text editor, we could use vi. Wow!

Hey, I have an idea! Lets really go into prehistory and start using punched cards and punched paper tape. That way no one will have the foggiest idea what we are doing but will still be willing to pay us huge sums for doing it. Which, I strongly suspect is the real reason for the existence of a "power shell".

GACK! Forgive me for thinking that a power shell isn't god's gift to mankind. I stopped using command line systems over 20 years ago and am quite happy to leave them to molder in the dust of ancient history.

 

[Layback Bear]

Tried it again and it say it not for my system. Could it be because I use Home Premium 64 that I can only use the 32 bit Power Shell?
From what I have read I should be able to use the 64. Of course I wrong a lot of times.

 

[karlsnooks]

The 64/32 refers to your operating system as opposed to the computer architecture.

You can see the computer architecture using MSINFO32.exe

You can see the OS System Type by:
WIN + PAUSE keycombo | in the middle, under System, you will see System Type.

Here's a snip of that area on my laptop.

 

[Layback Bear]

 

[karlsnooks]

those look good.

Have you installed all critical, all important, all optional updates (other than Bing Desktop)?