Outlook clients cannot connect to the new server.
: Last night I performed a migration install of Small Business Server 2011 from Small Business Server 2003.
During the network part of the migration/sbs console setup (http://filedb.experts-exchange.com/incoming/2010/12_w52/382913/Migration-Wizard-20.jpg
) the Exchange e-mail would bomb with a red x. It would report that to fix the issue, run Fix My Network under Network -> Connectivity in the SBS Console. This would not fix the error, however the client accounts do indeed report that they are under the correct email domain and at 9:30pm last night I needed to press forward. Perhaps I shouldn't have, but there really is no indication of what this part of the wizard does and I needed progress.
Later I successfully moved all the mailboxes to the new server and mail flow was working perfectly to and from eachother and the WAN. I tested this through Outlook Web Access. As a matter of fact, I have everyone use OWA as a workaround until this issue is resolved.
Following moving mailboxes, I attempted to Move all Replicas of the Public Folder to the new server. After redoing the server's certificate, this appeared to run successfully, but after 30 minutes, I noticed that the propogation status window that pops up wasn't doing anything and that the ESM was apparently frozen. I eventually closed the ESM process and attempted again with the same results. Attempts at browsing Public Folders in ESM also freeze ESM.
I see now that even while successfully connected to the OWA, I can browse the public folders hierarchy, but attempts at browing the individual items in the public folders yields "The public folder you're trying to access couldn't be found. For more information, contact your helpdesk."
At this point, I do not wish to move further into this migration until I can resolve this Outlook client issue. Any input would be appreciated.
Some things I have tried:
Specifically, in the Outlook client software, I tried turning on (and have now turned off) "Encrypt Data between Microsoft Office Outlook and Microsoft Exchange Server." I also ran a power shell command that reports that Exchange does not require encryption. So, despite this being one of the few fixes for the problem yielded by a Google search, is it undeniably not the issue here.
I have tried connected with Outlook 2003 and Outlook 2007 clients to no avail.