After settings up a new Exchange 2013 server in our environment (single server, all roles) we migrated from our Exchange 2007 server. The migration included mailboxes, public folders, shared boxes ... basically everything. In my past experience with Exchange 2003, 2007 and 2010 I've never had any issues with POP3 nor many issues with Public Folders (once they were migrated).
Now we're having issues with a few different things:
- POP3
We have an application that checks its mailbox every 15-seconds via POP3 PlainTextLogin. This application works fine for anywhere between 2-7 minutes and then throws a login error. The next time it retries it is successful but we never experienced this with Exchange 2007.
- Public Folders
Now with Public Folders on Exchange 2013, it seems to take a LOT longer to copy information into them. I'm talking around 10-30 seconds. Previously it was very quick. We've also noticed that Outlook runs slower being attached to 2013 but all the functionality is there.
Get-ServerHealth reports Unhealthy on:
- POP.Protocol\PopDeepTestMonitor (POP.Protocol)
- POP.Protocol\PopSelfTestMonitor (MSExchangePop3BE)
- HubTransport\Transport.ServerCertMismatch.Monitor (HubTransport)
This one I don't understand at all because I imported the cert directly from GoDaddy. I've also verified the Trusted CA is imported from GoDaddy along with the Intermediate Cert.
- HubTransport\SmtpProxyEhloOptionsDoNotMatchContinueProxyingMonitor (HubTransport)
- Autodiscover\AutodiscoverCtpMonitor (Exchange Server Name is the target resource)
- Autodiscover.Protocol\AutodiscoverSelfTestMonitor (MSExchangeAutoDiscover)
- ActiveSync\ActiveSyncCTPMonitor (ActiveSync)
- ActiveSync.Protocol\ActiveSyncDeepTestMonitor (ActiveSync)
- There are all DatabaseHealthCircLoggingMonitor errors on each database however we use a backup application to backup the databases specifically so we want Circular Logging turned off so that it catches all the changes
Any help would be greatly appreciated. I've checked around and all I can really find is to Invoke the monitor again to see if it truly fails but nothing really pointing me in the, hey, go over here and look at this config in powershell, type of answer.