Video Screencast Help

SEP on Exchange and SQL

Created: 05 May 2010 • Updated: 05 Jun 2010 | 6 comments
This issue has been solved. See solution.

I have been in the process of migrating all of my Windows 2003 servers over to SEP 11.0.5 client. The last six I have are two Exchange 2003 front end server (load balanced), two Exchange 2003 back end servers (active/passive cluster) and two SQL servers (active/passive cluster). Are there any special client installation steps for these types of server services? Any suggestions would be appreciated. Thanks!

Comments 6 CommentsJump to latest comment

Vikram Kumar-SAV to SEP's picture

Exchange and files are automatically excluded by SEP..however for SQL you need to create Manual Exclusions

As per microsoft recommendation
http://support.microsoft.com/kb/309422/

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

mykul's picture

Thanks for the info.

I was reading about centralized exception for the SQL database but I am not clear on how it should be configured. I have data bases spread out through multiple drives on the SQL cluster so would I have to make multiple exceptions? I don't see where I can exclude the MSSQL\Data folder through one policy for multiple drives. Any suggestions?

Vikram Kumar-SAV to SEP's picture

Make local exclusion from the client on SEP server..or from SEPM..
You will have to make exclusion for each and every folder.
In 1 policy you can add as many exclusion you want.
You cannot exclude multiple drives in one go..you will have to add each and every drive and path .

eg:e:\MSSQL\data,f:\MSSQL\data,g:\MSSQL\data etc..

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

SOLUTION
mykul's picture

Ok, thanks for the suggestion. I think I'll just do it from the SEP client on the SQL box when I install it.

Mick2009's picture

Hi Mykul,

I really, really recommend that you roll out RU6a client instead: details are in this article!

Microsoft cluster resources fail to transition from one node to another within the cluster after Symantec Endpoint Protection 11.0 RU5 installation  (http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009102815324448)

The advice given above about Exchange and SQL exclusions looks 100% to me.  Please do check back on the forum for any future questions or concerns! 

Thanks and best regards,

Mick

With thanks and best regards,

Mick