CTP: Platform Requirements

CTP: Platform Requirements

  • Comments 17

Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. I'm going to hold off saying what is in it until next week. The purpose of this email is to set your expectations about the CTP.

Platform Requirements

The first thing to be clear about is that the platform support for the CTP says nothing about the platform support for V2. There are lots of factors that go into that decision and those discussions happen late in the game. You don't need to provide any feedback on this topic – we know that the wider the platform support the better. I'll continue to push to make it available on Win98 but I failed the last time and probably will fail again this time. J

So here are the details:

  • The PowerShell CTP runs on x86 and x64 versions of Windows XP SP2, Windows Server 2003-sp2, Windows Vista, Windows Vista-SP1, Windows Server 2008
  • The PowerShell CTP includes Remoting features. This uses the latest (V1.1) version of WS-Management (also known as WINRM) and will not function property without this installed.
    • These bits are included in the beta of Windows VISTA-SP1 and Windows Server 2008. No action is required if you are using either of these.
    • You will have to download this feature to use remoting on XP-SP2 and 2003-SP2. You can get the bits from the Microsoft Download Center.
    • You cannot use Remoting on Windows Vista. You will have to use the VISTA-SPI beta if you want to use Remoting. (Apologizes in advance.)
    • PowerShell remoting features only work when used on systems where both (or "all") systems have PowerShell remoting. You'll need to install the WS-Management V1.1 and the PowerShell CTP bits on all systems you want to run against.

Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx


Leave a Comment
  • Please add 1 and 6 and type the answer here:
  • Post
  • Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. This release

  • Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. This

  • More about the very cool Powershell V2 CTP next week when my NDA expires, but before that a warning on

  • The Windows PowerShell Team is pleased to release the first Community Technology Preview (CTP) of Windows

  • The first CTP of Microsoft Powershell 2.0 is out! It doesn´t work very well with Vista RTM, so install

  • Le blog n'a même pas encore un message qu'on parle déjà de PowerShell 2.0 !! En effet depuis

  • There is no any available WINRM for Windows XP x86 SP2 in China...I have no idea to install CTP on my OS...There is only WINRM 1.1 for Windows 2003, Windows XP amd64.

    I hope I can play with PS2 CTP at home, sigh...

  • Edengundam,

    WS-Man (WinRM) is available for XP-SP2 as well along with for W2K3-SP1 and W2K3-SP2 at http://www.microsoft.com/downloads/details.aspx?FamilyId=845289CA-16CC-4C73-8934-DD46B5ED1D33&displaylang=en. Please read the System Requirements section of WS-Man download.

  • Thank you very much.

    But there is no available WS-Management v1.1 for chinese user.

    It seems they didnt release xp-sp2 x86.

    This is the page which is render in Chinese...


    Maybe later they will release it.

  • The PowerShell team released a Community Technology Preview of PowerShell 2.0 this week. They have had

  • really awesome post.

    quite helpful

  • Does Powershell run on Windows Vista Home Basic?

  • The PowerShell 2.0 CTP is nearly here!

  • I am trying to install it on a Windows 2008 Server 64 bit machine and I get the following error:Error writing to file: C:\Windows\system32\WindowsPowerShell\v1.0\en-US\about_Alias.help.txt.  Verify that you have access to that directory.

    I am using an administrator account and I have full administrator priveleges.

  • I have the same error as you Prashant.

    I have full access to the WindowsPowershell folder and all its files and folder. But I still get the same error..



Page 1 of 2 (17 items) 12