- Replication between Exchange 2000 and Exchange 5.5 servers. - Replicating Permissions From Exchange 5.5 to Exchange 2000. - Exchange 5.5 servers see multiple Public Stores on an Exchange 2000 server. - In Exchange 5.5 there was only one TLH called “Public Folders”. - In Exchange 5.5 the Public Folder Database was stored in the pub.mdb file (and the Information Store transaction logs). - In Exchange 5.5 all Public Folders were mail enabled (by default their directory entries were hidden and created in the Recipients container).. - This has implications for folder replication via an Exchange 5.5 IMC. - This applies equally to Exchange 5.5 ". - Exchange 5.5 replication as it does to Exchange 2000 ". - Exchange 5.5 replication. - This section describes the changes in Folder Permissions between Exchange 5.5 and Exchange 2000. - This is especially important during migration and co- existence between Exchange 5.5 and Exchange 2000.. - This can be especially dangerous in mixed Exchange 5.5 and Exchange 2000 environments. - When an Exchange 5.5 folder is replicated to Exchange 2000.. - If the replication message is not being addressed to any Exchange 5.5 servers (i.e. - If a replication message sent from an Exchange 2000 server has Exchange 5.5 Public Stores on its replica list, ptagACLData &. - ptagExtendedACLData will be calculated and included in the replication update (as an Exchange 5.5 server does not understand ptagNTSD).. - From Exchange 5.5 to Exchange 2000. - Exchange 2000 replicating when Exchange 5.5 stores exist on the replica list.. - Exchange 5.5 replicating out. - Therefore, Exchange 5.5 servers will get this property set on their copies of the folder.. - To Exchange 5.5 this is just another property and is ignored.. - this is so Exchange 5.5 can be made aware of permissions changes.. - Replication Co-existence with Exchange 5.5 62. - The Exchange 2000 Active Directory Connector (ADC) is used to replicate objects and containers between the Exchange 5.5 Directory Service (DS) and the Windows 2000 Active Directory (AD).. - Exchange 5.5 and the Active Directory. - Exchange 5.5 ". - Replicates the Exchange 5.5 Public Store’s Obj-Dist-Name to the LegacyExchangeDN of the Store object in the Active Directory. - Replicates the HomeMTA to Exchange 5.5, so the Exchange 5.5 can route replication messages to the Exchange 2000 Store. - Replication Co-existence with Exchange 5.5 64. - Exchange 5.5 differently. - This allows the Exchange 5.5 MTA to route replication messages to the correct Exchange 2000 server.. - Replication Co-existence with Exchange 5.5 66. - The User CA is very important in mixed Exchange 5.5 / Exchange 2000 organizations. - Exchange 5.5 Mailboxes will replicate to Users in the Active Directory. - Exchange 5.5 DNs ACL’d on folders can be changed to SIDs by the Exchange 2000 Store.. - User1 has a mailbox on the Exchange 5.5 server. - User1 is ACL’d on a Public Folder on Exchange 5.5 so ACL entry will read:. - Exchange 5.5 Server Exchange 2000 Server. - Replication Co-existence with Exchange 5.5 68. - The primary NT accounts of the Exchange 5.5 users are in the NT4 domain.. - Exchange 5.5 Server. - Exchange 5.5 Server User CA. - Explanation All the Exchange 5.5 mailboxes will appear it the Active Directory. - Replication Co-existence with Exchange 5.5 70. - Public Folder connection agreements replicate the actual Public Folders’ directory objects between Exchange 5.5 and the AD.. - Folders created on Exchange 2000 cannot be administered from Exchange 5.5 if they don’t have a directory entry in the Exchange 5.5 DS. - Replication Co-existence with Exchange 5.5 72. - Exchange 5.5 can use multiple containers for folder directory entries. - In Exchange 5.5 it was possible to set the directory container that public folder’s directory entries were created in. - Because the Public Folder CA will create Public Folder directory entries based on their LegacyExchangeDN, the Exchange 2000 folder’s directory entries will be placed in the same container as the Exchange 5.5 folder’s directory entries.. - Replication From Exchange 5.5 Replication From Exchange 2000. - msExchPfCreation is replicated from the Exchange 5.5 DS attribute Folders-Container. - Exchange 2000). - Exchange 5.5 and Exchange 2000 Folder Replication. - In Exchange 5.5 Public Folders are part of the MAPI TLH (there was only one).. - Therefore, replication between folders in the MAPI TLH can occur between Exchange 5.5 Public folder stores and Exchange 2000 MAPI Public folder stores.. - The translation occurs when a folder replicates from Exchange 5.5 to Exchange 2000 (and vice versa). - Replication Co-existence with Exchange 5.5 74. - Exchange 5.5 Exchange 5.5. - However, the App TLH stores are not replicated to the Exchange 5.5 DS (due to problems this would cause Exchange 5.5 Public Folder Replication). - This will fail because the Active Directory has no entry for the Obj-Dist-Name of the entry in the Exchange 5.5 DS.. - Replication Co-existence with Exchange 5.5 76. - *Special Instructions for App TLH replication over Exchange 5.5 IMC. - Replicating permissions between Exchange 5.5 and Exchange 2000 is the most hazardous area in mixed mode operation. - Much of this section equally applies to upgrading a Public Folder store from Exchange 5.5 to Exchange 2000.. - Replication Co-existence with Exchange 5.5 78. - When Exchange 2000 receives an inbound replication message from an Exchange 5.5 server the following properties are dropped:. - This means that Exchange 2000 must be able to find the DN of the Exchange 5.5 user in the Active Directory and find the SID associated with the account. - Replication Co-existence with Exchange 5.5 80. - Replication Co-existence with Exchange 5.5 82. - Scenario 1 – Exchange 5.5 user has a primary NT account in the W2K Domain. - The User CA will replicate the Exchange 5.5 mailbox information to the user’s account in the W2K AD.. - The SID of the primary NT account on the Exchange 5.5 Mailbox will be used to ACL the folder.. - Comments: Strictly speaking this is not an Exchange 5.5 / Exchange 2000 interoperability issue. - Replication Co-existence with Exchange 5.5 84. - Example: The Exchange 5.5 user Andy has been added to the ACL of a folder on Exchange 5.5. - Replication Co-existence with Exchange 5.5 86. - Public Folder replication between Exchange 5.5 and Exchange 2000 requires ADC CAs to be in place.. - Exchange 5.5 Store in the same Admin Group / Site*. - The first Exchange 5.5 server in the. - *We try to avoid using an Exchange 5.5 store. - (In Exchange 5.5 the store used the affinity table to sort the list). - Specific problems with a mixed Exchange 2000 /Exchange 5.5 topology. - This is a limitation caused by the way we allow App TLH public folder replication via Exchange 5.5 servers.. - Exchange 5.5 Server B. - Exchange 5.5 Server C X400 of RPC Site. - Below is an example of a simple Exchange 5.5 Organization. - In Exchange 5.5 Public Folder Affinities were non-transitive. - Public Folder Site Affinities are created using the Exchange 5.5 Admin program. - Mixed Exchange 5.5 and Exchange 2000 Organization. - Exchange 2000 views Exchange 5.5 links as having Public Folder Referral disabled by default. - Exchange 5.5 users will use affinities.. - in mixed Exchange 5.5 and Exchange 2000 topology set the following diagnostics to maximum on the MTA:. - Permissions are the most problematic area of Exchange 5.5 and Exchange 2000 co-existence. - Exchange 5.5 users ACL’d on folders are not in the W2K AD.. - Exchange 5.5 servers see multiple Public Stores on an Exchange 2000 server.. - This will cause a second MAPI public store to appear in the Exchange 5.5 Directory for the Exchange 2000 server. - Do not install Exchange 5.5 on a W2K DC. - By default Exchange 5.5 connectors are set to Disallow Public Folder Referrals.
Xem thử không khả dụng, vui lòng xem tại trang nguồn hoặc xem
Tóm tắt