We were running Symantec Protection for SharePoint servers 5.1, with scan engine 5.1.
The console and scan engine (entire product) was installed on each of our 2 DEV servers as well as our 1 production Sharepoint server (I'll refer to as SPS)
The product was happy and worked, but had some weird messages, skipped some files and the error messages were so plain that a 4 year old could read and understand them, but were basically worthless "there was a problem scaning this file, contact your admin" and the logs showed exactly the same thing as the email alerts! And I'm the admin.
I had the complete product on the SPS, and the scan engine only on another server so that if the SPS servers got busy scanning, overflow was handled by the scan engine on the other server. COOL setup! You could split the load and not overload the SPS machines.
Along comes an upgrade which was recommended by Symantec to solve the cryptic error situation.
So I go to install the new version, it installs over the top as an upgrade/update. HOWEVER, it was NOT happy! It said that there was no scan engine on the Web front end server. Balogna! Bunk. The SPS IS the main or front-end server, running IIS, etc. our DEV and production SQL servers were the back-end or database servers and the product was never on them.
This new version had a cow! It alerted me that no scannning could take place and named our SQL servers as the web front-end servers and said there was no registered scan engine on them. Of course not, they were just the back-side SQL servers. ALL the work was done on the SPS servers, web, sharepoint, etc.
Well, I ended up having to install the ENTIRE product on all of our SQL servers to make it happy. I showed our SQL admin what the product was telling me and he agreed - BS. They are simply the SQL servers holding the info, the processing and front-end was all taking place on the SPS servers..........
So what gives? Seems the latest protection for Sharepoint doesn't agree with our DBA! LOL Who is right - you or him?
SPS1 is the Sharepoint server, runs IIS and is what people deal with.
SQL1 is the production SQL server and is simply the database and has SPS reporting services installed on it.
When I go to the Sharepoint admin console on the SQL server, it jumps to the SPS1 server and port, so I KNOW SPS is being administered on and from the SPS server. Why does the Symantec product think otherwise?
Here's what it says NOW, but before, the bottom half was RED and full of errors:
-------------------------------------------------------------------
SharePoint Server Farm overview
This page gives information of all the SharePoint Servers in the Farm.
1. Server: VRDSMSPS1 (Local) Address: VRDSMSPS1 Farmrole: Application Server State: Online
Operating System: Microsoft Windows Server 2003 (Build: 3790 Service Pack 2)
SharePoint Server: Microsoft SharePoint Server 2007 (Version: 12.0.0.4518)
Symantec Protection 5.1 for SharePoint Servers
Version: 5.1.0.5019
Current State: Started
Virus definition: 03/22/2009 Revision: 18
Symantec Scan Engine: Registered: 3 Disabled: 0 Online: 3 Offline: 0
Connections: 0
384
2. Server: vrdsmsql1 Address: vrdsmsql1 Farmrole: Web Frontend Server State: Online
Operating System: Microsoft Windows Server 2003 (Build: 3790 Service Pack 2)
SharePoint Server: Microsoft SharePoint Server 2007 (Version: 12.0.0.4518)
Symantec Protection 5.1 for SharePoint Servers
Version: 5.1.0.5019
Current State: Started
Virus definition: 03/22/2009 Revision: 18
Symantec Scan Engine: Registered: 1 Disabled: 0 Online: 1 Offline: 0
Connections: 0
128