Hmm, I just noticed the grade of hardware you're talking about. Hard to believe you considered it acceptable before. Taskmgr.exe is your friend, check the memory load and CPU utilization while waiting for WSUS to do things, and also the CPU load when not asking WSUS to do things. That will reveal all.
-----Original Message----- From: James Kerr [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2008 12:52 PM To: NT System Admin Issues Subject: Re: WSUS Slowness No it has a RAID controller. ----- Original Message ----- From: "Carl Houseman" <[EMAIL PROTECTED]> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com> Sent: Thursday, July 17, 2008 12:40 PM Subject: RE: WSUS Slowness > Is there a directly connected drive which contains the AD database > (sysvol)? > > Directly connected = SCSI, SAS, SATA, IDE, withOUT any RAID controller. > > If so the write caches on those directly connected drives are disabled > when > it's a DC. If you want to call that "added overhead of having AD", feel > free. > > Carl > > -----Original Message----- > From: James Kerr [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 17, 2008 10:50 AM > To: NT System Admin Issues > Subject: WSUS Slowness > > I have a new install of WSUS on the server that had it before. I wiped the > drive and reinstalled everything. This time round I am finding that WSUS > is > running very slow listing and approving updates and just very slow in > general. The only difference is that now the machine is a DC. I saw some > info about running a SQL script that is supposed to speed it up but its > very > > dated. Anyone else have this problem before? > > Full disclosure: This server is old. P3 1.4GHz w/ 768MB but it didnt run > this slow before. Maybe its the added overhead of having AD now? > > James ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
