Forum Discussion
Migrated Surface Hub 2S to MTRoW - 3 things I don’t like
Hello! I recently migrated our 85” Surface Hub 2S from Windows 10 Team OS to MTRoW Experience. The process was simple and relatively quick. After getting everything dialed in, here is what I wish the new OS still retained:
1. No more apps. Specifically no browser. Previously, staff would launch Edge and display reports from the various software we subscribe to. Now, I know what most are thinking - why don’t you just cast to the device to achieve the same outcome?
2. Miracast no longer supported - no longer can users Windows + K and share the contents of their device. One workaround I found is to switch user and sign in as admin > launch screen share > alt tab back to Teams Room app. But this isn’t permanent and staff expect to just Windows + K like they have been on Windows 10 Team OS.
3. Casting from Teams - I do have the option to cast from the Teams app on my laptop to the Surface Hub. But this experience is abysmal. Content shared this way has been very choppy and delayed. This method holds true on the Surface Hub, a separate MTRoW device, and our MTRoA device.
23 Replies
We are also affected by this. We request that Microsoft restores the Miracast and HDMI functionalities for the Skype user on the migrated SH2s, not solely for the admin user. The removal of these functions should not have occurred in the first place.
- Also we have carried out the migration and we considered to buy other Surface Hubs for your institution due to the quality and reliability.
HOWEVER, looking on that kind of "software" it really offers nothing compared to Windows 10 Team OS. We will need to have a look again on other Hardware suppliers. RE casting via Teams -
Here is what I discovered today. Following this guide (https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/meetings/fix-choppy-video), I enabled high motion screen sharing (CTRL ALT SHIFT T) and achieved the below results which was a massive improvement in Sent Frame Rate. Prior to enabling this, the FPS never exceeded 3 FPS.I haven't found a policy or a way to enable high motion screen sharing for all users. Currently, to enable this feature, users have to press CTRL ALT SHIFT T every time they want to cast to the Surface Hub. Also tested this on MTRoW and MTRoA devices (Rally Bars) and achieved the same results.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 agree, I do not understand the decision to remove HDMI-Ingest, remove Miracast, and to remove all the apps (which removes OneDrive and web access). All of these were not only the most used and relied on features, but the things that made the Surface hub stand-out from every other MTR device. Now it's just another Touch MTR with a price tag of double or triple of every other MTR solution.
- I hope that someone from MS is reading this and will make the appropriate changes. We are not asking for the implementation of a new feature, but only for the reintroduction of what was already available. This should not be difficult, especially in the topic of screen sharing via HDMI cable.
I've just connected the Logitech TAP touch controller to the SH2S and the HDMI screen sharing option has appeared again next to CAST on SH2S, which indicates that it is still there from the software/hardware side, it has just been hidden, for some unknown reason.- So are you able to use HDMI ingest from the TAP to share content onto the SH2S?
- Disabling both of these functionalities makes no sense from the end-user's point of view. Screen sharing via cable is the oldest and most proven method of screen sharing when there are any problems with the wireless connection.
- My thoughts exactly. And I agree on the physical connection. My only gripe with this is that compared to other MTRoW devices (we have a few Logitech Rally systems), when you connect a MTR device to the laptop and tap on Share on the MTR device, HDMI or USB ingest is recognized and begins to share. Now on the Surface Hub, users have to connect the device with HDMI or USB and then change the input on the Surface Hub. That part doesn't make sense to me.
- We've also found that HDMI and USB ingestion is not working, is that the same for you?
slimjimwoods for the most part, yes. My expectation would be that when an HDMI or USB device is connected and you click on "Share" on the Surface Hub, it would detect the ingest and switch to that source. Exactly the same way it does on our Rally Bar system running MTRoW.
Instead, when you click on "Share", it prompts the user to only cast. The user now was to change the input on the side of the Surface Hub.
- Although, after testing it seems you can't share a connected device in a meeting, which is lost functionality.... I guess this really is just a Windows 11 PC now running Teams as a standard application with no decent ingestion to meetings...
