We help IT Professionals succeed at work.

Conversation History and Calendar do NOT sync with Outlook anymore?

SIP and Primary SMTP domains do not match. Skype for Business 2015 client displays EWS not deployed.
Hello, I have an Exchange 2007 and Skype for Business 2015 Server on-premise solution deployed.
Originally, functioning fine with SAN certs using <company>.org domain for required certs on mail server and SfB 2015 Standard Edition solution (Standard, Edge and WAP servers).
Primary SMTP domain was <longcompanyname>.com  (domain NOT included in the SAN certs) and everything functioned fine including Conversation History and Calendar synch between Outlook (2007-2013) and Skype for Business 2015 client.
Fast forward a few years and....
New domain purchased and Primary SMTP for each user changed to <shortcompanyname>.com
NOW, Conversation History and Calendar do NOT synch with Outlook anymore.
Research appeared to state I can have this circumstance without issue after running 'Set-CsClientPolicy -DisableEmailComparisonCheck $true'
Ran the powershell command on the SfB Standard Edition server, rebooted test client and SfB solution. STill Outlook Integration Error and EWS not deployed in SfB client Configuration info.
Advice?
Comment
Watch Question

Kyle SantosQuality Assurance Engineer at Dassault Systemes

Commented:
Hi,

I am here to help you with your open question.  Do you still need help?  I have the ability to alert more experts if you still need help.

If you solved the problem on your own, would you please post the solution here in case others have the same problem?

If you need me to delete this question just say "Delete."

Thank you for using Experts Exchange.

Regards,

Kyle Santos
Customer Relations

Author

Commented:
Yes! Please help!

Author

Commented:
Thanks Kyle.
Surprising that we're getting NO response on this.
Kyle SantosQuality Assurance Engineer at Dassault Systemes

Commented:
I adjusted the title.  I'll see if I can get some more alerts sent out for you.

You mentioned Powershell.  Is there a sample of the script you're running?

Author

Commented:
The command is referenced in the question. 'Set-CsClientPolicy -DisableEmailComparisonCheck true$'
Solved the issue myself by adding an additional FQDN for the additional domain to my Exchange 2007 SAN certificate.
I believe this was causing the problem with Exchange communication. SfB <-> Exchange communication was breaking due to a perceived invalid SSL certificate.
Kyle SantosQuality Assurance Engineer at Dassault Systemes

Commented:
Thank you for letting us know!