Hi Sk1z0tT, Shurik6,
When we initially installed the February SU, it broke our Outlook Search and EWS clients (Mac Mail, Mac Outlook). We uninstalled the SU and behavior went back to normal. We have since redeployed the SU along with the EWS workaround and everything is working fine. Below are our steps that may be helpful. I compiled them for our environment after a conversation with an Exchange Technical Advisor from Microsoft. We are running Exchange 2016 CU23 on Windows Server 2012 R2.
Run the Health Checker script as a baseline
Move all databases from server to be updated to another server and keep/pin them there
Remove the server from service on your load-balancer if one is in use
Disable antivirus software (disable antivirus service and reboot)
(Or better, uninstall antivirus software and reboot or you may have to stop services manually below)
Disable service for your Exchange backup software if in use
Install the February SU
(If installation says it's stopping services but it's not actually stopping any of them, click Cancel and stop them yourself)
(You can use get-service | ?{$_.Name -ilike “MSexch*”} | stop-service to stop most of them; also stop www, iisadmin, and SMS if installed)
After SU installs, reboot as prompted
Install EWS workaround
Reboot (this last reboot was required for Outlook search to work even though it should not have been needed)
Enable/reinstall your antivirus software
Enable your backup software if in use
Move one test database containing only test users to updated server
Test EWS using a Mac Mail or Mac Outlook client if in use
Test searching from OWA and a Windows Outlook client
If the above succeeds, move a single production database to that server and leave it there for two hours and listen for problems
If the above succeeds, put server back in service on your load-balancer if you use one and wait for problems
If the above succeeds, move additional databases to that server
Run the Health Checker script and look for problem reports