Facebook Twitter LinkedIn YouTube E-mail RSS

Lessons Learned in Migrating Emails to Office 365 from Exchange On-Prem

share save 120 16 Lessons Learned in Migrating Emails to Office 365 from Exchange On Prem

offline hero 300x168 Lessons Learned in Migrating Emails to Office 365 from Exchange On Prem

This is the second post in my two-part series about best practices and “gotchas” for migrating emails to Office 365/Exchange Online. In this post we’ll look at the lessons learned while doing a Hybrid Exchange migration, a process we first covered in this post.

  1. It is a good idea to have your MX record pointing to Office 365 only, for many reasons. But be careful and make sure that if your organization uses a domain name like company.lan or company.local, keep in mind that in order for Directory Synchronization to work properly, and hybrid mail flow, that you will have to add an internet rout-able domain (.com) to your AD and assign that domain as your users’ UPN (User Principle Name). Otherwise you will run into problems with mail flowing to your on-premises mailbox after changing the MX record.
  2. As a part of the setup, the Hybrid configuration automatically sets up the outbound and inbound connectors to allow for mail flow to occur on-premises to Office 365. The Hybrid Configuration wizards will initially setup these automatically, but something to remember is to change these connectors to use Opportunistic TLS vs. Forced TLS that is originally set on. These settings can be changed from the Exchange Online Admin portal under Mail Flow, and then Connectors.
  3. Mail flow to the on-premises organization also may be stopped because of the name of the server displaying on the Exchange Servers Banner from an EHLO command. By default, the Hybrid configuration wizard will put the external FQDN of your Exchange Server on the internal receive connector. So when Office 365 connects via that connector, if the banner names don’t match, it will put a stop on all traffic being sent to that connector, i.e., all on-premises mailboxes.
  4. In case there’s a need to setup UM on a Lync on-premises server, make sure to add the hosted UM server as EXAP.um.outlook.com, and make sure to setup the custom domain name in Office 365 to be authoritative. This can only be done by using PowerShell with the Microsoft Online or Windows Azure AD module installed.
  5. Use the Exchange Online Portal to initiate Mailbox moves rather than using the on-premises Exchange Server to do the remote mailbox moves. This provides more insight on the status of mailbox moves, and will display any errors more easily by doing it from the Exchange Management Console on-premises.

These are the best tricks I’ve gathered so far in the migrations I’ve completed for various GNet Group clients. What other best practices or “gotchas” have you found helpful in Office 365 migrations?

 

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

Email Migration to Office 365 Using a Hybrid Exchange Server Configuration

share save 120 16 Email Migration to Office 365 Using a Hybrid Exchange Server Configuration

This is the first post of a two-part series about best practices and “gotchas” for migrating emails to Office 365/Exchange Online. Usually the two options that come to mind for email migration are:

  1. Cutover Migration
    • In this approach, every mailbox and user is moved to Office 365 at once
    • The challenge here is that there is downtime for emails, and in today’s connected age, it’s just not practical to take this approach
  2. Hybrid Migration
    • This approach is the most widely-used approach
    • A Hybrid Migration makes sure there is minimal to no downtime for emails
    • This approach also allows migration of specific users or sets to Office 365

We’re going to focus on the more widely-used approach of a Hybrid Migration.

O365 migrate 300x99 Email Migration to Office 365 Using a Hybrid Exchange Server Configuration

Read more…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
1 Comment  comments 

The Cobra Effect in BI: Part 3

share save 120 16 The Cobra Effect in BI: Part 3

In my previous two posts I have tabled the concept of the Cobra Effect in BI and taken a closer look at Excel spread marts—the Cobras of BI, and the incentive EDW, aka the single version of the truth.

This week, let’s walk through the journey of creating and rolling out this single version of the truth. Will the EDW incentive prevail over Cobras of BI?

cobra3 300x201 The Cobra Effect in BI: Part 3

King Cobra Snake, credit: Flickr user Michael Allen Smith

Read more…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

The Cobra Effect of BI: Part 2

share save 120 16 The Cobra Effect of BI: Part 2

Last week we started to look at the concept of the cobra effect in BI. This week I want to dive in further and explore exactly what the cobras are in the case of business intelligence.

cobra2 300x224 The Cobra Effect of BI: Part 2

The Cobras of BI or the Excel spread mart: Within each organization, groups of analysts spend endless hours of manual labor producing reports in Excel. A large part of this manual effort is expended in gathering, massaging, standardizing, grouping, segmenting and loading data from a myriad of systems into Excel. Let’s call this first part data consolidation. The remaining effort is spent in creating calculations (several layers at times), Pivot tables, charts and graphs to present and make this data consumable by end users. In this process of producing reports, analysts also conduct analysis, albeit limited but crucial to producing insights for decision making. Let’s call this second part freedom of analysis and insights.  Read more…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
No Comments  comments 

The Cobra Effect in BI

share save 120 16 The Cobra Effect in BI

The cobra effect occurs when an attempted solution to a problem actually makes the problem worse. I came across this term in a Freakanomics podcast by Stephen J. Dubner and Steven D. Levitt. The term is used to illustrate the causes of incorrect stimulation in economy and politics. There is also a 2001 book with the same title by Horst Siebert, a German economist and professor.

By the way, I am an avid listener and follower of Freaknomics. I am amazed at their ability to combine research, insights and the fine art of storytelling. It’s an invaluable resource for BI & analytics professionals as we help organizations build data-driven cultures.

The term cobra effect began at the time of British rule of colonial India. The British government was concerned about the number of venomous cobra snakes in Delhi. They offered a reward for every dead cobra that was brought to the government leaders. Initially this was successful as a large number of snakes were killed for the reward. Eventually, however, enterprising locals began to breed cobras for the income. When the government became aware of this, the reward program was scrapped, and the cobra breeders set all their cobras free. As a result, the wild cobra population only grew. The apparent solution for the problem made the situation worse.

Indiancobra 300x214 The Cobra Effect in BI

The same problem has happened with rats in Hanoi, Vietnam and feral pigs in Fort Benning, Georgia. In each case, incentive seekers came up with creative ways to maximize their results – and pest populations grew. Incentives don’t always work out the way we expect them to.

So how does this relate to BI? Are there Cobras of BI? Read more…

 
 Share on Facebook Share on Twitter Share on Reddit Share on LinkedIn
2 Comments  comments