The Four Critical Email Capabilities Needed for Day One Collaboration
Posted by Vadim Gringolts, CTO

In the world of M&A, Day One is as critical of a concept as there exists: the first day when two legacy organizations can start acting as one. Effective Day One communication and collaboration between new colleagues using their legacy corporate email environments cannot be overstated. Why legacy? A good question with a fairly simple and common sense answer… there simply isn’t enough time prior to Day One to create and move the entire end-user population to a brand new unified corporate email platform. Therefore, enabling two diverse organizations to start collaborating on Day One via their existing email is an essential first step towards a successful merger or acquisition.

There are four key capabilities that email users in each of the two organizations will need to attain starting on Day One. This article attempts to illustrate them at a high level with some technical details.


Posted on 24.06.2015 09:00:00 | with 0 comments

If you viewed our last post, you’ve now scoped out your mission to move and merge the Active Directory environment from a division of the fictitious company, the Syndicate, into the IMF. However, knowing the scope and requirements doesn’t make your mission any less impossible.

It’s now time to focus on planning, preparing, and executing your mission. Your job is to study the environments, figure out how to bypass multiple layers of security, and make sure you have the proper resources and equipment to fulfill your mission. To increase your odds of success, you’ll develop a plan, test every element and possible variation, and perform detailed walk-throughs. Then, after you’ve accounted for every contingency, you’ll need to successfully complete your mission with a velocity migration.

Are you ready?



Posted on 16.06.2015 09:00:00 | with 0 comments

Acquiring company, the IMF, is buying a division of the Syndicate. Your mission, should you choose to accept it, is to plan out all of the technical aspects of an Active Directory migration and be ready for execution beginning Day One.

No one without a need-to-know in either company can know about this until the acquisition is announced publicly. You’ll be required to set up directory synchronization with the acquired entity but will not be able to establish a trust, because you won’t be permitted that level of access. Many of the sAMAccountNames in the Syndicate environment have different names than those in the IMF environment. There are 5,000 workstations that will need to be migrated – many of which are operated by remote workers who typically only access the corporate network via VPN. All of the technical back-end work must be ready in advance of the migration. You have three weeks to develop your plan and three weeks to perform the migration.

As always, should you, or any member of your migration team fail, you will be disavowed by the CIO. This message will self-destruct in five seconds. Good luck…

So, would you sign the NDA for this fictitious business situation and accept the assignment?


Posted on 21.05.2015 10:00:00 | with 0 comments

When Sunshine Children’s Home of Maumee, Ohio decided to transition from Exchange 2003 to Exchange 2010, they selected Binary Tree’s E2E Complete solution. The entire migration of 788 users was accomplished after-hours, in just one weekend—without disruptions to their current workflow.


Sounds pretty easy, right?  


Posted on 13.05.2015 09:00:00 | with 0 comments

The Migration Impact of Office 365’s Max Message Size Increase from 25MB to 150MB
Posted by
Justin Harris, Senior Solution Architect
Microsoft MCSM: Exchange
Microsoft MVP: Exchange

A lot of customers that I speak with on a daily basis are looking to migrate to Office 365 from a third-party hosting provider. In these types of environments, the hosting provider typically does not provide the rights required to migrate to Office 365 with the New-MoveRequest PowerShell cmdlet. This means that EWS or MAPI are often used as the transport mechanism to copy user mailbox data from the source hosted environment to Office 365.

The problem with this ‘copy’ based migration method is that the largest email message that could be moved into Exchange Online was 25MB. If you tried to move items larger than 25MB into Office 365 those messages would be rejected. As you can imagine – it is not hard to find users that have attachments in their mailbox that are larger than 25MB! Think about all those large PowerPoint slide decks, spreadsheets and videos that you have in “your” mailbox today!


But there is good news…


Posted on 30.04.2015 11:00:00 | with 0 comments

Path: /Blog Name: Blog