Anyone else having POP healthset errors based on the fact that the local Exchange server name is not in the Certificate? When the pop health check runs its connects and tests to its server name. This causes a cert name mismatch because we did not include the server names in the SAN of the cert as per MS Best Practice. The ease fix would be to have the healthset check on 110 and not 995 but there seems to be no way to configure that port.
MonitorIdentity : pop.protocol\popselftestprobe
RequestId : c2465e93-a932-47aa-a494-f60577604b62
ExecutionStartTime : 12/9/2014 5:40:22 PM
ExecutionEndTime : 12/9/2014 5:40:22 PM
Error : Unexpected response to the POP USER command for user:
HealthMailbox586bc919034f4c53b9458c742cba74cf on port: 995 with SSL encryption
Exception : System.InvalidOperationException: Unexpected response to the POP USER command for user:
HealthMailbox586bc919034f4c53b9458c742cba74cf on port: 995 with SSL encryption
at
Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.TcpProbe.VerifyResponse(TcpResponse
response, String failureMessage)
at Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.PopProbe.TestProtocol()
at Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.TcpProbe.InvokeProbe(Boolean
skipLogin)
at
Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.PopMailboxProbeSSL.StartProbe()
at System.Threading.Tasks.Task.Execute()