<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.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/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>WSUS Celerons and SVChost</title><link>http://msmvps.com/blogs/bradley/archive/2007/04/14/wsus-celerons-and-svchost.aspx</link><description>"BK" posts in what we've been suspecting all along..that 927891 isn't working/doesn't always work. Oh in my network where I don't have Celery.... I mean Celerons .... so the applications of 927891 does help a lot, but if you have underpowered machines</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>re: WSUS Celerons and SVChost</title><link>http://msmvps.com/blogs/bradley/archive/2007/04/14/wsus-celerons-and-svchost.aspx#894796</link><pubDate>Tue, 08 May 2007 16:22:59 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:894796</guid><dc:creator>Kore Breach</dc:creator><description>I can confirm that WSUS 3.0 still has the same problem.  We have a network of about 3000 XP computers, and recently began testing WSUS 3.0.  The issue is still the actual scan of the computer being a highly resource-intensive operation (when mixed with scanning computers with Windows Installer 3.1 software installed, such as Office 2003 or Office XP).  The fault is an interaction between the scanning engine (regardless of if it is started by WSUS, Microsoft Update, or XP Automatic Updates) and Windows Installer 3.1.  BITS does nothing for helping this since BITS is concerned with utilizing bandwidth better, not with utilizing memory better.  So for now, I am like the rest of you... waiting for MS to update the scanning engine to use less memory.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=894796" width="1" height="1"&gt;</description></item><item><title>re: WSUS Celerons and SVChost</title><link>http://msmvps.com/blogs/bradley/archive/2007/04/14/wsus-celerons-and-svchost.aspx#894794</link><pubDate>Tue, 08 May 2007 16:20:40 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:894794</guid><dc:creator>Kore Breach</dc:creator><description>I can confirm that WSUS 3.0 still has the same problem.  We have a network of about 3000 XP computers, and recently began testing WSUS 3.0.  The issue is still the actual scan of the computer being a highly resource-intensive operation (when mixed with scanning computers with Windows Installer 3.1 software installed, such as Office 2003 or Office XP).  The fault is an interaction between the scanning engine (regardless of if it is started by WSUS, Microsoft Update, or XP Automatic Updates) and Windows Installer 3.1.  BITS does nothing for helping this since BITS is concerned with utilizing bandwidth better, not with utilizing memory better.  So for now, I am like the rest of you... waiting for MS to update the scanning engine to use less memory.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=894794" width="1" height="1"&gt;</description></item><item><title>Windows Update Agent v2 Still Causing Problems</title><link>http://msmvps.com/blogs/bradley/archive/2007/04/14/wsus-celerons-and-svchost.aspx#805479</link><pubDate>Sun, 15 Apr 2007 01:15:40 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:805479</guid><dc:creator>The Daily Ramblings of an SMS Engineer</dc:creator><description>&lt;p&gt;This should sound familiar to a number of people. WSUS Celerons and SVChost &amp;quot;BK&amp;quot; posts in what we've&lt;/p&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=805479" width="1" height="1"&gt;</description></item></channel></rss>