Solved

sbs2003 to Office 365

Posted on 2013-11-20
4
1,176 Views
Last Modified: 2013-11-20
I now there has been a lot written about moving users mailboxes from SBS2003 to O365, however there are a couple of questions that I can't seem to find answers to.

I found this article that steps though the migration process (I am sure there are other articles) - http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx

The above article references this site - Exchange Deployment Assistant  - (http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e) - which allows for the migration of the mailboxes.  I am looking at doing a Cutover Migration.

 
What I am not sure about and would like answered is;
1)  Does the syncing continue after the initial sync, or do you have to manually run it again to bring in email that arrives between the time the initial sync was completed and MX replication has finished?

2) This article (which also covers the Cutover Migration) indicates, under next steps - Implement single sign-on,  which points to (http://community.office365.com/en-us/wikis/exchange/835.aspx)
In this article step 2 is  - Convert on-premises mailboxes to mail-enabled users.

I can't do Single Sign-On with FS.  Therefore do I need to do/is it advisable to do - this step.
I am looking at implementing Dirsync for password syncing.

3) Configuring Outlook.  
     We have a mixture of Outlook 2007/10 - Once we cut the MX records to O365 Outlook will need to be reconfigured - is it just a case of creating the autodiscover canme record?
If outlook does not pick up this autodiscover record, can Outlook be reconfigured manually without creating a new OST file?

I know there is a lot of information here, but I believe in providing everything I know and letting you determine if it is relevant.

You help is very much appreciated.
0
Comment
Question by:bmcollis
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 41

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 39663463
1) yes
2) this has nothing to do with SSO, it is to prevent Outlook related issues after the migration mainly. With SBS 2003 I think you will be fine though, if Im not mistaken E2003 does not have SCP, so the autodiscover CNAME will be the first thing the client hits. You might still need to push some registry settings to prevent Outlook connecting to the on-prem mailbox.
3) The autodiscover CNAME is a must, Office 365 no longer supports manual Outlook config. It still can be done, but it's not as easy as before. Make sure you have all the needed Outlook updates, at minimum these:

•Outlook 2010 must be current to at least the April 2012 cumulative public update (KB2553248).
•Outlook 2007 must be current to at least the July 2012 cumulative public update (KB2596598)

Preferably, isntall these also:

¿Outlook 2010 Nov 2012 cumulative public update (KB2687623)
¿Outlook 2007 Nov 2012 cumulative public update (KB2687404)

2007 needs to be SP3, 2010 SP1.

You will need to create a new Outlook profile/add the new mailbox
0
 

Author Comment

by:bmcollis
ID: 39663517
Thanks vasilcho for the quick response.

Your answer to 1 & 3 are great and the added info on the updates is really appreciated.  I will be adding a line item in my plan to confirm these updates.

In regard to 2.
Unsure what SCP is, but guessing as you refer to the autodiscover CNAME it has to do with Outlook autodiscovering where to connect to.
You indicate I might have to push out registry settings to prevent Outlook connecting to the on-prem mailbox.    If the mailboxes are converted to "mail-enabled users" would this not stop/prevent this from happening, as there would be no mailbox to connect to?

Thanks again for your quick response.
0
 
LVL 41

Expert Comment

by:Vasil Michev (MVP)
ID: 39663550
Yes, that's the idea. You convert them to avoid issues with the clients still connecting to the on-prem mailboxes. Take a look at this article for info on Autodiscover and the registry settings:

http://support.microsoft.com/kb/2212902
0
 

Author Closing Comment

by:bmcollis
ID: 39663856
Thanks for your very quick answers.
Look for additional questions as my project unfolds.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Find out what the Office 365 disclaimer function is, why you would use it and its limited ability to create Office 365 signatures.
This Experts Exchange lesson shows how to use VBA to loop through rows in Excel.  In order to sort, filter, and use database features, there needs to be a value in each column for every row. When data arrives with values missing, code to copy values…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question