windows-itpro-docs/devices/surface-hub/monitor-surface-hub.md
jdeckerMS 323b29e556 Squashed commit of the following:
commit d6a8bce79e491a8a245a37a9e20e6a6bec4d325b
Merge: 0ab4e4e1 a7c70ad4
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 23 10:35:16 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 0ab4e4e119590e0e8cef691eee2b87180b07c5b3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 23 10:29:48 2017 -0700

    Jordan feedback

commit 4454eeadbebb5fccdbfb3b1d07e87d708fefbe87
Merge: 03444e15 ef670cb5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 23 09:26:54 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 03444e15f5b51bd1bdf1e76745f62cbbed3b529d
Merge: 603408f3 660a6984
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 22 11:00:46 2017 -0700

    Merge branch 'rs2' into jdrs2sh

commit 603408f38ecd99e6f7fce1f61a4f199918fd67c4
Merge: 6821f22f b96e1555
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:54:33 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 6821f22f07f1864bb0a5c8eda33f7daf4f9531bc
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:41:44 2017 -0700

    change ICD references

commit 5804bc18db376fba16e8c863f5af8ffdd965359a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:39:55 2017 -0700

    rename file

commit 9268142c9b881b0e0ad4fc2a0d4dcfddc180a1b3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:32:31 2017 -0700

    update what's new

commit 503be68ec3a731434ca789df2da1f1c4783fdca7
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:30:48 2017 -0700

    art

commit 93914a2cf2aef9622b172c8ea97a3c1d72544c6a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 13:30:43 2017 -0700

    Jordan updates

commit 27b1445ba4149fa78b7ec628870b19933307ba38
Merge: 9578dffe 6f0a1f7f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 21 08:19:27 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 9578dffee198b0be16992368f571eed81f261818
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 20 09:09:56 2017 -0700

    new oobe image

commit 616c10e4e404574ecce7726fc76d7582c56b318e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 20 08:23:53 2017 -0700

    get bulk token warning

commit 5600a6c7b320c4968686c07df90c62d8110764c9
Merge: cf29bb53 4b34636b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 20 08:22:02 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit cf29bb53ec1c6e45e068219a796b2a5b04347b15
Merge: 695ec39f a5ec4c4d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Mar 17 09:42:51 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 695ec39f81b6da46b442ce8e52c9d9b28d65434a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 16 12:25:06 2017 -0700

    delete

    # Conflicts:
    #	devices/surface-hub/TOC.md
    #	devices/surface-hub/intro-to-surface-hub.md
    #	devices/surface-hub/surface-hub-administrators-guide.md

commit cc123f7aa0718efaa7cd355df4e3693afb073b9c
Merge: 6b7ddf3e 3c12e864
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 16 12:23:40 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 6b7ddf3e498d541c2dbb531dd132e7ec0f45eb9d
Merge: 278d14c4 032c25d4
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Mar 16 11:34:53 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 278d14c462fa386e8979c4e998c464f2cdbf6a6c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 15 10:26:22 2017 -0700

    get bulk token

commit 005f12e3939f8134143314e95e6bc9f76db8c3de
Merge: 410e7508 1bff6ddd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 15 10:25:19 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 410e750850a5037d843fe9d9c64a477d252ff10e
Merge: d2f94c8f 8eed0956
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 13:51:32 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit d2f94c8f9d73868dec86e472fe5ace87b7370ac3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 13:27:23 2017 -0700

    tweak

commit f629b4f1fd27fad24c258a7de903e6c18e85ec8c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 12:44:21 2017 -0700

    fix mdm enrollment

commit 1dd74f9e7e353ba9ce5e71c8797cfa8cd02342a7
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 12:33:24 2017 -0700

    add proxy

commit c71e5af71bc866f1a5fe9abefb82b5124fb957fd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 12:03:09 2017 -0700

    add install link

commit 0344deee4c68ae3c81529dc9cb602eec2af0b5c3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:57:43 2017 -0700

    stick

commit be7ed51e1fb7b1a578c8e843b56e701bcf90be9d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:56:52 2017 -0700

    resize art

commit 857be3cdfca07da3c5dfb470b3a3a3aee290a07c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:55:09 2017 -0700

    moved note to correct cell

commit a91ca3943b8c0454549a1c0c5455b919ed46de8c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:52:21 2017 -0700

    sync

commit 5bcf3c1db3c97d87ca60bfd4d688b908d4d9e518
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:43:25 2017 -0700

    fix link

commit de7d60524a2e1ba0d5e1bc1074da9bf887fa6457
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:42:46 2017 -0700

    add apps to provisioning

commit 67e14be35b30f4bfa45fb79815c25ef2317a171c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 11:37:27 2017 -0700

    sync to switch branches

commit c6b9d8dae5d29f441ea262323baaad5e41b2bc9f
Merge: 3260248b 4b13310a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Mar 14 08:35:04 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 3260248b8a0511c081a5547419109f9380ea9b26
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 13 08:56:25 2017 -0700

    fix table for non-IE browsers

    # Conflicts:
    #	windows/whats-new/images/wcd-options.png

commit a3ece5c8d4a6c37645f4aa5b39b582be855b98b9
Merge: 4ed80574 759b4a41
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Mar 13 08:53:34 2017 -0700

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 4ed80574020c1291ba4e853553330a7b84f21657
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 12:00:27 2017 -0800

    fix typo

commit 7541a4507508822dcd51da773536b89a5a49f305
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:53:38 2017 -0800

    fix table

commit 37254f098396342dd23115ea10885f121f5b9371
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:51:48 2017 -0800

    resize art

commit a936a6c4768729fec66775528a31c64132fa4f8e
Merge: a217a9ae 9786c53a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:50:43 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit a217a9ae8e48af3b533eb421a716b5a580daecba
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:45:55 2017 -0800

    sync

commit f09e8ae9e87db16b7ee6982864a1c4c2fc8ebcdc
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:39:34 2017 -0800

    add image to index

commit 80a133370000b2b7ff8c9e1383aca7eb1769258a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:30:34 2017 -0800

    fix link

commit d8aa55211a62fecf56e6404146917b8e84b3c296
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:25:33 2017 -0800

    tweak TOC, get rid of intro

commit 6415e3739e13f47f2d3a6355066015d0bcd4cc7a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 11:16:33 2017 -0800

    remove admin guide level from toc

commit 0d016720488e8aa1e3e0621b50596a66db8d232f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 07:53:03 2017 -0800

    release in change history

commit 67a8f585dd788db1a18247827b1f9d22378d5b9f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 07:50:20 2017 -0800

    add what's new

commit be5e195fc41d9ce94cd1b6189f0da25e9e50b9f2
Merge: e3e75663 8e80f0e1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Mar 8 07:40:34 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit e3e756632b462d8a110b0538782bc22487e96d4b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 28 13:46:55 2017 -0800

    end session

    # Conflicts:
    #	windows/configure/windows-10-start-layout-options-and-policies.md

commit 0a9b86a2f6b69e5883fcdab48bb22f19cf1e6c32
Merge: 13e94977 4530d39f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 28 13:42:38 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 13e9497711b34daab936735edcfa87f13c89d006
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 11:29:01 2017 -0800

    resize art

commit 17d830dfde1174c95cb2bde7018fa1c85b8dcacc
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:59:56 2017 -0800

    delete file from images

commit 395946c6c9b54516461e79a232525e965632686d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:50:39 2017 -0800

    fix link

commit c328942818f6e4b5d2bd2062724a90687b85926e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:40:29 2017 -0800

    set up wizard table

commit 942af3c56e6e6f7736e1ea03d6801633237a9311
Merge: 6ce5c31d 819ba842
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 10:03:16 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 6ce5c31d127662010841791aa6498cd1606ed31e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 09:55:32 2017 -0800

    change branches

commit a3c28ae9e83bde3c97dd2d9232ad430e08ae972b
Merge: b794a681 0a914cf9
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 08:31:41 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/jdrs2icd' into jdrs2sh

commit b794a6819b1a3ad9deb834986a184f6b488497fa
Merge: af38dabf 2d1267b5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Feb 27 07:37:48 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit af38dabf79f6b51971fbf3891d72be73f0f9035a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Feb 24 11:25:09 2017 -0800

    changed all to End Session

    # Conflicts:
    #	devices/surface-hub/index.md

commit 4e124566f0a01017232d6c2c6be95db15abf5db3
Merge: d07431ae 4b1663d8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Feb 24 11:18:06 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit d07431ae706af0af4c6c44909c4e08b16b904ccc
Merge: 237cb29c 8bfa038e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 14 13:48:31 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh

commit 237cb29ce337e73ab6d707c1c06eaa89f5b49f3b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 15:06:27 2017 -0800

    undo all

commit 5461ccb226a5ee079f07c59d719c52f3fefe2343
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:53:02 2017 -0800

    sync

commit 1e56393ac1a33ff3d1b5eb2183e1ece4e776a9a6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:41:45 2017 -0800

    sync

commit 25ad8424a8f0dff551367cebedad18563e9d1081
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:32:18 2017 -0800

    iframe

commit 114cccfb75b3f27f46b67b5577d05a5de55662c1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:22:49 2017 -0800

    try span

commit 03c4b1bb5aad5871b6808c2b7c48e0e71b6c10c7
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 07:10:29 2017 -0800

    remove test

commit 8a55ced11b6e8d4117d940ec73e2b045a0d7cf24
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 06:59:19 2017 -0800

    test compass video

commit f4ae742993fa9892f4d7c411fa87683697849cf7
Merge: dd9a3df0 94b855cd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Feb 7 06:55:10 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2sh
2017-03-23 10:36:02 -07:00

13 KiB
Raw Blame History

title, description, ms.assetid, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, author, localizationpriority
title description ms.assetid keywords ms.prod ms.mktglfcycl ms.sitesec ms.pagetype author localizationpriority
Monitor your Microsoft Surface Hub Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS). 1D2ED317-DFD9-423D-B525-B16C2B9D6942 monitor Surface Hub, Microsoft Operations Management Suite, OMS w10 manage library surfacehub jdeckerMS medium

Monitor your Microsoft Surface Hub

Monitoring for Microsoft Surface Hub devices is enabled through Microsoft Operations Management Suite (OMS). The Operations Management Suite is Microsoft's IT management solution that helps you manage and protect your entire IT infrastructure, including your Surface Hubs.

Surface Hub is offered as a Log Analytics solution in OMS, allowing you to collect and view usage and reliability data across all your Surface Hubs. Use the Surface Hub solution to:

  • Inventory your Surface Hubs.
  • View a snapshot of usage and reliability data for Skype meetings, wired and wireless projection, and apps on your Surface Hubs.
  • Create custom alerts to respond quickly if your Surface Hubs report software or hardware issues.

Add Surface Hub to Operations Management Suite

  1. Sign in to Operations Management Suite (OMS). You can use either a Microsoft Account or a Work or School account to create a workspace. If your company is already using Azure Active Directory (Azure AD), use a Work or School account when you sign in to OMS. Using a Work or School account allows you to use identities from your Azure AD to manage permissions in OMS.

  2. Create a new OMS workspace. Enter a name for the workspace, select the workspace region, and provide the email address that you want associated with this workspace. Select Create.

  3. Link Azure subscription to your workspace. If your organization already has an Azure subscription, you can link it to your workspace. Note that you may need to request access from your organizations Azure administrator.

    Note

    If your organization does not have an Azure subscription, create a new one or select the default OMS Azure subscription from the list. Your workspace opens.

  4. Add Surface Hub solution. In the Solutions Gallery, select the Surface Hub tile in the gallery and then select Add on the solutions details page. The solution is now visible on your workspace.

Use the Surface Hub dashboard

From the Overview page in your OMS workspace, click the Surface Hub tile to see the Surface Hub dashboard. Use the dashboard to get a snapshot of usage and reliability data across your Surface Hubs. Click into each view on the dashboard to see detailed data, modify the query as desired, and create alerts.

Note

Most of these views show data for the past 30 days, but this is subject to your subscription's data retention policy.

Active Surface Hubs

Use this view to get an inventory of all your Surface Hubs. Once connected to OMS, each Surface Hub periodically sends a "heartbeat" event to the server. This view shows Surface Hubs that have reported a heartbeat in the past 24 hours.

Wireless projection

Use this view to get usage and reliability data for wireless projection over the past 30 days. The graph shows the total number of wireless connections across all your Surface Hubs, which provides an indication whether people in your organization are using this feature. If it's a low number, it may suggest a need to provide training to help people in your organization learn how to wirelessly connect to a Surface Hub.

Also, the graph shows a breakdown of successful and unsuccessful connections. If you see a high number of unsuccessful connections, devices may not properly support wireless projection using Miracast. For best performance, Microsoft suggests that devices run a WDI Wi-Fi driver and a WDDM 2.0 graphics driver. Use the details view to learn if wireless projection problems are common with particular devices.

When a connection fails, users can also do the following if they are using a Windows laptop or phone:

  • Remove the paired device from Settings > Devices > Connected devices, then try to connect again.
  • Reboot the device.

Wired projection

Use this view to get usage and reliability data for wired projection over the past 30 days. If the graph shows a high number of unsuccessful connections, it may indicate a connectivity issue in your audio-visual pipeline. For example, if you use a HDMI repeater or a center-of-room control panel, they may need to be restarted.

Application usage

Use this view to get usage data for apps on your Surface Hubs over the past 30 days. The data comes from app launches on your Surface Hubs, not including Skype for Business. This view helps you understand which Surface Hub apps are the most valuable in your organization. If you are deploying new line-of-business apps in your environment, this can also help you understand how often they are being used.

Application Crashes

Use this view to get reliability data for apps on your Surface Hubs over the past 30 days. The data comes from app crashes on your Surface Hubs. This view helps you detect and notify app developers of poorly behaving in-box and line-of-business apps.

Sample Queries

Use this to create custom alerts based on a recommended set of queries. Alerts help you respond quickly if your Surface Hubs report software or hardware issues. For more inforamtion, see Set up alerts using sample queries.

Set up alerts with sample queries

Use alerts to respond quickly if your Surface Hubs report software or hardware issues. Alert rules automatically run log searches according to a schedule, and runs one or more actions if the results match specific criteria. For more information, see Alerts in Log Analytics.

The Surface Hub Log Analytics solution comes with a set of sample queries to help you set up the appropriate alerts and understand how to resolve issues you may encounter. Use them as a starting point to plan your monitoring and support strategy.

This table describes the sample queries in the Surface Hub solution:

Alert type Impact Recommended remediation Details
Software Error Reboot the device.
Reboot manually, or using the Reboot configuration service provider.
Suggest doing this between meetings to minimize impact to your people in your organization.
Trigger conditions:
- A critical process in the Surface Hub operating system, such as the shell, projection, or Skype, crashes or becomes non-responsive.
- The device hasn't reported a heartbeat in the past 24 hours. This may be due to network connectivity issue or network-related hardware failure, or an error with the telemetry reporting system.
Software Error Check your Exchange service.
Verify:
- The service is available.
- The device account password is up to date see Password management for details.
Triggers when there's an error syncing the device calendar with Exchange.
Software Error Check your Skype for Business service.
Verify:
- The service is available.
- The device account password is up to date see Password management for details.
- The domain name for Skype for Business is properly configured - see Configure a domain name.
Triggers when Skype fails to sign in.
Software Error Reset the device.
This takes some time, so you should take the device offline.
For more information, see Device reset.
Triggers when there is an error cleaning up user and app data at the end of a session. When this operation repeatedly fails, the device is locked to protect user data. You must reset the device to continue.
Hardware Warning None. Indicates negligible impact to functionality. Triggers when there is an error with any of the following hardware components:
- Virtual pen slots
- NFC driver
- USB hub driver
- Bluetooth driver
- Proximity sensor
- Graphical performance (video card driver)
- Mismatched hard drive
- No keyboard/mouse detected
Hardware Error Contact Microsoft support.
Indicates impact to core functionality (such as Skype, projection, touch, and internet connectivity).
Note Some events, including heartbeat, include the devices serial number that you can use when contacting support.
Triggers when there is an error with any of the following hardware components.
Components that affect Skype:
- Speaker driver
- Microphone driver
- Camera driver
Components that affect wired and wireless projection:
- Wired touchback driver
- Wired ingest driver
- Wireless adapter driver
- Wi-Fi Direct error
Other components:
- Touch digitizer driver
- Network adapter error (not reported to OMS)

To set up an alert

  1. From the Surface Hub solution, select one of the sample queries.
  2. Modify the query as desired. See Log Analytics search reference to learn more.
  3. Click Alert at the top of the page to open the Add Alert Rule screen. See Alerts in Log Analytics for details on the options to configure the alert.
  4. Click Save to complete the alert rule. It will start running immediately.

Enroll your Surface Hub

For Surface Hub to connect to and register with the OMS service, it must have access to the port number of your domains and the URLs. This table list the ports that OMS needs. For more information, see Configure proxy and firewall settings in Log Analytics.

Note

Surface Hub does not currently support the use of a proxy server to communicate with the OMS service.

Agent resource Ports Bypass HTTPS inspection?
*.ods.opinsights.azure.com 443 Yes
*.oms.opinsights.azure.com 443 Yes
*.blob.core.windows.net 443 Yes
ods.systemcenteradvisor.com 443 No

The Microsoft Monitoring Agent, used to connect devices to OMS, is integrated with the Surface Hub operating system, so there is no need to install additional clients to connect Surface Hub to OMS.

Once your OMS workspace is set up, there are several ways to enroll your Surface Hub devices:

You'll need the workspace ID and primary key of your OMS workspace. You can get these from the OMS portal.

Enroll using the Settings app

To Enroll using the settings app

  1. From your Surface Hub, start Settings.
  2. Enter the device admin credentials when prompted.
  3. Select This device, and navigate to Device management.
  4. Under Monitoring, select Configure OMS settings.
  5. In the OMS settings dialog, select Enable monitoring.
  6. Type the workspace ID and primary key of your OMS workspace. You can get these from the OMS portal.
  7. Click OK to complete the configuration.

A confirmation dialog will appear telling you whether or not the OMS configuration was successfully applied to the device. If it was, the device will start sending data to OMS.

Enroll using a provisioning package

You can use a provisioning package to enroll your Surface Hub. For more infomation, see Create provisioning packages.

Enroll using a MDM provider

You can enroll Surface Hub into OMS using the SurfaceHub CSP. Intune and Configuration Manager provide built-in experiences to help create policy templates for Surface Hub. For more information, see Manage Surface Hub settings with an MDM provider.

Manage Microsoft Surface Hub

Microsoft Surface Hub administrator's guide