Export (0) Print
Expand All

Installing a two-server topology on Windows Server 2008

Published: December 16, 2009

Applies To: Forefront Client Security

This topic gives an overview about how to install Client Security on a two-server topology on Windows Server 2008.

Important   If you are installing multiple Client Security deployments, you must use unique computer names for each collection database server and reporting database server, as well as unique Management group names. Unique names allow you to use the Client Security Enterprise Manager tool to aggregate reporting and to manage your Client Security environment from a single Client Security console.

Installing the software prerequisites

It is highly recommended that you install the software prerequisites in exactly the order shown in the following table.

 

Computer Task Steps

Client Security server (management, collection, and reporting server)

Install software prerequisites.

Verify that all critical security and computer updates have been installed, and then begin installing the software prerequisites.

Important

Install Microsoft .NET Framework 1.1 with SP1.

Install .NET Framework 1.1 from Microsoft .NET Framework Version 1.1 Redistributable Package (http://go.microsoft.com/fwlink/?LinkId=126621).

Install .NET Framework 1.1 SP1 from Microsoft .NET Framework 1.1 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=126622).

 

Install .NET Framework 3.0.

Use Server Manager in Windows Server 2008 in order to install .NET Framework 3.0. For more information, see Server Manager (http://go.microsoft.com/fwlink/?LinkId=126624).

 

Install IIS and ASP.NET

Use Server Manager in Windows Server 2008 in order to install IIS and ASP.NET. For more information, see Installing IIS 7.0 on Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=126625).

In the Add Roles Wizard, make sure you install the following role services:

  • Static Content

  • Default Document

  • HTTP Redirection

  • Directory Browsing

  • ASP.NET

  • ISAPI Extension

  • ISAPI Filters

  • Windows Authentication

  • IIS Metabase

  • IIS 6 WMI

Install SQL Server 2005 with SP2.

When installing SQL Server 2005, make sure to do the following:

  • Install the following components: Database Services, Reporting Services, Integration Services, and Workstation components.

  • Use a domain user or network service account for the SQL Server and SQL Server Agent service accounts. It is recommended that you use a domain user account. Have the SQL Server Agent service start automatically.

Install GPMC with SP1.

Use Server Manager in Windows Server 2008 in order to install GPMC. For more information, see "Appendix B: Resources for Learning About Group Policy for Windows Server 2008" in Installing GPMC on a server running Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=126626).

Add the Client Security server site to the Local intranet zone in Windows Internet Explorer®.

In Internet Explorer, on the Tools menu, click Internet Options. On the Security tab, add the reporting server site to the Local intranet zone.

Distribution server

Install software prerequisites.

Verify that all critical security and computer updates have been installed, and then begin installing the software prerequisites.

 

Install .NET Framework 3.0.

Use Server Manager in Windows Server 2008 in order to install .NET Framework 3.0. For more information, see Server Manager (http://go.microsoft.com/fwlink/?LinkId=126624).

 

Install IIS and ASP.NET

Use Server Manager in Windows Server 2008 in order to install IIS and ASP.NET. For more information, see Installing IIS 7.0 on Windows Server 2008 (http://go.microsoft.com/fwlink/?LinkId=126625).

In the Add Roles Wizard, make sure you install the following role services:

  • Static Content

  • Default Document

  • HTTP Redirection

  • Directory Browsing

  • ASP.NET

  • ISAPI Extension

  • ISAPI Filters

  • Windows Authentication

  • IIS Metabase

  • IIS 6 WMI

 

Install, configure, and synchronize Windows Server Update Services (WSUS) with SP1.

To install, configure, and synchronize WSUS 3.0 with SP1, see "Step-by-Step Guide to Getting Started" with Microsoft Windows Server Update Services 3.0 (http://go.microsoft.com/fwlink/?LinkId=126627).

When configuring WSUS, make sure you have configured automatic updates so that your client computers receive updates. In particular, make sure you have configured the following:

  • Synchronize Product: Forefront Client Security

  • Synchronize Classification: Definition Updates

  • Create an auto-approval rule for Definition Updates

Verifying a successful installation of the software prerequisites

Before continuing, it is recommended that you verify that the software prerequisites have been successfully installed and configured, as described in the following table. For detailed instructions, see Verifying the software prerequisites for a one-server topology.

 

Computer Task Steps

Client Security server

Verify and record the reporting server URL.

In Internet Explorer, on the Client Security server, verify that you can connect to the reporting server URL. Record the URL, because you will need to provide it when installing Client Security.

Installing Client Security for a two-server topology

In the Setup wizard, you will provide server names, SQL Server instances, and service accounts you have already set up. In addition, you must specify the following:

  • Size of the databases   Make sure the size does not exceed the space on your server.

  • Management group name   You can enter the name you want or use the default value (ForefrontClientSecurity). Record the name that you enter, because you will need to provide it when configuring Client Security.

For detailed instructions, see Installing Client Security on a two-server topology.

 

Computer Task Steps

Client Security server

Install Client Security.

Run the Server Setup wizard.

When the Program Compatibility Assistant dialog box appears, you can dismiss it.

On the Component Installation page, select all the check boxes except the Distribution server check box.

Complete the steps in the wizard.

 

Install Client Security SP1.

To install Client Security SP1, connect the appropriate server to Microsoft Update or to WSUS. For detailed instructions on how to install Client Security SP1, see Problems and update scenarios that are addressed in Forefront Client Security Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=126628).

noteNote:
This upgrade is only supported for Client Security server components; do not install it on your client computers.

Configuring Client Security for a two-server topology

After installing Client Security, you must configure it by following the steps in the following table. While completing the Configuration wizard, you will provide server names, SQL Server instances, service accounts, and the management group name you have already set up.

For detailed instructions, see Configuring Client Security on a one-server topology.

 

Computer Task Steps

Client Security server

Configure Client Security.

Open the Microsoft Forefront Client Security Console and run the Configuration wizard.

Complete the steps in the wizard.

All computers

Grant permissions to service accounts.

It is highly recommended that you follow the detailed instructions in Configuring Client Security on a one-server topology.

Verifying your Client Security installation

To verify a successful installation of Client Security and a successful deployment of the client components to the client computers, follow the steps described in the following table. For more information, see Verifying the installation of Client Security on a one-server topology.

 

Computer Task Steps

Client Security server

Open the Client Security console.

Make sure you can view all of the data in the console, including the 14-day History chart.

Browse the reports.

Make sure you can view all of the data in the reports.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft