Export (0) Print
Expand All
1 out of 3 rated this helpful - Rate this topic

Installing on a standalone server by using the Setup Wizard

 

Applies to: Forefront Protection for Exchange

Topic Last Modified: 2010-05-20

To run the Microsoft Forefront Protection 2010 for Exchange Server (FPE) installation program on Exchange Server 2007, you must have Local Admin privileges. For information about the security credentials required when installing FPE on Exchange Server 2010, see Security credentials required for installing on Exchange Server 2010.

To install on a standalone server
  1. Double-click the forefrontexchangesetup.exe file in order to launch the Setup Wizard.

  2. Read the license on the License Agreement page. Click the I agree to the terms of the license agreement and privacy statement check box, and then click Next.

    noteNote:
    If you do not have the required prerequisites to install FPE, you are given instructions about how to obtain the missing components. You do not need to exit the installation program while installing the components.
  3. If the Service Restart page appears, review the list of services about to be restarted, and then click Next. This screen only appears if a service restart may be required in order for FPE to install.

  4. On the Installation Folders page, specify the following information and then click Next:

    • In the Program Folder box, either accept the default program folder for the product, or click Browse in order to select a different one. This is the folder into which executable files are placed.
    • In the Data Folder box, either accept the default data folder for the product, or click Browse in order to select a different one. This is the folder into which data files, such as quarantined files and archived files, are placed. It is recommended that you select a drive that has sufficient space to store a large amount of files.
      CautionCaution:
      Do not specify a data folder location that is at the root of any volume where the virtual memory paging file is set, for example C:\. This causes the installation program to fail. You should also not specify the same location for the program folder and the data folder.
  5. If you use a proxy server for engine and definition updates, on the Proxy Information page, specify the following information and then click Next:

    1. Select the Use Proxy Settings check box.
    2. Type the Name or IP address of the proxy server.
    3. Type the Port of the proxy server. The default value is 80.
    4. If your proxy server requires a user name and password, type these values in the Username and Password fields.
  6. On the Antispam Configuration page, select to Enable Forefront Protection 2010 for Exchange Server antispam now or to Enable Forefront Protection 2010 for Exchange Server antispam later, and then click Next.

    If you plan to enable antispam on this server, it is strongly recommended that you enable FPE antispam now. Until you do so, any changes that you make to the antispam settings with the user interface will not work. If you want to enable the FPE antispam component later, this can be done by using the Forefront Protection 2010 for Exchange Server Administrator Console (for more information, see Enabling antispam protection) or by typing the following Windows PowerShell command from the Forefront Management Shell: Set-FseSpamFiltering -Enabled $true (for more information, see the Windows PowerShell help).

  7. In the Use Microsoft Update to help keep your computer secure and up-to-date dialog box, select whether you want to Use Microsoft Update to check for updates (recommended). When you opt-in to Microsoft Update, updates are enabled for all Microsoft products on the server. If the update schedule is already configured, the settings are left unchanged. If the update schedule is not already configured, it is enabled to download and notify you of product updates.

  8. On the Do you want to join the Customer Experience Improvement Program page, indicate whether you want to join the Customer Experience Improvement Program, and then click Next.

    The Customer Experience Improvement Program collects information about computer hardware and how you use FPE. This information helps Microsoft identify which FPE features to improve. If you choose to participate in this program, nothing else is required on your part. All information gathered is confidential and is not used to identify or contact you. Note that if you do not join this program now, you can elect to do so at a later date by following the steps in Joining the Customer Experience Improvement Program.

  9. On the Confirm Settings page, review the data presented to you. If any changes need to be made, click the back icon in order to navigate to the screen to be changed. Otherwise, click Next in order to begin the installation. A progress bar indicates that the files are being copied.

  10. On the Installation results page, you can optionally select to launch the Forefront Online Protection for Exchange gateway installation program. Select the Launch the Forefront Online Protection for Exchange gateway installation program check box, and then click Finish. For more information about installing this product, see Installing the Forefront Online Protection for Exchange Gateway.

  11. After you have installed FPE, it is recommended that you view the Release Notes file and perform the configuration steps described in Performing your initial configuration.

  • After a fresh installation, new definition files must be downloaded in order to ensure the most up-to-date protection. By default, an hourly check for updates for each licensed engine is scheduled. These updates start five minutes after FPE services are started. If a proxy server is being used for engine updates, these scheduled updates will fail until all the proxy server information has been entered. If you did not enter this information during installation, use the Forefront Protection 2010 for Exchange Server Administrator Console and enter it in the Global Settings - Engine Options pane. Then, immediately update each scan engine by clicking Update All Engines Now in the Actions section.
    noteNote:
    • You should successfully update at least one engine before the installation is considered complete.
    • Until all the licensed engines have been successfully downloaded, errors may appear in the event log. These errors include "Could not create mapper object".
  • To verify that FPE has been correctly installed with default protection enabled, use Windows Task Manager. You should see the following processes running after a default installation:
    • On a server that contains a Mailbox role, there should be four FSCRealtimeScanner.exe processes running, and there should be one FSCScheduledScanner.exe process running.
    • On a server that includes a Transport role (such as a Hub Transport, Edge, or Mailbox/Hub Transport server), there should be four FSCTransportScanner.exe processes running.
  • During the first run after installation, FPE automatically selects a Client Access Server (CAS) (provided that one is available), which may not be the optimal server for your environment. If you are using Exchange Server 2010 and a CAS is not available, the on-demand scan will not work. (For information about adding a CAS to your Exchange environment, see your Exchange Server 2010 documentation.) You can change the selected CAS by using the Forefront Protection 2010 for Exchange Server Administrator Console (for details, see Configuring the on-demand scan) or by running the following Windows PowerShell command from the Forefront Management Shell: Set-FseOnDemandScan
  • If you have Microsoft Office Manager 2005 or Microsoft System Center Operations Manager 2007 agents installed, you might see services start unexpectedly after the product has been installed. These agents are stopped (disabled) during an installation and automatically re-enabled when the process has completed. This is normal behavior.
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.