A client has a goofy configuration and this type of config is how is HAS to be unfortunately.
- MS SBS 2011 Std
- Mixed LAN clients of XP, 7
- Office 2007 on all clients
Client is "cost effective" in terms of IT. There is no static IP, only DHCP for WAN address. Further, they also have POP3 accounts at FatCow which can not be managed by the SBS server. Due to that, their user profile MSO has a primary SMTP/POP3 account with a secondary internal Exchange account. Mail is POP'd down and delivered to Exchange store. This setup works ok but they get a certificate mismatch error from FatCow when MSO is first opened up. Internal DNS has all of the correct records in place (autodiscover., mail., etc) to match the self signed internal certificate. I'm not sure what is triggering the certificate mismatch error from FatCow. Internal pings show all the records are hitting the correct server IP address. We've tried shutting down autodiscover on the clients and that causes GAL sync issues but does not eliminate the mismatch error.