"Brett" <Brett[ at ]discussions.microsoft.com> wrote in message news:C84A30D3-C882-4ADD-B3B2-A822FD388992[ at ]microsoft.com...
[Quoted Text] >I clicked the link provided http://support.microsoft.com/kb/922330> > and ran the command > > If you are using WSUS 3.0 with a Windows Internal Database that was > created > by a default WSUS installation, type the following command: > > %programfiles%\Update Services\Setup\ExecuteSQL.exe -S > %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q "update tbConfigurationC set > BitsDownloadPriorityForeground=1" > > my updates are now coming down at the correct speed and it has solved the > problem 100%. Thanks again, I can't belive that ini all the FAQ and the > wsus > site there is no metion of this fix. It is such a huge oversight on > microsofts part as this is a critical fix that I am sure is needed by may > people. Brett, it's not an oversight.
It's a non-standard configuration, primarly created for =diagnostic= purposes.
The NORMAL and CORRECT functioning of the WSUS system is to have BITS work in background mode (BitsDownloadPriorityForeground=0), so that it doesn't suck your Internet pipe dry while it's downloading gigabytes of content during normal operations.
The primary reason why it becomes necessary to enable foreground mode is because some device in your infrastructure has not been properly upgraded, and is not fully supporting the HTTP v1.1 protocol specification.
--- or, sometimes, just because the admin doesn't understand that downloads are supposed to be "slow" in the WSUS environment -- it's By Design!
-- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
|