Tuesday 3 May 2016

How to Managing Site Configuration

Overview   A site is a logical grouping of Exchange servers. The purpose of the grouping is to create a transparent messaging environment (users do not need to know on which server a resource is located). The properties of a site are the same type as with the organization object, the main one being permissions. Permissions can be assigned to a particular administrator allowing that administrator to create or modify child objects (like mailboxes) in the site. The difference between permissions granted at the organization object versus the site object is the context (i.e., the location in the hierarchy). Permissions granted at a site only apply to objects in the site, not to other sites and not to the organization.

Introduction to Site Configuration Container

1.         Configuration            This container object holds seven additional container objects that pertain to numerous aspects of a site configuration. There are also four non-container objects under Configuration. These eleven objects are listed here :-

            (a)        Add-Ins (container object)
            (b)        Addressing (container object)
            (c)        Connections (container object)
            (d)       Directory Replication (container object)
            (e)        Monitors (container object)
            (f)        Protocols (container object)
            (g)        Server (container object)
            (h)        DS Site Configuration
            (i)         Information Store Site Configuration
            (j)         MTA Site Configuration
            (k)        Site Addressing
            (l)         Recipients These are objects to which Exchange users can send messages. Recipient objects include-

            (i)         Mailboxes   A location from which messages can be received, sent,             stored, etc. also stores other types of data.

            (ii)        Distribution List    A grouping of individual recipients.
            (iii)       Public Folder    A storage container for group access.
            (iv)       Custom Recipients   E-mail addresses that represent a foreign mail             system address.



6.         Configuring Connection Container.

(a)    The configuration container has at least two property pages, the general page and the Service Account Password page (there are three pages if the Permissions page is present). These property pages are assessed by highlighting the Configuration container, then using the File menu, Properties option. The Service Account Password page is used to change the password used by the site service account. For example, suppose someone used User Manager for Domains to change the password of the site service account. The next time the Exchange server is stopped and restarted, none of the Exchange services will start because they will be using the old password. The Most efficient way to solve this problem is to use the Service Account Password of the site service account. To perform that procedure, you must be able to run the Microsoft Exchange Administrator program, and to run that program the system Attendant and Directory Service must be running.

(b)    That would be accomplished by manually starting those two service through Control Panel/Services and using the new password in the Startup parameters. Then the Exchange Administrator program can be run and the Service Account Password page accessed in order to change the password for the remaining Exchange services. The rest of the Site Management section will cover the objects under the Configuration container.

7.         Configuring Directory Replication Container.

(a)    All Exchange servers in a site contain a complete copy of the directory information of that site. This is accomplished by automatic directory replication between servers of a site. When an Exchange object, for example a mailbox, is created on a particular Exchange server, that mailbox information is automatically copied to all the other servers in that site. This is an important factor in creating a transparent messaging environment. Users see all site recipients in their site address book. And while users do not need to know the physical location of a recipient, each Exchange server can route a message to the correct server because it has a copy of the site directory which contains this information.

(b)    The Directory Replication Connector uses an existing messaging connector to send directory information to a remote site.

(c)        There can also be directory replication between sites. This is not an automatic process, and must be configured by an administrator. This ability allows administrators to decide what resources to share with other sites. But directory replication between sites can be used to create an enterprise messaging environment.

(d)       The four primary steps to setting up directory replication between sites are listed here.

(i)         Configure the messaging connector to be used for inter site directory replication. 

(ii)        Install a Directory Replication Connector for both sites. 

(iii)       Identify the directory replication bridgehead at each site that will be responsible for transferring directory updates. 

(iv)       Configure a replication schedule to determine how often directory updates will occur.


No comments:

Post a Comment