Sie sind auf Seite 1von 5

MS Transporter Setup Prerequisites 1. Install Windows Server 2003 with SP2 on two Images 2.

Provide similar IP range to Image1 and Image2 so that they can connect to each other 3. Configure you Domain Controller and Active Directory on Image1 4. Configure Exchange Server on (If you are installing Exchange and Domain controller on different machines and trying to use Outlook on a domain controller then there are few additional steps you need to take so that outlook work fine. In order to configure Outlook on a Domain Controller or on a Global Catalog server, carry the below steps on the target server, A. Open Domain Security Policy and browse to User Rights Assignment, Ensure that the particular user isLocal Policies provided Allow Log on locally rights. B. Open Domain Controller Security User Rights Assignment, Ensure that thePolicy and browse to Local Policies particular user is provided Allow Log on locally rights. C. A Now we need to force Outlook to point to the closest GC, use the below steps to perform this action a. Open Registry. b. Locate and then click the following key: HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider Note you may have to create the registry path On the Edit menu, click Add Value, and then add the following registry value: 1. Value name: Closest GC 2. Data type: REG_DWORD 3. Radix: Hexadecimal 4. Value data: 0x00000001 Restart the System and then login with the desired user profile, now you would be able to configure the outlook for this user. 5. Install Lotus Domino Partitioned server (LotusMail and LotusBT) on IMAGE2 5.1 To install three partitioned server add two IP addresses to the same LAN card. 5.2 You have to make changes in notes.ini to properly run these Domino Partitioned servers. Add additional lines in notes.ini TCPIP_TcpIpAddress = 0, IP address (of the current partitioned server). Ex: If you are editing LotusMail servers notes.ini, then use the IP address assigned for LotusMail server. So whatever IP address you specify here, will be assigned to that partition server. 5.3 Create host entries for all the domino servers in DNS so that they can recognize and trace each other. 6. Domain name for Domino and Exchange should be same 7. Install Lotus Notes Client with Admin ID on Exchange Server and outlook client on Domino Server with Admin IDs Installation and Configuration 8. Install transporter Suite on Exchange Server and Transporter add-in on Domino Server.( If you want to install Transporte Suite on a separate machine then you need to have Windows

Management tools installed on that machine). 9. Now for Directory Synchronization create a new Directory for exchange on Domino BT server With a virtual domain name. This same domain name will be used at the time foreign domain document creation. Create a new OU for domino names.nsf users on Exchange as contacts. Directory Synch will use the ID of lotus notes installed on Exchange server to synch with Domino Server. 10. Provide manager access to admin ID on new address book and Exchange Secuirty group full access to new OU. 11. Add a new line in notes.ini with primary and new address book ex: names=names.nsf, exchange.nsf 12. Create a new domino connector and configure it properly. Now synchronize both the directories. Note: If you face any difficulty during directory synch then check application logs for possible errors. To set transporter even logging level use the command : Set-TransportEventLogLevel high Notes.ini path should be there in environment variables.check this by using the command get dominodirectoryconnector 13. Users from AD will come in new directory on domino and domino users will come in new OU in exchange. 14. The Directory synchronization process uses four control files, which are located in the \Program Files\Microsoft Transporter Tools\Config\Connector folder. These files contains the attributes that will be synchronized. The files are: a. DominoAttributes.tbl: Maps Domino attributes to intermediate schema attributes. b. ExchangeAttributes.tbl: Maps Active Directory attributes to intermediate schema attributes. c. DominotoExchangeRules.tbl: Defines the rules for constructing values in the Directory Connector namespace targeted for Active Directory. d. ExchangetoDominoRules.tbl: Defines the rules for constructing values in the Directory Connector namespace targeted for the Domino directory. Note: a. If you edit these files using Notepad or another Text Editor, make sure that you save backup copies of the shipped files. b. Do not use the Tab key when making changes all white space characters should be entered using the space key. c. Ensure that directory synchronization is not active when editing the files stop the Microsoft Exchange Directory Connector Service for Lotus Domino. 15. Install Microsoft Mapi Cdo on exchange server as it is required for proper functioning of free busy connector. 16. Check if there are any public folders on exchange side using the Exchange Shell command Get-Public Folder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" Recurse If its not then create a new one using exchange management console. 17. Type the following command in the Exchange Management Shell to add the Domino and Exchange servers address space. Add-AvailabilityAddressSpace -ForestName -AccessMethod PublicFolder This is required when you want to do a free/busy lookup between cross forest Exchange

organization. So if from an Exchange 2007 organization you want to do a free busy look up on exchange 2003 server or domino server then you need thi s command as you have to tell exchange 2007 to use public folders in the target domain because Exchange 2007 does not use public folders by default for free busy look ups but Exchange 2003 does. Restart Microsoft System Attendant service 18. Remove SSL requirements from Public folders. 19. Open IIS and go to Public folder under Default Virtual Directories Go to Public folder properties In the Directory Security tab and in the secure communication click on edit. There remove all the check boxes. Now save and restart IIS. 20. Now create a free busy connector and start the free busy service. * Free busy service will not start if Exchange MAPI Cdo is not installed 21. To let Domino connect to Exchange server we have to create a foreign Domain document. 1. On the General Tab Leave the Domain type as Foreign Domain. Foreign domain name should be same what you have defined in the Directory Synchronization Connector on the Exchange server and the Exchange Directory profile document 2. On Mail Information tab type the Coexistence servers name (BT Server)as the Gateway server name, and specify mail.box as the Gateway mail file name. 3. On the Calendar Information tab, type the Coexistence servers name, (BT Server) , as the Calendar server name, and specify mail.box as the Calendar system. best practice is to create a new mail.box(ex: transporter.box) from the Mail Router Box template(mailbox.ntf) and use it in both Mail Information and Calendar Information tab. 4. Replicate domino directory to all other mail server. You can also create connection document to schedule the replication interval between domino servers. 5. Update the router table by using the command tell router update config 22. Load Excalcon task on BT domino server by using this command Load excalcon mail.box Or add the parameter excalcon mail.box in server task line in notes.ini. *Here the exchange server name is the host name. if the host name doesnt work then please use the fully qualified domain name. 23. To send/receive mails from Exchange end we have to perform few tasks a. On the Hub transport server create a new Accepted domain with the domain name exchange1.exchmig.com and make this as Authorative b. Create a new email address policy for this new domain so that all the users with exchange mailboxes, Resource mailboxes and mail enabled groups have two email addresses first @exchmig.com and second @exchange1.exchmig.com c. Create a new send connector with the smart host routing to Domino server i.e lotusbt.exchmig.com. d. Now create a new receive connector with the remote network server as again the domino server. Go to properties of receive connector and on the authentication tab deselect TLS and externally secured and on the permission groups tab select Anonymous users, exchange server and partners. If you will not do this option then you will receive an NDR while sending mails from domino to exchange that Client is not authenticated 24. To send/receive mail from domino end we to again perform some additional steps

a. Create a new foreign SMTP domain document with following parameters Internet domain - exchange1.exchmig.com Domain name - SMTPExchangeDirect b. Create a new SMTP connection document with following parameters Source Server LotusBT/Exchmig Destination server ExchAd.Exchmig.com Domain SMTPExchangeDirect SMTPrelayhost ExchAD.Exchmig.com Replication task disabled Routing Task SMTPMailrouting 1message pending and routing cost=1 Scheduled enabled(12:01AM 11:59PM) repeat 60 min each day c. Enable SMTP mail routing and SMTP listener task on the coexistence server d. Create/Edit(if exist) configuration document for coexistence server(LotusBT) In Router /SMTP tab change these parameters Number of mailboxes: 1 SMTP Used when sending messages outside local internet domain: Enabled SMTP allowed within the local internet domain: Disabled Servers within the local Notes domain reachable via SMTP over TCP/IP: Always Address lookup: Full name then Local Part Exhaustive lookup: Enabled On the MIME Tab, select Conversion Options and navigate to General and change Return receipts to Enabled. Finally, on the MIME Tab, select Conversion Options and navigate to Outbound Conversions Options and change the message content to, From Notes to HTML as shown below. e. Replicate domino directory 25. Now start with sending mails from both the sides and check the calendar synch between Exchange and Domino. Migrations 26. For migrations using MS Transporter Suite 2007 there are few prerequisites: a. Create a new OU in AD for migrated users. b. Create catalog.nsf on domino end and provide access to the migratory ID c. The Active Directory user used to perform the migration must have permission to impersonate the users to inject mail into their mailboxes .Perform impersonation on exchange management shell so that the migratory account can perform migrations for all users. Add-ADPermission -Identity (get-exchangeserver).DistinguishedName -User (Get-User Identity User1 select-object).identity -extendedRight ms-Exch-EPI-Impersonation d. Open transporter suite click on migrate->directory->users. select the user we want to migrate and click migrate users. this step will create a new AD object and exchange mailbox for this user and. e. Now click on migrate ->mailbox and click on migrate selected mailbox f. It will migrate the mailbox. Note:

1. MS transporter suite works on multithreaded mode but threads on a single mailbox at a time. Threads are open TCP connections to the same target mailbox, not multiple concurrent mailboxes. The tool only support connecting to one target mailbox at a time; to increase this you'd need to run it on multiple workstations 2. To resolve SSL cert error. open the error source URL in internet explorer and install the certificate to resolve the issue. 3. For organizations that have message size limits greater than 4 megabytes (MB), the maximum attachment size for Web Services must be increased. We recommend that you increase this limit for the duration of migration anyway. You increase the message size limit by editing the web.config file in the exchweb\EWS subdirectory of the ClientAccess directory on each CAS, adding a line similar to the following in the section (this line sets the maximum to 10 MB): 4. If you find matching user not found or IPC port error refresh the view few times.it might be due to network latency. 5. The Transporter Suite uses Exchange Web Services to inject messages into a users mailbox, and the Client Access Server used is determined by AutoConfiguration in the default case.If an error indicates Could not retrieve E12 Web Services URL, this could be due to AutoConfiguration not being configured correctly, or that the target Client Access Server is not available

Das könnte Ihnen auch gefallen