The latest cumulative update for Exchange Server 2016 is now available on the download center. There is no release for Exchange Server 2013 or Exchange Server 2010 as these products are both in the e...
Updated Jul 01, 2019
Version 2.0
Blog Post
@Dave, Exchange does not explicitly require IPv6. The errors you are encountering indicate the Exchange Server cannot contact a domain controller. This is normally due to wrong credentials being used, e.g. logging on as the local admin, or an underlying networking issue, e.g. DNS, IPsec Policy or IP routing.
as I wrote above on the same server under the same user CU10 is installed without any problems and errors.
- seem to have found the cause: in event log
ExSetupUI.exe 3516 Get Servers for mydomain.com TopologyClientTcpEndpoint (localhost) 3 System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0230759. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout) --- End of inner exception stack trace ---
it is obvious that no Exchange.Directory.TopologyService on the server - as this is a fresh installation!
After clean install of CU10 and attempt to upgrade to CU11 finally got a sane error that need to update the AD from the same site where the schema master located.
- Having the same issue. CU11 reports multiple errors in readiness checks. One error states "The mailbox server role isn't on this computer". When it clearly has mailbox role installed I have installed C++ 2010 update, C++ 2012, and C++ 2013.
- I was able to install CU 11 by installing the update on an exchange server located in the same site as the DC holding the schema master. Once the DCs replicated the changes, i was able to install CU 11 on the other exchange 2016 serves located in other sites.