Several important points to note when installing Exchange Server 2016 on Windows Server 2016

I tried to install ExchangeServer2016 on Windows Server 2016 in the past two days. I encountered two headaches. Fortunately, after several searches and groping, I finally solved the problem. Now I will share my experience. Come out and give it as a reference for others who encounter the same problem. Installing Exchange Server 2016 on Windows Server 2016 is no longer like installing the system in the past. You can start the installation program directly and click Next to follow along. There are some places that require special settings:

1. First, The installation of Exchange Server 2016 requires a domain environment and the UCMA4.0 runtime library needs to be installed in advance. This is no problem. You can just set it up yourself, otherwise the rule check will not pass.

2. The first pitfall: It is not possible to install the original version of Exchange Server 2016 directly on Windows Server 2016. You must use Exchange Server 2016 CU3 or above version , CU3 is cumulative update 3. I chose to install CU5 directly. If you use the original version, you will be stuck in the rule checking stage, requiring the system to install desktop experience. However, there is no desktop experience in the add server function after Windows Server 2016 is installed with GUI, so it is a dead end. Therefore, version CU3 or above must be used.

3. ExchangeServer2016 CU3 itself is actually a complete version, similar to "ExchangeServer2016 with CU3". Novices like me think it is just an update package when they first see the name. In fact, just download and install it directly.

4. After crossing the first pit, you can pass the rule checking stage and enter the actual installation stage. There are 13 stages in the installation stage. There is another pit in the 7th stage where an error will occur. The error text is similar to So it goes like this (I won’t format it):

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

Error: The following error was generated when running

"$error.
Clear();           
Install-ExchangeCert
ificate -WebSiteName "Exchange Back 
End
" -services "IIS, POP, I
MAP
" -Do
main
Controller $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true           
if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)           
{             
Install-AuthCertificate -DomainController $RoleDomainController           
}

" ":

"Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRule
Crypt
ographic
Exception
: 由于引发了加密异常，无法授予网络服务访问包含指纹 C2DBB62E06004C5488A1BF6D0B7F84F7FD9A44D9 的证书的权限。 ---> 
System.Security.Cryptography.CryptographicException: 拒绝访问。

in

Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)    
在 Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)    
在 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)   
 --- 内部异常堆栈跟踪的结尾 ---    
 在 Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)    
 在 Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)    
 在 Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services)    
 在 Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()    
 在 Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>bc()    
 在 Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)"。
--------------------------------------------------

The solution to this problem is this:Run MMC, open the Microsoft Management Console, File menu->Add snap-in, select Certificate, and change "Certificate (Local Computer)" Add it to the node. The next key step is to find the "Personal" node and move the certificate named "Microsoft Exchange Server Auth Certificate" under the "Personal" node to the "Trusted Root Certification Authority" Under the node. You can use drag and drop to move the certificate. The pure menu cannot be used. Only cut, copy and not paste.

##The installation can be completed successfully. I don’t know if the "Microsoft Exchange Server Auth Certificate" certificate must fail to be installed once before it will appear under the personal node. I don’t know if there is a way to avoid it in advance. If it doesn’t work, just fail the installation once.

Exit and then set it up again. . These two pitfalls are very troublesome. Microsoft's installation program may not be in place.

is different from 2010. The server management interface of Exchange Server 2016 is completely the B/S version. What surprised me was

.

The above is the detailed content of Several important points to note when installing Exchange Server 2016 on Windows Server 2016. For more information, please follow other related articles on the PHP Chinese website!