Notes for installing ExchangeServer2016 on Windows server ., Exchangeserver2016

Notes for installing ExchangeServer2016 on Windows server ., Exchangeserver2016

In the past two days, I tried to install ExchangeServer2016 on Windows Server and encountered two headaches. Fortunately, after several searches and exploration, I finally solved the problem and shared my experience, for reference. The installation of ExchangeServer2016 on Windows Server is no longer the same as the previous installation system. After the installation program is started directly, click Next to complete the process. In some cases, you need to set ExchangeServer2016:

1. First, the ExchangeServer2016 installation requires the domain environment and the UCMA4.0 Runtime library to be installed in advance. This issue is okay and you can set it yourself. Otherwise, the rule check won't go through.

2. First pitfall:You cannot install the original version of ExchangeServer2016 directly on Windows server. You must use ExchangeServer2016 CU3 or a later version., CU3 is cumulative update 3. I chose to directly install cu5. If the original version is used, it will be stuck in the Rule Check phase and requires the system to install the desktop experience. However, after Windows Server is installed with GUI, the server adding function does not have a desktop experience, which means a dead end. Therefore, you must use a version later than CU3.

3. ExchangeServer2016 CU3 is actually a complete version, similar to "ExchangeServer2016 with CU3 ". A newbie like myself thought it was just an update package at the beginning. In fact, just download and install it.

4. after crossing the first pitfall, you can go through the Rule Check phase to enter the actual installation phase. There are 13 phases in the installation phase, and there is a pitfall in the 7th phase that will cause errors, the error text is similar to this (I will not organize the format ):

--------------------------------------------------

Error: Run "$ error. clear (); Install-ExchangeCertificate-WebSiteName "Exchange Back End"-services "IIS, POP, IMAP "-DomainController $ RoleDomainController-InstallInTrustedRootCAIfSelfSigned $ true if ($ RoleIsDatacenter-ne $ true-And $ RoleIsPartnerHosted-ne $ true) the following error is generated when {Install-AuthCertificate-DomainController $ RoleDomainController} ":" Microsoft. exchange. management. systemConfigurationTasks. addAcc EssRuleCryptographicException: Due to an encryption exception, the network service cannot be authorized to access the certificate containing the fingerprint C2DBB62E06004C5488A1BF6D0B7F84F7FD9A44D9. ---> System. Security. Cryptography. CryptographicException: access is denied.

In Microsoft. exchange. security. cryptography. x509Certificates. tlsCertificateInfo. CAPIAddAccessRule (X509Certificate2 certificate, AccessRule rule) in Microsoft. exchange. security. cryptography. x509Certificates. tlsCertificateInfo. addAccessRule (X509Certificate2 certificate, AccessRule rule) in Microsoft. exchange. management. systemConfigurationTasks. manageExchangeCertificate. enableForServices (X509Certificate2 Cert, AllowedServices services, String websiteName, Boolean requireSsl, ITopologyConfigurationSession dataSession, Server server, List '1 warningList, Boolean allowConfirmation, Boolean forceNetworkService) --- end of internal exception stack trace --- at Microsoft. exchange. configuration. tasks. task. throwError (Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) in Microsoft. exchange. configuration. Tasks. task. writeError (Exception exception, ErrorCategory category, Object target) in Microsoft. exchange. management. systemConfigurationTasks. installExchangeCertificate. enableForServices (X509Certificate2 cert, AllowedServices services) in Microsoft. exchange. management. systemConfigurationTasks. installExchangeCertificate. internalProcessRecord () in Microsoft. exchange. configuration. tasks. task. <ProcessRecor D> B _ c () in Microsoft. Exchange. Configuration. Tasks. Task. InvokeRetryableFunc (String funcName, Action func, Boolean terminatePipelineIfFailed )".

--------------------------------------------------

The solution to this problem is as follows: Run MMC, open the Microsoft console, choose file menu> Add Management Unit, select a certificate, and set "Certificate (Local Computer) "Add to the node. The next key step is to find the "personal" node and place a Certificate named "Microsoft Exchange Server Auth Certificate" under the "personal" node, move to the Trusted Root Certificate Authority node. You can drag and drop a mobile certificate directly. You cannot operate a pure menu, but you can only copy and cut the certificate without pasting it. After completing the above operations, you can successfully complete the installation.

Here, the "Microsoft Exchange Server Auth Certificate" Certificate does not know if it will appear under the personal node only after the installation fails once. I do not know if there is any way to avoid it in advance, if this is not the case, the installation fails and you need to exit and set it again. These two pitfalls are a headache. Microsoft Installer may not be in place in some places, but we only need to set it manually.

Different from 2010, ExchangeServer2016's server management interface is completely B/S. This makes me feel a little surprised.