Automating the world one-liner at a time…
Today, we released Windows PowerShell 2.0 and WinRM 2.0 for pre-Windows 7 operating systems on Windows Update. This non-security, optional update is designed for Windows Server 2008 SP2, Windows Vista SP2, Windows Server 2003 SP2, and Windows XP SP3.
Windows PowerShell 2.0 and WinRM 2.0 are also available as part of the Windows Management Framework (WMF) Core Package on the Microsoft Download Center and Windows Server Update Services (WSUS).
The WMF Core Package available on the Microsoft Download Center and the Windows Update release contain the same binaries of the products, so you can now download them from either source. Because Windows PowerShell 2.0 is in-place upgrade to Windows PowerShell 1.0, we will no longer be offering Windows PowerShell 1.0 on Windows Update.
Windows PowerShell 2.0 appears as an option in a Windows Update scan only if the computer meets the following conditions.
Hemant Mahawar [MSFT]Program Manager
Windows PowerShell 2.0 and WinRM 2.0 were offered in Windows Update on my Windows XP SP3 box, but the installation failed with code 0x8007F0F4. Any suggestions how to fix this please?
Please see the following KB article support.microsoft.com/.../958051
If the KB fails, you may also want to check out this link for more suggestions social.technet.microsoft.com/.../d3597138-d000-43e1-a223-a4556bf2073f
This was a clever move by Microsoft as many folks, such as me, have found PowerShell for the first time just because it showed up as a optional download in Windows Update.
Why, as an ordinary Vista (Win 6.0) and Win7Pro (Win 6.1) user, am I being offered this update every time when I am already totally dissatisfied with the excessive bloat and poor performance of Vista and unsure of Win7 Pro (Win 6.1) compatibility and performance?
Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)
Windows Management Framework makes some updated management functionality in Windows 7 and in Windows Server 2008 R2 available to be installed on Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008. Windows Management Framework contains Windows Remote Management (WinRM) 2.0, Windows PowerShell 2.0, and Background Intelligent Transfer Service (BITS) 4.0.
WinRM is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)–based, firewall-friendly protocol that allows for hardware and operating systems from different vendors to interoperate. The WS-Management Protocol specification provides a common way for systems to access and exchange management information across an IT infrastructure.
Windows PowerShell 2.0
Windows PowerShell is a command-line shell and scripting language that is designed for system administration and Automation. Built on the Microsoft .NET Framework, Windows PowerShell enables IT professionals and developers to control and automate the administration of Windows and applications.
BITS is a service that transfers files between a client and a server. BITS provides a simple way to reliably and politely transfer files over HTTP or HTTPS. File downloads and file uploads are supported. By default, BITS transfers files in the background, unlike other protocols that transfer files in the foreground. Background transfers use only idle network bandwidth in order to preserve the user’s interactive experience with other network applications, such as Internet Explorer. Foreground or typical transfers are also supported.
I'm not sure Windows Update has the ability to automatically detect your total dissatisfaction.
Hope this helps.
P.S. Loving Powershell guys! Keep up the good work.
I am missing some features and would be really grateful if you could think about them.
Apart from the emacs editing environment of bash, another very awesome feature of bash is using previously used commands with super ease. e.g. I can type v and then ctrl-P in succession, and it will show me all the commands I gave, e.g. vim ast/ast.h, or vlock.
Or I do m and then ctrl-P and I get make, make clean, make -C test etc.
Its done using:
Right now, this is the ONLY, I repeat, ONLY reason I’m using linux in my lab. The only thing I use on it is bash in yakuake and vim, as I do C++ development, and because I have to handle a lot of files all the time, I switch between them using command line.
Yakuake is another secondary reason, but its actually bash that I’m stuck with, though I wouldn’t mind if the powershell gui could look better, I mean really, how can you even look at the default fonts. And I hate going through the process of changing them to Lucida console, though finally I did it.
Where is the .net 4.0 support? How on earth can PS not allow me to utilize a current version of the companies flagship runtime?
I'm tring to install Vista Ultimate and get a compatibilty issue with Windows Powershell yet this program is not listed in the list of programs installed.
How do I un-=install this to move forward with intallation?
Does PowerShell 2.0 upgrade require a reboot in Windows Server 2003 SP2?
Windows 7 x64 w/.Net 4... don't get offered powershell in windows update... why?
Why can't I install WinPowerShell in my laptop? I am running Windows Vista Ultimate SP2 x32.
Are there any plans to support remoting on Win XP Home Edition? I have a PC with Win XP Media Center Edition and a XP Home Edition PC. I can enable remoting without any problems on the MC Edition PC but not on Home Edition. I believe the issue is that the commands to enable remoting need to be executed using the administrator account (i.e. using runas, after setting a password for the administrator account) but on XP Home you cannot use this account except in Safe Mode.
I'm interested in learning Powershell, especially remoting but I cannot do so unless I upgrade my X P home machine.
Why was PowerShell pushed out to my machine? It's supposed to be optional and "recommended" but all of a sudden today it appears on my Vista SP2 machine.