How-To : Install A One Server Forefront Client Security Topology
Some time ago I posted on my blog that I’m running my whole test-infrastructure on a Windows Server 2008 Enterprise Edition with Hyper-V. Right now I don’t have a anti-malware and anti-virus solution solution implemented, so I’m going to get Forefront Client Security running on my Forefront Virtual Machine.
I’m going for the one Server topology, so all the Forefront roles are installed on one server. My initial idea was to install the FCS 1 Server Topology on Windows Server 2008. Too bad MOM 2005 won’t install on Windows Server 2008 so I had to install it on Windows Server 2003. When it’s possible to install FCS on Server 2008 I will let you guys know! (If you have it running please let me know too 
)
Click here to read the How-To
Server specs :
Hyper-V Virtual Machine
Core2Duo E6600
2048 MB Memory
127 GB Harddisk
Forefront Roles to be installed
- Management Server
- Collection Server
- Collection Database
- Reporting server and reporting database
- Distribution Server
Installing Prerequisites for Forefront Client Security
I’m assuming that you know how to install Windows Server 2003 before you start installing Forefront, so I’m not telling you how you have to do it. I used Windows Server 2003 R2 SP2 for the installation.
Before you can install Forefront Client Security you have to install the following software prerequisites :
- Windows Components
- Internet Information Services
- ASP.NET
- Microsoft .NET Framework 2.0
- I used SQL Server 2005 Standard x868 edition
- You need at least SP1, but I installed SP2
- Download
- Step-by-Step Guide
- Before you install Forefront you have to run an initial WSUS sync.
Before you start the installation you will have to create a domain user account which you can use during the Forefront Setup.
Installing Microsoft Forefront Client Security
- Start the setup by clicking the Run the setup wizard on the autorun page
- Fill out the form with your name and organization and click Next
- Select I accept the terms in the license agreement and click Next
- Select all the components and click Next
- You can leave the Collection server and Management group name default. Use the domain account you created before at the DAS account info and click Next
- Keep the Collection database and Database size default. The Re-use the DAS account for the reporting account checkbox can stay checked (default) and click Next
- Keep the Reporting database and Database size default. The Re-use the DAS account for the reporting account checkbox can stay checked (default) and click Next
- Keep the Reporting server and URLs for reports default and click Next
- Keep the DAS account checkbox checked (default) at the Action account page
- Keep the default installation location (C:\Program Files| and click Next
- On the Verifying Settings and Requirements page everything should be Successful (except my verifying hardware requirements, it has a Warning status). Just click Next
- The installation is starting
- When the installation is finished Forefront has been installed
Related posts:
- None Found
Posted in View Comments to “How-To : Install A One Server Forefront Client Security Topology”
Leave a Reply
|
|
|
Nice thanks!
My installation keeps erroring out when it installs the collection database. Followed your instructions to the letter. Any idea why this is happening?
I have installed FF on Windows 2003 (32 bit). Everything is running on Hyper-V (8 cores + 24 GB memory) with a lot of other VMs, mostly running Windows Server 2008. I would like to try install FF Client Security on Windows Server 2008 64 bit. Can’t find out if this is supported or not. Any Idea?
BTW ForeFront Client Security reports “Updates Available” but when I click download, I can only select items I want to download, but I cant find any way to start the download.
Cheers
Ulf Holt
Excellent explanation, with all relevant links to items that must be downloaded first – Thanks, you've saved me hours of work!!! Peter
You explain very clearly. It's easy to understand.
Hi, I found this and it is very helpful. At the end it says “Before you can use Forefront you have to configure some more things, that will be discussed next week!”, but I can’t find the later article. Also, it says “Before you start the installation you will have to create a domain user account which you can use during the Forefront Setup.” How would I do that? Thanks!
Ehh…I think I forgot to add the follow-up article back in 2008. Too bad I don’t have the info available anymore, so I deleted the last line.
About the domain user. Just add a domain account on a current Windows Server before you start installing Forefront.
What kind of errors do you get?
As far as I know Forefront Client Security (the management part) can’t be installed on a 64-bit Windows Server 2008 machine. You CAN install the Client part (which you also install on your clients) on the Windows Server 2008 64-bit.
In normal English :You can’t install the FCS Server Roles (Management Server, Reporting Server, Distribution Server) on Windows Server 2008 (not on 32-bit and not on 64-bit), but you CAN install FCS Client on Windows Server 2008 (32-bit and 64-bit)