Miracast not working on Surface Hub 3 (Windows 11 IoT mode)
Hi everyone, we’re currently experiencing issues with Miracast on our Surface Hub 3 devices when running in Windows 11 (IoT) mode. As far as we recall, Miracast used to work correctly in Windows 11 mode without any issues. We are also aware of the planned rollout for this functionality in MTR mode around May 2026. However, since this was already working for us in W11 mode, we’re wondering if something has recently changed that could have impacted this behavior. So far, we’ve tried all the usual troubleshooting steps, including: - Device reboots - Policy/configuration checks and changes - Full device reinstallation Unfortunately, none of these actions resolved the issue. Has anyone experienced something similar or is aware of recent changes that might explain this? Thanks in advance, AndreaMeeting Control, Now Within Reach: Surface Hub 3 + MAXHUB Universal Console
Modern meeting spaces require flexibility, simplicity, and consistency for IT teams managing collaboration environments. Announced at Microsoft Ignite 2024, center-of-table console support for Surface Hub 3 extends Microsoft Teams Rooms on Windows by enabling certified third-party touch consoles for in-room meeting control. Center-of-Table Console Support Surface Hub 3 now supports Teams Rooms Certified Universal Consoles, introducing an additional option to control meetings beyond the interactive display. This includes the MAXHUB TCP33T Universal Console, a certified hardware solution in this ecosystem. By connecting a touch console directly to Surface Hub 3, users can join meetings, manage controls, and share wired content from their PCs while seated at the table. Benefits of Certified Universal Consoles Teams Rooms Certified Universal Consoles can help provide IT admins with: Microsoft Teams Rooms integration through certified accessories Flexible room design options including front-of-room deployments Consistent user experience across meeting spaces Simplified meeting controls for table-based interaction MAXHUB TCP33T Universal Console Overview The MAXHUB TCP33T is a Teams Rooms Certified Universal Console designed to work with Windows-based touch board devices such as Surface Hub 3. It delivers touchscreen control for Microsoft Teams Rooms meetings and serves as a dedicated entry point for wired content sharing. Common Deployment Scenarios Large conference rooms requiring table-based control Standardized Teams Rooms deployments across buildings Collaborative meetings requiring easy content sharing Requirements Deployments require Surface Hub 3 running Microsoft Teams Rooms on Windows and a Teams Rooms Certified Universal Console such as the MAXHUB TCP33T. Looking Ahead This new Universal Console ecosystem reflects Microsoft's commitment to flexible, scalable collaboration experiences. By pairing Surface Hub 3 with certified accessories like the MAXHUB TCP33T, organizations can design meeting spaces that meet modern collaboration needs. Live Webinar Wednesday the 14th of January... Sign up now! Join us for an exclusive webinar with Microsoft and MAXHUB as we explore how the MAXHUB Universal Console enhances the Microsoft Surface Hub experience. Hear from industry experts and learn how to: ✔ Reduce friction in the room ✔ Streamline collaboration workflows ✔ Centralize meeting controls — without leaving your seat! Featured Speakers: • Frank Buchholz, Director, Product Marketing — Microsoft • Jean Barrett, Technology Solutions Professional — Microsoft • Alan Nicholls, Microsoft Teams Professional — MAXHUB Register for a session and secure your spot👇 January 14 @9AM PST session: Register here January 14 @5PM PST session: Register here Resources Center-of-table console support Teams Rooms app version needed Center-of-table console support announcement during Microsoft Ignite 2024
Provisioning does not add to MDM - Surface hub
When using the Windows Configuration Designer to create a provisioning package I'm unsure what to add for the MDM devices. Some devices seem to enter the MDM and some don't. Unsure if it's the build on these devices. I've looked for documentation and can't find any for what credentials to use for the following on the Enrol in device management I need to know what to enter for the following fields please. So that I can insure these devices populate into Intune. I don't know why MS make it so hard for this as the setup of the older 2s devices was much easier. Thanks Michael
Safe to delete the Surface Hub 3 "admin" account?
We manage our Surface Hubs with Teams Rooms Pro (and Intune where needed). The Windows default local administrator account is disabled during enrollment by the Deployment policy. Intune is configured to add an Entra group to the Local Administrators group, whose membership we manage with an Identity Governance policy. We are all set for administration. And if we were ever to be locked out of a Surface Hub, we would re-image it and begin again. During the Out-of-box experience, a new administrator account named ".\admin", with a well-known simple three letter password, is added to Surface Hub 3 devices. Presumably, the account is added a "convenience". All my testing and research has shown that this account is not needed or used. Is it safe to delete ".\admin" account? Or later, will I find Microsoft expected to use that account in some way? Thanks, in advance.
