Because administrative lists exist on a per-process and per-machine basis, different groups of principals can have different sets of administrative privileges within a domain. It is often useful, however, to have the same group or user on several lists. For example, the same users will probably administer filesets and the Fileset Location Database, so they should be included on all of the lists necessary to perform operations related to such administration.
In some cases, it is also practical to include the same users on multiple lists. For example, individuals listed in the admin.bos list can issue all bos commands, including those to add members to other administrative lists. Therefore, principals added to the admin.bos list should also be granted administrative privileges on the other administrative lists.
To simplify the management of these lists, use the domain's System Control machine as the source of all administrative lists for the domain. The System Control machine runs the upserver process; the other server machines in the domain run the upclient process. The upclient process takes updates of the administrative lists from the upserver process. As a result, all of the machines in the domain share the administrative lists and, thus, share a common set of administrators. (See Part 2 of this guide and reference for more information on the upserver and upclient processes.)
More:
Maintaining Administrative Lists
Disabling DFS Authorization Checking on a Server Machine