What's new in the transport stack of the Microsoft Transporter Suite for Lotus Domino ?

re: What's new in the transport stack of the Microsoft Transporter Suite for Lotus Domino ?

Alison.Wing@gartmore.com — Tue, 06 Feb 2007 15:53:01 GMT

Very interested to see this documentation as soon as it is available. Your scenario with the single domain and 2 sub-domains is relevant to us. Am I right in assuming you set the foreign domain for the domino directory connector to exchange.contoso.com, that then appends onto the end of the internet address in the forwarding address field of the person document in Notes and a foreign smtp domain doc for domain Exchange.contoso.com is created? Is there a rough date for the RTM of transporter by the way?

re: What's new in the transport stack of the Microsoft Transporter Suite for Lotus Domino ?

NBlogger — Wed, 07 Feb 2007 21:49:17 GMT

You are correct. As for the RTM... Within the next week. We are closing out the final test passes and reviewing final comments in the beta program.

Erik

Weekend reading

subject: exchange — Sun, 11 Feb 2007 21:52:24 GMT

How to: Install Exchange 2007 Management Tools for Windows Vista Look out BlackBerry, Palm is back Moving

re: What's new in the transport stack of the Microsoft Transporter Suite for Lotus Domino ?

felipeg007 — Wed, 14 Feb 2007 19:30:37 GMT

Is there a knowledge base for transporter yet.

or a beta user community.

I am getting a wierd error

"could not retrieve E12 webservice url"

re: What's new in the transport stack of the Microsoft Transporter Suite for Lotus Domino ?

NBlogger — Wed, 14 Feb 2007 20:14:17 GMT

There is not a KB base yet since these are new however the E12 webservice URL would be a good first one. (We are seeing this by several customers in the beta.)

Anyway, the problem is usually either a mis-configured AutoDiscovery service or CAS server. We use the Exchantge AutoDiscover service to find the Exchange CAS server. We then use the Exchange CAS server as our entry point to migrate the mailbox to Exchange. If AutoDiscover is misconfigured it will not be able to give us a CAS server, or if the CAS server is mis-configured we can not connect. Both result in this error.

To fix this:

A> Make sure that the Exchange WebServices is configured correctly. You can use ExBPA or PowerShell Scripts (See: Test-WebServicesConnectivity or Test-OWAConnectivity)

B> Make sure that you have the right permissions. (You need to setup Impersonation on each CAS server. Follow the documentation on setting this up)

C> Finally (Not available in the beta) you can use the Move-DominoMailbox with the parameter -TargetCASServer that will direct you to a specific location for migration. This new parameter will be available in the final product when we ship.