A few tips on installing Microsoft Forefront Client Security
We decided to try out Microsoft Forefront Client Security, since we get free licenses, and it’s time to end the hodgepdge of third-party antivirus apps we have. Once again, Microsoft has proven to me “the Linux lesson”: just because the software license is free, does not mean that my time working with a cranky system is cheaper than buying something better. In this case, it took me over a week to get it installed! Here are a few of the pitfalls I ran into along the way:
- It will not install on Windows 2008 R2.
- It will not install on 64 bit Windows.
- It is not compatable with SQL Server 2008; only SQL Server 2005.
- SSRS (SQL Server Reporting Services) is still a pain in the neck to install and get working right. On Windows 2008, you need to go into the IIS Management Console, select the “ReportServer” application for the installation, click “Handler Mappings” and then “Edit Feature Permissions” and enable “Script” and “Execute”. This is the hidden, undocumented trick.
- The “Distribution Server” will not install on 64 bit Windows either, but that’s OK if you have an existing WSUS 3.X install, since that can handle the definition updates. You’ll need to manually deploy (or use SCCM) the client yourself in that scenario, though.
Yes, I basically tried every permutation of Windows 2008, 32 and 64 bit, and SQL Server (the requirements documentation is not very clear on most of this, other than the 32 bit requirement which I overlooked) until I finally got this thing installed.
I haven’t gotten to use it yet, but given the installation nightmare, I already strongly prefer TrendMicro which I had great success with a few years ago.
J.Ja