“We all know how stellar the Coherence migration teams are, and it is hard to believe, but they have upped it a notch. This team not only has delivered high quality, consistent work in a political nightmare environment, but they have uncovered new business. This is the synergy we have been speaking to for years – how these guys as technical experts can bring in additional products and services because they are so highly technically-skilled.”
Anyone who’s been in AD / Email migration business long enough, can appreciate Exchange cross-org (or on-prem to Online) Federated Calendar sharing feature. Old days
With the arrival of Outlook 2016 and Migration Manager adding its support starting with CPUU 5.6, it now has some additional parameters which I wanted to cover in this article.
This case is another one of those countless issues which reminds you every day that no matter how long you have been doing migrations you can never rest on
During computer migration upon it joins the Target Domain, you may experience the following error trying to log in: “The security database on the server does
I keep running into this error in some customer’s environments when installing QMM (DMM) OS prerequisites requiring Windows Update service, such as Windows Management Framework
Part of PF migration challenge is that Exchange 2013 CU7 hierarchy mailboxes cannot exceed 100 GB as prescribed by Microsoft (https://technet.microsoft.com/en-us/library/dn594582(v=exchg.150).aspx) This is the absolute maximum,
In this post I wanted to highlight some changes in the mailbox move logic of QMM MAgE Calendar Sync compared to the legacy CSA (Calendar
My resent project involved some non very standard migration requirements that led me to some interesting discoveries which I wanted to share in this post. In
Here is the real-world scenario that I was recently working on: QCS currently runs AD and Legacy F/B Sync. QMM DirSync comes in, QCS AD
