Sumatra Undo in Action

Ever since high school film strips we've been convinced that visual aids are the most effective.

And ever since college we've been convinced that designing a software system without a back out strategy is just darned irresponsible.

So we combined both of these lessons in our video of Sumatra's UNDO capability in action.

Inserting holidays into hosted Exchange without an Outlook client

Holidays.We've been doing them server-side for years now.
So extending Decaf to insert holiday files was not too much of a stretch.
Since we focus on migrating OCS to Exchange, we used the relevant parts of their ICS format for our template.
Create a text file using this template to insert holidays:

BEGIN:VCALENDAR BEGIN:VEVENT TRANSP:TRANSPARENT SUMMARY:New Year’s Day STATUS:CONFIRMED LOCATION: Any time zone in your system DESCRIPTION: No work day DTSTART;VALUE=DATE:20120101 DTEND;VALUE=DATE:20120101 END:VEVENT END:VCALENDAR BEGIN:VCALENDAR BEGIN:VEVENT TRANSP:TRANSPARENT SUMMARY:Holiday on the 14th STATUS:CONFIRMED LOCATION: Company-Wide DESCRIPTION: Suppose Jan 14 was a holiday in your company DTSTART;VALUE=DATE:20120114 DTEND;VALUE=DATE:20120114 END:VEVENT END:VCALENDAR

This will insert server-side and happen on the given dates, regardless of time zone (!) So a user in the USA or Canada need only put one holiday file together and can use it for all users.

And you go here to insert it.  Our usual restrictions apply.  Of course UNDO works for this.

As always, any feedback is welcome.

We're debating whether to include an option to insert for all users on a domain -- which is certainly possible but we're a little leery if it's in demand.

Sumatra Decaf: Insert Oracle Calendar ICS into Hosted Exchange

We made our street cred on full-state migrations server-side to server-side.

But there have been folks who either want to try out just ONE user or go for a simpler migration that trades off full-state migration for something faster and simpler.

This is the reason we've done Sumatra Decaf which we're now happy to open for general inspection at http://www.sumatraresourcewatch.com/decaf

A few things to note:

• This works only for hosted Exchange (e.g., Live at Edu, Office365, BPOS)
• We keep track of the domains that insert and limit it to 5 accounts on that domain by default
• We've geared this to the ICS exports from Oracle Calendar System. Others MIGHT work, but they are a lower priority to us. Each ICS upload is limited to 1 Mb and it inserts only from Today (i.e., the date you are inserting) forward.
• In a few days we'll show you how to use this to insert holidays server-side.
• Read the Help PDF at the site for more information.

Creating All Day Events with EWS in Office365

You might remember our recent post:

http://calendarservermigration.blogspot.com/2010/12/ews-outlook-live-exchange-release.html

about the head trip that we went through with migrating all day events into Exchange using EWS and how weirdly the display was different between versions of Outlook and OWA.

Well we're adding this to tell you it's the same head trip in Office365 (no real surprise there but we just feel the need to document it).

Web-Based, one-step Oracle Calendar to Hosted Exchange migration

This is an early look at something we call Sumatra Decaf and a call for informed consent volunteers.

We've built a really good business out of migrating calendars full-state into Exchange.

But some folks do not need the whole magilla and are just looking for the simplest way of getting data from your legacy system into Exchange in a "good enough" fashion. So we've done that as well.

So yea, we have server-side ICS insertions to Hosted Exchange.

Let's take a look at Puffy Amiumi's calendar in OCS (also in Japanese Standard Time)

Use UNIICAL to export it and then read it into our web-based application (shown here in Alpha):

and in Outlook Web Access on Live at Edu, the results look like this:

Notice we're prefacing them with _TEST_ for the moment to make sure it does not get into the wild before we're ready.

The 5:00 PM Meeting at which Puffy is a guest looks like this in the agenda so that you know who's organized it and who else is supposed to be there.

Quick, simple, and executable without a lot of prep time.

Now our other option for a migration remains: longer, planned, and full-featured.
We're looking at how we want it to evolve and would welcome some input from you folks.

Outlook Live URL changes

Quoting from an email Microsoft sent, we want to remind you about upcoming URL requirements for accessing Outlook Live. Due date: June 30, 2011. It's already been extended so now is a good time to get it all done.

URL Changes

URLs that go directly to Outlook Web App, such as http://outlook.com or http://outlook.com/owa should be changed to go to http://outlook.com/ - for example, http://outlook.com/contoso.edu. To prepare for URL changes:

Inform your users of the change so that they can update any bookmarks they may have Inform your support desk of the upcoming changes and how to help users use the new URL Update any related links on Web pages and in documentation

If you are using the URL http://outlook.com/ecp to access the Exchange control panel management interface, you will also want to modify that URL to look like this: http://outlook.com/ecp/?realm=contoso.edu.

Single Sign-On Changes

Single sign-on solutions using the Live@edu SSO toolkit must make the following changes:

Update the Outlook URL in the web.config file as follows: Change: https://outlook.com/owa”> To: https://outlook.com/edu”> Custom solutions have to make this change also, though the location will vary. In addition, we have seen some cases where Live ID removes URL parameters, resulting in undesired behavior. To mitigate this issue, we advise that all single-sign-on solutions add the parameter exsvurl=1 as a setting in the URL. This setting will force the URL parameters to be preserved. Typically, the setting is appended to the end of the redirection URL and preceded with an ampersand, like this: https://outlook.com/edu&exsvurl=1.

More Zimbra 6 to Exchange 2010 / Cloud

So I promised you could see the before and after of contacts and tasks. Here they are.

Migrates to Exchange like this:
Tasks come over with very few problems. What in Zimbra looks like this

Becomes this in Live @ Edu. It could just as easily be in Outlook -- but we're grooving on someone else keeping an Exchange server running for a change.

One thing to keep in mind: Migrating to Live @ Edu is slower than migrating into on-premises Exchange (by a factor of about 7). We're pretty sure it's going to be that way for the foreseeable future.

Zimbra 6 to Exchange 2010 calendar migration

It's been a year since Yahoo sold Zimbra to VMware (which reminded me of some of the scenes from prison movies involving cigarettes).

And now is when people are starting to contact us en masse asking if we can move their calendars from Zimbra 6 to Exchange 2010.

Yes, we can.

The way we do it is really convenient. We open the mySQL database and read all the calendar, contact, and task data directly and insert it into Exchange using our usual, field-proven process.
You heard that right: NO user intervention, one spot for an Admin to pull the data and insert the data.

So let's take a look at the BEFORE and AFTER.

Jimi Hendrix's calendar on Zimbra 6.0.7 looks like this:

After extraction and insertion into Live @ Edu it looks as we would expect:

Note, the tentative meeting is tentative, the accepted is accepted, and the declined doesn't appear because that's the way Exchange works. We keep all recurrences and the meetings are completely LIVE on live @ Edu.

But wait -- there's more.
Contacts and Tasks come along for the ride too.

But we'll show you those in a separate posting.

More on Live @ Edu vs. On-Premises Exchange Speed Differential

		Live@EDU		On-Premises
Object Count		7675		7585
Total Time (seconds)		4193.25		597.01
Total Time (minutes)		69.89		9.95
Average Insertion time		0.55		0.08
Mode		0.41		0.05
Median		0.44		0.05
Max		9.29		3.5
Min		0.10		0.03

So our latest tests on inserting calendar items into Live@Edu vs. inserting into on-premises Exchange gives us a 7:1 time ratio.
That is: it is currently about seven times faster to migrate calendar data into your own Exchange server than it is to migrate it to Live@Edu. We've seen the same data set go far longer, but this is a good estimate to use in your planning purposes. Also yesterday another real-world site reported a figure similar to the one we found.
Just so you know.

Asynchronous Programming

Earlier this week I went to a Microsoft Firestarter Event on Windows Azure. The event was run by a Microsoft Developer Evangelist Jim O'Neil. Jim's talks always inspire me to tweak Sumatra's code bases, ensuring we take advantage of as much of the emerging Microsoft technology as practical. One segment of the day talked about patterns and practices, specifically, the use of asynchronous communication when interacting with cloud (and the web).

They told us about a new Asynchronous Programming module (http://msdn.microsoft.com/en-us/vstudio/async.aspx.) I'm very interested in this because many customers in Sumatra's Education market segment are migrating to Exchange in the Cloud -- Microsoft's
Live@EDU. When inserting lots of data, the variability of "network speed" makes insertion times difficult to predict. We explored changing the Sumatra code to run on multiple threads, but concluded it added more complexity to the code and didn't address the underlying bottleneck: network latency.

What I find interesting about this CTP is that the new async calls have the potential to work around latency issues without increasing code complexity. We'll be testing this in our labs in the next few weeks!

Putting Holidays into Live @ Edu Server-Side

We tested our holiday insertion code on Live @ Edu and a list of holidays like this:






Note that this is an All Day Event (and you can specify if the time is to be shown BUSY or FREE):

While this is an appointment we've put into every calendar without any muss or fuss. You could use the same technology to do that for anything else you want (Shareholder's Meetings, Fire Drills, as your business and imagination dictate).

Any of you who have been through a migration with us know why we keep the "(Migrated)" tags, but you can decide to not use them.
This is scriptable so you can create holidays as you provision users if you have an automated system for so doing.


A few other things to keep in mind:

• This runs as an EWS application from a 32-bit workstation. So all your credentials are completely under your control. If there's demand to run this as an online service we'll listen.


• We take the default time zone of your server for all insertions. If you have users in multiple time zones and want to do this contact us -- that would be a different version.


• You can specify a single user, a list of users, or an LDAP query to handle your insertion.

Migrating from Exchange to Live@Edu - NOT a no-brainer

We've been getting a lot of email from people who are weighing the decision between on-premises Exchange and Live @ Edu. We got worried when we started picking up on two assumptions that a lot of them are making: that both Live @ Edu and on-premises Exchange 2010 are functionally equivalent and that should you decide to move between them it is a simple, no-brainer activity to shift from on-premises Exchange 2010 to cloud-hosted Exchange later on.

Disillusionment Time!

There are two things you need to be aware of at the outset:

1. Live @ Edu has limits compared to on-premises hardware (and this affects migrations disproportionately)
2. Going from on-premises hardware to Live @ Edu is just as major a migration as going from (say) Oracle Calendar Server to Live @ Edu.

We've dealt with the first issue already in this blog, including some differences from a coding perspective.
Now let's talk about going from on-premises to Live @ Edu:
First the voice of experience, in this case a user going from E2K7 to Live @ Edu:
http://nzschooltech.blogspot.com/2010/04/migrating-from-exchange-2007-to-liveedu.html
Yes, you CAN devise and execute your own migration process. But but do not plan on it being either simple or fast.
Second, we have the voice of authority, Microsoft, warning about this:
http://outlookliveanswers.com/forums/p/519/4961.aspx#4961
So Microsoft is working the IMAP mail migration angle (be sure to test how long it takes), but calendars, contacts, tasks are not included.

Third, we have the voice of Sumatra:
If someone is moving your calendars, ask if the meetings come over live with guest lists and responses intact.
Our general recommendation: If you're looking at migrating from a legacy system and considering going into Live @ Edu sometime down the road -- all indications are that it is better to make your end-point decision FIRST. It will save you tons of work down the road.

Outlook Live and Outlook On-Premises Differences

You know.... there's a bunch of these differences between Outlook live and Exchange on-premises.
And like discovering land mines you're only going to know when you step on one of them.
Such is the case with Throttling Policies and the EWSFindCountLimit.
What does this have to do with calendar migrations? Just in our UNDO function (a prudent safeguard which many of you seem to find comforting).
Our QA team discovered weird behavior in Live @ Edu that does not exist in on-premises Exchange when we were trying to UNDO several test insertions at once. The default limit in ESWFindCOuntLimit is 1000 items (and this in our case includes things in the Deleted folder).
So some of our higher-end users were not being UNDO-ne.
We're fixing that and preparing for the next landmine.
Stay tuned.