<?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>Determining which packages are &amp;quot;Needed&amp;quot; across your managed environment</title><link>http://blogs.technet.com/systemcenteressentials/archive/2008/04/30/determining-which-packages-are-needed-across-your-managed-environment.aspx</link><description>Over the past six months, many within the System Center Essentials community provided feedback on the inability of SCE to show which updates and software are needed by managed systems. Workarounds exist today for Microsoft Update content, but when it</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>http://beta.bloglines.com/b/view</title><link>http://blogs.technet.com/systemcenteressentials/archive/2008/04/30/determining-which-packages-are-needed-across-your-managed-environment.aspx#3055896</link><pubDate>Fri, 16 May 2008 01:05:47 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3055896</guid><dc:creator>TrackBack</dc:creator><description /></item></channel></rss>