Exchange 轉移



贊助商連結


victortung
2001-08-23, 11:12 AM
快要被微軟的EXCHANGE搞死了
一個朋友的exchange server 5.5 因為機器有問題 所以決定換系統
原來機器是 NT4.0 Server + Exchange 5.5
現在新裝的是一部 Windows 2000 Server + Exchange 2000 的機器
問題是他要求原來5.5內所有的東東 包括信件/聯絡人/行事曆 一定要轉過去
不知是否有高手有過相關經驗的可以提供

贊助商連結


milwater
2001-08-23, 03:37 PM
設定很多, 懶得打了. 借貼一下:
來源:微軟
 
Quick Start: Integrating with Exchange 5.5
Installation steps depend on whether Exchange Server 5.5 currently is installed in your company. If you want to integrate your new Exchange 2000 servers into an existing organization, your installation planning and execution must include the following steps. Although it is possible to perform an in-place upgrade of your Exchange 5.5 server, it is best to first install at least one Exchange 2000 server into the organization to ensure that the Active Directory™ service was deployed properly.
Preparing Your Exchange 5.5 Organization
Before you install your first Exchange 2000 server, you must look closely at any existing Exchange 5.5 deployment and make changes if necessary.
· Ensure that Domain Name System (DNS) name resolution is working among Exchange 5.5, Active Directory, and the proposed Exchange 2000 servers.
· Remove invalid characters from the organization and site display names.
· Set permissions so that Exchange 2000 can be installed into the first site. For more information on permissions, refer to the “Exchange 2000 Internals: Permissions Guide” white paper available at http://www.microsoft.com/exchange/techinfo/e2kpermmisions.htm.
· Use the NTDSAtrb tool to identify multiple mailboxes that are mapped to the same Microsoft Windows NT® account if your user domains are running Windows NT Server network operating system version 4.0. Resolve duplicates by using NTDSNoMatch in custom attribute 10.
· Run the Directory Service/Information Store (DS/IS) consistency adjuster on all servers to remove unused permissions on mailboxes and public folders.
Preparing Your Active Directory
Use the following steps to prepare your Active Directory:
1. Install Microsoft Windows® 2000 Service Pack 1 and any hotfixes on all domain controllers and global catalog servers.
2. Ensure that DNS is working correctly by using the NSLOOKUP tool.
3. Ensure that at least one domain in the forest is in native mode.
4. Extend the Active Directory schema with the Active Directory Connector (ADC) schema extensions. Use the following command: Setup /Schemaonly
5. Wait for the schema extensions to replicate to the domain where the first instance of the ADC service will be installed.
6. Install the first instance of the ADC service.
7. Extend the Active Directory schema with the Exchange 2000 schema extensions. Use the following command: Setup /ForestPrep
8. Wait for all schema extensions to replicate to the entire forest.
9. Check DomainPrep prerequisites.
10. Prepare each Active Directory domain for Exchange 2000. Use the following command: Setup /DomainPrep
11. Wait for replication of the DomainPrep data.
12. Test DomainPrep replication by connecting to a domain controller with Active Directory Users and Computers and search for the Microsoft Exchange System Objects container.
13. Create a two-way Recipient Connection Agreement between the Active Directory domain and the first Exchange 5.5 site that will host an Exchange 2000 server.
14. Create either one-way or two-way Recipient Connection Agreements between the Active Directory domain and the other Exchange 5.5 sites in the organization.
15. Create Public Folder Connection Agreements between the Active Directory and all sites in the Exchange 5.5 organization.
16. Check that all Connection Agreements are replicated.
Preparing and Installing the Exchange 2000 Server
With the prerequisites complete, you can install the first Exchange 2000 server in your organization:
1. Install Windows 2000 Service Pack 1.
2. Use NLTEST on the proposed Exchange 2000 server to ensure correct Active Directory and DNS integration.
3. Run Setup and install the first Exchange 2000 server into the selected Exchange 5.5 site.
4. Verify the installation and check for errors.
Start moving users to the new server and install additional Exchange 2000 servers if needed.