mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 21:37:22 +00:00
Update FQDN article (#245)
* Update install-apps-on-surface-hub.md * Updates to new articles Install apps: - Cleaned things up to make the article more clear. MDM: - Added links to CSP references - Cleaned up steps to create a custom config policy for SCCM Monitoring - Fixed various typos, formatting issues * Removed comment about using certs for UWP apps * Suggested RS1 updates for FQDN article
This commit is contained in:
parent
f914103225
commit
dc3c4979df
Binary file not shown.
Before Width: | Height: | Size: 39 KiB After Width: | Height: | Size: 52 KiB |
@ -7,21 +7,17 @@ author: TrudyHa
|
||||
localizationpriority: medium
|
||||
---
|
||||
|
||||
# When to use a fully qualified domain name with Surface Hub
|
||||
# Configure domain name for Skype for Business
|
||||
|
||||
A fully qualified domain name (FQDN) is a domain name that explicitly states the location in the Domain Name System (DNS) hierarchy. All levels of a domain are specified. In the case of Skype for Business on the Surface Hub, there are a few scenarios where you need to use a FQDN.
|
||||
There are a few scenarios where you need to specify the domain name of your Skype for Business server:
|
||||
- **Multiple DNS suffixes** - When your Skype for Business infrastructure has disjointed namespaces such that one or more servers have a DNS suffix that doesn't match the suffix of the sign-in address (SIP) for Skype for Business.
|
||||
- **Skype for Business and Exchange suffixes are different** - When the suffix of the sign-in address for Skype for Business differs from the suffix of the Exchange address used for the device account.
|
||||
- **Working with certificates** - Large organizations with on-premise Skype for Business servers commonly use certificates with their own root certificate authority (CA). It is common for the CA domain to be different than the domain of the Skype for Business server which causes the certificate to not be trusted, and sign-in fails. The Skype app needs to know the FQDN of the certificate in order to set up a trust relationship. Enterprises typically use Group Policy to push this out to Skype desktop, but Group Policy is not supported on Surface Hub.
|
||||
- **Working with certificates** - Large organizations with on-premise Skype for Business servers commonly use certificates with their own root certificate authority (CA). It is common for the CA domain to be different than the domain of the Skype for Business server which causes the certificate to not be trusted, and sign-in fails. The Skype app needs to know the domain name of the certificate in order to set up a trust relationship. Enterprises typically use Group Policy to push this out to Skype desktop, but Group Policy is not supported on Surface Hub.
|
||||
|
||||
## Add FQDN to Surface Hub
|
||||
**To configure the domain name for your Skype for Business server**</br>
|
||||
1. On Surface Hub, open the **Settings** app.
|
||||
2. Navigate to **This device** > **Calling**.
|
||||
3. Under **Skype for Business configuration**, select **Configure domain name**.
|
||||
4. Type the domain name for your Skype for Business server. You can type multiple domain names, separated by commas. <br> For example: lync.com, outlook.com, lync.glbdns.microsoft.com
|
||||
|
||||
You use the Settings app on Surface Hub to add FQDN information. You can add multiple entries, if needed.
|
||||
|
||||
**To add Skype for Business Server FQDN**</br>
|
||||
1. On Surface Hub open the **Settings** app.
|
||||
2. Navigate to **System**, **Microsoft Surface Hub**.
|
||||
3. Under **Skype for Business**, click **Add FQDN**.
|
||||
4. Type the FQDN for the Skype for Business certificate. You can type multiple FQDNs separated by a comma. For example: lync.com, outlook.com, lync.glbdns.microsoft.com.
|
||||
|
||||

|
||||

|
Loading…
x
Reference in New Issue
Block a user