<?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>Reassigning a Configuration Manager Client Across Hierarchies</title><link>http://blogs.technet.com/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx</link><description>[Today's post comes to us from Carol Bailey ] When you reassign a Configuration Manager client from one hierarchy to another, the client already has a trusted root key from its original hierarchy. Reassigning the client to a new hierarchy means that the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Round-up of New Posts on the Configuration Manager Team Blog: April 04 – April 10 2009</title><link>http://blogs.technet.com/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx#3225162</link><pubDate>Fri, 10 Apr 2009 23:11:46 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3225162</guid><dc:creator>Configuration Manager Writers - Announcements, Comments and other Stuff</dc:creator><description>&lt;p&gt;In case you missed them, the following posts were published on the System Center Configuration Manager&lt;/p&gt;
</description></item></channel></rss>