Shulou(Shulou.com)06/02 Report--

Later notice: from next I will explain to you the importance of Active Directory active Directory and how to troubleshoot problems in daily management and operation and maintenance. As the saying goes, running an abnormal Active Directory domain environment can lead to an unhealthy Exchange environment. For the study of Microsoft technology, it is difficult to find someone who disagrees with this view. Because the Windows Active Directory infrastructure has replaced its own directories since the Exchange 2000 release, the Active Directory active Directory group has become a prerequisite for deploying Exchange mail servers to design, deploy, and manage Exchange users. In our daily operation and maintenance management, we can use various default management tools to solve Active Directory domain problems that affect Exchange, and before we gain insight into possible problems, let's first discuss how Exchange and Active Directory replicate interactively.

The Active Directory domain active catalog database is divided into several partitions (sometimes called naming contexts), each of which replicates between domain controllers and contains a variety of data. The default partition includes schema partition, domain partition, configuration partition, and application partition. First consider what Exchange data is contained in that partition.

The Active Directory schema contains definitions of object classes and attributes used in the forest. Before installing Exchange, Active Directory had no idea what an Exchange server, mailbox database, database availability group (DAG), or mailbox was because the schema did not define these objects. When the Exchange installer executes a mode update (Setup / PrepareSchema), it adds definitions of the various objects used by Exchange so that the objects become known to the directory and can be manipulated by administrative tools. When it is said that Exchange requires schema updates, it means that the Active Directory schema must be updated to allow existing objects to accept new functionality or to adapt to completely new objects.

Because the schema partition is essentially a large repository defined, it is extremely rare to encounter failures during the update process. From a troubleshooting perspective, I never found myself spending a lot of time looking at schema schema partitions unless it was possible to verify the current schema version after an update. The most common problem is Schema permissions or reachability issues encountered when trying to update.

These problems are usually due to the following:

1. Your account is a member of the Schema Admins group

two。 You can communicate with domain controllers that hold the role of architecture master FSMO

The 3.Active Directory remote server management tool is installed on the workstation running the update

A domain partition contains all objects created in a single domain and replicates only its data fields. Here you will find user objects, distribution groups, computer objects, and organizational units.

When the Exchange client (Outlook,OWA, etc.) performs a query on the address list, this is part of the Active Directory that is queried by the client. When an additional SMTP address is added to the recipient, the user object in the partition is postmarked (using the ProxyAddresses attribute).

This Exchange property is mail-enabled or mailbox-enabled when many other people are populated on Active Directory objects. Although these properties exist on all user objects, they are not populated until the user object is used in some way with Exchange.

Follow-up (2)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.