Shulou(Shulou.com)06/03 Report--

SFB project experience-71-Project 01 sharing-Exchange 2010-upgrade-Exchange 2016 (with forest) (October 2018)

Project requirements:

1) 2 domain controllers (1 Windows 2003 and 1 Windows 2008 R2).

2) on the domain controller of Windows 2003, other application systems are reading LDAP to obtain user information in AD.

3) the virus is serious in one Exchange in 2010.

4) the enterprise user operating system is Windows XP\ 7\ 8.1\ 10.

5) the office software for enterprise users is Office 2010\ 2013. (not Office 2010 SP2, not Office 2013 SP1).

6) it is necessary to upgrade the domain controller without changing the preferred DNS server and backup DNS server IP address of the client.

7) it takes a long time to coexist with Exchange 2010 and 2016.

8) the enterprise user Outlook client is configured in Exchange cache mode, and the POP3,Foxmail client is configured as POP3\ IMAP4.

Solution suggestion: (if you forget, it will be added!)

1) check whether the domain controller is normal? (DCDIAG)

2) check whether the DNS server is normal?

Nslookup (test A record, test PTR record, test mail exchange record).

3) check the name included in the certificate. (https://mail.contoso.com/OWA)

4) change other applications from 2003 AD reading LADP to 2008 AD reading LDAP.

5) considering that the use of the client will not be affected, an additional Exchange 2010 migration user will be added to kill the Exchange 2010 that is infected.

6) at present, 1 physical machine domain controller is Windows 2003 is too old, and it is ready to upgrade to 1 virtual machine domain controller Windows 2008 R2.

7) in order to ensure that the IP address of the preferred DNS server and standby DNS server of the client does not change, two more virtual machines will be added to replace the domain controller.

a. Add the first domain controller to kill the domain controller of Windows 2003.

b. Add the second domain controller, kill the first domain controller. (keep the computer name and IP consistent with the domain controller of Windows 2003.

8) add 2 sets of Windows 2012 R2 to install Exchange Server 2016 CU10, and use DNS round robin to make high availability.

9) upgrade Office 2010 to Office 2010 SP2 and Office 2013 to Office 2013 SP1 for enterprise users.

10) the certificate contains the computer name of Exchange 2010 and 2016, mail.contoso.com\ autodiscover.contoso.com\ contoso.com.

11) DNS round robin is not recommended for high availability, because anti-spam in the enterprise may not be supported to 2 internal mail servers.

12) if DNS round robin is used, at least 2 public network IP are required.

13) Note that the above configuration for Exchange 2010 in the Anti-Spam Gateway will be used for the Exchange 2016 reference.

14) Note that the port mapping above the firewall for Exchange 2010 will be used for the Exchange 2016 reference.

15) Note that the above configuration for Exchange 2010 on the public network DNS will be used for Exchange 2016 reference.

16) Note that the Outlook Anywhere configuration above Exchange 2016 cannot be configured as mail.contoso.com.

17) Note that the virtual directory above Exchange 2016 cannot use mail.contoso.com.

18) Note that test users need to create 3 new users on Exchange 2010 and Exchange 2016 respectively.

Ex2010User01\ Ex2010User02\ Ex2010User03

Ex2016User01\ Ex2016User02\ Ex2016User03

19) coexistence testing

Ex2010User01 configuration Outlook 2010 SP2

Ex2010User02 configuration Outlook 2013 SP1

Test sending and receiving email between Ex2010User01 and Ex2010User02.

Test sending and receiving email between Ex2016User01 and Ex2016User02.

Test sending and receiving email between Ex2010User01 and Ex2016User01.

Test sending and receiving email between Ex2010User02 and Ex2016User02.

20) Migration testing

Migrate Ex2010User01 to Exchange 2016.

Migrate Ex2010User02 to Exchange 2016.

Test whether Ex2010User01 reopens Outlook 2010 SP2, whether it is normal, and whether it can send and receive email to and from Ex2016User01.

Test whether Ex2010User02 reopens Outlook 2013 SP1, whether it is normal, and whether it can send and receive email to and from Ex2016User02.

Test whether Ex2010User03 and Ex2010User01\ Ex2010User02\ Ex2016User01\ Ex2016User02 send and receive email properly.

21) formally migrate IT personnel testing.

Note:

Please refer to 19) and 20) to test whether the migrated IT personnel are normal, and if so, prepare for formal migration.

22) formal relocation.

Note:

For users with formal migration, please upgrade Office 2010 to SP2 and Office 2013 to SP1 first. Remember! Remember! Remember!

23) modify the Exchange 2016 configuration.

24) kill Exchange 2010.

25) restart Exchange 2016 to test whether sending and receiving email is normal.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.