Microsoft released Forefront Endpoint Protection (FEP) 2010 on December 16th 2010. I started digging into the RTM version and so far I’m impressed.
Today we’re going to talk about the installation of FEP. If you currently have existing anti-virus software in your environment including Microsoft Forefront Client Security installing FEP will not interfere with your current products. Installing FEP installs the management parts and in no way does it install any clients or make changes to your current production environment.
- The first step is to run serversetup.exe from the CD/ISO. Since I’m using a 64-bit server I’ll be running the 64-bit version of serversetup.
- You’ll have to supply a Name and Organization.
- You’ll have to accept the software license terms. If you don’t then just give up because the Next button will be unavailable to click.
- I’m going to choose Advanced topology for this example. I currently have a lab server that is my DC, SQL with multiple instances, WSUS, and Routing and Remote Access. It’s not recommended to have all of those roles on a DC but it’s fine for a lab. The server I’m working on is my SCCM server with SCCM 2007 R3 installed.
- I’m going to check all three.
- The DB and instance is already pre-populated from the SCCM install. The name of the FEP 2010 DB is recommended or you can change it. FEPDB_SITECODE seems to be the default (SITECODE being your 3 digit SCCM site code).
- Below is what it pulled minus the password for the SQL reporting services account. In this lab environment I’m using the domain administrator for a lot of things. I don’t recommend using domain admin accounts for roles but for a lab it’s fine. If you use a domain admin account FEP setup will bark at you when you click next asking if you really want to have a domain account do this. I like how it barks at you but allows you to continue.
- Sure I want to keep my productions up to date and join the Customer Experience Improvement Program. Why wouldn’t I?
- I would like to join the Advanced SpyNet membership. Basic is the default but the more we can help Microsoft the more they can update the products and services for us since they know what is going on in the real world.
- The default location is fine and I think I have enough room.
- Now this is where serversetup will run a Prerequisite check. As you can see I have errors and it won’t let me continue. Clicking More for each detail will give you more information that will basically tell you step by step how to resolve your error(s).
- This one was simple. I had to add the .NET Framework Feature on the server I’m installing FEP on. Remember it’s my SCCM server also.
- This one was pretty simple also. I had to change the service startup type to Automatic for SQLAgent$SCCM. SQLAgent for the SCCM instance. In my lab environment it did take a few tries to get past this. I guess my lab environment is slow and it was having a problem but after a few attempts without me doing anything it went through.
- I had to dow
nload and install Microsoft Analysis 2008 Management Objects on the server I’m working with (SCCM). No reboot required.
- Here I had to install a Hotfix. No reboot required.
- After taking care of the four errors I got all green checks now!
- A text review of what will be done. BTW you can highlight it and copy it.
- YAY it’s installing!
- YAY it’s installed!
- YAY it’s telling me it’s installed and asking if it should open up the SCCM console and check for updates.
- As you can see two databases got created in the SCCM instance for FEP.
Installing FEP is pretty darn simple.