Do you have the hardware to run Exchange 2019?.If you are going to be using a new namespace, do you have your new SSL certificate or are you using a wildcard?.Are you going to be using the same namespace or a new one? For example, are you going to be using for OWA or ?.Is your forest and domain level on the correct level to support Exchange 2019?.Do you have the correct domain controllers to support Exchange 2019?.Here is a checklist of a few to-do items: When you plan on bringing in Exchange 2019 into your Exchange 2016 environment, there are a few things that need to be done. Too often, clients start to get certificate popups on Outlook or get disconnected. One of the mistakes made by IT admins is bringing in a new Exchange server and thinking nothing bad will happen. Just remember, if you have Exchange 2010 in your environment, you cannot introduce Exchange 2019 until migrations are done to a newer version of Exchange - for example, 2016 - and then decommissioning Exchange 2010. ![]() ![]() ![]() The process is exactly the same for having Exchange 2016 and Exchange 2019 coexist. This can be having Exchange 20 in the same environment or Exchange 20 coexisting or Exchange 20 running in the same environment. Exchange coexistence has been around for a long time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |