<?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>Trick/Tip:  Assigning a Default Maintenance Window to Systems that do not already have one Assigned in ConfigMgr</title><link>http://blogs.technet.com/kevinsul_blog/archive/2009/04/13/trick-tip-assigning-a-default-maintenance-window-to-systems-that-do-not-already-have-one-assigned-in-configmgr.aspx</link><description>So a few weeks ago, Mr. Joseph Corey at Carnegie Mellon University presented on how they use ConfigMgr to keep their servers in their data centers updated and patched.&amp;#160; As one would imagine, they need to be able to tightly control the window of time</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>