Symantec SMSDOM

As a virus protection we are running Symantec SMSDOM 4.1.0.21 on Domino R6.5.4FP1. The “LiveUpdate” is running fine excepted for two boxes on which we need to go in the settings each time a new definition come in and set the last definition to “Set As Active Definition”. Each servers are setup with the same OS and Domino releases. We un-installed and re-installed SMSDOM several times but it is still acting up.

Anybody ran into this problem?

Subject: Symantec SMSDOM

I remembered we had a similar problem. Look at your rights for the document and try to modify it with another id.

The problem we had was that an admin locked the document and only him was enable to modify it.

Joel Jancovic

http://www.c2j.ca

Subject: RE: Symantec SMSDOM

Nop, there is no difference, same access at the ACL level and to the document level.

And, there is only one server getting the LiveUpdate then I replicate the definition dbse.

Subject: Symantec SMSDOM

The way I would do it, is to setup one server to receive the update, then replicate the Virus Defination DB to all the servers. Make sure that you have replication working correctly.

If you set each server with liveupdate you potentially open your servers up for external attack…

Subject: Symantec SMSDOM

personally i think it’s buggy, we tried it that way orginally and got what you are getting, no one touched the defs (i’m the only one who could). it would run fine for a while and then go weird.

as the os level scanner is installed we went back to having it download the defs (which it did anyway) and smsdom just uses those.

i’ve still go one server that has been configured not to download defs but it’s constantly generating

“unable to complete liveupdate session” which makes no sense at all. it is partitioned so that may account for the weirness.

we just ignore the “errors” as it is definately using the correct version of the signature database.

sometimes i wonder if it’s not just passing on errors from liveupdate itself and it’s not really smsdom at all.