Installed Updates on Exchange Server, Outlook clients will not connect

I applied the 2018-05 Security and Quality Rollup for .NET Framework 3.5 - 4.7.1 (KB4099635) and now my outlook 2013 clients cannot connect to my exchange 2016 server. The outlook clients take forever (about 5 minutes) to load (Loading profile). Once up, all exchange folders are in the status "This folder has not yet been updated" "Trying to Connect" "Disconnected".  When I restore the system state to last night's backup, it works. Unfortunately, windows automatically reinstalled the update and it quit working again.

How do I go about troubleshooting this problem? I dont see any problems in the event log, though there could be and I dont recognize their importance. I found a Health Checker script and ran it. It says I'm on .NET 4.7.1 and the maximum is 4.5.2.

Note: I started the outlook clients in safe mode, same problem.
MikeBroderickAsked:
Who is Participating?
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
another i did not think of initially ensure all CU for Exchange amd OS 2016 are installed
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
this is not good.

I would update your outlook client 100% and underlying OS. if problem still persists i would be a bit worried.

At this point i feel this is MS Issue and not EE
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
use exchange bpa and test connectivity cmdlets impersonating users via autodiscover and any other relevant test cmdlets.

seriously though this is MS Issue all day MS professional services.

Obviously you have options to use a restore of backup in some way or to even look at uninstalling the updates/programs you installed that caused the issues.
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
i also do not say MS issue lightly BOL
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
also take a look at exchange server shooter ps script by MS can detect critical issues
0
 
FOXActive Directory/Exchange EngineerCommented:
Restore the system state back to where it worked originally and hide the update that is causing this issue so it does not install again until Microsoft can fix the bug.

ref link: https://community.spiceworks.com/how_to/115281-uninstall-and-block-specific-windows-updates-7-8-1
0
 
MikeBroderickAuthor Commented:
I have restored the system state from last night (again) and everything is working. Fortunately my backup is scheduled for 12AM and the auto update procedure started around 4:30AM. I hid the update rollup so it would not automatically install again. I also made another system state save that I am setting aside. Waiting for Microsoft to fix what they broke is reasonable (sooner or later somebody important will demand this gets fixed and MS will fix it).
0
 
FOXActive Directory/Exchange EngineerCommented:
Good
0
 
MikeBroderickAuthor Commented:
In the results of running the Health Checker script it mentioned that I havent applied Cumulative Updates for over 2 years. I assumed the Exchange updates were applied along with windows updates. When I applied the latest Cumulative Update, applying the rollup update did not cause problems.

The Health Checker script mentioned some other things I am looking into. For anybody interested, here is where you can download it:

https://gallery.technet.microsoft.com/Exchange-2013-Performance-23bcca58

Thanks to both of you for all of your help.
0
 
Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
TY I deliberately avoided restoring a backup to find out what the issue is here, resolution came across because MS will not deal with you unless these steps are completed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.