question

ChrisWager-0464 avatar image
0 Votes"
ChrisWager-0464 asked ChrisWager-0464 edited

Exchange 2013 Cumulative Update Archive

Morning All, I am facing on-going challenges with patching Exchange Server 2013, in several instances I have been unable to install CU23 and then the Security Update due to the C:\Windows\Installer Folder having been cleared out. At present the issue I have is not being able to download CU8, CU10. and CU13 as Microsoft no longer seem to offer a link to download them. Unfortunately I require these to have come from a verified source i.e. the manufacture "Microsoft" I cannot download them from just any site. Does Microsoft have a source that they can confirm is safe where I can get these from please. Thanks Chris

office-exchange-server-administration
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @ChrisWager-0464

Any progress about your issue?

0 Votes 0 ·

1 Answer

joyceshen-MSFT avatar image
0 Votes"
joyceshen-MSFT answered ChrisWager-0464 edited

Hi @ChrisWager-0464

According to Microsoft policies, only the 2 latest CUs are support. In your scenario, I would suggest you deploy the new Exchange server(s) in your environment to replace the old server(s) then uninstall the old server(s).

Or you may try the solution introduced here: Recover an Exchange Server


If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
 

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Policy or not I find Microsoft inability to forsee such situations that call for needing an archive of legacy CU's and thereby leaving MSP's unable to patch customers that reacted instead of being proactive luicrious.

Deploying servers again is never practical no rational as this would cost a considerable amount.

In the end I resolved this for a number of customers by collecting the contents of C:\Windows\installers, from as many exchange servers I could get access to. I then used a powershell script that restored the installer cache from the files I collected.

This is why I never turn to Microsoft forums, because I never get helpful answered, yet another example of being able to fix something Microsoft say can't be fixed..

So the answer is collect files from other servers C:\Windows\installer and restore using an installer cache restore script that can be found using Google. "Other search engines are available."

0 Votes 0 ·