Featured Post

How the Sumatra Double-Booking cmdlet works

Free license through 2017 if you qualify and contact us . First: you can always get help at the PowerShell prompt with: get-help Get-suDo...

Saturday, August 12, 2017

Special Cases of Attachments in Oracle Calendar Migrations to Microsoft Exchange

Secure signed attachments in Oracle Communication Convergence Calendar, that is anything named “smime.p7m” or with a “.p7m” extension.  These are signed, secured attachments in in Oracle Communication Convergence Calendar so the Sumatra process takes them as the secured, signed (therefore encrypted) attachments they are.
Please make sure your security-tasked admins know this and are prepared to deal with it in a post-migration Microsoft Exchange environment and have their certificates and security arranged appropriately.
Otherwise we are migrating data that cannot be read in your Office 365 / Microsoft Exchange environment.
Inline attachments in Oracle Communication Convergence Calendar
OCC identifies inline attachments by excluding the file name and the format type.  Since Sumatra doesn’t know the file name or file type, we name the attachment “att_” + <>, without extension, and attach as a FILE (not inline.) 

Oftentimes users can leverage their browsers to view each attachment.  In the calendar event select the attachment and Right-Click-Open, selecting the appropriate application if you know what it is or Microsoft Explorer if you do not.  If the attachment does not display correctly please contact the meeting organizer.

Tuesday, August 08, 2017

Attachments in Oracle Communication Convergence Calendar Migration to Exchange Version 2

Okay okay....

Remember this article?

We changed our minds.

Our test site did not want just the URL.

SO we needed to actually attach the damned binary file(s).

Sure.  We're getting a paycheck somewhere in here, right?

The insertion team (kudos to Russ!) put this together.

Export using fetchattach=1 in WCAP.

Select this option in your configuration:


Attachments will slow down the process!
Attachments are not supported in historical archive mode.  

Tuesday, July 11, 2017

Daylight Savings Time and Exchange Hybrid Environments -- Remember to apply CU6

Microsoft released June 2017 Quarterly Exchange Update (for Exchange 2016) on June 27, 2017. This pushes the build number to 15.01.1034.026

It's a MUST update for:

  • Exchange Hybrid Environments (for more see a recent Sumatra Blog post on hybrid directory structures), particularly when the alias and SAM account names are different.  
  • US customers -- it has the latest DST updates.  
  • Sumatra's European customers -- it  fixes an error when the mailbox name contains an umlaut (Jörg, Hans-Günther, Köller, Müller, Dück and MANY more will be happy!)

Download Exchange CU6 for Exchange 2016 here.

Tuesday, July 04, 2017

How To Do It: Microsoft Exchange Hybrid Directory Structures

 A typical Sumatra client deploys our Microsoft Exchange migration and calendaring solutions in either on-premises or the cloud (Office 365).  This deployment is supported by a straight-forward network topology: user, room mailboxes are setup in a Single Forest.  This simple topology gets more complicated, particularly as Office 365 makes inroads in larger enterprises and higher education segments.
Some client deployments require two different Active Directory configurations.  We see this implementation when only a portion of the enterprise needs Exchange (e.g., office worker vs manufacturing, retail store, etc).  This is called creating a Dedicated Exchange Forest (see http://technet.microsoft.com/en-us/library/aa997312(EXCHG.65).aspx);  
Other client deployments host Active Directory and Exchange on two physically separate forests (e.g., parent company, acquired subdivision.) In Exchange 2007  this configuration was called an Exchange Resource Forest Topology (see: http://technet.microsoft.com/en-us/library/aa998031(EXCHG.80).aspx).    
This Exchange Resource Forest Topology has evolved in these cloud-centric times to an Exchange hybrid deployment topology (e.g., where on-premises Exchange server and Office 365 coexist in one domain (e.g., professors on-prem Exchange; Students & Alums on Office 365.)
This requires clients synchronize Active Directory between these two physically discrete servers to ensure users have a seamless single-signon experience.  Thus, when the client signs in, they are redirected to either on-premises or the cloud, depending upon their configuration.  If cloud-based users start from a company intranet, they are often required to resubmit their credentials.  This adds a small wrinkle to a calendar migration.
Follow this guide
We do not duplicate efforts when we find an excellent how-to already published.  Such is the case with Step-By-Step: Configuring a Hybrid Office 365 Deployment via Hybrid Deployment Wizard.  It’s hard to go wrong following those steps.
For those of you who need a more detailed set of instructions for earlier Exchange 2007/2010 resource forest trust environments, please contact Sumatra.
Your mantra: Validate before you Impersonate!
Your slightly longer mantra: Validate on the on-prem before you impersonate in Office 365.
In the Sumatra user interface, use your service credentials.  Hazy on service credentials?  Check out our posting The Cookbook Version of Exchange 2013 Migration Rights  and do not be afraid to use our debugging guide.
But how do I migrate on-prem Exchange to the Office 365 environment?
Easy:  For email user imapsync.  In fact we wrote a DIY guide to on-prem to Office 365 migrations.
We can handle the calendars better than anyone else, keeping meetings from an on-prem environment as meetings in Office 365, including incremental sync!  Check out our video.

Questions?  Contact Sumatra.  Or visit our site or blog.

Tuesday, June 27, 2017

MDaemon migration: Suggested Contacts to Office 365 / Exchange

As usual we cannot keep ourselves out of trouble.  "Trouble" in this case meaning "adding more migration features so legacy calendar systems hate us even more."

The latest is migrating Suggested Contacts from MDaemon into Office 365 / Microsoft Exchange.

This has subtlety.  As is the case with Notes going from MDaemon into Exchange, we cannot place them directly in the folder "Suggested Contacts."  On Suggested Contacts, see this link.  

So we insert into the main Contacts folder (usually under an interface tag of "People" now) and give it the category "Suggested Contacts" to make them easy to find. 

Viewing your Contacts as a List and looking at Categories you'll see them this way:

As the above link documented,  "You can no longer add contacts to the Suggested Contacts folder."

To set this up in our migration tool we added a new option to the user interface.

We also have field confirmation that our migration works with two-byte character systems, such as Chinese:

Tuesday, June 06, 2017

Attachments in Oracle Communication Convergence Calendar Migration to Exchange


The bane of full-state calendar migration, largely because it slows down the entire process and really grinds every gear we have.

So in the Oracle Communication Convergence Calendar server migration where you can extract URLs to attachments -- we insert URLs to the attachment.

We've given it to one site to try out.  If anyone else out there is looking for Oracle Communication / nee Sun Java Calendar, let us know.

The configuration looks like this:

Tuesday, May 23, 2017

Customizing the Sumatra Double Booking cmdlet

There are a simple ways to customize the Sumatra Double Booking cmdlet, and most of them involve a text editor.

Let's look at the messages.txt file to see what we can modify there.

The entire point is to separate out the text sent to meeting organizers to inform them of conflicts.

Separating this from the application gives you the ability to easily customize it for your workplace social environment or to translate it into a different language.

Any text editor will do, and note that there are specified place holders, such as "(1)" for Conference Room Name that are reserved for the cmdlet.

The text in comments tells you the circumstances that generate the message.  For example:

#Message to notify One organizer (the one that came in after the booking was made  -or- trumped by a VIP)

The vips.txt file is the list of the primary SMTP addresses of VIPs who get automatic preference when you invoke the VIPsGetBookingPreference flag.

As you can see from this example, Janis Joplin will get preference over all other users in that scenario.

Finally there is license.txt, the domain-specific license that allows you to execute the cmdlet in your environment.  Copy the license key you got from Sumatra into this file: