Do not set permissions on Exchange objects using Windows Server 2003 MMC snap-ins, such as the Active Directory Sites and Services or Active Directory Users and Computers. Important When setting permissions on Exchange objects, use Exchange System Manager. Inherited permissions are convenient because you do not have to set the permissions for every object in your Exchange organization manually. For example, the permissions that you apply to a particular server are inherited by the objects that the server contains, such as the public folder and mailbox stores on that server. Permissions in Exchange are inherited by default. When you look at an object's permissions, Active Directory permissions appear first in the list, followed by Exchange extended permissions. Examples of extended Exchange permissions are Create public folder and View Information Store status. Examples of Active Directory permissions are Read, Write, and List contents. ![]() For these objects, Exchange uses and extends Active Directory permissions. ![]() These objects include public folder trees, address lists, mailbox stores, protocols, and servers. You can set permissions on some Exchange objects individually. Permissions control access to Exchange objects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |