Configuring central control center management to push global rules to multiple control centers.
Environment
SMG 10.8 10.9
Resolution
Configuring a Federated Control Center Cluster:
Add an HTTPS certificte to each control center web UI (can be self-signed) if you do not already have an HTTPS certificate installed (Demo Certificate is not sufficient)
Create a certificate signing request. (Administration > Certificates > TLS and HTTPS certificates). Once the signed certificate (CA) is imported or a self-signed certificate is created, proceed to next step.
Select the certificate to be used by the control center web UI. (Administration > Control Center > Certificates)
???Import each remote control center certificate into the central control center (Administration > Certificates > TLS and HTTPS certificates OR Applications ???)
Add the role of "Central" to the central control center (Administration > Control Center > Policy Sharing > Local). Check "Configure this Control Center as the central Control Center of the Control Center cluster". (WARNING: Once you enable this option, there is no way to revert the change. Backups from this control center will only be able to be restored on a central control center)
Add the role of "Remote" to each remote control center (Administration > Control Center > Policy Sharing > Local). Check "Join the Control Center cluster as a remote Control Center".
Add each remote control center into the central control center (Administration > Control Center > Policy Sharing > Remote)
<IMAGE>
Add a Description for the remote control center
Additional Information
Once the role of "central" or "remote" is applied to a control center, the backups from that control center can only be restored on a control center with the same role.
Global rules are only for content rules and can only be applied to the Default group.
When a control center is promoted to the role of "central", you cannot revert the change.