Endpoint Protection

Dear All,

We have a Symantec System Center (ver. 10.0.1.1009) in our environment and all of our clients are using SAV 10.1 and 10.2. Some new Win2008 R2 servers will join into the environment. I want to ask whether the existing Symantec System Center can manage the SAV client for WIn2008 R2 and how can I get the current managed client for installation? many thanks~

BR,

Derek

Symantec AntiVirus Corporate Edition 10.2 Maintenance Release 1 (MR1) and higher includes support for Windows 2008.

SAVCE 10.2 MR 4 introduced client-only support for Microsoft Windows 2008 Server SP2 and Windows Vista SP2. The Symantec AntiVirus Server, Symantec System Center and deployment tools have been modified to support the management of clients that run on Windows Server 2008 or Vista, but the management components cannot be installed on these operating systems.

SAVCE 10.2 Client support for Windows Server Core 2008 was added as of SAVCE 10.2 MR2.

Symantec AntiVirus Corporate Edition 10.2 MR3 and later are supported on Windows Server 2008 R2. All previous versions of Symantec AntiVirus will not run on Windows Server 2008 R2. Symantec AntiVirus Corporate Edition is not supported on Windows 7.

Symantec System Center can manage the SAV client for WIn2008 R2 and how can I get the current managed client for installation? 

it can manage the policy, however the definition updates will NOT be provided to Windows 2008 R2 client as it is 64 bit OS. The agent setup can be found under the CD. You may also use the remote deployment of SSC console.

Thanks all of you.

The SSC mainly for the definition updates in our environment,  so I think I will install SEP or SAV 10.2 MR4 for those 2008R2 and schedule the updates by internet in this way.

Yes, 64 bit SAV clients can get updates from Internal Liveupdate or the Symantec Liveupdate.

Hi derek,

As stated above: 64-bit SAV 10 clients need to update via LiveUpdate rather than the VDTM technology that 32-bit clients use.

Depending on how many 64-bit SAV 10.x clients you have in your network, the internal LiveUpdate Administrator 2.x tool (LUA 2.x) can save you some bandwidth.  It will download the necessary definitions once from the Internet and then make them available internally on your network.

Here's a link with more information:

How to Identify What Contents to Download and Distribute with LiveUpdate Administrator 2.x for Symantec AntiVirus 10.x
Article: TECH92594 
Article URL http://www.symantec.com/docs/TECH92594
 

If you have more than a handful of 64-bit SAV 10.x clients, I recommend the use of LUA 2.x.  Hope this helps!

Thanks and best regards,

Mick

We have a Symantec System Center (ver. 10.0.1.1009) in our environment and all of our clients are using SAV 10.1 and 10.2.

It is not recommended that the SSC be an earlier version than your SAV clients (the exception being SAV 10.2.x, which is managed by 10.1.x SSC). Communication errors can occur. I would recommend bringing SAV to the latest build, all around.

The following includes links to migration documents:

Best practices for configuring Symantec AntiVirus Corporate Edition 10.x
http://www.symantec.com/docs/TECH101213

Release notes for Symantec Client Security 3.1.x and Symantec AntiVirus 10.1.x
http://www.symantec.com/docs/TECH101820

sandra

hi Mick,

Thanks for your advice. We only have 2 machines with Win08R2 and will upgrade the SAV infrastructure later, so I think just leave it alone now, thanks again~

Yes, I think so, but I can't do much in my environment for some reason..

Actually I have really bad experience on upgrade Symatec product, from SAV to SEP and BE, BESR...esp. the JAVA and Tomcat...sign

Based on my personal experience. In migrating from SAV to SEP, it would be better to have another server to handle the SEP instead of migrating the SAV server directly. Worst case scenario is that your SAV clients won't get updates from the server until everything is upgraded to SEP.