Feb 16 2017 11:01 AM
Last week I configured a surface hub (successfully joined to domain, on-prem mbx and SfB w/EV). I used the ICD (Imaging and Config Designer) to push additional settings to the device after OOBE. One of the settings is the workspace and primary key for OMS. It looks like the settings took because when I browse to settings | device management on the hub and select OMS, the checkbox is selected and I see in yellow text "The Microsoft Monitoring Agent has successfully connected to the Azure Operational Insights service." I also see the correct workspace ID. What I dont see is the workspace key in the appropriate field. (not sure if that's by design)
Looking in OMS I added the Surface Hub solution last Friday but that specific tile in OMS shows 'No Surface Hubs found'.
Can someone confirm that has their hub(s) showing up in OMS whether or not they see the workspace ID in their OMS settings on their hub?
Dave
Feb 21 2017 12:01 PM
Update: I removed the OMS config on the hub and then manually enabled OMS and entered the workspace ID and primary key. Again it looks like the config took as I see "The Microsoft Monitoring Agent has successfully connected to the Azure Operational Insights service." But I do not see the hub appear in the surface hub solution in OMS.
I neglected to mention in my initial post that the exchange and Skype for Business accounts are both on-prem. Does that matter?
Feb 21 2017 02:10 PM
SolutionFeb 24 2017 01:38 PM
My colleague Per Larsen, wrote some about here:
https://osddeployment.dk/2017/01/15/management-of-windows-10-team-on-surface-hub/
Hope it helps.
/Lars Berlau
Aug 16 2017 04:33 PM
I am having the same experience. Did you ever figure out what was causing this?
Aug 18 2017 11:31 AM
OMS was flaky for me until the Creators Update rolled out. Once my Surface Hubs updated to that, every device showed up in OMS.
IIRC, there was an issue with storing a certificate pre-Creators Update that was causing the problem. The original workaround was to reset the device to clear the certificate store then rejoin to OMS. Hopefully if you haven't updated to CU that will fix the issue for you.
Sep 08 2017 02:43 AM
Feb 21 2017 02:10 PM
Solution