Featured Post

Three Basic Ways of Dealing with Double-Booked Resources in the Sumatra cmdlet

There are three basic ways of automatically dealing with double-booked resources in the Sumatra cmdlet suDoubleBookedMeetings. You guys wo...

Tuesday, February 19, 2019

Non-mapping contact info in migrations from Zimbra to Office 365

It happens.

You have data in custom contact fields in Zimbra that do not map one-to-one to existing contact fields in Office 365.

So this contact, Horatio Warmonger in Zimbra has info like this:

Note his current "Note:" field in Zimbra pre-migration:

Have no fear -- Sumatra's migration takes all contact data not readily categorize-able in Office 365 and inserts it into the Notes field.

Tuesday, February 12, 2019

Calendar Recurrence Patterns NOT supported by Microsoft Graph and What Sumatra Does About Them

Microsoft is obsoleting Exchange Web Services (which is too bad since it's been working like a champ) in favor of Microsoft Graph (which is too bad since it's.... immature.)

One of the sad consequences of this is that some recurrence patterns for calendar events which can be created in EWS are impossible to create in Graph.

For example:

What does this have to do with the price of tea in San Francisco?

We're in the business of migrating calendars.

When the recurrence pattern isn't something we can re-create we get testy.

We insert in the standard format, hoping that when Microsoft Graph gets its act together to deliver something like this we're going to be seamlessly running.  Even though the results are a little weird on insert you can correct them by opening the series and re-setting in Outlook.

But we do make it easy to find these.

We tag problem recurrences with "ZimbraRecurrencePatternNotMigrated" (this is configurable on a server-basis).  So you can readily find them.

You can easily sort them all together in Calendar List view:

You can also set the color for these categories to find them in your calendar.

Note that in the above example we have the category "ZimbraMeetingsYouOrganize" (yes, the names are configurable on a per-migration basis) to help you find meetings you organize and re-propose them.  Our full-state migration process makes this step unnecessary.  But full-state is also more expensive.

Tuesday, February 05, 2019

Migrate Zimbra Calendar and Contacts to Office 365: US$499

Since 2001 Sumatra Development has been doing full-state migrations of legacy calendar systems, where meetings are functional meetings and guest lists are functional in meetings.

This is our answer to demands for a less expensive, simpler, faster migration path for smaller sites and enterprises that do not need full-state meetings.

If you can migrate your email from Zimbra to Office, you can now migrate your calendars and contacts for under US$500, using the same permissions and similar methods.  No limits on the number of users you can migrate but we cap code at 30 days (we're willing to talk on timing).

This is a fast, simple method for moving calendar and contacts from Zimbra to Office 365.

So Jimi Hendrix's calendar in Zimbra:

Becomes his calendar in Office 365 in a few seconds (as opposed to a PST or an export/import).

Since this is faster, simpler, and cheaper, we do not re-create meetings in this version -- but we do make it easy for you to find meetings you organized and the guest list:

Our experience so far shows this method takes considerably less than half the time and effort on the part of Admins than our full-state solution, and that it is of course much faster than client-side solutions.


Tuesday, January 29, 2019

Conference Room Calendar Migration from Zimbra to Office 365

Our latest version of Zimbra to Office 365 calendar migration is also moving resource calendars fine.

So for instance a Zimbra resource calendar (Room_222), has a schedule that looks like this one week:

Comes into Office 365 looking like this:

Keep in mind this is also server-to-server so it's fast and much less hassle than going via PSTs.

Since this is a fast-flat migration we make this convenient on the side of the end user by including the information that the resource was booked in Zimbra.

Tuesday, January 22, 2019

Remember Exchange 2010?? If you still have it, read on....

A friendly reminder that Exchange Server 2010 End of Support is (Still) Coming.

We don't normally see Exchange except for the current version, but we feel the need to pass on info like this.

Support for Exchange 2010 ends on January 14, 2020.

Tuesday, January 08, 2019

Migrating Zimbra calendars and contacts to Office 365 via the Microsoft Graph API


Microsoft is sun-setting Exchange Web Services (EWS) which we have been using for about 10 years for migrations in favor of Microsoft Graph.  So we're porting our code to the next generation of technology.

We've got Zimbra calendar and contacts going into Office 365 via the Microsoft Graph API in our lab and are looking for a few test sites wanting to move calendars and contacts as next generation early-adopters.  

If you can run imapsync or the Microsoft email migration you can use the same permissions to move calendars for all users server-side with no intervention.

And we've radically simplified our interfaces.

If interested drop us a line via our contact page.

Tuesday, October 23, 2018

Exchange online: Conference Room Provisioning changed to AutoAccept

A heads up for admins who plan to provision new resources in Exchange Online: the defaults will change from AutoUpdate to AutoAccept.  This change will occur on November 15, 2018.

What does this mean? It's another 80/20 rule: depends on the type of resources and if you are a new or existing customer.

For existing Office 365 customers:  
  • 80%: Most of our clients configure resources (rooms, equipment) as AutoAccept. If the user wants to book a room on a particular date/time, Exchange will book it if it's free. 
  • 20%: "Managed" rooms.  Those are the ones only specific users can book, or an admin has to approve. Examples are the Executive conference rooms, HR Interview rooms, the Auditorium, etc.  For those rooms, this will be a problem. 
For new Office 365 / Sumatra's Migration customers,
  • NO IMPACT:  For all migration customers, we recommended you set ALL of your rooms to either None or AutoAccept (depending upon the migration tool). You will replace the defaults.
To check:
Get-Mailbox -RecipientTypeDetails @("Equipment","RoomMailbox") -ResultSize unlimited | Get-CalendarProcessing | Format-Table-Property Identity, AutomateProcessing

See the MS announcement here: Exchange Online - calendar AutomateProcessing changes through PowerShell