Forum Discussion
Outlook - Certificate has been revoked
Opened a 2nd ticket for Outlook since MS support always points fingers back and forth (117052515798731). Still getting no where and they've already quit trying to try and support the ticket since we are unable to reproduce the issue on command.
Note, we have tried applying the "workarounds" by suppressing the prompt in IE and Outlook (HKCU\software\policies\microsoft\office\16.0\outlook\security\usecrlchasing Value=2) but still doesn't seem to work.
Only solution so far is to roll people back to Office 2013.
Our case is also still open (REG:117052315783924). Not getting closer to a solution yet unfortunately. They keep asking for traces we cannot give as the issue can't be reproduced on demand. In the mean time I've supplied some dump files, but that didn't bring us any closer as well it seems... I'll update when we get more news from MS.
Javier Garcia wrote:Opened a 2nd ticket for Outlook since MS support always points fingers back and forth (117052515798731). Still getting no where and they've already quit trying to try and support the ticket since we are unable to reproduce the issue on command.
Note, we have tried applying the "workarounds" by suppressing the prompt in IE and Outlook (HKCU\software\policies\microsoft\office\16.0\outlook\security\usecrlchasing Value=2) but still doesn't seem to work.
Only solution so far is to roll people back to Office 2013.
Javier I got word you closed the case because you find the issue to be related to your reverse proxy, is this correct?
Hap wrote:
Javier Garcia wrote:Opened a 2nd ticket for Outlook since MS support always points fingers back and forth (117052515798731). Still getting no where and they've already quit trying to try and support the ticket since we are unable to reproduce the issue on command.
Note, we have tried applying the "workarounds" by suppressing the prompt in IE and Outlook (HKCU\software\policies\microsoft\office\16.0\outlook\security\usecrlchasing Value=2) but still doesn't seem to work.
Only solution so far is to roll people back to Office 2013.
Javier I got word you closed the case because you find the issue to be related to your reverse proxy, is this correct?
Thank you for the response. we opened a case and worked with MS support on the issue and they recommended bypassing autodiscover by modifying the registry keys, however issue still persists. Issue only affects a couple of users. Will check to make sure they have the latest Office 2016 updates
and alos run an online full repair. We prefer not to downgrade to Office 2013.
