We have a small server running a couple of internal classic asp and .net websites. SQL 2008 is also installed on this box.
How should Endpoint Protection be configured to not screw with the normal functioning of the apps?
We have a small server running a couple of internal classic asp and .net websites. SQL 2008 is also installed on this box.
How should Endpoint Protection be configured to not screw with the normal functioning of the apps?
That's strange. It sounds like the sysadmin has a sense of ownership of the server if he's insisting that it be installed. It also sounds like he is the AV administrator, but it doesn't sound like he knows what AV exclusions to configure on a web and SQL server. Is that the case?
Have a look here: http://myitforum.com/cs2/blogs/scassells/archive/2007/05/14/what-anti-virus-scanning-exclusions-should-be-considered-for-system-and-servers.aspx.
And here: http://support.microsoft.com/kb/943556.
Assuming you have access to the Management console, Create Exclusions / Centralized Exceptions for files with the following extentions -
*.MDF ; *.NDF and *.LDF
Additionally, create an exception for the folder where your database data files (*.MDF ; *.NDF and *.LDF) are going to be stored
Not sure waht the imapct on IIS will be. Not aware of any specific exceptions needed.
Is any part of the SEPP arcitecture on the box other than the client?