Antivirus Packages for Clients vs Servers

Antivirus Packages for Clients vs Servers

in

Once upon a time while working as a junior Sysadmin I was taked with deploying an anti-virus on various servers.
One such server was a public fileshare.
You really out to be careful when deploying anti-virus software onto public fileshares because anti-virus policies are designed to be catch-all constructs and may be too restrictive which turned out to be the case for me and unfortunately every user in the company.
The anti-virus packaged we used, Symantec, has two general packages that you can create for your Endpoints.
One of them is a client package designed for workstations and the other is a server package designed for … servers.
At this point in my career I wasn’t very familiar with Symantec Enpoint Manager Console(SEPM) or the nuances in packages and so I installed the client package on the server which hosts the public fileshare.
It turns out that the policies in the client package are far too restrictive for a public fileshare, so at 8 in the morning we got a bunch of complaints that our user couldn’t access company files on the fileshare. The CEO even got wind of this. To make matters worse, the day before, I sent out a company wide email telling everyone that the fileshare would be down for maintinence, so everyone knew exactly who to blame.
Not good…
After panicking uninstalled Symantec on the server hosting the filshare and magically access was re-granted to everyone.
The moral of this story is that before installing any piece of software it’s important to READ THE ******* MANUAL so you don’t embarress yourself in front of everyone at your job company.