Ganesh Anand
asked on
SfB 2015 and Exchange 2016 on-premises integration
I have SfB 2015 enterprise pool without enterprise voice (not-published) and on-premises Exchange 2016.
Exchange 2016 with DAG
Frontend-Servers - Skype for Business Enterprise Edition 2016
Office Online Server - 1
Created DNS records in internal AD DNS including all default records.
Split-DNS brain (default domain is : axl.com),
The published domain is : abcexcel.com
Both servers VM and VDI infra is Citrix based XenDesktop and thin clients
Installed Citrix HDX software to support SFB for thin clients.
Tried the integration part as mentioned in http://lyncdude.com/2015/10/06/the-complete-skype-for-business-exchange-2016-integration-guide-part-i/index.html except DNS record part for autodiscover.abcexcel.com which does not exist and SCP is pointed to mail.abcexcel.com pointing to mail.
Do we need to add autodiscover.abcexcel.com in public certificate, and SRV and DNS records to make a successful integration. As mentioned in the article the SRV and autodiscover record is required but clients are connecting without autodiscover records in DNS. Does this works without updating the public autodiscover certificate SAN name.
Please advice.
Exchange 2016 with DAG
Frontend-Servers - Skype for Business Enterprise Edition 2016
Office Online Server - 1
Created DNS records in internal AD DNS including all default records.
Split-DNS brain (default domain is : axl.com),
The published domain is : abcexcel.com
Both servers VM and VDI infra is Citrix based XenDesktop and thin clients
Installed Citrix HDX software to support SFB for thin clients.
Tried the integration part as mentioned in http://lyncdude.com/2015/10/06/the-complete-skype-for-business-exchange-2016-integration-guide-part-i/index.html except DNS record part for autodiscover.abcexcel.com which does not exist and SCP is pointed to mail.abcexcel.com pointing to mail.
Do we need to add autodiscover.abcexcel.com in public certificate, and SRV and DNS records to make a successful integration. As mentioned in the article the SRV and autodiscover record is required but clients are connecting without autodiscover records in DNS. Does this works without updating the public autodiscover certificate SAN name.
Please advice.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER