Working in a multiple Policy Server environment

In distributed environments, or deployments with a large number of users, it may be appropriate to install multiple Policy Server instances. This entails some special considerations.

• Because policy information is managed by Policy Broker, policy changes are made available to all Policy Server instances when you click Save and Deploy.
• Many global configuration settings (like risk class definitions and alerting options) are also shared between Policy Server instances.
• Configuration settings that are specific to a single Policy Server (like its Filtering Service and Network Agent connections) are stored locally by each Policy Server and not distributed.
• In order to apply time-based actions (Confirm, Quota, Password Override, or Account Override) correctly, one or more instances of State Server is required. State Server allows the timing information associated with these features to be shared, so that clients are granted exactly the Internet access than you intend (see Policy Server, Filtering Service, and State Server).