Windows PowerShell RC2 Now Available

  • Comments 59

Windows PowerShell RC2 Now Available

Today Microsoft announced the availability of Microsoft Windows PowerShell RC2, the command line shell and scripting language that helps IT Professionals achieve greater productivity and control of system administration. Using a new admin-focused scripting language and consistent syntax and utilities, Windows PowerShell accelerates automation.  Windows PowerShell is easy to adopt, learn, and use, because it works with existing IT infrastructure and scripting tools.


·         This Release Candidate 2 of Windows PowerShell addresses numerous customer requests based on their evaluation of Beta3 and RC1 including:

·         Direct ADSI support to allow IT Pros to more easily administer Active Directory

·         Improved support for Windows Management Instrumentation through ability to change WMI properties via methods

·         Additional logical operators (XOR and binary XOR) that make it easier to write sophisticated scripts

·         Improved help content and help functionality including new views that make it easier to find the right information.

·         Windows PowerShell 1.0 will release-to-web in Q4 CY06

·         Windows PowerShell will be leveraged by Microsoft Exchange Server 2007 and System Center Operations Manager 2007.


Customers can download Windows PowerShell RC2 at


Leave a Comment
  • Please add 5 and 7 and type the answer here:
  • Post
  • Windows PowerShell Windows PowerShell RC2 Now Available 달라진 점:...
  • Trying to run WindowsServer2003-KB923567-x86-ENU.exe on Windows Server 2003 SP1 (all latest updates) I get an error during setup.

    Running logging on the install I see this at the end of the log:

    10.531: Starting process:  "C:\WINDOWS\$NtUninstallKB923567$\PSCustomSetupUtil.exe" /install "C:\WINDOWS\system32\WindowsPowerShell\v1.0\\System.Management.Automation.resources.dll"
    10.610:  Return Code = 4
    10.610: DoInstallation:RunInfProcesses for ProcessesToRun Failed

    Looks like setup is failing because of the double backslash in the path to the file that is trying to be registered. I can repro this on a number of systems.

    I have logged this on Connect but does anyone have a workaround?
  • Still can't download it...
  • Which version for Windows Vista RC1
  • Ofer: As of 1:41 PST, Tobias updated the PowerShell IDE to work with RC2.  Check again!
  • Trying to use the ADSI support, and can't get get-member to return the methods of the object, only properties.  
  • Since most of the scripts I write use ADSI, I haven't been very interested in PowerShell until now. After scanning the PowerShell Primer, I didn't see anything in the table of contents related to ADSI. Where do I need to start to get up to speed on using PowerShell with ADSI?
  • I haven't seen it announced anywhere yet but it looks like the version 1.0 RC2 installation files for PowerShell/Monad are available thru KB 925228

    If you ever plan on using Exchange 2007, you will want to get comfy/familiar with this scripting langua
  • I've been impressed with PowerShell and try to get others hooked to it. Great job cleaning up the sections. It would be nice, though, if the phrase "Specifies only those items upon which the cmdlet will act" under the "Include" parameter description were changed to "Specifies only those items the cmdlet will act on".
  • Arul has a good blog entry on the new ADSI stuff at:


    Bruce Payette
    Windows PowerShell Technical Lead
  • It looks like the URLs on the KB page are all messed up.  There doesn't appear to be any direct way to download the Windows Server 2003 x86 version.  Can somebody fix the links on that page?
  • You can get all the PowerShell distributables from this link:
  • Get the download from here and more information on the PowerShell blog
  • You've been kicked (a good thing) - Trackback from
  • Ok, so putting the release notes under %SystemRoot%\system32\windowspowershell on x64 was a really bad idea: it results in mysterious "File not found" errors when the 32bit version of Word tries to open it (because it redirects to SysWow64). Took me about five minutes to figure that one out.

    Secondly, I notice that 'ls | rm' now works when there are files with special chars in them, even without specifying LiteralPath. Great! How is this working? Do the commandlets no longer reparse the file-names for piped input?

    Thirdly, can we expect any speed improvements in the future, particularly to the start-up time (before I can type at the prompt). When it's been loaded before, it starts up in about two seconds, but the first time can take up to twenty seconds (well, an annoying amount of time, anyway). This inhibits me from using it as a full-time shell.

Page 2 of 4 (59 items) 1234

Windows PowerShell RC2 Now Available