Tools for Moving to a Microsoft Collaboration Platform

Good Bye and Good Luck

NBlogger — Fri, 08 May 2009 22:28:00 GMT

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

NBlogger — Thu, 20 Nov 2008 18:52:00 GMT

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

NBlogger — Fri, 05 Sep 2008 16:45:00 GMT

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.

NBlogger — Tue, 08 Jul 2008 19:06:00 GMT

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

NBlogger — Fri, 04 Apr 2008 19:40:00 GMT

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

NBlogger — Mon, 11 Feb 2008 21:10:00 GMT

# 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.

NBlogger — Fri, 25 Jan 2008 12:40:00 GMT

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

NBlogger — Thu, 08 Nov 2007 23:43:00 GMT

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

NBlogger — Sat, 27 Oct 2007 01:36:00 GMT

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

NBlogger — Thu, 31 May 2007 20:14:00 GMT

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

NBlogger — Thu, 12 Apr 2007 00:05:00 GMT

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 !

NBlogger — Thu, 15 Feb 2007 04:34:00 GMT

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?

NBlogger — Wed, 07 Feb 2007 04:20:00 GMT

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

NBlogger — Sat, 03 Feb 2007 04:05:00 GMT

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 ?

NBlogger — Fri, 02 Feb 2007 22:36:00 GMT

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