Export (0) Print
Expand All

Planning processor and memory configurations

Published: December 16, 2009

Applies To: Forefront Client Security

There are three main items to consider when planning hardware requirements for Client Security: processor choice, memory requirements, and disk storage selection. This topic discusses processor and memory options. For more information about disk storage selection, see Tuning Client Security database components in the Client Security Performance and Scalability Guide (http://go.microsoft.com/fwlink/?LinkId=89667).

Processor

Processor configurations are determined by the number of managed computers in the Client Security deployment, as well as the Client Security components deployed to a server. In general, the more managed computers in a Client Security deployment, the more processors per component are needed.

For up to 3,000 managed computers, with all Client Security components installed on a single server, the processor recommendation is for two 2 GHz or faster processors.

When there are between 3,000 and 5,000 managed computers, processor recommendations are as follows.

 

Components on server Processor recommendation

Collection server, collection database, reporting server, and management server

Four 2 GHz or faster

Reporting database

Two 2 GHz or faster

Distribution server

One 2 GHz or faster

When managing between 5,000 and 10,000 computers, the processor recommendations for the Client Security components are as follows.

 

Components on server Processor recommendation

Collection server and collection database

Four 2 GHz or faster

Reporting server and reporting database

Four 2 GHz or faster

Management server

Two 2 GHz or faster

Distribution server

Two 2 GHz or faster

ImportantImportant:
The server components of Client Security are not supported on 64-bit systems.

When selecting the processors for your Client Security servers, you must consider the topology you are using in your organization. For more information about Client Security topologies, see Choosing your topology.

Memory

All of the components of Client Security are heavily dependent on the available memory on the server on which they are running. As with processors, in general, the more managed computers in a Client Security deployment, the more physical memory, or RAM, the Client Security components will need. However, there are additional factors for the amount of RAM a server will need for a specified set of Client Security components:

  • Number and frequency of events and alerts from managed computers

  • Topology deployed

  • Additional non-Client Security services and applications running on a server

For more information about Client Security events and alerts from managed computers, see "Database growth factors" in Database sizing in the Client Security Performance and Scalability Guide (http://go.microsoft.com/fwlink/?LinkID=89813).

When sizing the perspective Client Security servers, keep in mind that the most heavily RAM-dependent servers are typically the collection and reporting servers, as well as the servers on which their databases are installed (collection database and reporting database).

When planning the Client Security deployment, consider the following RAM recommendations.

With all Client Security server components on a single server, and up to 1,000 managed computers, the RAM recommendation is 2 GB. For more than 1,000 managed computers, up to 3,000, the recommendation increases to 4 GB.

The following table outlines the RAM recommendations for 3,000 to 5,000 managed computers.

 

Components on server RAM recommendation

Management server, collection server, collection database, and reporting server

4 GB

Reporting database

4 GB

Distribution server

1 GB

The following table outlines the RAM recommendations for 5,000 to 10,000 managed computers.

 

Components on server RAM recommendation

Collection server and collection database

4 GB

Reporting server and reporting database

4 GB

Management server

2 GB

Distribution server

2 GB

For more information about memory options for SQL Server 2005 and Client Security, see "DTS transactions" and "Memory tuning" in Database sizing in the Client Security Performance and Scalability Guide (http://go.microsoft.com/fwlink/?LinkID=89813).

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