Source where EWS uri not matching the certificate name
Is there a way to force the connection to be non HTTPS if the source system allows it? i feel no urge to implement changes to the old system since its beeing decomissioned after the move. Product version: 8.13
Without looking at the log, you can try and set the autodiscover URL's using the below document. support.quest.com/.../9 The tool issues the cmds via Remote PowerShell and then from there it's Windows/Exchange that handles the communication and certificate validation.