I've been trying to cure a client side lag issue on my network for a few months. I eventually traced it to a potential problem which occurred when converting the local accounts into domain accounts. I fixed it, or so I thought, by running Microsoft's User Profile Hive Cleanup Service (here). At the same time I updated various patches via WU.
The lag vanished and everything went back to normal.
BUT!
Today is Patch Tuesday and the lag issue has reared it's stupid ugly smug head again - meaning it wasn't a Hive issue.
Briefly, the issue is a four to five minute total freeze (100% CPU) of a machine usually hourly, sometimes every two hours. No two machines will freeze at the same time but all machines on the network will eventually freeze.
The freeze is sometimes preceded by a Launchpad alert on my admin machine, stating "Computer Monitoring Error". The error states; Some health evaluations did not complete. The incomplete items are: MicrosoftSecurity!XP_WindowsUpdateMissing.
SBS2011e doesn't include WSUS so all updates are manually applied as and when I have time, usually on the weekend following Patch Tuesday. As a result of this, all machines are set to look for, but not download any updates.
I've deduced that as soon as there's an update available, the SBS monitoring service craps itself - as evident by the monitoring error - and the client machine begins the freezing process.
I'm assuming I can prevent it happening either by stopping the client machines checking for updates or by turning BPA off on the server. There are a few TN discussions relating to the monitoring error and there's even a beta patch (here), but I'm loath to install it when I am not getting the exact error messages it claims to be able to cure.
The point of this post is to ask if anyone happens to know why this is happening?
Ta!


LinkBack URL
About LinkBacks
Reply With Quote