Started an install of SEP on a Friday night on an SBS2003 machine and 15 WinXPPro workstations. We downloaded SEP from Symantec's fileconnect server as an upgrade to SAV 10.2. To make a long story short, what started out as a simple upgrade on a Friday night turned into an all-weekend pull-all-your-hair-out-of-your-head-a-thon trying to get this program working. After spending hours on Symantec's message boards and reading multiple SAV bulletin boards (many of which were found by Googling "Symantec Sucks") we finally managed to get the damn thing working. For us, the biggest issues were as follows:

1. You need JAVA to run the management console, and only Java 1.5 and Java 1.6 r4 is supported. If you have your JAVA applet set to download updates automatically, you will receive v. 1.6 r3 which is not supported. You need to manually download 1.6 r4 as of today.

2. If you have multiple web servers on the SBS2003 machine, check that the TCP ports they use don't conflict with the TCP ports used by SEP. You can download a TCP port utility from microsoft that runs from a command line to help with this.

3. The drive/directory/share containing the SAP install files and database MUST allow read/execute permissions for the USER object, EVEN if you are logged in as an admin or power user.

4. We had to go into the ODBC manager and manually enter information in order to get SAP to talk to it's own database (the database included with the program, not SQL server). Most importantly, we had to enter the name of the SBS2003 server machine in the "server" field, even though the field should be able to be left blank (as the database resides on the same machine as the endpoint manager).

My advice to small businesses without a dedicated IT staff and the time/funding to deploy a test environment.... "DON'T INSTALL THIS PRODUCT RIGHT NOW". Keep using SAV 10.x until Symantec works out all the major bugs.

Having said all this, if you are able to get SAP to work on your network, it appears to work very well.