Posted by: kurtsh | December 23, 2008

BETA: Powershell for Failover Clustering in Windows Server 2008 R2

Powershell2 <as taken from the Microsoft Clustering blog>

In Windows Server 2008 R2 (“R2”) we are introducing PowerShell as the new scripting language for clustering technologies. PowerShell with Failover Clustering will replace Cluster.exe and the Windows Server 2008 R2 release will be the deprecation release for Cluster.exe. This means it will still available for use so it doesn’t break legacy scripts, but no improvements have been made and Cluster.exe will be completely removed in the next release of Windows Server. This allows ample time for you to learn (and love) PowerShell.

PowerShell provides numerous benefits over standard command line interfaces, including easily customizable scripts and the dynamic use of variables. In Windows Server 2008 R2, PowerShell can also be run on Server Core machines. Using PowerShell on a Core cluster, you can directly run cluster Validation and generate dependency reports, without needing to manage the Core node through a UI-based remote machine.

This blog post will provide an overview of PowerShell with Failover Clustering. In the next few weeks, a post about PowerShell with Network Load Balancing (NLB) will be added to the site.

How do I get R2 Beta?

There are numerous ways to get the Windows Server 2008 R2 Beta build which includes Failover Clustering (on Enterprise and Datacenter editions). If you work for an organization which partners with Microsoft, try contacting your Technology Account Manager (TAM) to see if they can provide you with access. If your organization is enrolled in the Technology Adoption Program (TAP) you may also have access through this channel. Others may enroll in the Microsoft Connect program (http://connect.microsoft.com/) to receive access to major builds. The Beta build will be available very shortly for deployment and testing.

We want your feedback!

PowerShell is going to be the cluster scripting language for the future – and you have the opportunity to influence its design and use for the next decade during the Beta feedback period. Some high-level areas of feedback for the PowerShell commands (cmdlets) which we are looking for include the following:

  • Was it easy to find the cmdlet you wanted?
  • Are the parameters consistent between cmdlets?
  • Is the in-box help and example useful?
  • Has the PowerShell utility met your scripting needs?
  • Was there a cmdlet which did something different than you expected from its name or description?
  • Anything else?

We encourage you to provide feedback through the appropriate channels on the Microsoft Connect site, through your TAM, or TAP Program Manager.

———————

MORE INFORMATION:
http://blogs.msdn.com/clustering/archive/2008/12/20/9243367.aspx

Digg This


Categories

%d bloggers like this: