Tools for Moving to a Microsoft Collaboration Platform

I'm back..............

2010-03-22T04:08:00Z

I'm happy to have returned to Microsoft.

My new blog is http://blogs.technet.com/loum/

Good Bye and Good Luck

2009-05-08T22:28:00Z

I've spent the past six years here at Microsoft, 1/2 of which was dedicated to helping move customers to our platform from Lotus.

I wish the remaining team good luck.

Sincerely,

Lou Mandich.

Free Scripts from the Migration Community

2008-11-20T18:52:00Z

I would like to thank Mark Smith for contributing this IP and allwing me to blog this on his behalf for the benefit of the community.

Here is Mark's introduction...

"Mark is the Infrastructure Practice Manager and Principal Architect for Capax Global Consulting. He has been involved with Email/messaging systems since 1992 and with Microsoft Exchange since 5.0. Mark’s current work is with Microsoft Infrastructure products with a focus on upgrades/migrations to Microsoft Exchange Server. Mark has a BS (Computer Science) and BA (Mass Communications) from Widener University."

Please download the attachment below.

Updated script for Moving Domino Groups containing SMTP Addresses

2008-09-05T16:45:00Z

Thank you Casey Spiller for updating this script!

##################################################################################################
# Move-DominoGroupWithSMTP.ps1
#
# Written by Casey Spiller
#
#
# This script will move Domino Groups to Active Directory while preserving SMTP Addresses by
# creating contacts in AD for these users. By default Move-DominoGroupToAD will drop SMTP
# addresses if they do not already exist in AD.
#
# For troubleshooting, please locate the transcript of the script which should be located
# in your My Documents folder (by default).
#
# Known issues: If a user has an SMTP Address on a Domino Group that is also the SMTP Address used
# of a MailUser, we will drop this address. Search the transcript for "SKIPPING" to locate any
# MailUsers who were dropped.
#
#
# Disclaimer:
# This script is not supported under any Microsoft standard support program or service. This
# sample script are provided AS IS without warranty of any kind. Microsoft further disclaims
# all implied warranties including, without limitation, any implied warranties of merchantability
# or of fitness for a particular purpose. The entire risk arising out of the use or performance
# of the sample scripts and documentation remains with you. In no event shall Microsoft, its
# authors, or anyone else involved in the creation, production, or delivery of the scripts be
# liable for any damages whatsoever (including, without limitation, damages for loss of business
# profits, business interruption, loss of business information, or other pecuniary loss) arising
# out of the use of or inability to use this script or documentation, even if Microsoft
# has been advised of the possibility of such damages.
#
##################################################################################################

# Input Parameters
param ([string]$DominoGroup = "", [string]$GlobalCatalogServer = "", [string]$ADContainer = "", [switch]$help=$false, [switch]$All = $false,[switch]$CreateContactsOnly=$false);

#regex to identify SMTP addresses
$smtpregex = "^([a-zA-Z0-9_\-\.]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)|(([a-zA-Z0-9\-]+\.)+))([a-zA-Z]{2,4}|[0-9]{1,3})(\]?)$";
$iAddress = 0;

Function ShowHelp
{

Write-Host "Written by Casey Spiller" -foregroundcolor "White";
Write-Host "This Script will Move Domino Groups to Active Directory while preserving SMTP";
Write-Host "Addresses by creating Contacts in AD for these users.";
Write-Host "";

Write-Host "Options:" -foregroundcolor "White";
Write-Host "-DominoGroup          : Used to specify the Domino Group we wish to migrate for";
Write-Host "                        migrating groups one at a time";
Write-Host "";
Write-Host "-All                  : Used to migrate all Domino Groups at once. This option";
Write-Host "                        overrides the -DominoGroup option";
Write-Host "";
Write-Host "-GlobalCatalogServer : Used to specify the GC/DC";
Write-Host "";
Write-Host "-ADContainer          : Used to specify the Container in AD to write contacts to";
Write-Host "";
Write-Host "-CreateContactsOnly   : Used to Create Contacts in AD and NOT Move Groups";
Write-Host "";
Write-Host "Usage: " -foregroundcolor "White";
Write-Host "Move-DominoGroupwithSMTP.ps1 -DominoGroup ContosoAll -GlobalCatalogServer dc.contoso.com -ADContainer Users" -foregroundcolor "Green";
Write-Host "";

}

Function VerifyParams
{
if (!$DominoGroup -and $All -eq $false)
{
ShowHelp;
Write-Host "Missing 'DominoGroup' or 'All' Parameter. Either 'DominoGroup' or 'All' is required" -foregroundcolor "Red";
Write-Host "";
stop-transcript;
exit;
}

if (!$GlobalCatalogServer)
{
ShowHelp;
Write-Host "Missing 'GlobalCatalogServer' Parameter" -foregroundcolor "Red";
Write-Host "";
stop-transcript;
exit
}

if (!$ADContainer)
{
ShowHelp;
Write-Host "Missing 'ADContainer' Parameter" -foregroundcolor "Red";
Write-Host "";
stop-transcript;
exit
}

}
Function CheckForAddress
{
#initialize integer

#Write-Host $member.ToString();
if (Get-MailContact $member.ToString() -ErrorAction SilentlyContinue)
{
$iAddress++;
Write-Host "Contact detected for" $member "SKIPPING" -foregroundcolor "Blue" ;
}

#Detect if we've found a Contact with the Address already for performance

if ($iAddress -eq 0)
{

if (Get-MailBox $member.ToString() -ErrorAction SilentlyContinue)
   {
    $iAddress++;
    Write-Host "Mailbox detected for" $member "SKIPPING" -foregroundcolor "Blue";
   }

}
#Detect if we've found a Contact with the Address already for performance

if ($iAddress -eq 0)
{

if (Get-MailUser $member.ToString() -ErrorAction SilentlyContinue)
   {
    $iAddress++;
    Write-Host "MailUser detected:" $member "SKIPPING" -foregroundcolor "Blue";
    Write-Host "Move-DominoGroupToAD will not move this user as it is a MailUser" -foregroundcolor "Blue";
   }

}
return $iAddress;
}

#
#Begin actual script
#

start-transcript -Verbose;
# Display help if -help is specified
if ($help -eq $true)
{ShowHelp; exit }
else { }

#Check for params
VerifyParams;

Write-Host "";
Write-Host "Using the folling regex to detect what a valid SMTP Address is: " $smtpregex
Write-Host "-----------------------";

#Set DominoGroup to null if we are doing all DominoGroups
if ($All)
{$DominoGroup = $null}

foreach ($group in (Get-DominoGroup $DominoGroup))
{
Write-Host "Domino Group: " $group.Name;

foreach ($member in ($group.Members))
{

# we need to parse through the members to look for smtp addresses.
# ie user@domain.com. We need both the @ and the "."

if ($member -match $smtpregex)
   {


    # Call CheckForAddress to verify if the address already exists in AD, set iAddress if we find the Address in AD
    $iAddress = CheckForAddress;

     if ($iAddress -eq 0)
      {

      #create a new alias, we will change "@" to "_"
      $alias = $member.ToString().Replace("@","_");
      Write-Host "-----------------------";
      Write-Host "Domino Group contains member identified with an SMTP Address:" $member
      Write-Host "New-MailContact -Name" $member "-ExternalEmailAddress" $member "-OrganizationalUnit" $ADContainer "-DomainController" $GlobalCatalogServer -foregroundcolor "Green";
      New-MailContact -Name $alias -ExternalEmailAddress $member.ToString() -OrganizationalUnit $ADContainer -DomainController $GlobalCatalogServer
      Write-Host "-----------------------";

}
}

}
Write-Host "----------------------------------------------";

}

Write-Host "----------------------------------------------";
Write-Host "";
Write-Host "";

if (!$CreateContactsOnly -eq $true)
{
Write-Host "Now calling Move-DominoGroupToAD ";
Write-Host "MoveDominoGroupToAD" $DominoGroup "-TargetOU" $ADContainer "-GlobalCatalog" $GlobalCatalogServer -foregroundcolor "Green";
Move-DominoGroupToAD $DominoGroup -TargetOU $ADContainer -GlobalCatalog $GlobalCatalogServer -verbose;
}
else {
Write-Host "Contact Only mode, No DominoGroups will be created in ActiveDirectory";

foreach ($group in (Get-DominoGroup $DominoGroup))
{
Write-Host "Domino Group: " $group.Name;

foreach ($member in ($group.Members))
{

# we need to parse through the members to look for smtp addresses.
# ie user@domain.com. We need both the @ and the "."

      }
   }
   }
   }


}

Write-Host "";
stop-transcript;
############
# End Script #
############

What's new for Transporter Suite in regards to Lotus Domino in the July 2008 Release.

2008-07-08T19:06:00Z

What's new for Transporter Suite in regards to Lotus Domino in the July 2008 Release.

Download the Suite from here -> http://www.microsoft.com/downloads/details.aspx?FamilyId=35FC4205-792B-4306-8E4B-0DE9CCE72172&displaylang=en

Customers have been asking what's new or updated ? Below is the list based on customer feedback and our continued improvement in our products.

Domino User Migration (Move-DominoUser Cmdlet)

Address matching

· Improved support for interoperability with ILM

Alias handling

· Additional periods in alias are replaced with underscore after migration

Multi-domain replication issue

· User migration fails with duplicate proxy address caused by RUS and move-dominouser DC concurrency.

Custom attributes

· Custom Attributes now preserved from DirSync contacts

Domino Mail Migration (Move- DominoMailbox Cmdlet)

BCC recipients

· Bcc: recipients now preserved

Attachment handling & text alignment

· Improved Attachment handling

· Improved handling of Hebrew text

Recurring Meetings & Appointments

· Better logic for maintaining parent-child relationship of recurring meetings

· Addressed issues with preserving Meeting Organizer role

· Relationship between meeting organizer and meeting attendee now preserved

· Improved handling for yearly recurring appointments and all day events

Domino Group Migration (Move-DominoGroup)

Better extraction support

· Better default handling for non-default names.nsf templates

Move-DominoGroupToAD: How to migrate SMTP addresses with groups

2008-04-04T19:40:00Z

When attempting to migrate groups from Lotus Notes to Exchange 2007 with the Transporter for Lotus Notes, you may notice that Groups that contain SMTP addresses (non Exchange or Notes users) are not migrated with the group. I became aware of this issue recently when working with a customer and wrote a script to assist in getting these SMTP addresses migrated over cleanly.

So in the first screenshot we see a group in Domino that we want to migrate. By default the addresses highlighted below will not be migrated to AD.

Above: The circled users will not be migrated to AD unless the contacts are created beforehand.

Enter Move-DominoGroupToADWithSMTP.ps1:

So the solution is to create a powershell script to come along beforehand and create the contacts. What we risk here is that the contacts will not be created and replicated in the time it takes to run the script, so we tell the script a Global Catalog Server to point to. In the first stage we use this server to write the contact to. In the second stage we call MoveDominoGroupToAD which expects the contact to be there.

In cases where we cannot do this or encounter problems with Move-DominoGroupToAD not detecting contacts in Active Directory, we can use the –CreateContactsOnly switch to create the contacts. Once these contacts replicate throughout Active Directory, we can continue on with the next step of running Move-DominoGroupToADWithSMTP.ps1 or just call Move-DominoGroupToAD directly.

The Script:

# Input Parameters
param ([string]$DominoGroup = "", [string]$GlobalCatalogServer = "", [string]$ADContainer = "", [switch]$help=$false, [switch]$All = $false,[switch]$CreateContactsOnly=$false);

#regex to identify SMTP addresses
$smtpregex = "^([a-zA-Z0-9_\-\.]+)@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.)|(([a-zA-Z0-9\-]+\.)+))([a-zA-Z]{2,4}|[0-9]{1,3})(\]?)$";
$iAddress = 0;

Function ShowHelp
{

}

Function VerifyParams
{
if (!$DominoGroup -and $All -eq $false)
  {
  ShowHelp;
  Write-Host "Missing 'DominoGroup' or 'All' Parameter. Either 'DominoGroup' or 'All' is required" -foregroundcolor "Red";
  Write-Host "";
  stop-transcript;
  exit;
  }

if (!$GlobalCatalogServer)
  {
  ShowHelp;
  Write-Host "Missing 'GlobalCatalogServer' Parameter" -foregroundcolor "Red";
  Write-Host "";
  stop-transcript;
  exit
  }

if (!$ADContainer)
  {
  ShowHelp;
  Write-Host "Missing 'ADContainer' Parameter" -foregroundcolor "Red";
  Write-Host "";
  stop-transcript;
  exit
  }

}
Function CheckForAddress
{
#initialize integer

#Write-Host $member.ToString();
if (Get-MailContact $member.ToString() -ErrorAction SilentlyContinue)
  {
   $iAddress++;
   Write-Host "Contact detected for" $member "SKIPPING" -foregroundcolor "Blue" ;
  }

#Detect if we've found a Contact with the Address already for performance

if ($iAddress -eq 0)
{

  if (Get-MailBox $member.ToString() -ErrorAction SilentlyContinue)
   {
    $iAddress++;
    Write-Host "Mailbox detected for" $member "SKIPPING" -foregroundcolor "Blue";
   }

}
#Detect if we've found a Contact with the Address already for performance

if ($iAddress -eq 0)
{

}
return $iAddress;
}

#
#Begin actual script
#

start-transcript -Verbose;
# Display help if -help is specified
if ($help -eq $true)
{ShowHelp; exit }
else { }

#Check for params
VerifyParams;

Write-Host "";
Write-Host "Using the folling regex to detect what a valid SMTP Address is: " $smtpregex
Write-Host "-----------------------";

#Set DominoGroup to null if we are doing all DominoGroups
if ($All)
{$DominoGroup = $null}

foreach ($group in (Get-DominoGroup $DominoGroup))
{
Write-Host "Domino Group: " $group.Name;

foreach ($member in ($group.Members))
{

# we need to parse through the members to look for smtp addresses.
# ie user@domain.com. We need both the @ and the "."

      }
   }


}
Write-Host "----------------------------------------------";

}

Write-Host "----------------------------------------------";
Write-Host "";
Write-Host "";

Casey Spiller

merge-dominoUser.ps1 a powershell script for move-dominoUser cmdlet

2008-02-11T21:10:00Z

# merge-DominoUser.ps1

# ------------- DISCLAIMER -----------------------

# The code herein is provided as is with no gurantee or waranty concerning

# the usability or impact on your messaging system and may be used, distributed

# or modified for use provided the parties agree and acknowledge the Microsoft or

# Microsoft Partners have neither accountabilty or responsibility for results

# produced by use of this script.

# Developed by Jeff Kizner, Brad Hughes and Ed Thornburg

# -------------------------------------------------

# The script below provides the same functionality as move-dominoUser but does not enable

# the email address policy generator [RUS]. The default behavior of move-dominoUser is to

# mailbox enable the user object, apply email address policy as primary addresses and

# then add email addresses from contacts as secondary email addresses. If you intend to

# persist contact email addresses as primary email addresses of the mailbox enabled user,

# then this script is for you.

# The script takes a csv with header of samAccountName,InternetAddress and

# mailbox enables the user object matching the samAccountName and merging

# the contact with the matching primary smtp address.

# In this case the DisplayName is persisted as well.

# The minimum csv header: samAccountName,InternetAddress,displayName

# The script has four major sections, each of which can be run independently

# in sequence; a variable delay timer separates the major sections and is

# implementedto accomodate for directory replication latency

# process flow:

# add the heading for Domino directory values to be persisted to Active Directory

# note that the combinedObjectData merges the attribute data from the csv and

# the contact for the associated user into the same object and that object

# is finally exported to csv to provide the data for the enable-mailbox cmdlet

# the last part adds specific data to the mailbox enabled user

# -verbose provides realtime viewing of operations

start-transcript .\move-dominoUserScript.txt

# $netbiosDomainName = is a static definition of the netbios domain name of your active directory forest

# this value combined with the samaccountname;

# cmdlets accept domain\samaccountname for -identity switch

$netbiosDomainName = "Your_netBIOS_domain"

# ParseEmailAddresses function is necessary as contact.emailAddresses returns an array object;

# not the content of the array.

function ParseEmailAddresses([object[]] $addresses)

{

$sbAddress = New-Object System.Text.StringBuilder;

$tmp = $sbAddress.Append($addresses[0])

for($x = 1; $x -lt $addresses.Length; $x++)

{

$tmp = $sbAddress.AppendFormat(",{0}",$addresses[$x]);

}

$sbAddress.ToString();

}

# end function

# the code below merges the data for each entry in the csv

# with data from the contact that corresponds to that entry in the csv

# the combined data is in turn written to a csv containing all data

# necessary to persist the data for the mailbox enabled user

$dominoExportData = Import-Csv .\migrationList.csv

$combinedObjectData = $dominoExportData | foreach {

$contactInfo = Get-MailContact -Identity $_.InternetAddress | Select-Object PrimarySmtpAddress,LegacyExchangeDN,EmailAddresses;

Add-Member -InputObject $_ -MemberType NoteProperty -Name PrimarySmtpAddress -Value $contactinfo.PrimarySmtpAddress;

Add-Member -InputObject $_ -MemberType NoteProperty -Name LegacyExchangeDN -Value $contactinfo.LegacyExchangeDN;

$strAddress = ParseEmailAddresses($contactinfo.EmailAddresses);

Add-Member -InputObject $_ -MemberType NoteProperty -Name EmailAddresses -Value $strAddress;

$_;

}

$combinedObjectData | Export-Csv -NoType .\mkmbx.csv

# variable delay timer to accomodate directory replication latency

sleep -seconds 60

import-csv MigrationList.csv | foreach {

get-mailcontact -identity $_.internetaddress | remove-mailcontact -confirm:$FALSE

}

# variable delay timer to accomodate directory replication latency

sleep -seconds 60

import-csv mkmbx.csv | foreach {

$targetdatabase = ((get-mailbox -resultsize unlimited | group-object -Property database | select-object name,count | sort-object -Property count)[0].name)

Enable-Mailbox -Identity "$netbiosDomainName\$($_.samAccountName)" -database $targetdatabase -ManagedFolderMailboxPolicyAllowed:$TRUE -ActiveSyncMailboxPolicy "Default" -ManagedFolderMailboxPolicy "Empty Deleted Items" -confirm:$FALSE

}

# variable delay timer to accomodate directory replication latency

sleep -seconds 120

# code adds to the previously enabled mailbox

import-csv mkmbx.csv | foreach {

$mailaddr = $_.emailaddresses

$mailaddr = $mailaddr.Split(",")

# add the legacyExchangeDN of the contact as X500 of user to allow

# for reply to mail sent when user was in foreign system

$mailaddr += "x500:$($_.LegacyExchangeDN)"

set-mailbox -Identity "$netbiosDomainName\$($_.samAccountName)" -EmailAddressPolicyEnabled $false -PrimarySmtpAddress $_.primarySMTPAddress -verbose

set-mailbox -Identity "$netbiosDomainName\$($_.samAccountName)" -EmailAddresses $mailaddr -verbose

set-casmailbox -Identity "$netbiosDomainName\$($_.samAccountName)" -ActiveSyncEnabled $FALSE -IMAPEnabled $FALSE -POPEnabled $FALSE -verbose

# persist displayName from csv input file

Set-User -Identity $_.samAccountName -DisplayName $_.displayName.Trim() -verbose

}

stop-transcript

A major update to the Microsoft Transporter Suite was released on Monday, January 21st, 2008.

2008-01-25T12:40:00Z

Earlier this week we released a major update to the Microsoft Transporter Suite (A set of tools that help customers migrate content into Exchange, SharePoint and Active Directory). The Microsoft Transporter Suite is now available for download (here)

What’s New?

This release focused on adding the ability to migrate mailboxes from Generic POP/IMAP servers and improving the overall quality of the previously released Domino migration tools.

New Features/Fixes in this release

o NEW: Transporter Suite for Internet Mailboxes (A whole new console and tools for migrating POP/IMAP Mailboxes)

§ Migration of mailbox content from generic servers through POP or IMAP to Exchange 2007

§ Preserves all messages and folder structures

§ Preserves rich content including formatting, message flags and even calendaring through iCAL

§ Exposed through GUI and a rich set of PowerShell tasks

o Updated: Domino migration tools

§ Improved support in the Console for large organizations

§ Enhanced troubleshooting through tracing, improved logging, and capturing of items that do not migrate

§ Improved application migration by preserving created/modified identities

§ Enhanced security of the Free/Busy connector

Screen Shots Of Internet Mailbox Migrations

Initial Screen

List of Mailboxes

(Notice the migration status feature to track mailboxes that have been migrated)

Mailbox Migration Wizard

Domino to Exchange Messaging Migration Tools Solutions Matrix

2007-11-08T23:43:00Z

This is a living document to describe the features between multiple different messaging migration tools used for Domino to Exchange.

It is only meant to be an aid, not a definitive solution. It will help you narrow your choices when comparing toolsets.

Please send me a list of features you would like added, or other products. I'm not perfect, I make mistakes too, so if you need me to fix the

sheet, please let me know.

Transporter Suite End-to-End Guidance Released

2007-10-27T01:36:00Z

Have you been waiting with bated breath for fantastic end to end guidance around the Microsoft Transporter Suite for Lotus Domino? Well my good reader, your wait is over! We’ve been working hard with support and with the field to make sure that the information in here is solid. This is a release where even support is excited about the quality. It covers planning and executing on your directory and mail transition, including groups, archives, and PABs! It can be downloaded here.

We already know that there are some topics that we didn’t get a chance to cover, so stay tuned for future updates on this doc. If there are particular topics you are interested in, please feel free to leave them in the comments. In the meantime, go forth and be guided!

Microsoft Transporter Suite End to End Guidance

Alternative way of migrating Document Library

2007-05-31T20:14:00Z

I’ve been testing the scenarios for applications migration and one of the testing areas was application data mapping. Today I’d like to talk about alternative migration of Notes Document Library databases.

The default target for Notes Document Library is a Windows SharePoint Services 3.0 Document Library list. However this is not the only way to go and our new Transporter tool allows us to migrate Notes Document Library to SharePoint Discussion Boards list. This will be useful when preserving the hierarchy of the Notes Document Library is important, since the hierarchy from the Notes document library will be preserved after migrating it to a Windows SharePoint Server 3.0 Discussion Board.

To do this type of alternative migration from GUI the customer will have to select Target Mapping “Discussion Board” when migrating Notes Document Library database. In the command line it would look like this:

Move-DominoApplication –SourceIdentity DocLib.nsf –TargetMapping DiscussionBoard –TargetSharePointList “My SharePoint Discussions”

-Ruslan Babadzhanov

New OLE info for Outlook 2007 and the NDL option for Connector for Lotus Notes

2007-04-12T00:05:00Z

Hello it’s Lou again, I’d like to thank Omar Castillo Rodriguez for his work on this topic.

“In Office 2007 here are your two options for OLE-

1. Use the registry key that we need modify to enable Outlook 2007 to permit the access to OLE Objects is “HKCU\Software\Policies\Microsoft\Office\12.0\Outlook\Security” and the DWORD value that you must create to enable the feature is “AllowInPlaceOLEActivation” equal to 1.

2. The second option is to use the templates, located here-> Office 2007 Admin Templates

http://www.microsoft.com/downloads/details.aspx?FamilyId=92D8519A-E143-4AEE-8F7A-E4BBAEBA13E7&displaylang=en”

Thanks Omar! In addition, the newer versions of the Connector for Lotus Notes for Exchange 2003, support a fourth option, NDL’s, a Notes document link as an attachment.

See this article on how to enable it- Lotus Notes DocLinks in e-mail messages are replaced with bitmap icons in Exchange 2003 Lotus Notes DocLinks in e-mail messages are replaced with bitmap icons in Exchange 2003-http://support.microsoft.com/kb/920781/en-us

In addition here is my previous blog on this topic.

Previous Blog on OLE Options

http://blogs.technet.com/collabtools/archive/2006/04/20/425760.aspx

Thanks! -Lou

Microsoft Transporter Suite For Lotus Domino Release - On Valentine's Day !

2007-02-15T04:34:00Z

Today we release the Microsoft Transporter Suite 2007 for Lotus Domino. It is publically available for download at http://www.microsoft.com/technet/interopmigration/collaboration/default.mspx. Customers, Partners and consultants can download the released product immediately and begin using these tools to transition from Domino to the Microsoft 2007 collaboration platform.

Personally, I would like to thank all the partners, customers, and consultants that made the beta program such a success. Even though the program was very short, we had a record number of participants with overwhelming feedback. This feedback was valuable in tuning the final released product.

Finally, I thought it was fitting to ship on Valentine’s day. What is more romantic than a pair of PowerShell tasks that can automatically migrate data elements into Active-Directory, SharePoint or Exchange.

PS1> Get-DominoUser | Move-DominoUser -TrueLove:$True

Erik

P.S. We will continue to blog here and feel free to use this for feedback to our group about these tools.

Want to learn more about PowerShell?

2007-02-07T04:20:00Z

The Windows PowerShell team has a great blog where you can learn all kinds of interesting tips and tricks. They recently posted this great PowerShell "cheat sheet" and we thought our readers might be interested, so we're reposting it here.

The PowerShell Getting Started Guide and other helpful guidance can be downloaded from the Windows PowerShell website.

Enjoy!

- Amy

Webcast Recap

2007-02-03T04:05:00Z

Wow, Tuesday’s webcast was great ! Tons of interest and fantastic questions. Plus it was fun to take a break for a couple of hours during these final weeks before we ship and show off the Transporter a little. If you missed Tuesday’s webcast overview of the Transporter Suite we have posted a replay here at and I will post the entire Q&A log as a comment.

Enjoy !

Erik

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

2007-02-02T22:36:00Z

There isn’t transport stack in the Microsoft Transporter Suite for Lotus Domino. We have switched the transport stack from using the Exchange Development Kit Gateway from the Connector for Lotus Notes which was available in Exchange 5.5, Exchange 2000 and Exchange 2003 to using SMTP between Domino and Exchange. Yes, you read it right, SMTP, this means no more MFCMAPI/GWCLIENT to check out the MTS-IN and MTS-OUT on the Connector Server or exchange.box/exchange.bad on the Domino server.

The key reasons were to increase performance and reliability between the two messaging systems using a standard industry protocol. It also takes advantage of the iCAL format when sending and receiving meeting request information between the two messaging systems.

Currently we have tested and supported two methodologies for deploying this strategy in your environment. The first methodology is using sub domains within a single domain, for instance Contoso.com would route between the two systems by using exchange.contoso.com for Exchange and domino.contoso.com for Domino. The second methodology is if the domains were different, such as an acquisition scenario, contoso.com buys litware.com and they only need to synchronize information and send/receive e-mail. With both of the previous scenarios you use the same options in Exchange and Domino. In Exchange you will be using the configuration options for Send and Receive Connectors, Remote Domains, and E-mail Address policy. In Domino you will be using the configuration option for Foreign SMTP Domain Document and Connection Documents. This is all SMTP routing based, the majority of this is documented in our help file within the Transporter Suite documentation. Based on feedback from the beta, we will be working to write some more specific scenarios in an upcoming document. More information can be found about SMTP routing from the two web sources listed here:

Microsoft Exchange 2007- http://technet.microsoft.com/en-us/library/bb124558.aspx

Lotus Domino -IBM

Mailbox Migration: What have you done for me lately?

2007-02-01T03:01:00Z

Hi again! We talked briefly before about what was new with directory migration, but you may well ask what have you done for me lately? Well I’ll tell you. Directory migration wasn’t the only place we made improvements, mail migration also got some love.

Performance! We’ve improved performance for mail migration in a couple of ways. First of all, whereas we used to write everything to disk and then read everything from disk between extraction and injection. Now everything is passed from the extractor to the injector in memory, so you no longer have to take the disk I/O hit in migration. Secondly, we’ve implemented multi-threaded mailbox migration, which makes us much faster than before.
Merge Mode! Let’s say you’re migrating a 2GB mailbox, and somewhere in the middle, you lose network connectivity. In the past, if you re-migrated the whole mailbox, you’d get duplicates of any messages that had already come over. You could limit the re-migration down to a specific date range to overcome this, but that solution is a little cumbersome. In the new world order, we have merge mode! Now when you re-migrate the mailbox, we’ll detect which messages are already there and not re-inject them.
No More SC2! We now have better calendar content fidelity in migration, which is possible because we now inject calendar content directly into the target mailbox instead of sending it through an SC2 file along the way.
Web Services! Our mail injector now populates the target mailbox through Exchange 2007 Web Services. We used to inject using MAPI, which meant that the ports that you needed to have open between the migration client and the target server were all of the MAPI RPC ports. Web Services uses HTTPS, which means that 443 is what you need to have open between you and Exchange for mail injection.
PowerShell! Like the rest of our tools, all of this glorious functionality is exposed through PowerShell tasks, which infuses you with Fabulous Scripting Powers (fabulous scripts to follow)!

--Jenna

Connectors: What's new?

2007-01-30T22:09:00Z

With this blog I would like to open a series of Connector blogs and will start with what is new in Transporter Connectors.

We have made significant changes in this release of Connectors in Transporter Suite, including:

1. Ability to configure and control Connectors through Power Shell independently. Connector Tasks are divided in to two sets: DominoDirectoryConnector and DominoFreeBusyConnector and each supports 6 tasks: New, Get, Set, Remove, Start and Stop. The “New” commands create the appropriate connector object in the Configuration Container, and the “Set” tasks allow you to fully configure those objects. The “Start” and “Stop” commands allow you to start and stop the service, one service per connector unlike previous version. Using Start command with a combination of self-explanatory keys (–FullReloadToAD –FullReloadToDomino –UpdateToAD and –UpdateToDomino), you are able to control synchronization. And obviously the Remove task allows you to delete Connector object from AD.

2. Directory Synchronization can be deployed as a standalone connector and does not depend on mailflow, however FreeBusy connector requires objects to be populated by Directory Connector on both Domino and AD. The Directory Connector design supports standard as well shared name space configuration.

3. Directory Synchronization can be set up through a wizard that allows you to choose one of 4 sync modes with a simple explanation of each action.

4. Although the Directory Connector is not designed to perform direct upgrades from previous versions, through Power Shell with DominoDirectoryConnector you can take ownership of the DirSync objects created by E2K3 Directory Connector.

5. The Connector configuration previously set in the ini file has been converted to XML format and dramatically simplified.

6. Mapping tables are much simpler and file names are easy to follow.

Separating the Directory connector from messaging allows us to use the industry standard SMTP protocol for mail transport, which brings reliability, better SMTP/MIME format handling, ability to leverage existing servers and SMTP paths, and predictable performance.

New GUI allows the admin to configure and control both Directory and FreeBusy connectors from the same screen as well as perform migration of Domino users, mailboxes and applications.

And at the end I would like to mention that Power Shell allows you to set the Connectors’ diagnostic level through Get/Set-TransporterEvenLogLevel, and that is a perfect tool for troubleshooting connectors. Thank you and let me know if you would like to see blog for specific area.

Have a great day.

Kahren

Live Meeting Invite: Meet the Microsoft Transporter for Lotus Domino 2007 (and team)

2007-01-27T03:49:00Z

After the release of the public beta last week, I thought it would be fun/good to have an open Live meeting to allow everyone to meet the team, do some demos, and answer some questions. So consider this your invitation to join us in a review of this recent release.

Erik

Tuesday Jan 30th, 2007 10:00am PST

Live Meeting: Meet the Microsoft Transporter for Lotus Domino 2007

LiveMeeting Attendee URL:

https://www.livemeeting.com/cc/microsoft/join?id=99F23F&role=attend&pw=TS2007

Internet Audio Broadcasting enabled – Please listen to the audio via your PC speakers.

Questions can be submitted using the Live Meeting Question Manager.

NOTE: There will be a limited phone bridge to the first 50 callers if you are having audio problems. Live Meeting Internet Audio Broadcasting (IAB) has been enabled, please adjust the volume on your pc to audit the session and submit questions via the Live Meeting Question Manager.

Conference Call:

Toll free: +1 (866) 500-6738

Toll: +1 (203) 480-8000

Participant code: 4785480

Directory Migration: What's New?

2007-01-26T00:23:00Z

You may be wondering to yourself, what’s new about directory migration in the Transporter Suite? Well, I’m glad you asked. There were a couple of things that we were trying to accomplish in the area of directory. First of all, it occurred to us that you might want to do a directory migration *before* you do a mail migration rather than have it stapled onto the beginning of MigWiz. Well, we’ve separated it out into its own task, called move-DominoUser. Second of all, our previous directory migration required an act of God (or a Domain Admin) to get things done. We designed the permissions in this new task to allow Account Operators/Recipient admins to do their job. On top of that, when you execute the migration, we’ve enabled you to create the target accounts with mailboxes (if you’re ready for your mailbox migration) or without mailboxes (if you want your mail to keep being delivered to Domino). Finally, we’ve exposed all of this functionality through PowerShell, which makes this whole process easy to automate. Your boss will think you were up working all night, but just between us…

$SecureString = ConvertTo-SecureString –String P@ssw0rd –AsPlainText -Force

Get-DominoUser | Move-DominoUser –TargetOU Users –InitialPassword $SecureString

…will migrate all of your users from Domino to Active directory, creating any new users as Exchange MailUsers in the Users OU with an initial password of P@ssw0rd. If it finds an existing user, it’ll just merge the Domino directory information for that user into the existing account and upgrade it to a MailUser if necessary. You’re done! Time for you to go have dinner. Bon appétit!

--Jenna

Up late and blogging...

2007-01-24T08:09:00Z

Had some down time this evening so I wanted to quickly blog about some of our thinkig around the GUI and the PowerShell tasks.

The New Consolidated Transporter Management Console;

The decision to make life easier for the admin by consolidating the tools in the Microsoft Transporter suite into a single install and unified console was really a no-brainer. IT departments constantly are looking for ways to ease migrations and a single download and single management console is obviously easier than separate tools with different interfaces. This was really a no brainer. However….

A New Migration Platform on PowerShell;

We already had some existing tools and although I guess we could have bundled them together with some ‘menu’ interface this would have not really consolidated the experience. Instead we decided to take a step back and consolidate the core functionality by building a common migration platform based on PowerShell. The GUI then would use this platform and would not only provide a single console but implement a single consolidated underlying functionality. (Same authentication method, similar conversion experience, similar client install requirements, etc.)

Using the PowerShell Tasks;

So how it works is that all functionality in the Microsoft Transporter stems from a core set of PowerShell tasks that do the actual work. For example, in a user migration the Management Console calls the ‘Get-DominoUser’ and ‘Move-DominoUser’ tasks to do the actual work. These are the core PowerShell migration tasks:

Get-DominoUser : Lists users in a Domino Directory
Move-DominoUser : Migrates users to Active Directory

Get-DominoMailbox : Lists Domino mailboxes

Move-DominoMailbox : Migrates mailbox content to Exchange 12

Get-DominoApplication : Lists Domino applications on a server

Move-DominoApplication : Migrates application data to Windows SharePoint Services

Beyond these core tasks are more specific tasks such as Get-DominoApplicationData or Add-SharePointApplicationData and a set of tasks around coexistence. This made it easy to build the GUI, but what really is cool (if you like this sort of thing) is that all this functionality can be automated, scripted, and enhanced by you. The sky really is the limit.

enjoy...

Erik

FW: Announcing Role-Based Templates for SharePoint My Sites

2007-01-24T02:32:00Z

Just thought I would post a pointer to Bob's site on the Sharepoint Templates released.

http://blogs.msdn.com/sharepoint/archive/2007/01/22/announcing-role-based-templates-for-sharepoint-my-sites.aspx

-todd

Greetings from Lotusphere!

2007-01-23T20:45:00Z

Yes, as the team releases the beta of 2007 tools, I am here in Orlando suffering through all the sunlight and warmth...

I've been attending Lotusphere since it started 14 years ago, but only as a Microsoft employee for the last two. Last year was shortly after I joined Microsoft, so I was pretty nervous about how people would approach me, but this year, I'm not nervous at all! (Also, no one has thrown anything at me....yet.) This has been a really good conference so far - ~~John Glenn~~ Neil Armstrong was the opening speaker at the Keynote yesterday morning and I got to learn and see the upcoming Lotus products and hear IBM declare that Lotus Notes is now the official email product from IBM.

What's been different this year from a Microsoft perspective is the number of people approaching me and telling me that they are changing their business model to incorporate SharePoint 2007 into their business plans and practices. A couple of business partners mentioned to me that they are really impressed with it and are beginning to develop and work with SharePoint as a new part of their business. This reinforces my belief that the new version of SharePoint really is well thought out and makes sense for any collaborative environment - and to hear others who have been involved in collaborative technology agreeing with me always makes me happy (anyone agreeing with me generally makes me happy, by the way). I'd recommend anyone that is considering IBM Websphere Portal to take a look at what Windows SharePoint Services 3.0 , Microsoft Office SharePoint Server 2007 (aka "MOSS") and Office 2007 have to offer. (You can use earlier versions of Office as the fat client for SharePoint, but you don't get all of the kewl features unless you're using the latest and greatest, of course).

Also, I've noticed a bunch of people are posting questions and issues with the beta on here as comments. You'll get a lot quicker and better response if you post them in the Feedback mechanism on the Connect site where you downloaded the software from. That automatically generates tracking issues\bugs that get routed to the appropriate folks to investigate.

If you're at Lotusphere and have any questions about SharePoint or the beta tools, feel free to grab me!

Later,

Amy

Edited 2/3 cause I mixed up my astronauts.

Public Beta for Microsoft Transporter Suite 2007 for Domino Released

2007-01-22T23:22:00Z

Busy Day…Week…Year…

Today, Microsoft publicly announces a new set of tools to make the transition from Lotus to Microsoft easier. The announcement details:

· A new set of coexistence and migration tools (Microsoft’s Transporter Suite 2007 for Lotus Domino)

· Role-Based Templates for SharePoint My Site: Specific application templates based on common roles like sales managers, IT engineer, etc.

· 40 Windows SharePoint Services 3.0 Application Templates: Providing a great starting point for many custom applications.

(* you can read the whole Press Release here )

As part of this we are opening up a public beta for the Transporter Suite for Lotus Domino for anyone interested to download, trial and provide feedback. The beta program is being run through Microsoft Connect at http://connect.microsoft.com. To access the Beta simply signup for Connect and select to apply for ‘Microsoft Transporter Public Beta’ under the programs in ‘Available Connections’.

Great day for customers who are deploying Microsoft’s collaboration products:

The Transporter Suite is a huge step forward at making transitions easier. We look at this release from several points:

· 2007 collaboration: We fully support Microsoft’s 2007 product line. All our tools are designed for Exchange 2007, Office 2007 and SharePoint 2007 - enabling customers to migrate to the latest and greatest collaboration software available.

· New features: We added a ton of new features (like a unified admin GUI, PowerShell foundation, ACL migrations, User migrations, scripting, multi-threading, and more) that ease the migrations for our customers migrating accounts, mailboxes, applications and doing analysis.

· Enabling future scenarios: We built the suite as a platform that we are now using to add additional scenarios for future releases. Including the support for custom application migration, local archive migration, encrypted mail migrations, personal address books and more. We are also working closely with partners to extend even further…

· Endless possibilities and customization: our new tools are setting a new coexistence & migration direction for our customers and partners to expedite their migrations. Being built on PowerShell, there is nothing they can not do!!!

Check out the cool video on Channel 9: http://channel9.msdn.com/go/mscolab/transporter !!!

There will be lots of additional information, some Live Meeting demo’s showcasing the extensibility of our tools for customers and partners & more.

All of this starts today & will be happening later this week and more…

-erik

We are still alive and kicking...

2007-01-18T01:50:00Z

After what looks to be a long break, I want to make sure folks know we are still alive and well!!!

From a team perspective, we have really been cranking hard on our tools, doubling down our efforts, helping customers with their migrations and doing the things you do when you build software. The team has grown substantially over the year & it has been great seeing all the progress.

I believe you will find all the cool new things and various customer\partner scenarios we are addressing exciting & helpful. Over the next few weeks, you will begin to see more more more more & more stuff from us...

I look forward to hearing from all of you and its nice to come up for a breath of fresh air :)

More to come.

- todd wanke

Director, Notes Compete