Microsoft KB Archive/254349: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
| Line 46: | Line 46: | ||
When you rehome a public folder between two sites that share the same address space (for example, microsoft.com), the directory object that represents that folder exists in two places for a brief period of time.<br /> | When you rehome a public folder between two sites that share the same address space (for example, microsoft.com), the directory object that represents that folder exists in two places for a brief period of time.<br /> | ||
<br /> | <br /> | ||
When this duplication occurs, the Simple Mail Transfer Protocol (SMTP) address on the destination server has a number added to the end of the SMTP address prefix. For example, | When this duplication occurs, the Simple Mail Transfer Protocol (SMTP) address on the destination server has a number added to the end of the SMTP address prefix. For example, "PublicFolder@microsoft.com" becomes "PublicFolder2@microsoft.com." | ||
</div> | </div> | ||
| Line 57: | Line 57: | ||
After you rehome the public folder and inter-site replication removes the original SMTP address from the directory of the organization, you must manually change the SMTP address of the folder back to the correct address.<br /> | After you rehome the public folder and inter-site replication removes the original SMTP address from the directory of the organization, you must manually change the SMTP address of the folder back to the correct address.<br /> | ||
<br /> | <br /> | ||
For example, if a folder named | For example, if a folder named "faxes" exists in the Dallas site with an SMTP address of "faxes@microsoft.com," and you rehome it to the Atlanta site, the SMTP address of the folder becomes "faxes2@microsoft.com."<br /> | ||
<br /> | <br /> | ||
However, if the two sites had SMTP suffixes (which is the Exchange default) such as | However, if the two sites had SMTP suffixes (which is the Exchange default) such as "atlanta.microsoft.com" and "dallas.microsoft.com," this would not be a consideration.<br /> | ||
<br /> | <br /> | ||
For additional information about rehoming public folders, click the article number below to view the article in the Microsoft Knowledge Base: | For additional information about rehoming public folders, click the article number below to view the article in the Microsoft Knowledge Base: | ||
Latest revision as of 13:52, 21 July 2020
Article ID: 254349
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q254349
SUMMARY
When you rehome a public folder between two sites that share the same address space (for example, microsoft.com), the directory object that represents that folder exists in two places for a brief period of time.
When this duplication occurs, the Simple Mail Transfer Protocol (SMTP) address on the destination server has a number added to the end of the SMTP address prefix. For example, "PublicFolder@microsoft.com" becomes "PublicFolder2@microsoft.com."
MORE INFORMATION
A duplication of the directory object that represents the public folder on the source server occurs in the Recipients container (or the default public folder container designated on the General tab of the Site Information Store Configuration object) of the destination site. The original object and the new object coexist in the directory for the period of time that it takes to complete replication. The change in the SMTP address of the public folder occurs because the design of the Exchange Server directory prevents duplication of addresses within an organization.
After you rehome the public folder and inter-site replication removes the original SMTP address from the directory of the organization, you must manually change the SMTP address of the folder back to the correct address.
For example, if a folder named "faxes" exists in the Dallas site with an SMTP address of "faxes@microsoft.com," and you rehome it to the Atlanta site, the SMTP address of the folder becomes "faxes2@microsoft.com."
However, if the two sites had SMTP suffixes (which is the Exchange default) such as "atlanta.microsoft.com" and "dallas.microsoft.com," this would not be a consideration.
For additional information about rehoming public folders, click the article number below to view the article in the Microsoft Knowledge Base:
185043 XADM: How to Re-home Public Folders Using 5.5 Admin Program
For additional information about duplicate SMTP addresses in an organization, click the article number below to view the article in the Microsoft Knowledge Base:
168367 XADM: Error Creating New Address
Additional query words: public folder rehoming; smtp address; 2@
Keywords: kbinfo KB254349
