Video Screencast Help

Installing SEP on Exchange Server

Created: 16 Jun 2008 • Updated: 21 May 2010 | 10 comments
We are pretty close to installing SEP on our Microsoft Exchange 2003 server.  I know the KB articles says that you install this one the exchange server the way you would any client but we've had problems every step of the way with the migration to SEP.  My question to my fellow forum members is how many of you guys have installed SEP on an exchange server and have you guys had problems.  This is Exchange 2003 and Windows Server 2003 standard.  Thanks.



Message Edited by CoveWolf on 06-16-2008 09:21 AM

Comments 10 CommentsJump to latest comment

Knottyropes's picture
I am staying with sav 10 for a while on EXCH 2003.
I know its working this way.
robert rohrer's picture
The setup here is Exchange 2003 Enterprise, Server 2003 standard, sp2.  I am running MR2 , not managed just because I find it easier to control the install.  Been running for a while now, works just fine, have had no problems.  I only use the AV part of sep (file system protection).  The only exclusions I added were for the c: inetpub folder and the Antigen folder.
 
 
Springersrhule's picture

Hi,

A key piece to assuring that Endpoint Protection is safe to run on your Exchange server is the exclusions on the MSE data base. The SEP client software is 'smart' enough to know that exclusions should be made for Exchange servers. The below document notes this, and adds some additional information for other Symantec producsts like Symantec Mail Security for MSE.

http://service1.symantec.com/support/ent-security....

~SR

Yes, I do have a Springer :smileyhappy:

mistywilliams28's picture

I have tried to deploy SEP to several different servers with no success. Is it unnecessary to install SEP on the server that is running the SEPM? The server running the SEPM is a WIn server 2008, Standard Ed. 64 bit- not a DC or anything- just runs DNS, DHCP, and IIS. I also tried to install SEP on a WIn Server 2008 Standard Ed with Exchange 2007 on it to no avail. I get a message when attempting to install to either server that says: This installation package is not supported by this processor type- Contact your product vendor. I am trying the 64 bit. What am I doing wrong?

sandra.g's picture

For file system protection, yes.  The SEPM is a management console only.  It does not provide any protection.

Hopefully these will be of help:

Title: 'Error: "This installation is not supported by this processor type. Contact your product vendor." when installing Symantec Endpoint Protection Client'
Document ID: 2007120308160648
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007120308160648

Title: 'Preventing Symantec Endpoint Protection 11.0 from scanning the Microsoft Exchange 2007 directory structure'
Document ID: 2007072619121148
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007072619121148

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

sandra.g's picture

From : 'About the automatic exclusion of files and folders for Microsoft Exchange server and Symantec products'
Document ID: 2007090220241148
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007090220241148

If Microsoft Exchange servers are installed on the computer where you installed the Symantec Endpoint Protection client, the client software automatically detects the presence of Exchange. When the client software detects a Microsoft Exchange server, it creates the appropriate file and folder exclusions for File System Auto-Protect and all other scans. Microsoft Exchange servers can include clustered servers. The client software checks for changes in the location of the appropriate Exchange files and folders at regular intervals. If you install Exchange on a computer where the client software is already installed, the exclusions are created when the client checks for changes. The client excludes both files and folders; if a single file is moved from an excluded folder, the file remains excluded.

The client software creates file and folder scan exclusions for the following Microsoft Exchange server versions:

  • Exchange 5.5
  • Exchange 2000
  • Exchange 2003
  • Exchange 2007

...
There's more info in the document.

If you install Exchange to a non-default location, you may need to verify the exclusions were created.

Title: 'How to Verify if an Endpoint Client has Automatically Excluded an Application or Directory'
Document ID: 2008090512574448
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008090512574448

Hope this helps--
sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!

mistywilliams28's picture

The server with the SEPM is not liking the 64 bit SEP:) It is now telling me to reboot, over and over again. I tried to push it from the SEPM and I tried to install it from the Installer on CD1 (it is unzipped- I made sure. I ran into that horribly embarrassing issue when I installed the SEPM:) but no luck yet. The SEPM says it was successful, but I can't find it in my programs, which is where I had to check on all the clients after getting a false successful status on several of those when I first deployed. We used the find unmanaged computers because we had to go around and uninstall the older version with the clients, but this is a new server with no AV protection at this point. Any other suggestions? I haven't even retried with the exchange servers because they at least have AV. SO to me, the new server with the SEPM is more important right now.

sandra.g's picture

Glad to hear!

sandra

Symantec, Senior Information Developer
Enterprise Security, Mobility, and Management - Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best helps you!