Hello everyone, Attached below is a Microsoft Outlook 2010 Reference Guide for Lotus Notes Users to assist with training for Outlook 2010 deployments.

Click to Download

Hope this helps everyone! Thanks! –Lou

Hello everyone, as some customers have reminded me, not everyone is using Outlook 2010 yet.

Attached below are Outlook 2007 reference guides.

Enjoy!

Outlook2007ReferenceGuides.zip

I wrote this article on help inform everyone of the options they have with the Transporter Suite  for Lotus Domino and Exchange Server 2010.

Problem
Installation completes, the configuration fails. Why ? It was never designed for Exchange Server 2010.

What does not function ?

• Directory Synchronization
• Free Busy
• Move-DominoMailbox

What does function ?

• Move-DominoUser UI/powershell

Solution

Solution is to install on an Exchange 2007 Server. Use that as your bridge server to and from Domino for the duration of the coexistence and migration, then retire it when complete.

Two system integrators have products which can help you go directly without this bridge method, Binary Tree and Quest Software

High Level Overview

Configuring the Exchange Server 2007 Bridge

1. Install a full CAS/HT/MBX with Exchange 2007 Sp2 and rollups as the FIRST SERVER in the NEW EXCHANGE ORGANIZATION.
2. Install Notes Client
3. Install Transporter Suite
4. Install MAPI/CDO Pack
5. Create Connectors
6. Set notes ini path (shell) for both
7. Directory Synchronization
   • Add Machine Account (Exchange server $) to OU for Target Domino users, ensure do all sub containers (this object/all descendant objects)
8. Free Busy Connector
   • Check Windows firewall on 2k8 (key thing people miss)
   • Disable SSL on VDIR on 2k7 then iisreset
9. Install the first Exchange Server 2010 in your new Exchange organization
10. When migration/coexistence is done, retire the Exchange Server 2007 bridge.

User Migration / Data Migration

• Evaluate the system integrators migration tools to eliminate the double hop migration, to 2007 then 2010.
• You will have to do a two stage migration if you use the free tools, once to 2007, then move the mailbox to 2010.
• Don’t forget to follow the directions in the end to end guide on impersonation so you can migrate mail to 2007

Domino to Exchange Server 2010 Summary

• Transporter Suite does not function on Exchange Server 2010 because it was never designed to do so.
• Use a Exchange Server 2007 Bridge, using the Transporter Suite for Directory Synchronization and Free Busy query capability.
• Consider a system integrator for mailbox migration directly to Exchange Server 2010
• Always read the definitive guide –> Click on the seal of approval

This isn’t my specialty but I helped someone locate these registry keys which may help others so I’m posting them here.

The error symptoms are:

Summary: 1 item(s). 1 succeeded, 0 failed.

Elapsed time: 00:03:52

xyz@xyz.com

Completed

Warning:

Failed to retrieve the properties of a message in folder INBOX for the following reason: Failed to retrieve the properties of a message in folder INBOX for the following reason:  Command line too large..

The two registry keys which could help with this scenario are: The first key fixed the command too large issue, the second could help migration machines that have a limited amount of memory.

HKCU\Software\Microsoft\Transporter\Preferences\ImapFetchBatchSize

Sets the chunk size for mail extraction using IMAP.  If not specified, or if the specified value is invalid then it is default to 2500.

Scenario: customer is receiving errors from the source server indicating “Request too large”.  This registry key allows the customer to define a smaller request size.

HKCU\Software\Microsoft\Transporter\Preferences\PipelineFlushThresholdMB

Registry key to specify the pipeline memory after it grows to a certain size. Default size is 600MB, can be overridden with a registry value. This will prevent any potential System.OutOfMemroyException caused by oversized mail migration.

Scenario:  Customer is receiving system out of memory exceptions on the machine running the Migration tools.  The Transporter will spool up items from the source until the memory usage reaches a certain size, at which point it will flush the pipeline by submitting the items to the target server.  This registry key reduces the amount of data we’ll spool up before flushing the pipeline.  The other tool available for this scenario is reducing the max thread count for the migration process via PowerShell.  This scenario is typically one we see on 32 bit machines.

Hello everyone! Lou Mandich has returned to Microsoft!

This blog will start becoming more active in the next few months.