<?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>OpsMgr 2007 Design Tips from the Field</title><link>http://blogs.technet.com/stefan_stranger/archive/2008/05/08/opsmgr-2007-design-tips-from-the-field.aspx</link><description>Source: Raymond Chou Raymond has posted an article about some Design Tips for OpsMgr 2007. I totally agree with Raymond&amp;#8217;s list of Design Tips. These are the ones I used for my last OpsMgr Design: Design Rules/Best practices: (1) No more than 2000</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>