4 Stage Process For Ing And Installing Updates Taking
Edit: The latest update is now Exchange 2013 Cumulative Update 18. See for a list of all updates and KB articles.I’ve got a few Exchange 2013 installations in production now so I thought it was about time I wrote a post on best practices when installing Exchange 2013 Cumulative Updates and Service Packs.Each Cumulative update is a version of Exchange in it own right. Therefore if you are installing a new deployment of Exchange you can install straight from latest Cumulative Update, which at the time of writing is CU11 (released December 2015). Contains a list of fixes and enhancement for CU11. Check to see what the current latest version is.This also means that once installed you cannot uninstall a Cumulative Update, if you do you uninstall Exchange.The update is approximately 1.6GB in size and can be downloaded from.In my test lab with a single Exchange server and single Domain Controller the update took an 60 minutes to install.The official Exchange Team blog post can be found.Microsoft Support PolicyMicrosoft will support the last two Cumulative Updates.
So currently they support CU10 and CU11. They will support the oldest Cumulative Update for 3 months after the release of the latest Cumulative Update. Which makes sense as the Cumulative Updates are based on quarterly releases. ↓. Joe ZTHANK YOU!My MAPI/Exchange protocol started failing and ticking me off, possibly due to a.Net 4.6.x update which ended up crashing IIS app pool running the Exchange protocol. Failed on loading some Health DLL assembly. Instead of trying to re-create virtual dirs, I just decided to try a CU11 re-upgrade worked like a charm with your instructions but I couldn’t get to far in the UI.
Windows Update Manually Trigger Start
The Next button on bottom right never un-grayed itself. Maybe I was impatient but geez it was at least 20 mins 🙂 killed it and followed your three commands to do it all on command-line, seeing progress and watching all steps complete was great.Ran into one small issue (likely because a previous re-upgrade removed the folder) on the actual upgrade where it complained that a folder did not exist, once created and re-ran, it worked. This was the folder but the moral of this story is if you get an error that folder does not exist, just create it and re-try: C:Program FilesMicrosoftExchange ServerV15UnifiedMessaginggrammarsNow my Outlook easily connects to my home Exchange server and I’m all set. Thanks again! ↓.
Joe ZSorry for the multiple replies but I wanted to consolidate a few of the issues in your thread because your manual routine was ultimately THE SOLUTION for me.Below are a few related articles to the error I was facing. My guess is any and all of these can be resolved via a re-install of your current or even newer CU. Having said that, the UI has not been great for me and I’m very thankful for the command-line alternative that you documented.Event Viewer Error after applying.Net 4.6.x — probably what killed it. FYI it could me another assembly name that fails to load due to my extensive research. Mine just happened to be Microsoft.Exchange.HttpUtilities:Exception message: Could not load file or assembly ‘Microsoft.Exchange.HttpUtilities, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies.
The system cannot find the file specified.Other links talking about the error but none highlight that RE-INSTALLING a CU will make it disappear:Thanks again as it saved me hours of work and I didn’t have to re-create a bunch of my virtual IIS folder then modify attributes on the newly created folders, etc. Just a dreaded nightmare that your article helped me solve in like 40 minutes. This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website.
These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies.
But opting out of some of these cookies may have an effect on your browsing experience. This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website.
We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies.
But opting out of some of these cookies may have an effect on your browsing experience.