<?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>Troubleshooting WSUS clients</title><link>http://blogs.technet.com/b/sus/archive/2008/07/10/troubleshooting-wsus-clients.aspx</link><description>Client communication When troubleshooting clients, the first thing you'll want to look at is the windowsupdate.log which will be in c:\%windir%\Windowsupdate.log. In order to understand how to read the windowsupdate.log , the reference for it is located</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Cool WSUS troubleshooting tools and script examples</title><link>http://blogs.technet.com/b/sus/archive/2008/07/10/troubleshooting-wsus-clients.aspx#3137257</link><pubDate>Thu, 16 Oct 2008 16:24:49 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3137257</guid><dc:creator>The WSUS Support Team Blog</dc:creator><description>&lt;p&gt;You're probably already well aware of Microsoft's CodePlex open source project hosting website but in&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3137257" width="1" height="1"&gt;</description></item></channel></rss>