Share the pitfalls encountered in the hybrid deployment of Exchange and 21V

Recently, I made a mixed deployment project of Exchange and 21V Exchange Onlin for customers. This project made me a little physically and mentally exhausted. All kinds of pits. Let's take a look at two larger pits together.

Kengichi

Like the picture: after clicking Exchange mix, the pop-up hybrid wizard tool unexpectedly deployed a 21V hybrid wizard tool (at first I thought I forgot to point that my Office 365 organization was hosted by Century Internet, but I came back to check it out), I was also drunk.

The downloaded tools are shown in the figure:

Asked under 21V, only to know that they actually need to download this tool manually, I am also very speechless.

Download address: http://aka.ms/HCWCN

Pit

After downloading the tool, finally finished mixing, then start to migrate mailbox, a little migration, login address unexpectedly ran to the international version, click on the above Office 365 and modify mixed to jump to the international version, hey, can also have a good time to play.

Solution:

After asking 21V Exchange again for 2 days, I replied to an email and asked me to manually modify the web.config file of the local web.config back-end server. (it's a bit of a complete breakdown, isn't it naked BUG?)

The path to the Web.config file is C:\ Program Files\ Microsoft\ Exchange Server\ V15\ ClientAccess\ ecp

The steps are as follows:

1. Navigate to the web.config folder and back up this file

2. Open this file with notepad, search with the keywords "url0" and "url1", and see the following value. If it is https://outlook.office365.com/ecp/, please change it to https://partner.outlook.cn/ecp/ and save it.

Screenshot before modification

Modified screenshot:

Restart IIS after modification is completed