![]() ![]() ![]() |
|
I'm not convinced the issues I had were caused by the patch, I think it's more our legacy exchange servers are badly in need of taking out the back and shooting.
I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup.
Tested on our DR (Exchange 2016 CU19) - took 30mins running the security patch from windows update
It seems ok - will run the update tonight on prod
gjm:
ok thanks. No Exchange test environment here apart from my home lab so I think Ill hold off for a day or two. I see that people who have a special character in the account name that they use when installing the patch are having some problems. Doesn't apply to me but also not confidence inspiring in terms of quality
Given the hype over these updates I wouldn't delay too long. Take a backup, then run the update.
|
![]() ![]() ![]() |