As with single-site deployment, collect relevant network information and identify how this information relates to deploying Control Manager to your multiple sites.
A multi-site deployment using multiple Enterprise Control Manager parent server and mixed child servers.
The following are required:
Group managed products or child servers
Consider the following when you group managed products and child servers:
Company network and security policies
If different access and sharing rights apply to the company network, group managed products and child servers according to company network and security policies.
Organization and function
Group managed products and child servers according to the company's organizational and functional division. For example, have two Control Manager servers that manage the production and testing groups.
Geographical location
Use geographical location as a grouping criterion if the location of the managed products and child servers affects the communication between the Control Manager server and its managed products or child servers.
Administrative responsibility
Group managed products and child servers according to system or security personnel assigned to them. This allows group configuration.
Determine the number of sites
Determine how many sites your Control Manager deployment will cover. You will need this information to determine the number of servers you need to install, as well as where you need to install the servers.
You may get this information from your organization�s WAN or LAN topology charts.
Determine the number of managed products and child servers
You also need to know the total number of managed products and child servers Control Manager server will be managing. Trend Micro recommends gathering managed product and child server population data per site. If you cannot get this information, even rough estimates will be helpful. You will need this information to determine how many servers you need to install.
Plan for network traffic
Control Manager generates network traffic when the server and managed products/child servers communicate. Plan the Control Manager network traffic to minimize its impact on an organization's network.
These are the sources of Control Manager-related network traffic:
Control Manager commands
Logs
Communicator schedule
Managed product registration to Control Manager server
Control Manager servers, by default, contain all the product profiles available during the Control Manager release. However, if you register a new version of a product to Control Manager, a version that does not correspond to any existing product profiles, the new product will upload its profile to the Control Manager server.
Child server registration to Control Manager parent server
Downloading and deploying updates
Plan for an optimal server-managed products/cascading structure ratio
When deploying Control Manager across the WAN, the Control Manager server in the main office administers child servers and managed products in the remote office. If you will have managed products or child servers in the remote office reporting to the server in the main office over the WAN, you need to consider the diversity of the network bandwidth in your WAN environment. Having different network bandwidth in your WAN environment can be beneficial to Control Manager. If you have managed products or child servers both on the LAN and across the WAN reporting to the same server, reporting is staggered naturally—the server prioritizes those with the faster connection, which, in almost all cases, are the managed products or child servers on the LAN.
Use the recommended system requirements as a guide in determining the CPU and RAM requirements for your Control Manager network.
Designate the Standard Control Manager server or Enterprise Control Manager server
Decide where to install the Control Manager server
Once you know the number of clients you have and the number of servers you need to install, find out where to install your Control Manager servers. Decide if you need to install all your servers in the central office or if you need to install some of them in remote offices.
Place the servers strategically in certain segments of your environment to speed up communication and optimize managed product and child server management:
Central office
A central office is the facility where majority of the managed products and child servers in the organization are located. The central office is sometimes referred to as "headquarters", "corporate office", or "corporate headquarters". A central office can have other smaller offices or branches (referred to as �remote offices� in this guide) in other locations.
Trend Micro recommends installing a parent server in the central office.
Remote office
A remote office is defined as any small professional office that is part of a larger organization and has a WAN connection to the central office. If you have managed products and child servers in a remote office that report to the server in the central office, they may encounter difficulties connecting to the server. Bandwidth limitations may prevent proper communication to and from the Control Manager server.
The network bandwidth between your central office and remote office may be sufficient for routine client-server communication, such as notifications for updated configuration settings and status reporting, but insufficient for deployment and other tasks.
Given the uniqueness of each network, exercise judgment as to how many Control Manager servers would be optimal for you.
Deploy Control Manager servers in a number of different locations, including the DMZ or the private network. Position the Control Manager server in the DMZ on the public network if you want to administer managed product or child servers and access the Control Manager management console using Internet Explorer over the Internet.