If you set up one TSM server as a configuration manager, you can distribute policy to other TSM servers. To distribute policy, you associate a policy domain with a profile. Managed servers that subscribe to the profile then receive the following definitions:
The names of client nodes and client-schedule associations are not distributed. The ACTIVE policy set is also not distributed.
The distributed policy becomes managed objects (policy domain, policy sets, management classes, and so on) defined in the database of each managed server. To use the managed policy, you must activate a policy set on each managed server. If storage pools specified as destinations in the policy do not exist on the managed server, you receive messages pointing out the problem when you activate the policy set. You can create new storage pools to match the names in the policy set, or you can rename existing storage pools.
On the managed server you also must associate client nodes with the managed policy domain and associate client nodes with schedules.
See Setting Up an Enterprise Configuration for details.