Exchange 2013 CU Downloads

[ITGURU]

Hi

 

Does anyone have any older CU Updates they could possibly share with me? I'm on CU8 and only 17 and 18 is available to download from microsoft.

 

I've read about .net issues and recommends updating to CU15 first.

 

Anyone who can help me out so i can get onto teh latest update without any issues would be great.

 

Thanks.

[RobD]

I think the updates are Cumulative so you should be able to go from CU8 to CU18 which will include the fixes for CU15.

[ITGURU]

They are, although I believe there was a dot net version issue so want to jump in multiple steps rarther than jump straight in with the latest.

Exchange server has been solid for 3 years on Cu8 (no issues whatsoever) and get scared updating it!!

[Steve21]

https://1drv.ms/f/s!Al3AUZAtYRy8o-xlRq55J4yX5mc6vQ

 

(Note, Not mine but an MS MVP own blog site)

 

Steve

[RobD]

Got you, the thing is if it did break and it got to the point where you had to get MS involved all they'd make you do is install the latest update. I'd risk it for a biscuit.

[3s-gtech]

Exchange CUs do rather induce a puckering effect, but I have run loads on our 2013 box from an early version (we moved over in mid-2013) to CU18 without real issue - the only one being one version removed the mail notification 'ding' and another set all the Windows services for Exchange to Disabled after updating! Easily fixed.

[ITGURU]

Think i'll restore a DC and exchange into a test envrionment first!

[Steve21]

This is a specific issue with CU14+ though, as the new update requires .NET 4.6.2+ and the old one can't run on it it needs 4.6.1, the only bridge is 15 unless something changed

 

Steve

[kernelmart]

Hi,

 

Mine was on CU11 till I upgraded in October.

 

Due to the .net framework compatibility with CUs I went to CU15 first, .net Framework to 4.6.2 (from 4.6.1). Then installed CU18. With each step I let it all 'settle' at least overnight, before the next install.

 

I did fortunately have a 2 week half term break to do it in. It was all a bit scary as each CU process is a full re-install. I hadn't touched Exchange since it was Exchange 2000 on NT4.

 

I followed the steps in this guide;

 

https://www.oxfordsbsguy.com/2015/12/20/exchange-2013-cumulative-update-installation-tips-best-practices/

 

I used the command line type for the AD schema parts. Then the GUI for the actual install.

 

I also read around it all here;

 

https://enterpriseit.co/microsoft-exchange/2013/upgrade-cu5/

 

and here;

 

https://enterpriseit.co/microsoft-exchange/2013/prepare-ad-prepare-schema/

 

Thanks,

Martin

[ITGURU]

Hi,

 

Mine was on CU11 till I upgraded in October.

 

Due to the .net framework compatibility with CUs I went to CU15 first, .net Framework to 4.6.2 (from 4.6.1). Then installed CU18. With each step I let it all 'settle' at least overnight, before the next install.

 

I did fortunately have a 2 week half term break to do it in. It was all a bit scary as each CU process is a full re-install. I hadn't touched Exchange since it was Exchange 2000 on NT4.

 

I followed the steps in this guide;

 

https://www.oxfordsbsguy.com/2015/12/20/exchange-2013-cumulative-update-installation-tips-best-practices/

 

I used the command line type for the AD schema parts. Then the GUI for the actual install.

 

I also read around it all here;

 

https://enterpriseit.co/microsoft-exchange/2013/upgrade-cu5/

 

and here;

 

https://enterpriseit.co/microsoft-exchange/2013/prepare-ad-prepare-schema/

 

Thanks,

Martin

 

Thanks for this - how much of the customised install does it reset after an update is installed? i have all my users set with a custom OWA policy along with other settings. are they retained?

 

Hopefully going to restore an ad backup and exchange to test environment first if i can find somewhere to put a 500gb database!

[kernelmart]

I couldn't see there were any customisations on my server (I'd inherited the network) and the OWA logon page was plain MS out of the box. I had a look at the web.config file (in Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa) and it had the date and time from when CU15 was installed. So I risked it and couldn't see any changes after.

 

The other thing I did read though was make sure there a no certificate warnings on the server, expired, etc. before running the CU as apparently that can muck up the install.

 

I ran this tool (its a powershell script that runs in the Exchange Management Shell) on my server before and after each step;

 

https://exchangeanalyzer.com/

 

It gave me confidence I was going in the right direction.

 

Thanks,

Martin

[ITGURU]

I couldn't see there were any customisations on my server (I'd inherited the network) and the OWA logon page was plain MS out of the box. I had a look at the web.config file (in Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa) and it had the date and time from when CU15 was installed. So I risked it and couldn't see any changes after.

 

The other thing I did read though was make sure there a no certificate warnings on the server, expired, etc. before running the CU as apparently that can muck up the install.

 

I ran this tool (its a powershell script that runs in the Exchange Management Shell) on my server before and after each step;

 

https://exchangeanalyzer.com/

 

It gave me confidence I was going in the right direction.

 

Thanks,

Martin

 

all my users have a custom OWA policy as it's set not to display photos in OWA - so just wondering when i update the server with the CU it is going to reset this back so all users get photos until i can get the policy re-created.

[3s-gtech]

It doesn't change any customisations or policies IME - the only thing it does for us is overwrite our modified OWA login page back to default.

[sernet]

Hi,,, the link to Exchange 2013 CU5 dont have more.... please... i need this CU5,,, do you have help me? Edited March 15, 2019 by sernet

[Arthur]

https://justaucguy.wordpress.com/2017/07/03/a-bridge-too-far-exchange-2013-cu15

 

As a final note to this saga, Microsoft is now advising that it is OK to update .NET and then Update the CU to handle and bridge CU upgrade issues. This happened earlier this year and I wanted to make sure this was clear at the top of the article:

 

https://blogs.technet.microsoft.com/rmilne/2017/03/27/exchange-2013-cu16-and-exchange-2016-cu5-net-framework-requirement/

 

With the latest release for Exchange 2013, Cumulative Update 21, your only other concern is making sure you update Microsoft C++ from 2012 to 2013 as noted in the Release Notes for the CU.

 

https://blogs.technet.microsoft.com/rmilne/2017/03/27/exchange-2013-cu16-and-exchange-2016-cu5-net-framework-requirement

 

Since the older versions of Exchange 2013 and 2016 CUs are no longer available, the Exchange Support Matrix has been updated with the below:

 

When upgrading Exchange from an unsupported CU to the current CU and no intermediate CUs are available, you should upgrade to the latest version of .NET that's supported by Exchange first and then immediately upgrade to the current CU. This method doesn't replace the need to keep your Exchange servers up to date and on the latest, supported, CU.

Microsoft makes no claim that an upgrade failure will not occur using this method, which may result in the need to contact Microsoft Support Services.

[Arthur]

Here's a working download link to CU15 I found in a Spiceworks thread.

 

www.dropbox.com/s/9qnvv0bu4bqimov/Exchange2013-x64-cu15.exe?dl=0

Edited March 15, 2019 by Arthur