Summary


In previous versions of Exchange Server, the concept of a site was used to define both the physical routing boundaries of a group of well-connected servers and the administrative boundaries within an organization. In Exchange Server 2003, sites have been replaced by administrative groups, which are objects logically grouped together for permissions management, and routing groups, which are physical groupings of Exchange servers used to define routing boundaries.

The use of both types of groups depends on whether your organization is running in mixed mode or native mode. Mixed mode allows Exchange Server 2003 servers and servers running earlier versions of Exchange to coexist in the same organization. It allows this interoperability between versions by limiting functionality to features that both products share.

Microsoft defines three basic administrative models: centralized, decentralized, and mixed.

  • In the centralized model, one administrator or group of administrators maintains complete control over an entire Exchange organization. This can be done with one administrative group or a few administrative groups created to make certain functions earlier.

  • The decentralized model is typically used to define administrative boundaries along real geographical or departmental boundaries. Each location would have its own administrators and its own administrative group.

  • The mixed model is really a catchall model for any other ways you can think of to use administrative groups. It is useful for when you do not necessarily want the tight control of the centralized model and the strict geographic division of the decentralized model is not appropriate.

By default, Exchange Server 2003 is configured with a single administrative group that is named First Administrative Group. You can add new administrative groups, name them what you want, and then create Public Folder, Routing Group, and Policy containers inside the new group. Once these are created, you can move resources from other groups into the new group.

A routing group is a collection of Exchange servers that have full-time , full-mesh, reliable connections between each and every server. Exchange servers in the same routing group must also belong to the same Active Directory forest.

You create routing groups in System Manager in much the same way as you create administrative groups. When created, they are simple containers waiting for you to fill them with servers.

Once your routing groups are defined, you must connect them together using one or more of three types of connectors. The Routing Group Connector (RGC) is the main connector used to connect routing groups and is the simplest to configure. It uses SMTP as its default transport mechanism but may also use a Remote Procedure Call (RPC) if the situation requires it. The SMTP Connector is a bit more involved to set up than the RGC and sports some different features. It is mainly used to connect routing groups where you want to force SMTP to be used for the transport mechanism. The X.400 Connector can be used to connect routing groups and to connect to a foreign system.




MCSA[s]MCSE
MCSA[s]MCSE
ISBN: 735621527
EAN: N/A
Year: 2004
Pages: 160

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net