BinaryTree

Blog-Header-(2013)-FINAL-(1).jpg

Time to Get Ready for Notes Archive Migrations to Exchange Archive Mailboxes
Posted by Richard Dean, Principal Consultant

Do your IBM/Lotus Notes archive databases reside on file servers, or perhaps on different Domino mail and application servers, or locally on user workstations? If this rings true for your enterprise, how can you get all these archive mail databases centrally located and ready for migration?

Notes-Archive-Migration-02.jpg

READ MORE >>

Posted on 26/02/2015 9:00:00 | with 0 comments


Posted by
Justin Harris, Senior Solution Architect
Joe Sharmer, Team Lead Senior Solution Architect (N. America)

 


Here’s the news: Microsoft has increased the size of messages that can be migrated from Exchange on-premises to Office 365…from 25MB to a whopping 150MB!

According to a January 12th blog post, Microsoft announced that:

“We now allow messages up to 150MB to be migrated to the service. The change is available immediately to all customers and is published as a new limit in the Exchange Online limits page in the Office 365 service description. This change enables customers with large messages to easily migrate their existing content to the message.”

E2E-Complete-Migrating-Mailbox-with-104MB-File-to-MS-Office-365-(1).jpg

Great News...Right?
 

READ MORE >>

Posted on 11/02/2015 9:00:00 | with 0 comments


Mailbox Copy vs. Move – Don’t Let This Dilemma Get in The Way of Your Exchange Migration
Posted by Vadim Gringolts, CTO

When considering an Exchange migration, it’s important to understand there are two radically different approaches to migration from the legacy to the new platform:

  • Creating brand new mailboxes and copying legacy content into them
  • Or moving legacy Exchange mailboxes in their entirety to the new environment
While few administrators start out by considering these alternatives, I’d like to highlight the importance of proper evaluation of these two very different approaches.


READ MORE >>

Posted on 13/01/2015 9:00:00 | with 0 comments


Moving Local Archives During a Notes-to-Exchange Migration
No Problem…With a Little Self-Help From Your Friends

Posted by Joe Sharmer, Team Lead Senior Solutions Architect


A lot of enterprise clients are moving off of Lotus Notes and onto Microsoft Exchange. One of the challenges they face is dealing with the abundance of local Lotus Notes mail archives that users have on their desktops. How did this occur? When using Notes, it’s very easy for users to create a local archive and simply copy their emails into that database—right on their desktops allowing users to easily bypass mailbox size quota limits. Sounds pretty simple and convenient, right? But what do you do with all the Notes mail on individual users’ desktops when the entire enterprise is migrating to Exchange?

The challenge starts with understanding the volume of Lotus Notes data that could be stored on the user’s desktop computer.  Each user may have upwards of 50 GB worth of email data stored locally and unless you have robust email analysis software, you probably will not know how much data each user has in their archive.  So what should you do?

READ MORE >>

Posted on 19/11/2014 9:00:00 | with 0 comments


Life Before Availability Service Sharing
How to Address Free/Busy Coexistence Between Microsoft Exchange 2003 and 2013

Posted by Val Vasquez, Principal Solutions Architect


In my previous blog post, I discussed how you can utilize Availability Service sharing to set up Free/Busy coexistence between your source and target forests. Now, I must reveal there’s a catch—that method only works if all of the elements in the lookup chain support the Microsoft Exchange Availability Service. What that means is your end users must be using Outlook 2007 (or greater), have their mailboxes on Exchange 2007 (or greater), and perform lookups against a mailbox in a different forest hosted by Exchange 2007 (or greater), as well.

What if your company is still on Exchange 2003 and using Outlook 2003 when you are migrating to Exchange 2013? Luckily, there is a Microsoft process available for this exact scenario. While it does involve making changes to your source environment, it will deliver the best experience for your users, and is very similar to the process I described in our earlier blog post.


 

READ MORE >>

Posted on 29/10/2014 8:50:36 | with 0 comments


Path: /Blog Name: Blog