<?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>SMS 2003: Troubleshooting the data flow for Security and Office updates</title><link>http://blogs.technet.com/smsandmom/archive/2008/02/11/sms-2003-troubleshooting-the-data-flow-for-security-and-office-updates.aspx</link><description>It seems like a fairly common situation we find ourselves in around here is troubleshooting Security or Office updates so I imagine that on occasion you might find yourself in the same boat.&amp;#160; If so, the steps below are a high level overview of the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>SMS 2003: Troubleshooting the data flow for Security and Office updates</title><link>http://blogs.technet.com/smsandmom/archive/2008/02/11/sms-2003-troubleshooting-the-data-flow-for-security-and-office-updates.aspx#2869470</link><pubDate>Mon, 11 Feb 2008 17:46:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2869470</guid><dc:creator>Ron Crumbaker at myITforum.com, Inc.</dc:creator><description>&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.technet.com/smsandmom/archive/2008/02/11/sms-2003-troubleshooting-the-data-flow-for-security"&gt;http://blogs.technet.com/smsandmom/archive/2008/02/11/sms-2003-troubleshooting-the-data-flow-for-security&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>