<?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>Best Practice for Multiple FCS Deployments</title><link>http://blogs.technet.com/clientsecurity/archive/2007/08/17/Best-Practice-for-Multiple-FCS-Deployments.aspx</link><description>Hi Folks, Here’s a FCS Best Practice from the Engineering team for those of you that have deployed or will deploy multiple FCS deployments across an enterprise. Best Practice : As indicated in the FCS v1.0 Release Notes , each FCS deployment should be</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Forefront Client Security release notes and best practices</title><link>http://blogs.technet.com/clientsecurity/archive/2007/08/17/Best-Practice-for-Multiple-FCS-Deployments.aspx#1778128</link><pubDate>Sat, 18 Aug 2007 22:35:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1778128</guid><dc:creator>Aaron Tiensivu's Blog</dc:creator><description>&lt;p&gt;I noticed this post over at the Forefront Client Security blog asking for feedback from customers that use the same management group name for multiple deployments within the same environment. As a best practice they recommend using different manageme&lt;/p&gt;
</description></item></channel></rss>