download
release notes
We know a lot of you have been waiting for this, and so it is with great excitement that we announce that Exchange Server 2013 RTM Cumulative Update 1 (CU1) has...
Updated Jul 01, 2019
Version 2.0
Blog Post
Well, this CU1 setup has been a f.... nightmare! On one exchange server it failed at first because I had set the powershell execution policy through GPO. If you do, setup will not only fail, but it will if run again constantly deactivate all exchange related services and then fail when it tries restarting them.
Still trying to install on the second exchange server. I get this:
Mailbox role: Client Access service FAILED
The following error was generated when "$error.Clear();
Start-SetupProcess -Name "iisreset" -Args "/noforce /timeout:120"
" was run: "Process execution failed with exit code 1052.".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:ExchangeSetupLogs folder.
How about some more quality out of Redmond? Thank you!!