Small Business Susan

SMBKitchen: Looking at public folders

Next up … http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part3.html


Now up public folders….


Quoting again…


“Public Folder Infrastructure


In previous versions of Exchange, a public folder migration could certainly be a pain, but it was a rather straightforward procedure (unless you needed to troubleshoot) as the key method was to replicate the current public folders to the new Exchange servers, then remove the original replica.


With Exchange 2013, we’ll migrate our Public Folder infrastructure to Modern Public Folders. This means the approach is different, and for larger organizations has additional planning concerns due to the removal of the multi-master model, that while troublesome, allowed users in different sites to access a local copy of the Public Folder they were using.


Our small example site doesn’t have such concerns, but we’ll take a quick snapshot using the Exchange Management Shell to ensure we know the sizes we’ll need to migrate, and in the case you have multiple Public Folder databases, list the replicas.


Get-PublicFolder -Recurse `
|Where {$_.Identity.ToString() -ne “\NON_IPM_SUBTREE”} `
|Select Identity,@{N=”Replicas”;E={[String]::Join(“;”, $_.Replicas)}}, `
MailEnabled,@{N=”Size MB”;E={(Get-PublicFolderStatistics $_).TotalItemSize.Value.ToMB()}} `
|Export-CSV .\PublicFolderOverview.CSV -NoTypeInformation


I personally think that SMBs have more complications in public folders as we’ll stick things in there and forget why we need it.


“If you don’t use Public Folders, or can easily move away from them, there’s no requirement to implement them with Exchange 2013. As the Outlook 2003 client is no longer supported, there is no client dependency.


Clients


We’ve collected data about our Exchange Server and some high level information about the mailboxes on it that we’ll feed into the design, so now we’ll look at what’s connecting to Exchange 2007 and see if we’ve got any work to do.


Windows Outlook clients supported by Exchange must meet minimum requirements, and for Exchange 2013 that means they must be either:


  • Outlook 2013 (Build 15.0.4420.1017 or higher)
  • 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)

Remember, Exchange 2007 supports clients as old as Outlook 2002, but in general, we’d expect the majority of older clients to only be as old as Outlook 2003.


Exchange 2013 also supports Mac clients, including Outlook 2011 and Entourage Web Services addition. Apple’s Mac Mail also connects, and naturally you may expect to find ActiveSync, POP3 and IMAP clients if these protocols are enabled. Outside of Exchange, we also have BES users in our environment; however we’ll collect information about these separately when we examine the BES server in a later section.”


Let’s make this really really clear here.  You need to be on outlook 2007 or higher.  Outlook 2010 and higher is really preferred.  You can’t use Outlook 2003 to connect to Exchange 2013.


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