I dragged the stake machine over to the FHC to give it a connection and see what it would do. I did find a way of manually triggering the Live Update. Simply run C:\Program Files\Symantec\LiveUpdate\LUALL.exe. It connected to something identified as "LDS Liveupdate" and then proclaimed all my files were up to date. I noticed that anti-virus definition updates were not listed in the things it was going to check for. In fact the only things listed was "LiveUdate" itself and "Symantec Security Software Update".
Again, LiveUpdate is not
disabled, manual triggering
from the client screen is what is disabled.
So far what I see is consistent with our clients being centrally managed. Our computers check in with our
(LDS) server rather then going direct to Symantec. That's what "Corporate Edition" is all about.
Rummaging around the help file, I found the following: "Note: Your administrator may have specified a maximum number of days that the virus and security risk definitions can be out of date. After exceeding the maximum number of days, Symantec AntiVirus automatically runs LiveUpdate when an Internet connection is detected."
So, I wonder what this is set to? My definitions are a few months out of date. It's older then Alan's. But it still may not be old enough to trigger LiveUpdate. Remember, we've been asked to do quarterly updates. So it's wouldn't be set for less then 90 days.
So at this point I think our "myth" that old virus definitions could cause problems with MLS connections remains as "plausible". (An MLS connection looks just like an Internet connection to the computer. In fact it fires up the MLS dialup connection in the Network Neighborhood.) But you have to let the definitions lapse beyond the quarterly update that's been asked of us. A side effect of this is that SAV won't update on a daily or weekly schedule by itself when connected to broadband.
As a reminder, the above applies to administrative computers running Desktop 5.5, not FHC computers which are managed by a different policy.