Planning and migrating a small organization from Exchange 2007 to 2013 (Part 8) :: Migration & Deployment :: Exchange 2013 Articles :: Articles & Tutorials :: MSExchange.org:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part8.html

Next up is to prepare our Exchange 2007 for the upcoming migration to Exchange 2013.

Go into Server configuration, mailbox, check the mailbox database properties.  (Right mouse click on properties)

Check the client settings tab and check to see if there is a default offline address book.  There should be.

You shouldn’t need the below PowerShell command:

Get-MailboxDatabase | Where {$_.OfflineAddressBook -eq $null} | Set-MailboxDatabase -OfflineAddressBook (Get-OfflineAddressBook | Where {$_.IsDefault -eq $True})

If you see no offline address book there, I’d say step back and see what else is screwed up in this Exchange deployment because it honestly should be there.

Next up we need to raise the domain functional level in AD

Raise Domain Functional Level:

For Exchange 2013 sp1 we need to be at least Windows 2003:  http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx

Ensure that there are no Windows 2000 servers around in the domain.

Go into Administrative tools, then into active directory users and computers. 

Right mouse click on the domain name, then raise functional level.

When you are done you should be at a server 2003 functional level

 

Remember this is the time to make sure we’ve updated our Outlook clients:

To recap, the update levels we’ll need to achieve are as follows:

  • Outlook 2010 Service Pack 1 with at least the November 2012 update (Build 14.0.6126.5000 or higher)
  • Outlook 2007 Service Pack 3 with at least the November 2012 update (Build 12.0.6665.5000 or higher)

No Outlook 2003 is supported on Exchange 2013.

Next confirm our IIS is set to go.  Launch the IIS manager and scroll to the SBS Web applications.  Now click on RPC.  Windows authentication should be enabled and ready to go.

Again, if any of these settings are not already there, you may want to step back a bit and review if this setup is healthy.

Lastly before we are ready again to deploy Exchange 2013 sp1 on 2012 R2, let’s see if there are any other third party software we need or is not yet ready to support our deployment.

BES server?  Yes or no?

Exchange disclaimer software?  (I use policy patrol from RedEarth software – http://www.policypatrol.com/

Antivirus?  Support Exchange 2013 sp1 yet?

Blogging my way (starting over) through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at – http://www.thirdtier.net/enterprise-solutions-for-small-business  and check out our new project the ASP http://www.thirdtier.net/2014/03/smbkitchen-update-asp-project/

 

Comments are closed.