Installing SEP on Exchange and SQL servers
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
If you install SEP (package that is set to remove settings like scheduled scans) on a server that has SAV 10 already installed and configured with exclusions for Exchange and database folders, will the SEP package get rid of those exclusions?
How does SEP determine if the machine has Exchange or SQL installed and how does it where the files are that need to be excluded?
Discussion Filed Under:
Comments
I dont have it installed on a server with those exclusions...
But I am going to assume that once you upgrade the management console, because it is a new console and centrally managed server, most likely you are going to need to recreate the exclusions in the new server...
Exclusions
When SEP is installed the existing (SAV) settings will be replaced by those of the SEP client. You'll need to setup exclusions within SEP and apply those to the group to which that client belongs. Currently SEP has the ability to create automatic exclusions for the following:
also be aware that during
also be aware that during migration from SAV10 to SEP11 some scheduled scnas are not removed from the registry so you may see some unexpected scans occuring. best practice is to disable all scheduled scans before migration.
David, do exclusions need to
David, do exclusions need to be made for SQL databases?
Exclusions
Yes, exclusions should be set for SQL. Basically for any product we recommend you contact the vendor in order to determine what (if any) exclusions need to be made for a particular product. Vendors are best placed to determine what needs to be excluded for optimal performance of their particular product.
For example Microsoft has published the following KB article concerning exclusions for SQL server:
http://support.microsoft.com/kb/309422
Would you like to reply?
Login or Register to post your comment.