Endpoint Protection

Managing a standalone server

What is the best way to manage a single server (Windows 2008 R2) connected to the network on a separate subnet from my current SEPM server and not connected to the internet? Should I install the manager or just the client? I installed the client but there is no path to the inbox to paste the .jdb file to update the virus definitions.

What SEP version are you using ?

In SEP 11 C:\Program files\Common files\Symantec shared\VirusDefs\Incoming

In sep 12 You can copy and paste JDB file Below Location

C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\12.xx.x \inbox

install the client on the server and have it updated by the SEPM. Is this not possible?

Otherwise you can just download and run the Intelligent Updater to update the definitions. You can download here:

http://www.symantec.com/security_response/definitions/download/detail.jsp?gid=savce

"Thumbs Up" to Brian.  I'd say use a standalone unmanaged client and update using the Intelligent Updater myself.

If you really do want to use the JDB files however, you'll need to run through the below article to allow an unmanaged client to accept them:

http://www.symantec.com/docs/HOWTO80914

This method was working in 11.x , I haven't checked for 12.x

open C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Definitions

you wiil find numbered folders  for each virus defs till date

copy all the contents of the dated folder

create a new folder called incoming on the target computer you want to update

paste it inside 

restart smc service.

Keep us posted

James,

     I am using version 11.0.6200.754. The file path does not exist.C:\Program files\Common files\Symantec shared and there is no VirusDefs file. Should I create the files?

Thank you.

Hello,

What do you mean exactly by "manage"? Just updating the definitions? Any specific reason to use the .jdb file instead of the .exe (AKA intelligent updater)?

Not sure why the fact that server is not in the same subnet of the manager can be a problem, don't you have a router to connect the two subnets?