Endpoint Protection

I've installed SAV 9 on a Windows NT 4 server in unmanaged mode.  The Insallation Guide for SAV 9 mentions installing the AMS client manually for unmanaged clients, but doesn't say anything about how to configure it.

Does the AMS service require the server component to be installed somewhere?

Is standalone configuration of the AMS service documented anywhere?

Thanks!

Hmm..

I looked around a little bit for you and found a couple documents that might help you out. I've never done the standalone install myself and don't have quick access to a SAV9 CD to look through the administrator's guide to see if there is anything else useful regarding this in there, but I hope that these are useful to you. YMMV.

Title: 'How to install the Alert Management System Server as a stand-alone application'
Document ID: 2002101113152548
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2002101113152548?Open&seg=ent

Title: 'How to configure unmanaged client alerting on Symantec AntiVirus Corporate Edition clients'
Document ID: 2000072514384348
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2000072514384348?Open&seg=ent

Hope that helps!

Alright, so, I've got things set up to the point where I can configure actions with AMSAdmin.exe. 

Let's say I want to send an SNMP trap if a virus is found.  I can open the AMS Configuration, click "Virus Found" and click Configure.  From here, I choose "Send SNMP Trap" and click next.  The next dialog box asks me to "Select Action Computer".  Unfortunately, the local server isn't on this list.  Another old server with AMS is shown, but I don't want the SNMP trap to come from that computer... I want it to come from the local server.

Any ideas what might be happening here?  I can post screen shots if requested.

Before you proceed, You might like to check this out
https://www-secure.symantec.com/connect/forums/stay-abreast-0

Dont want to get in the midst of the thread discussion, But just as FYI that you should be on MR7 or higher to be on the safe side. Now, I am not sure if this vulnerability affects a self managed client as well , couldnt find it documented anywhere.

Turns out that the SAV Management console needed to be installed before this would work.  We've got it working now.  Thanks for your help everyone.