Forum Discussion
Migrated Surface Hub 2S to MTRoW - 3 things I don’t like
RE casting via Teams -
This is interesting information for us, AV technicians, but it changes nothing about the use of these devices by our end-users. We have over 2,000 employees in the company, all our meeting rooms have been upgraded to MTR technology and we offer standardisation - no matter which room, it's always the same experience - a TAP Scheduler at the door and a TAP touch screen with an HDMI cable for screen sharing on the table in the room - and it's up to the end-users to decide whether they prefer to use a cable or share wirelessly. In my case, it won't go through the CAB panel that the end-user has to press a combination of buttons each time before each meeting to get the sharing working properly - they'd rather tell me to throw all the Surface Hubs in the storage room and replace them with Yealinks/DTENs/Cisco or other boards, where screen sharing is working as intended.
- We have similarly standardized on ensuring that every room has an HDMI cable with adapters allowing our users to immediately share their screen weather in or out of a meeting. Wireless has always been an optional feature, not part of the standard. There are too many variables in our environment to make wireless reliable enough for a standard. Its a nice-to-have feature that when it does work, it's good for text and static images and not great with video. As of now, our standards are now up for review and possibly replacement to another MTR solution that can offer consistent reliable screensharing via HDMI.
- I completely agree with you, we also consider a HDMI cable connection as standard and wireless as an option.
However, there is a huge problem here - all these negative experiences that we share here on the forum are not really reaching anyone. Up until a few months ago there was constant advertising of SH3/SH2 upgrade kits on various panels by Jimmy and Michel, and now complete silence. You can't get anything from anyone about Surface Hubs, their support is completely laughable - the lady I contacted, who in theory was an ‘SH support specialist’, had no idea about their operation and functionality, I also sent several emails to MS people dealing with these devices - no reply. You have bought the device and goodbye, have a nice life - this is how support for these devices currently works. This is a completely preposterous approach, in my company we will no longer purchase any MTR devices from MS in any future generation.
Just a few days ago I spoke to the excellent people at Huddly (L1, S1 and Crew cameras), shared my feeeback and thoughts with them and guess what - with a very high probability my comments make it onto their roadmap, they really listen to their customers.
And here, out of the blue, an ‘upgrade’ withdraws a great feature from an older version (HDMI Ingest, Miracast) - apparently it's still available, just completely blocked for no reason, then there's still no one to talk to about it. Great support, I would say 2/10 level.- cezarcretu
Microsoft
Hello Slav1155,
On behalf of the team please accept my apologies for the experience you are having with both the device features and support.
We have various channels from which we gather feedback from our customers and the Product Group is aware of the missing features and I can assure you that these have been taken into consideration.
In regard to your support experience, I have sent you a PM asking for your case details so I can follow up on this. Once again, please accept my apologies for these issues and thank you for your patience while we work on resolving them. I'm happy to be your point of contact for any issues regarding Surface Hub in the near future and I will make sure to connect you with the right team if I'm unable to help.
Thank you,
Cezar
In my case we have Surface hub 2S with 50" screens. We were projecting the Surface hub screen over to big projector using HDMI out.
After Win11 MTRoW update, HDMI out does not work as well which is huge problem for us, and the Surface hub screen way too small for our rooms.
( I also found that when you go to Windows admin side, HDMI works perfectly fine, so this does looks like MTR app is not capable of handling second monitor via HDMI.
I also tried configuring extended monitor using xml file assuming this work as a normal MTR, but there is no luck with that either).
I have currently opened a case with Microsoft, hope they can give us a solution.
- Thanks for posting your experience. I hadn't tested the video out yet, and I'm almost not surprised its been nurfed too. TBH, we had to move on from testing the v3 to testing other devices for deployment because of these issues. We also have a couple dozen 50" screens connected to projectors for large spaces (which proved challenging enough on its own).
I hope your case gets some movement and positive change out of the MTR team.
