I’m trying to take the temperature from the community here on an issue that I’ve seen pop up on a few of the computers at a few of my sites. I’ve lodged the issue with Trend now here in Australia, and I’ve started to hear from a few others around the world that they too might be experiencing the same issue. So what I’m trying to do is to use the power of the community to feedback to Trend some additional information so that they can better investigate and resolve the issue. If you are experiencing the issue I mention below, please lodge the case with your local Trend support line and then let me know directly via email your case number. What I’ll do with that is to pass it on to the Trend Product team so that they can look at the issues as one rather than individually. My email address is [email protected]
The issue I’m talking about seems to affect CSM 3.6 for SMB only. What occurs is that a few (maybe 1 or 2) computers in a network with CSM 3.6 installed will take abnormally long to start up and be VERY slow for some time after it’s booted up. From my investigations I have seen large amounts of disk activity and the TSC.EXE (Trend System Cleaner) running hard on CPU. Initially I thought it was as a result of an infection and that TSC was doing it’s job cleaning the system, however this now appears to not be the case. Other potentially unrelated aspects to this may be error messages indicating that the client is out of system resources and the like. I must stress that this issue does not affect ALL systems. Certainly out of the many hundreds of Trend clients we have, we’ve seen it now on a total of 6 PCs across all of them. From what I can see, it does not affect Vista clients, only XP and 2000 clients. It does not seem to affect 2003 servers themselves either.
So if you have this problem – please – let me know so that we can help resolve it sooner than individual cases might allow.
8th December 2007 Update – Trend have released patches and fixes for this – please see my blog post for more information