{"id":1271,"date":"2012-07-02T09:38:09","date_gmt":"2012-07-02T16:38:09","guid":{"rendered":"http:\/\/blog.brainlitter.com\/?p=1271"},"modified":"2012-07-02T09:38:09","modified_gmt":"2012-07-02T16:38:09","slug":"office-365-transition-notes","status":"publish","type":"post","link":"https:\/\/regroove.ca\/brainlitter\/2012\/07\/02\/office-365-transition-notes\/","title":{"rendered":"Office 365 Transition Notes – transitioning my family was a snap, once I stopped trying to outgeek the process"},"content":{"rendered":"

Well, I had a pretty painful Office 365 transition for wallbridge.com this past weekend. However, I can now honestly say that most of it was my fault<\/strong><\/em>.\u00a0 And the reason is, I signed up for the P1 plan which has no human support (just community\/forum posts) and that I was simply too impatient.<\/p>\n

Basically, between trying to rush DNS and trying to coordinate people (connecting to 6 family members so I could migrate their mailboxes and their phones, was maddening).<\/p>\n

Here\u2019s what I learned, because otherwise the service is pretty slick.<\/p>\n

    \n
  1. Be patient<\/strong><\/u>. When they say something could take up to 72 hours, they mean it. Even DNS.\u00a0 I was furiously proving to them that my DNS settings had propagated to every DNS server I tested against but my domain wouldn\u2019t verify.\u00a0 This is because they have internal processes (and scripts and such) and their own internal systems take as much time as their process does.\u00a0 Lesson<\/strong>: No client migration should start on a Friday night and be expected to be done on the Monday AM.\u00a0 Instead, start the DNS, etc. process a week in advance, get your ducks in a row and then schedule the actual cutover<\/li>\n
  2. You can migrate email in pieces but the deal is this\u2026 all mail needs to go through your old system and then get routed to the new system, if you are moving mailboxes one at a time (you can\u2019t do Office 365, forwarded back to on premise) as there is no way to provision an upstream routing path \u2013 no big deal, but just know this is true<\/li>\n<\/ol>\n

    Why I Did It<\/h2>\n

    Because I\u2019m Bat Shit Crazy.\u00a0 And\u2026<\/p>\n

    While a family SharePoint site collection is in the cards and Lync could be fun, I did it because I\u2019m tired of supporting POP3 for family members. Email on desktops get lost, crappy anti-spam\/antivirus and now they can access ALL (25gb worth) of their email from their phones, webmail and Outlook 2007 or better.\u00a0 Sweet. My time is worth that<\/u>.<\/p>\n

    Settings You\u2019ll Want To Know<\/h2>\n