Another useful link on #MDaemon migration to #Exchange via Linux

Gentle Soon-to-be-MDaemon-free Migrating Reader,

Ms. Migrations recommends reading MDaemon to Microsoft Exchange migration for real-world experience going from MDaemon on Linux to Exchange. 

This article focuses on email using imapsync (for email, just use imapsync, really) and mentions nothing about calendars, but that of course is what we are here for.

Enterprise #Exchange to #Office365 Calendar Migration -- Now with Sync!

Things do not stand still at Sumatra.

With Exchange to Exchange full-state calendar migrations about to hit beta, we added and are testing Sync in our labs.  In the spirit of how things like email sync works, we've added sync to our full-state Microsoft Exchange to Microsoft Exchange calendar migration.  You get contacts and tasks as a by-product.

A few teaser images. starting with the Sync button (We're still discussing how we're going to make this work):

So the SOURCE Exchange server had this:

Which resulted in this on the TARGET Exchange account (note live meetings and recurrence!):

We leave the TARGET system alone while the SOURCE system evolves (1 additional item on the 27th and a modified appointment on the 18th, and a change in meeting response on the 26th).  After hitting SYNC these changes come in:

This capability will not be in this week's beta, but we'll roll it out as necessary when we deem it stable.

Migrating live calendars into #Exchange -- Manage Delegate Forwarding

Those of you who have been diligently following the workings of the mighty Sumatra bullpen know that we're nutcases about making sure migrations go well.

One thing in a full state migration into Exchange is that you need to turn off Delegate forwarding if you want us to recreate the meeting responses.

So to turn off forwarding for an entire domain, you use Set-RemoteDomain, like this: 

Get-RemoteDomain | Set-RemoteDomain -MeetingForwardNotificationEnabled $false

To turn off forwarding for an individual user use set-calendarprocessing:

Set-CalendarProcessing -Identity user email@yourdomain.com  -RemoveForwardMeetingNotifications $true

In the days of Exchange 2007/2010 you would have used set-mailboxcalendarsettings.

Enterprise-Level Calendar Migration #Exchange to #Office365

Last week (which is like forever in Sumatra Development time) we showed you the interface to our full state Microsoft Exchange to Microsoft Exchange calendar migration.

This week we'll show it working in a video:

This is showing the full state migration keeping recurrence patterns, guest lists, guest responses.  You know, everything that makes your calendar useful in an enterprise environment.  The stuff Microsoft does NOT do in a migration.  The stuff everyone else who claims to migrate calendars glosses over.

If you do not need or want all that utility we have an option that runs faster but still tells you who is supposed to be in your meetings.  Again, the stuff Microsoft and everyone else does not do.

Next week we'll release it to the sites we've got as early betas.

If you need Microsoft Exchange to Microsoft Exchange calendar migration after that, feel free to contact us.

Preview #MSExchange to MSExchange Calendar Configuration

Well  it finally happened,  We got folks realizing that bringing your enterprise calendars from on-premises Exchange to Hosted Exchange was not a trivial matter.

But we at Sumatra have radically simplified it and are giving you a preview of the application.

We are offering options to do a full-state migration or a flat migration which will insert your meetings as appointments in everyone's calendar (it's faster and easier, but it's probably not for your executive level).

Watch this space for more info as it becomes available.

And yes, we could theoretically do a Google Calendar into Exchange / Office 365 migration, but everybody who opted for Google is still too deep into denial to deal with that possibility.

Lone hackers and the calendaring connection

My best Internet read of the last few months has been How a Lone Hacker Shredded the Myth of Crowdsourcing.  

What's the calendar connection in this?  In the lesson that in any sufficiently large group of people (let's say a 1000 user calendar migration) you will see the spectrum of all types of behavior.  And this very much includes destruction for its own sake.

We see things like this in raw calendar data all the time: calendars booked through 2039 (no joke), people who have put birthdays in calendars starting in the 1960's (why?) and of course, during a migration the great conference room attempted land grab.

The lesson: any open door can become an opportunity for malfeasance.

#MDaemon Notes migrating into #MSExchange

We got a request from some friends in Canada for MDaemon Notes to migrate into Exchange.

Now there is a small problem with this.  Exchange Web Services does not support creating Notes.

On the other hand over the last fourteen years we all could have gotten doctorates for our work doing the impossible with Microsoft Exchange.  So we insert the Notes into Tasks.

European #MDaemon Calendar to #MSExchange Migration: Field Notes

Short answer:  Version   4.0.xx of our MDaemon calendar migration tool works.

A site in Germany (thanks, guys!) did the pioneering field work that resulted in some minor fixes for time zone issues (and will result in a few more changes).

But we have confirmed that European time zones in translation, international characters, and non-US date formats are working fine.

And we've added the capability to work with localized MDaemon folders (so Calendar becomes Kalender in a German language pack).

One of our guys put the extra effort in to translate our screens as well (these will change):

So if you folks in Europe want to migrate your MDaemon calendars drop us a line.

Inserting SQL data into Microsoft Exchange

When we say SQL data being inserted into Microsoft Exchange or Office 365, it's through our soda straw view of the world: calendar items, contacts, and tasks.

You can of course write one-off code in Exchange Web Services to accomplish a specific task – but why reinvent the wheel?  Sumatra has been  inserting calendar, contact, and task items into Exchange from legacy systems for the last fourteen years.  We’ve created a tool-set that allows you to read data from your SQL databases and insert them into Exchange. 

Most of our users of this feature are using Oracle as the SQL of choice, but there's nothing specific to that vendor.

We call this the Sumatra Calendar Pump or just the "Pump" if you hear us referring to it in casual conversation.

BES 12 is out

BlackBerry Enterprise Server 12 is out.

We have a long history with BES in calendar migrations, usually as an indicator of permissions issues.

We're not making any endorsements on upgrading except for the main recommendation we always make in a migration: test the snot out of it beforehand in a lab environment and have a back-out plan.  

You're only dealing with something that has an impact on all of your users here.

A few miscellaneous useful links and articles to close out the year

Closing out 2014 with a few Exchange / Outlook related tips.

Really good info in Ways to Avoid Email Tracking.

This includes my favorite advice: Don't even click the UNSUBSCRIBE link.

What these guys are looking for is any kind of response.  You play into their hands by clicking anything.  Best to ignore them.

also -- 

The Best Command Line Replacements for Bloated Desktop Apps gives you some really good tools that are compact and functional.  That we use the exact same philosophy on our calendar migration tools is one of the attractions of this article to me.

and finally --

Adding Sun, Moon, and Stars to Google Calendar.  

Apple iCalendar to Office 365 Migration

Got a request for migrating Apple to Office 365.

It was for 80 users, so not a viable site for us to write a full-state migration.  

Always wanting to put useful information up here we thought we'd sketch how to do small migrations like this on your own.  Since last I looked at iCalServer 1.0.6, Apple Calendar Admin did not make migration an easy thing.

The Quick and Dirty Way

You will need to execute an AppleScript like this one: http://forums.macrumors.com/showthread.php?p=20317282  to produce ICS exports.  We have not tested this script so we cannot  guarantee it works, but you get the idea:  you need to extract your data in some meaningful form.    Next you need to read this file into Outlook via client-side import.  Yep -- one user at a time.

You will lose guest lists, guest responses, recurrence patterns, and live meetings.  Not to mention any resource bookings.  

But it is inexpensive and immediately actionable.

The Right Way

The right way is where we read the iCalendar calendar data store and insert into Office 365 of Exchange directly.  I.e., the right way is server-to-server rather than script-to-client. This also allows users to be remapped, and then inserted into Office 365 / Exchange while maintaining full-state calendar information

This amount of engineering is impossible to justify for small sites.  

If however, you have a few thousand users you need to migrate feel free to contact us.

(Later addition: We did this, as the video shows)

On-Prem #MSExchange to #Office365 Full-State Calendar Migration: Looking for testers!

Folks, we're looking for beta testers for our full-state Exchange to Office 365 (and vice-versa!) calendar migration.

We've got it all there: live guest lists, re-created responses, meetings being actual functional meetings when it's all done.  But we always find the real world is a lot better place to test things out than our labs (however good we've gotten at anticipating problems).

Interested?  Want to discuss for informed consent?  Contact us. 

#Oracle Calendar Server to #MSExchange migration option comparison matrix

Because you asked for it -- a comparison matrix of Oracle Calendar Server to Exchange calendar options.

	FREE	Flat	Partial	Full
Description	Inserts  ICS export as-is FREE	Generates Recurring meetings. Add guests to agendas FLAT	Generates Recurring meetings. Add guests to meetings & sends out proposals PARTIAL	Full state for all accounts FULL-STATE
Migrate Selected Accounts in phases or batches	ü	ü	ü	Big bang
Re-Map legacy accounts to Exchange Addresses	û	û	ü	ü
Adds Appointments, All Day Events	ü	ü	ü	ü
Merge individual occurrences into recurring item	û	ü	ü	ü
Guests added to Current Meetings	û	ü (added to agenda)	ü (added to item)	ü (added to item)
Proposes Current Meetings	û	û	ü (optional, tagged)	ü
Adds meetings you attend	ü(as appointment)	ü(as appointment)	ü (as tentative item)	ü
Responds to Meeting Requests	û	û	û	ü
Archives Historic (Completed) Meetings	û	ü	ü	ü
Re-Books Resources for Meetings	û	û	ü	ü
No Server-Side Install	ü	ü	ü	ü
Migrate to Exchange 2013/Office 365	ü	ü	ü	ü
Email – use imapsync	ü	ü	ü	ü
Uses which OCS Export? Via UNIICAL	ICS	ICS	ICS	ICS
UNDO (back out strategy!)	ü	ü	ü	ü

Exchange On-premises to Office 365 calendar Migrations

One of our long time friends of Sumatra is considering an on-premises Exchange to Office 365 migration and has determined that the lack of a full-state calendar migration is a problem.  All meetings come over as appointments without guest lists or they come in through the long, tedious PST method and there is no way to easily re-map the addresses.

Not that we predicted this coming issue a few years ago or anything.

So the short answer is: yes, we can handle this, keeping the meetings and guest responses live.

Anyone else out there looking to be an early informed consent test subject?

Free #Oracle Calendar to #MSExchange / #Office365 Migration Software for Download

We've made our Oracle Calendar Server (OCS) to Exchange 2013 / Office 365 migration software available for free at this link.

See our previous post for documentation.

This will let you insert ICS exports from OCS from today one month forward.

If that works for your needs, go hog wild in your production systems, we will not mind.

If you want to preserve recurrence patterns and guest lists, you will need a license key from Sumatra.

We wish you successful migrations!

Oracle Calendar Server to Exchange Migration Documentation

The software is coming really soon (like this week or next week depending on final Quality Assurance regressions).

But in the meantime you can view the documentation here.

Recurring appointments in Oracle Calendar Server to Office 365 migrations

We've greatly simplified the migration process for retaining recurrences in migrating from Oracle Calendar Server to Office 365.  This video shows it in action and goes over some of the gory details of matching recurring patterns.

New #Oracle Calendar Server to #MSExchange #Office365 migration tools

Lately we have been getting lots of folks (mainly medium businesses and small universities) contacting us looking to migrate their Oracle Calendar Server data into Exchange better than the current crop of low-end solutions can accomplish.  This means three things:

1. Give us recurring meetings and appointments
2. Please please please make the meetings live post-migration
3. We want to choose solutions that reflect our budgets and business goals (i.e., we do not have a lot of money or time)

OK -- we've heard you and we can do all of that.  You could try to write this at home, but we have years of experience that keep us safe.  

So we've created three new options, the first of which we'll let you download and run if you contact us with your work email and size of the migration.

The application allows you to try out what we refer to as our FREE insertion, we think of it as a trial, but if all you need is the next 30 days worth of calendar data from your OCS, hey -- go ahead and use it in production.

The Free version does not re-create recurrence patterns.  You need to license that in what we call the Flat option, which will also include the attendees in the meeting agenda, like this:

The Partial version will actually RE-PROPOSE all current meetings (i.e., not meetings in the past) so that the meetings are real MEETINGS, not static entries in your calendar.  Post-migration your users will need to respond to these meeting invitations (this is part of the deal for lower cost).  But they're live, functioning meetings.  Like this:

Note that now "Attendees" is active because Jimi Hendrix has invited Janis.Joplin to the meeting and that it is remapped to their new domain.

Clicking Attendees shows us that Janis is Required but we have no response from her yet.

Got questions, feel free to contact us.

This also comes with our selective UNDO which will remove ONLY the data we've inserted.

You can see the current version in action in this video:

Want a convenient summary?  Here you go:

If you want your OCS calendar migration…	Choose this Sumatra OCS Migration option
Free, fast, no frills no live meetings, no recurrence patterns.  No history and only 30 days into the future.	FREE -- Inserts ICS export as-is
Inexpensive, fast recurrence patterns and guests in agendas but no live meetings	Flat-- Generates Recurring meetings. Add guests to agendas
Reasonably priced, fast recurrence patterns and current meetings re-proposed (but not responded to automatically)	Partial -- Generates Recurring meetings. Add guests to meetings & sends out proposals
White glove full state-recreation for an enterprise	Full – Recreates Full calendar state recreation for all accounts

Looking to migrate your email as well?

We have found imapsync is an excellent product for email migrations.

Please see our blog postings MDaemon Mail to Exchange via imapsync and imapsync vs PST: Tonnage and Speed (spoiler alert: PSTs are incredibly slow and inefficient) as well as any other recent email migration postings on our blog to give you an idea how easy and fast it is to use imapsync.

Russian Time Zone Changes and Exchange

The title says it all:  Be aware: October 26, 2014 Russian Time Zone Changes and Exchange

Daylight savings time changes -- the gift that kept on giving.  We only tell stories of the great 2007 US DST shift with fermented beverages in our hands.

Buona fortuna aux nos amis les russes !