Windows Management Framework is here!

Windows Management Framework, which includes Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0, was officially released to the world this morning.  By providing a consistent management interface across the various flavors of Windows, we are making our platform that much more attractive to deploy.  IT Professionals can now easily manage their Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 machines through PowerShell remoting – that’s a huge win!

You can download the packages here:

A big, hearty thanks to everyone who made this release possible.

Tell your friends!


Nathan Burkhart

Program Manager  |  WS-Management

Comments (20)

  1. Ryan says:

    Nathan, just FYI, but that link doesn’t work, it looks like it’s directed to your OWA account…

  2. Woops, looks like when I copied it from an email it brought the OWA-specific link with it!  It’s fixed now.

  3. Chuck says:

    Is the Windows Management Framework supported on Server 2003 IA-64?

  4. Hey Chuck, Windows Management Framework is not supported on IA-64 for any of the Windows platforms.

  5. Geert Diddens says:

    Hi,…and what about windows 7 ? The link says :

    "This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.

    Visit the Windows 7 Solution Center"

    + There are no links for windows 7



  6. Chuck says:

    Hey Nathan, thanks for the info.  So no PoSh 2.0 for legacy O/S’s on Itanium … I got it.

    Does this also mean you get only PoSh 1.0 if you purchase or upgrade to Server 2008 R2 on IA-64?

  7. powershell says:

    Are BITS cmdlets supported on XP SP3 if Windows Management Framework 2.0 / PowerShell 2.0 is installed?

  8. Chuck, PowerShell 2.0 works just fine on IA-64 machines if you install Windows 7 or Windows Server 2008 R2.

    Geert, these packages don’t apply to Windows 7 because the included components (WinRM 2.0, PowerShell 2.0, and BITS 4.0) are already installed as part of the OS.

    Powershell (if that is your real name), the BITS cmdlets are indeed supported on Windows XP SP3 and they are installed as a part of PowerShell 2.0.

  9. Thom says:

    Are these going to be released as updates via WSUS?

    If so, when?

    It would be great to deploy PowerShell v2 and BITS 4 to all my machines ASAP.

  10. Chuck says:

    Nathan … thanks, again, for the clarification.

  11. Thom, we will indeed be releasing these packages through WSUS, the plan is to make them available later this year.

  12. wdbradley3 says:


    We suffer a lot with issues between SCCM and WMI, and want better tools to detect those issues.  Now that you have released a newer version of WMI for WinXP, is there a newer version of WMIDiag that is "SP3-Aware", or, is there a better tool to use?



  13. Bill, we did not release a newer version of WMI — the Windows Management Framework Core package includes WinRM 2.0 and Windows PowerShell 2.0.

  14. wdbradley3 says:

    Sorry, Nathan, I misunderstood–thought you guys had renamed WMI…

    IS there a newer version of WMIDiag coming out, then?


  15. Hey Bill, I haven’t heard any plans about a new version of WMIDiag coming out.

  16. Sam says:

    Are there any known issues of applying this package on a VM? I installed it on a VM server running Windows 2008 OS (not R2), and from that point the Winrm service shows errors of

    Received the response from Network layer; status: 404 (HTTP_STATUS_NOT_FOUND)



  17. Hi Sam, are you getting that error when you run a specific winrm command or any command?  Are you running the command locally (from within the VM), or are you trying to access it remotely?

  18. SAM says:

    Elaborating a bit – I want to collect event log events using event forwarding. When setting a subscription on the server, the client gets it, but when I’m testing the creation of an event (to see Winrm is loading it to the server), the event is being uploaded (which is good), but I also get this error, so I wonder what it is: Error 129, Microsoft-Windows-Windows Remote Management/Operational,

    Received the response from Network layer; status: 401 (HTTP_STATUS_DENIED)

    Also, Where can I find more information about WinRM service itself? for example, why does it have so many network activity with the destination server that it is subscribed to?

  19. If everything is working, that may just be a spurious error due to an authentication round trip that you can ignore.