Outlook is continuously connected and disconnected after Exchange 2007 upgrade to Exchange 2013

The author of the weekend two days for a customer Exchange 2007 to Exchange 2013 upgrade, in the upgrade process can be really all kinds of circumstances ah, just started 1 set as an additional domain control of the IBM server down to identify the raid card, the next day to install Exchange

2013 ready to move the mailbox, Exchange 2013 server and the failure to identify the raid card, at this time on the IBM server is also very disappointed, after constant excitement of information, worship, consulting IBM after the sale, finally the server firmware upgrade finally is the basic environment. Subsequent customer Exchange Server 2007 computer names are used by mail, and customer access to the internal and external network address, OUTLOOK anywhere is also mail, the idea of coexistence for some time eventually burst, direct upgrade to 2013, test 1 hours no problem, Uninstall Exchange 2007, with the idea of not delaying users for the next day. Can be this brings a great risk, but also heartfelt caution to the small partners, the back of the unloading must be cautious. During the test there was also an episode in which Microsoft Outlook.com and my company exchange mails were not sent out and stuck in the queue. But to 139,QQ Mail all sent no problem, but received mail no problem, after viewing queue information, found that the IP address was blacklisted by the international anti-Spam Alliance, and then to the Spamhaus application from the blacklist removed my IP, after a period of time to find out again, Then found that customers in the firewall using a number of IP do Pat to achieve internal Internet access, and then no way to the customer all the public IP address from the Spamhaus application to remove, until now very stable.

OK, start the next morning to the customer on-site observation, found that users are always in the use of Outlook is constantly connected, disconnected, disconnected state, memories of the morning walk when testing everything is normal, Exchange 2007 at the time also everything is normal, immediately began to troubleshoot, in the RPC Log inside to see Prompt user authentication failed, but the user name, password clearly entered is correct. Immediately let friends help to see, the final suspicion is public folder problem, after troubleshooting public folder configuration found also no problem, then began to constantly google change keyword, finally found a Microsoft official KB said can solve the problem.

650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/6E/7E/ Wkiol1v-iu-bbrkmaaclqbhz9ys847.jpg "" 486 "height=" 273 "/>

650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M00/6E/83/wKiom1V-h6WgKE4oAACa6_ 06lvq121.jpg "" 479 "height=" 269 "/>

KB connection for Microsoft: https://support.microsoft.com/en-us/kb/2962915

As described in KB, publicfolder exists as a database at the time of Exchange Server 2007, but in Exchange 2013, Publicfolde is in the form of a mailbox. So after we upgrade successfully, we delete the public folder database for Exchange Serve 2007, but in the Active Directory schema, there is also a connection to the old Exchange Server 2007 publicfolder. Outlook keeps trying to communicate to the public folder in Exchange Server 2007, and Exchange Server 2007 has already uninstalled exchange, so there is a constant failure to retry. So what we need to do is to remove the point of Exchange Server public Folderde in the Active Directory schema as described in KB.

1. Log on to the domain controller, open ADSIEdit, connect to the configuration

2. Locate Domain.com/configuration/services/microsoft exchange/org/administrative groups/exchange Administrative Group ( FYDIBOHF23SPDLT)/databases

3. Right-click the database directory and Tap properties

4. Clear the msexchhomepublicmdb value, set to "not set"

650) this.width=650; "title=" image "style=" border-top:0px; border-right:0px; Background-image:none; border-bottom:0px; padding-top:0px; padding-left:0px; border-left:0px; padding-right:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/6E/83/ Wkiom1v-h6bqav6caaiazqxjplc043.jpg "" 462 "height=" 398 "/>

5. Set up other databases as well as the above actions

After Setup is complete, the client can return to normal.

Finally, summarize the steps for Exchange Server 2007 to upgrade Exchange Serve 2013:

1. Database backup, System state backup

2. Upgrade Exchange Serve 2007 to SP3, SP3 upgrade with SP3 CU16 patch (previous test found no CU16,PBF migration will be problematic)

3. Installing Exchange Server 2013

4. Old server with legacy record connection

5. Set up individual virtual directories for Exchange Server 2013, using mail logging

6. Set the legacy record of the old server, set the Send connector for Exchange2013

7. During coexistence, use the client, OWA Test MAPI, Outlookanywhere test 07, and 13 to access the normal

8. Move mailboxes to Exchange SErver 2013

9. Move PBF to Exchange Server 2013

10.Exchange 2013 use test (send and receive mail, intranet connection, ActiveSync, Ooutlookanywhere, OWA)

11. Turn off Exchange 2007 to test to see if Exchange Serve 2013 is healthy

12. Delete the Exchange 2007 mailbox database, the PBF database

13. Uninstalling Exchange 2007

14. Observe the user's use

I first do Exchange Server 2007 to Exchange Server 2013 upgrade migration, there may be some local considerations are not too thoughtful, you can see my brother's article, the environment a lot of advice to my brother, thank you.

Outlook is continuously connected and disconnected after Exchange 2007 upgrade to Exchange 2013