<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Windows Server 2008 and 2008R2 Failover Cluster Startup Switches</title><link>http://blogs.technet.com/b/askcore/archive/2010/06/08/windows-server-2008-and-2008r2-failover-cluster-startup-switches.aspx</link><description>&amp;#160; I am here today to discuss the troubleshooting switches used to start a Windows 2008 and 2008 R2 Failover Cluster. From time to time, the Failover Cluster Service will not start on its own. You need to start it with a diagnostic switch for troubleshooting</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Windows Server 2008 and 2008R2 Failover Cluster Startup Switches</title><link>http://blogs.technet.com/b/askcore/archive/2010/06/08/windows-server-2008-and-2008r2-failover-cluster-startup-switches.aspx#3469681</link><pubDate>Thu, 08 Dec 2011 03:11:31 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3469681</guid><dc:creator>khemarin Set</dc:creator><description>&lt;p&gt;it is very helpful.&lt;/p&gt;
&lt;p&gt;We can using script to check:&lt;/p&gt;
&lt;p&gt;Get-WmiObject -class Win32_Service -computername . -namespace &amp;quot;root\CIMV2&amp;quot; | Where-Object {$_.Name -match &amp;quot;clussvc&amp;quot; -and $_.StartMode -match &amp;quot;auto&amp;quot; -and $_.state -match &amp;quot;stopped&amp;quot;} | net start clussvc /forcequorum node_name &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3469681" width="1" height="1"&gt;</description></item></channel></rss>