<?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>Microsoft IT's OpsMgr 2007 Deployment: The RMS</title><link>http://blogs.technet.com/momteam/archive/2008/03/04/microsoft-it-s-opsmgr-2007-deployment-the-rms.aspx</link><description>Here is the next entry in the posts I’m migrating over. Again this intended to be a “snapshot in time” supplement to the Implementing System Center Operations Manager 2007 at Microsoft white paper. The Root Management Server (RMS) So what exactly does</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Microsoft IT's OpsMgr 2007 Deployment: The RMS</title><link>http://blogs.technet.com/momteam/archive/2008/03/04/microsoft-it-s-opsmgr-2007-deployment-the-rms.aspx#2960384</link><pubDate>Tue, 04 Mar 2008 21:42:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2960384</guid><dc:creator>jguillet</dc:creator><description>&lt;p&gt;Nice article.&lt;/p&gt;
&lt;p&gt;Microsoft could do better in the business continuance/disaster recovery arena by providing a simple wizard to automate the promotion/demotion of the RMS.&lt;/p&gt;
&lt;p&gt;Most DR scenarios usually involve a site failure (power or network) that simple clustering won't resolve. &amp;nbsp;The steps required to failover to a remote site (importing the RMS keys and updating the agents) currently require someone with sufficient rights to follow a seperate DR procedure document. &amp;nbsp;It would be nice if this could be done from the GUI (where the admins live).&lt;/p&gt;
</description></item></channel></rss>