Microsoft Small Business Server 2003 Best Practices If installing on an older machine (or virtual machine) make sure that your system meets the minimum requirements:
Processor Dual-Core / Dual CPU Memory 2GB RAM (installed in the machine) Disk Space 20GB of free disk space (mostly to allow room for the database to grow over time) Note: At least 500mb of free space is required on the system drive (usually C:) even if not installing there.
An introduction:
When I took over administration of a network, a previous admin had installed Symantec Antivirus (aka SAV) on all the machines and had a server to download the virus definitions from Symantec. None of the other techs knew how it worked, we all just assumed that it worked and didn’t require our intervention.
Then one day I thought of moving the server to a virtual machine; in the process I broke the connection from the clients to the server. This created a minor emergency. Over the course of that day I reinstalled the system and created a new server/client communication and completely reconfigured the system. It was now working really well.
Time passes and so do software versions. Soon enough, it was time for an upgrade. Here are some of the things that I learned while upgrading a system from Symantec Antivirus to Symantec Endpoint Protection.
Installation of the server:
Overview Open up the installer and follow the prompts for your server info etc.
Detailed installation info can be found in the Installation Guide. We choose default options in almost every case. The embedded database was the best choice for this small network.
Installation of the clients:
Depending on your network situation, this should also be a simple procedure.
We tried the deployment wizard, which appeared to make everything very simple and automatic. Deploy Symantec Endpoint Protection to your client computers (using the Wizard). Alas, it was not so simple and we ran into many errors, including: Error: “No Network Provider accepted the given the network path”. From windows, we issued this command to investigate: START->RUN->’cmd’ netstat -abn. In the end, we decided to manually install SEP by creating deployment packages and saving them to a USB or network share:
I choose the following options:
How to manually uninstall Symantec Endpoint Protection Manager 11.0
Best Notification Overview
Creating notifications in the Symantec Endpoint Protection Manager
We worked on this aspect for a long time and couldn’t figure out what was wrong. We think that this is one of the weakest ‘improvements’ that Symantec made in this version of their software. First of all, there is no
Symantec Endpoint Protection Manager 11.x communication troubleshooting
I had a lot of problems getting email notifications to work for several reasons:
How to setup email alerts in the Symantec Endpoint Protection Manager more detail on the same topic
How to test the e-mail notification feature