SOLVED

connecting surface hub to OMS

%3CLINGO-SUB%20id%3D%22lingo-sub-46576%22%20slang%3D%22en-US%22%3Econnecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46576%22%20slang%3D%22en-US%22%3E%3CP%3ELast%20week%20I%20configured%20a%20surface%20hub%20(successfully%20joined%20to%20domain%2C%20on-prem%20mbx%20and%20SfB%20w%2FEV).%26nbsp%3B%20I%20used%20the%20ICD%20(Imaging%20and%20Config%20Designer)%20to%20push%20additional%20settings%20to%20the%20device%20after%20OOBE.%26nbsp%3B%20One%20of%20the%20settings%20is%20the%20workspace%20and%20primary%20key%20for%20OMS.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20It%20looks%20like%20the%20settings%20took%20because%20when%20I%20browse%20to%20settings%20%7C%20device%20management%20on%20the%20hub%20and%20select%20OMS%2C%20the%20checkbox%20is%20selected%20and%20I%20see%20in%20yellow%20text%20%22The%20Microsoft%20Monitoring%20Agent%20has%20successfully%20connected%20to%20the%20Azure%20Operational%20Insights%20service.%22%26nbsp%3B%26nbsp%3B%20I%20also%20see%20the%20correct%20workspace%20ID.%26nbsp%3B%26nbsp%3B%20What%20I%20dont%20see%20is%20the%20workspace%20key%20in%20the%20appropriate%20field.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20(not%20sure%20if%20that's%20by%20design)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20in%20OMS%20I%20added%20the%20Surface%20Hub%20solution%20last%20Friday%20but%20that%20specific%20tile%20in%20OMS%20shows%26nbsp%3B%20'No%20Surface%20Hubs%20found'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20someone%20confirm%20that%20has%20their%20hub(s)%20showing%20up%20in%20OMS%20whether%20or%20not%20they%20see%20the%20workspace%20ID%20in%20their%20OMS%20settings%20on%20their%20hub%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDave%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-104542%22%20slang%3D%22en-US%22%3ERe%3A%20connecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-104542%22%20slang%3D%22en-US%22%3EYup%2C%20basically%20this.%20Although%20I%20was%20told%20that%20the%20certificate%20had%20expired%20and%20they%20couldn't%20deliver%20a%20new%20one%20without%20pushing%20a%20new%20build%20(hence%20fixed%20in%20Creators%20Update).%3CBR%20%2F%3E%3CBR%20%2F%3EInterestingly%20device%20reset%20never%20worked%20for%20us%2C%20we%20had%20to%20wait%20for%20the%20Creators%20Update.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97693%22%20slang%3D%22en-US%22%3ERe%3A%20connecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97693%22%20slang%3D%22en-US%22%3E%3CP%3EOMS%20was%20flaky%20for%20me%20until%20the%20Creators%20Update%20rolled%20out.%20%26nbsp%3BOnce%20my%20Surface%20Hubs%20updated%20to%20that%2C%20every%20device%20showed%20up%20in%20OMS.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIIRC%2C%20there%20was%20an%20issue%20with%20storing%20a%20certificate%20pre-Creators%20Update%20that%20was%20causing%20the%20problem.%20%26nbsp%3BThe%20original%20workaround%20was%20to%20reset%20the%20device%20to%20clear%20the%20certificate%20store%20then%20rejoin%20to%20OMS.%20%26nbsp%3BHopefully%20if%20you%20haven't%20updated%20to%20CU%20that%20will%20fix%20the%20issue%20for%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-97077%22%20slang%3D%22en-US%22%3ERe%3A%20connecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-97077%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20having%20the%20same%20experience.%20Did%20you%20ever%20figure%20out%20what%20was%20causing%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-48653%22%20slang%3D%22en-US%22%3ERe%3A%20connecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-48653%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20colleague%20Per%20Larsen%2C%20wrote%20some%20about%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fosddeployment.dk%2F2017%2F01%2F15%2Fmanagement-of-windows-10-team-on-surface-hub%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fosddeployment.dk%2F2017%2F01%2F15%2Fmanagement-of-windows-10-team-on-surface-hub%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20it%20helps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2FLars%20Berlau%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47546%22%20slang%3D%22en-US%22%3ERe%3A%20connecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47546%22%20slang%3D%22en-US%22%3EHi%20David%2C%3CBR%20%2F%3Eit%20is%20expected%20that%20after%20the%26nbsp%3Bjoin%20the%20key%20is%20will%20not%20longer%20be%20showing%20in%20the%20UI.%3CBR%20%2F%3EIt%20can%20also%20take%20some%20time%26nbsp%3Bif%20you%20just%20added%20the%20Solution%20to%20OMS%20and%20added%20the%26nbsp%3BSurface%20Hub%20to%26nbsp%3BOMS.%26nbsp%3B%3CBR%20%2F%3EI%20don%C2%B4t%20have%20an%20exact%20timeframe%20for%20this%20but%20for%20adding%20the%20Solution%20to%20OMS%20give%20it%20maybe%2024h%2C%26nbsp%3B%3CBR%20%2F%3Eadding%20new%20Surface%20Hub%20to%20OMS%20should%20not%20take%20longer%20then%201h.%20%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20me%20this%20always%20just%20works%20fine%20and%20the%20Hubs%20are%20showing%20up%20after%20a%20short%20time.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20the%20Hubs%20are%20still%20not%20showing%20up%2C%20I%20would%20recommend%20to%20open%20a%20case%20with%20our%20CSS%20Support%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FSurfaceHubSupport%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FSurfaceHubSupport%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E-%20Christian%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47519%22%20slang%3D%22en-US%22%3ERe%3A%20connecting%20surface%20hub%20to%20OMS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47519%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20I%20removed%20the%20OMS%20config%20on%20the%20hub%20and%20then%20manually%20enabled%20OMS%20and%20entered%20the%20workspace%20ID%20and%20primary%20key.%26nbsp%3B%26nbsp%3B%20Again%20it%20looks%20like%20the%20config%20took%20as%20I%20see%20%22The%20Microsoft%20Monitoring%20Agent%20has%20successfully%20connected%20to%20the%20Azure%20Operational%20Insights%20service.%22%26nbsp%3B%20But%20I%20do%20not%20see%20the%20hub%20appear%20in%20the%20surface%20hub%20solution%20in%20OMS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20neglected%20to%20mention%20in%20my%20initial%20post%20that%20the%20exchange%20and%20Skype%20for%20Business%20accounts%20are%20both%20on-prem.%26nbsp%3B%20Does%20that%20matter%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

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

6 Replies

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?

 

 

best response confirmed by Nydia Cavazos (Microsoft)
Solution
Hi David,
it is expected that after the join the key is will not longer be showing in the UI.
It can also take some time if you just added the Solution to OMS and added the Surface Hub to OMS. 
I don´t have an exact timeframe for this but for adding the Solution to OMS give it maybe 24h, 
adding new Surface Hub to OMS should not take longer then 1h.

For me this always just works fine and the Hubs are showing up after a short time.

If the Hubs are still not showing up, I would recommend to open a case with our CSS Support:
https://aka.ms/SurfaceHubSupport

- Christian

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

I am having the same experience. Did you ever figure out what was causing this?

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.

Yup, basically this. Although I was told that the certificate had expired and they couldn't deliver a new one without pushing a new build (hence fixed in Creators Update).

Interestingly device reset never worked for us, we had to wait for the Creators Update.