Free Computer Repair Service

In the process of select security tools, performance and security need to concern. 
How to improve Forefront performance by optimize the topology? However, according to the my experience, performance is not only related with the product itself, and even closely related with the deployment.If the way is wrong, the performance will be greatly reduced. the topological structure of the Forefront directly related to its running speed. Forefront support for single-server topology, two-server topology, three-server topology and so on. The scope and performance of each topology supported is different. Experienced engineers of forefront recommended topology based on the corporate network. In this article I will analysis several topologies Forefront supported, to help readers to make a reasonable choice.

Single-server topology apply to small-scale network

Single-server topology refers to the various components of Forefront server are installed on a single server.For Forefront single-server topologies is the smallest topology which supported. Typically, single-server topology is mainly used in small-scale networks.If the client is little, the performance of this topology is optimal. However, the number of clients to reach a certain value, the line may occur the phenomenon of line up, competition for resources, thus affecting network performance.
Although single-server topology can support up to 3,000 clients. But this is only a theoretical data.I have done a test before, if the client more than 500 case, we can clearly feel the low efficiency. Therefore I suggest that if corporate have more clients, or need to deal with larger data traffic, it’s better to take two-server topology or three server topology.
If the business have financial constraints, and must use a single server topology, then it’s better to improve the server configuration. Such as memory used should be more than 4GB; or separate data files, operating system, the log file; or use disk array with better performance etc. These measures will help improve server performance.

Separating Forefront server topology into two-servers

In the single-server topology, Forefront server needs to complete the daily management, information collection, report generation, distribution strategy and many other tasks. When the number of the client much more, these tasks are concentrated in a single server, obviously the pressure is relatively large. In these tasks, distributing work occupied more resources, such as need larger-bandwidth and CPU, memory and other resources. In the two-server topology, the distribution of work will be placed in a separate distribution server to complete.
In practice, Forefront system engineers can monitor server performance. If you find that “distribution” operation take more resource utilization, and even has affected the performance of the entire server. Then consider to separate the server, so a separated server to be responsible for the distribution of Forefront operations. Note in the double-server topology, and database are not separated from the server. This is mainly because for SMEs Forefront data record is not great. Database is not a performance bottleneck. Therefore, in the two-server topology structure, the database is not independent.
Of course, if engineers found that the database has become a performance bottleneck in the follow-up performance testing, such as reports showing slower or the operating time of data conversion services can not accept, you will need to consider separate database from server. Now you needs to use the three-server topology.
The biggest difference of three-server topology and dual-server topology is that separate the database server from the ForeFront server.It should be note that, in general, there are two Forefront Server database, the collection database server and reporting database server. Independent only is the reporting database server. General, the collection database placed in Forefront server, which will help improve data storage performance.
If an enterprise has special requirements, then the number of clients super-large, reaching more than 5,000, you can use more complex topology, such as deployed the four operations (management, collection, distribution, reporting) of the ForeFront in different server.

When using three-server topology, I have the following two suggestions to improve Forefront performance by  optimize  the topology.

1, when using three-server topology, they must first need to confirm whether the current ForeFront’s performance caused by the database in the end. Even if the number of clients are more, in the beginning data will not be great when using ForeFront. In other words, the reporting database will not be a performance bottleneck.If independent the reporting database server in blind, most likely not achieve the desired effects. when assessing whether need to separate database server, there are two main indicators to look at. Such as to look at the speed of report generation and data forwarding operation time.If two indicators all are not very good, then the database server may be considered independent. If these two indicators are good, then this operation is not table to finally solve the problem. Because the administrators did not find the crux of the problem.

2, If you really need a three-server topology, because the task of three server is different, configurations requirements is different. From a performance view, for the statements of the database server, the best disk array requires the ability to advance.The case, which can improve data access performance, but also to improve their security (usually disk arrays have a data checking). As for the distribution of servers, it’s better to place the operating system, data files, log files in different partitions when installing. Although these measures are modest, but can be significantly improved operating performance of ForeFront.

For ordinary enterprise, three-server topology is sufficient. As long as the server’s configuration and deployment are more reasonable, then three-server topology to support three or four thousand clients is not a problem. Finally it’s need to be reminded that in addition to single-server topology, other topology in advance needs to achieve the organizational structure of WSUS. In other words, if place a service of the management, collection, distribution, reporting services on a separate server, you must have WSUS support structure.