-->
Surface Hub 2S enables you to connect external devices, mirror the display on Surface Hub 2S to another device, and connect multiple third-party peripherals including video conference cameras, conference phones, and room system devices.
With a range of intelligent and interactive devices and services, Teams empowers everyone to connect and collaborate in more immersive ways. Microsoft Teams for Surface Hub has full Teams calling and meeting capabilities, including one-touch join and up to four incoming video streams—all with side-by-side compatibility with Skype for Business. Apr 17, 2019 With a new 50-inch 3:2 display, integrated speakers, and tiny 15.5 millimeters bezels, the Surface Hub 2S is a beautifully designed PC on wheels. Hub 2S is meant to live in your workspace and runs. Apr 17, 2019 With a new 50-inch 3:2 display, integrated speakers, and tiny 15.5 millimeters bezels, the Surface Hub 2S is a beautifully designed PC on wheels.
You can display content from your devices to Surface Hub 2S. If the source device is Windows-based, that device can also provide TouchBack and InkBack, which takes video and audio from the connected device and presents them on Surface Hub 2S. If Surface Hub 2S encounters a High-Bandwidth Digital Content Protection (HDCP) signal, such as a Blu-ray DVD player, the source is displayed as a black image.
Note
Surface Hub 2S uses the video input selected until a new connection is made, the existing connection is disrupted, or the Connect app is closed.
Recommended wired configurations
In general, it’s recommended to use native cable connections whenever possible such as USB-C to USB-C or HDMI to HDMI. Other combinations such as MiniDP to HDMI or MiniDP to USB-C will also work. Some additional configuration may be required to optimize the video-out experience, as described on this page.
| Connection | Functionality | Description |
|---|---|---|
| HDMI + USB-C | HDMI-in for audio and video USB-C for TouchBack and InkBack | USB-C supports TouchBack and InkBack with the HDMI A/V connection. Use USB-C to USB-A to connect to legacy computers. NOTE: For best results, connect HDMI before connecting a USB-C cable. If the computer you're using for HDMI is not compatible with TouchBack and InkBack, you won't need a USB-C cable. |
| USB-C (via compute module) | Video-in Audio-in | Single cable needed for A/V TouchBack and InkBack is supported HDCP enabled |
| HDMI (in port) | Video, Audio into Surface Hub 2S | Single cable needed for A/V TouchBack and InkBack not supported HDCP enabled |
| MiniDP 1.2 output | Video-out such as mirroring to a larger projector. | Single cable needed for A/V |
When you connect a guest computer to Surface Hub 2S via the USB-C port, several USB devices are discovered and configured. These peripheral devices are created for TouchBack and InkBack. As shown in the following table, the peripheral devices can be viewed in Device Manager, which will show duplicate names for some devices, as shown in the following table.
| Peripheral | Listing in Device Manager |
|---|---|
| Human interface devices | HID-compliant consumer control device HID-compliant pen HID-compliant pen (duplicate item) HID-compliant pen (duplicate item) HID-compliant touch screen USB Input Device USB Input Device (duplicate item) |
| Keyboards | Standard PS/2 keyboard |
| Mice and other pointing devices | HID-compliant mouse |
| USB controllers | Generic USB hub USB composite device |
Connecting video-in to Surface Hub 2S
You can input video to Surface Hub 2S using USB-C or HDMI, as indicated in the following table.
Surface Hub 2S video-in settings
| Signal Type | Resolution | Frame rate | HDMI | USB-C |
|---|---|---|---|---|
| PC | 640 x 480 | 60 | X | X |
| PC | 720 x 480 | 60 | X | X |
| PC | 1024 x 768 | 60 | X | X |
| PC | 1920 x 1080 | 60 | X | X |
| PC | 3840x2560 | 30 | X | X |
| HDTV | 720p | 60 | X | X |
| HDTV | 1080p | 60 | X | X |
| 4K UHD | 3840x2560 | 30 | X | X |
Note
The 4K UHD resolution (3840×2560) is only supported when connecting to ports on the compute module. It is not supported on the “guest” USB ports located on the left, top, and right sides of the device.
Note
Video from a connected external PC may appear smaller when displayed on Surface Hub 2S.
Mirroring Surface Hub 2S display on another device
You can output video to another display using MiniDP, as indicated in the following table.
Surface Hub 2S video-out settings
| Signal Type | Resolution | Frame rate | MiniDP |
|---|---|---|---|
| PC | 640 x 480 | 60 | X |
| PC | 720 x 480 | 60 | X |
| PC | 1024 x 768 | 60 | X |
| PC | 1920 x 1080 | 60 | X |
| PC | 3840 x 2560 | 60 | X |
| HDTV | 720p | 60 | X |
| HDTV | 1080p | 60 | X |
| 4K UHD | 3840 x 2560 | 60 | X |
Surface Hub 2S includes a MiniDP video-out port for projecting visual content from Surface Hub 2S to another display. If you plan to use Surface Hub 2S to project to another display, note the following recommendations:
- Keyboard required. Before you begin, you’ll need to connect either a wired or Bluetooth-enabled external keyboard to Surface Hub 2S. Note that unlike the original Surface Hub, a keyboard for Surface Hub 2S is sold separately and is not included in the shipping package.
- Set duplicate mode. Surface Hub 2S supports video-out in duplicate mode only. However, you will still need to manually configure the display mode when you connect for the first time:
- Enter the Windows logo key + P, which opens the Project pane on the right side of Surface Hub 2S, and then select Duplicate mode.
- When you’re finished with your Surface Hub 2S session, select End Session. This ensures that the duplicate setting is saved for the next session.
- Plan for different aspect ratios. Like other Surface devices, Surface Hub 2S uses a 3:2 display aspect ratio (the relationship between the width and the height of the display). Projecting Surface Hub 2S onto displays with different aspect ratios is supported. Note however that because Surface Hub 2S duplicates the display, the MiniDP output will also only display in a 3:2 aspect ratio, which may result in letterboxing or curtaining depending on the aspect ratio of the receiving display.
Note
if your second monitor uses a 16:9 aspect ratio (the predominant ratio for most TV monitors), black bars may appear on the left and right sides of the mirrored display. If this occurs, you may wish to inform your users that there is no need to adjust the second display.
Selecting cables
Note the following recommendations:
- USB. USB 3.1 Gen 2 cables.
- MiniDP. DisplayPort cables certified for up to 3 meters in length.
- HDMI. If a long cable is necessary, HDMI is recommended due to the wide availability of cost-effective, long-haul cables with the ability to install repeaters if needed.
Note
Most DisplayPort sources will automatically switch to HDMI signaling if HDMI is detected.
Wirelessly connect to Surface Hub 2S
Windows 10 natively supports Miracast, which lets you wireless connect to Surface Hub 2S.
To connect using Miracast:
- On your Windows 10 device, enter Windows logo key + K.
- In the Connect window, look for the name of your Surface Hub 2S in the list of nearby devices. You can find the name of your Surface Hub 2S in the bottom left corner of the display.
- Enter a PIN if your system administrator has enabled the PIN setting for Miracast connections. This requires you to enter a PIN number when you connect to Surface Hub 2S for the first time.
Note
If you do not see the name of the Surface Hub 2S device as expected, it’s possible the previous session was prematurely closed. If so, sign into Surface Hub 2S directly to end the previous session and then connect from your external device.
Connecting peripherals to Surface Hub 2S
Bluetooth accessories
You can connect the following accessories to Surface Hub-2S using Bluetooth:
- Mice
- Keyboards
- Headsets
- Speakers
- Surface Hub 2 pens
Note
After you connect a Bluetooth headset or speaker, you might need to change the default microphone and speaker settings. For more information, see Local management for Surface Hub settings.
-->Troubleshoot common problems, including setup issues, Exchange ActiveSync errors.
The Surface Hub Hardware Diagnostic tool contains interactive tests which allow you to confirm essential functionality of your Hub is working as expected. In addition to testing hardware, the diagnostic can test the resource account to verify that it is configured properly for your environment. If problems are encountered, results can be saved and shared with the Surface Hub Support Team. For usage information, see Using the Surface Hub Hardware Diagnostic Tool to test a device account.
Common issues are listed in the following table, along with causes and possible fixes. The Setup troubleshooting section contains a listing of on-device problems, along with several types of issues that may be encountered during the first-run experience. The Exchange ActiveSync errors section lists common errors the device may encounter when trying to synchronize with an Microsoft Exchange ActiveSync server.
Setup troubleshooting
This section lists causes, and possible fixes to help troubleshoot issues you might find when you set up your Microsoft Surface Hub.
On-device
Possible fixes for issues on the Surface Hub after you've completed the first-run program.
| Issue | Causes | Possible fixes |
|---|---|---|
Not receiving automatic accept/decline messages. | The device account isn't configured to automatically accept/decline messages. | Use PowerShell cmdlet |
The device account isn't configured to process external meeting requests. | Use PowerShell cmdlet | |
Calendar is not showing on the Welcome screen, or message 'Appointments of date (no account provisioned)' is being displayed. | No device account is set up on this Surface Hub. | Provision a device account through Settings. |
Calendar is not showing on the Welcome screen or message 'Appointments of date (overprovisioned)' is being displayed. | The device account is provisioned on too many devices. | Remove the device account from other devices that it's provisioned to. This can be done using the Exchange admin portal. |
Calendar is not showing on the Welcome screen or message 'Appointments of date (invalid credentials)' is being displayed. | The device account's password has expired and is no longer valid. | Update the account's password in Settings. Also see Password management. |
Calendar is not showing on the Welcome screen or message 'Appointments of date (account policy)' is being displayed. | The device account is using an invalid ActiveSync policy. | Make sure the device account has an ActiveSync policy where |
Calendar is not showing on the Welcome screen or message 'Appointments may be out of date' is being displayed. | Exchange is not enabled. | Enable the device account for Exchange services through Settings. You need to make sure you have the right set of ActiveSync policies and have also installed any necessary certificates for Exchange services to work. |
Can't log in to Skype for Business. | The device account does not have a Session Initiation Protocol (SIP) address property. | The account does not have a SIP address property and its User Principal Name (UPN) does not match the actual SIP address. The account must have its SIP address set, or the SIP address should be added using the Settings app. |
Can't log in to Skype for Business. | The device account requires a certificate to authenticate into Skype for Business. | Install the appropriate certificate using provisioning packages. |
First run
Possible fixes for issues with Surface Hub first-run program.
Find The Mac Address On Microsoft Surface Hub Free
| Issue | Causes | Possible fixes |
|---|---|---|
Cannot find account when asked for domain and user name. | Domain needs to be the fully qualified domain name (FQDN). | The FQDN should be provided in the domain field. |
Device account page, issues for new account settings
| Issue | Causes | Possible fixes |
|---|---|---|
Unable to find the provided account in Azure AD. | The provided account's User Principal Name (UPN) has a tenant that can't be reached in Azure AD. | Make sure that you have a working Internet connection, and that the device can reach Microsoft Online Services. Make sure the account credentials are entered correctly. |
Unable to reach the specified directory. | The provided account domain specifies a domain that can't be reached. | Make sure that you have a working network connection, and that the device can reach the domain controller. Make sure the account credentials are entered correctly. You can also try using the FQDN instead. |
Can't auto-discover Exchange server. | The Exchange server isn't configured for auto-discovery. | Enable auto-discovery of the Exchange server for the device account, or enter the account's Exchange server address manually. |
Could not discover the SIP address after entering the account credentials. | There was no SIP address entry in Active Directory or Azure AD. | Make sure the account is enabled with Skype for Business and has a SIP address. If not, you can enter the SIP address manually into the text box. |
Device account page, issues for existing account settings
| Issue | Causes | Error codes | Possible fixes |
|---|---|---|---|
Account could not authenticate with the specified credentials. | The account is not enabled as a user in Active Directory (AD), needs a password to authenticate, or the password is incorrect. | None | Make sure the credentials are entered correctly. Enable the account as a user in AD and add a password, or set the RoomMailboxPassword . |
Error 0x800C0019 is displayed when providing an Exchange server. | The device account requires a certificate to authenticate. | 0x800C0019 | Install the appropriate certificate using provisioning packages. |
Device account credentials are not valid for the provided Exchange server. | The provided Exchange server is not where the device account's mailbox is hosted. | None | Make sure you are providing the correct Exchange mail server for the device account. |
HTTP timeout while trying to reach Exchange server. | 0x80072EE2 | ||
Couldn't find the provided Exchange server. | The Exchange server provided could not be found. | None | Ensure that you have a working network or Internet connection, and that the Exchange server you provided is correct. |
http not supported. | An Exchange server with http:// instead of https:// was provided. | None | Use an Exchange server that uses https. |
People land on the page titled 'There's a problem with this account' regarding ActiveSync. | The ActiveSync policy PasswordEnabled is set to True (or 1). | None | Create a new ActiveSync policy where PasswordEnabled is set to False (or 0), and then apply that policy to the account. |
The Surface Hub doesn't have a connection to Exchange. | None | Make sure that you have a working network or Internet connection. | |
Exchange returns a status code indicating an error. | None | Make sure that you have a working network or Internet connection. |
First run, Domain join page issues
| Issue | Causes | Possible fixes |
|---|---|---|
When trying to join a domain, an error shows that the account couldn't authenticate using the specified credentials. | The credentials provided are not capable of joining the specified domain. | Enter correct credentials for an account that exists in the specified domain. |
When specifying a group from a domain, an error shows that the group couldn't be found on the domain. | The group may have been removed or no longer exists. | Verify that the group exists within the domain. |
Find The Mac Address On Microsoft Surface Hub Tips
First run, Exchange server page
| Issue | Causes | Possible fixes |
|---|---|---|
People land on this page and are asked for the Exchange server address. | The Exchange server isn't configured for auto-discovery. | Enable auto-discovery of the Exchange server for the device account, or enter the account's Exchange server address manually. |
First run, On-device issues
| Issue | Causes | Error codes | Possible fixes |
|---|---|---|---|
Can't sync mail/calendar. | The account has not allowed the Surface Hub as an allowed device. | 0x86000C1C | Add the Surface Hub device ID to the whitelist by setting the ActiveSyncAllowedDeviceIds property for the mailbox. |
Exchange ActiveSync errors
This section lists status codes, mapping, user messages, and actions an admin can take to solve Exchange ActiveSync errors.
| Hex Code | Mapping | User-Friendly Message | Action admin should take |
|---|---|---|---|
0x85010002 | E_HTTP_DENIED | The password must be updated. | Update the password. |
0x80072EFD | WININET_E_CANNOT_CONNECT | Can't connect to the server right now. Wait a while and try again, or check the account settings. | Verify that the server name is correct and reachable. Verify that the device is connected to the network. |
0x86000C29 | E_NEXUS_STATUS_DEVICE_NOTPROVISIONED (policies don't match) | The account is configured with policies not compatible with Surface Hub. | Disable the PasswordEnabled policy for this account. We have a bug were we may surface policy errors if the account doesn't receive any server notifications within the policy refresh interval. |
0x86000C4C | E_NEXUS_STATUS_MAXIMUMDEVICESREACHED | The account has too many device partnerships. | Delete one or more partnerships on the server. |
0x86000C0A | E_NEXUS_STATUS_SERVERERROR_RETRYLATER | Can't connect to the server right now. | Wait until the server comes back online. If the issue persists, re-provision the account. |
0x85050003 | E_CREDENTIALS_EXPIRED (Credentials have expired and need to be updated) | The password must be updated. | Update the password. |
0x8505000D | E_AIRSYNC_RESET_RETRY | Can't connect to the server right now. Wait a while or check the account's settings. | This is normally a transient error but if the issue persists check the number of devices associated with the account and delete some of them if the number is large. |
0x86000C16 | E_NEXUS_STATUS_USER_HASNOMAILBOX | The mailbox was migrated to a different server. | You should never see this error. If the issue persists, re-provision the account. |
0x85010004 | E_HTTP_FORBIDDEN | Can't connect to the server right now. Wait a while and try again, or check the account's settings. | Verify the server name to make sure it is correct. If the account is using cert based authentication make sure the certificate is still valid and update it if not. |
0x85030028 | E_ACTIVESYNC_PASSWORD_OR_GETCERT | The account's password or client certificate are missing or invalid. | Update the password and/or deploy the client certificate. |
0x86000C2A | E_NEXUS_STATUS_DEVICE_POLICYREFRESH | The account is configured with policies not compatible with Surface Hub. | Disable the PasswordEnabled policy for this account. |
0x85050002 | E_CREDENTIALS_UNAVAILABLE | The password must be updated. | Update the password. |
0x80072EE2 | WININET_E_TIMEOUT | The network doesn't support the minimum idle timeout required to receive server notification, or the server is offline. | Verify that the server is running. Verify the NAT settings. |
0x85002004 | E_FAIL_ABORT | This error is used to interrupt the hanging sync, and will not be exposed to users. It will be shown in the diagnostic data if you force an interactive sync, delete the account, or update its settings. | Nothing. |
0x85010017 | E_HTTP_SERVICE_UNAVAIL | Can't connect to the server right now. Wait a while or check the account's settings. | Verify the server name to make sure it is correct. Wait until the server comes back online. If the issue persists, re-provision the account. |
0x86000C0D | E_NEXUS_STATUS_MAILBOX_SERVEROFFLINE | Can't connect to the server right now. Wait a while or check the account's settings. | Verify the server name to make sure it is correct. Wait until the server comes back online. If the issue persists, re-provision the account. |
0x85030027 | E_ACTIVESYNC_GETCERT | The Exchange server requires a certificate. | Import the appropriate EAS certificate on the Surface Hub. |
0x86000C2B | E_NEXUS_STATUS_INVALID_POLICYKEY | The account is configured with policies not compatible with Surface Hub. | Disable the PasswordEnabled policy for this account. We have a bug were we may surface policy errors if the account doesn't receive any server notifications within the policy refresh interval. |
0x85010005 | E_HTTP_NOT_FOUND | The server name is invalid. | Verify the server name to make sure it is correct. If the issue persists, re-provision the account. |
0x85010014 | E_HTTP_SERVER_ERROR | Can't connect to the server. | Verify the server name to make sure it is correct. Trigger a sync and, if the issue persists, re-provision the account. |
0x80072EE7 | WININET_E_NAME_NOT_RESOLVED | The server name or address could not be resolved. | Make sure the server name is entered correctly. |
0x8007052F | ERROR_ACCOUNT_RESTRICTION | While auto-discovering the Exchange server, a policy is applied that prevents the logged-in user from logging in to the server. | This is a timing issue. Re-verify the account's credentials. Try to re-provision when they're correct. |
0x800C0019 | INET_E_INVALID_CERTIFICATE | Security certificate required to access this resource is invalid. | Install the correct ActiveSync certificate needed for the provided device account. |
0x80072F0D | WININET_E_INVALID_CA | The certificate authority is invalid or is incorrect. Could not auto-discover the Exchange server because a certificate is missing. | Install the correct ActiveSync certificate needed for the provided device account. |
0x80004005 | E_FAIL | The domain provided couldn't be found. The Exchange server could not be auto-discovered and was not provided in the settings. | Make sure that the domain entered is the FQDN, and that there is an Exchange server entered in the Exchange server text box. |
Find The Mac Address On Microsoft Surface Hub 1
Contact Support
Find The Mac Address On Microsoft Surface Hub 2s
If you have questions or need help, you can create a support request.