I managed to get my hands on a set of Logitech Meetup Kit for Microsoft Teams lately and almost immediately fell in love with both the equipment and the Microsoft Teams Room system. The one-touch to start the meeting works great and does improve a lot the whole video meeting experience.
The Kit includes a 4K camera, a touch-enabled Tap device, and a Lenovo MniPC that is preloaded by the Microsoft Teams Room system.
I was so intrigued by the preloaded system that I dug a bit deep to see if I can use my existing devices to build the system up on my own. Believe it or not, it’s totally doable.
Requirements
- A miniPC that runs Windows 10 with its ePKEA license key.
- A Windows I0 IoT Enterprise installation media, build 19041.631 or 19042.631 for the moment.
- A certified Tap device to pass the initial setup.
- A resouce mailbox that subscribes to Microsoft Teams license.
If you are setting it up on a Surface Pro 4 or up, you might be able to pass the room’s initial setup without a Tap device.
Speaking of the Tap device, it’s really nice to have it. As matter of a fact, for the Teams meeting, it seems a must because, for Teams meeting, you will need 2 screens to operate, one for the console and one for the actual meeting. If you are only using Zoom, you can get away with only one screen. Meaning that the tap is not necessary if you are only on Zoom meetings.
As for Windows 10 license, the devices from the vendors that run Teams Room are licensed by Windows 10 IoT enterprise. But technically, it should be able to run on other versions of Windows 10 as well.
Setting it up
First of all, prepare the installation media.
Simply download theĀ CreateSrsMedia.ps1 script and run it through an elevated PowerShell window.
Choose OEM when first asked, then you will need the following to prepare the installation media.
Select 7 for none when prompted by this:
When asked for the path to the root of the Windows install media, right-click the Windows 10 IoT Enterprise Media and choose Mount to mount as a drive on your system. And then use the drive letter for the question.
Then, wait…it could take some time to prepare the media.
Now, boot from this media on the miniPC you want to set up as the Teams Room.
You will have a Microsoft Teams Room ready shortly after.
A few quick notes
The default password for the local admin account of a Teams Room is sfb. So you should change it right after you have set it up.
You can join the room to your on-premise domain or Azure AD but it’s totally optional. I actually prefer it’s being a standalone machine solely for one function.
Honestly this is the best thing ever.
You had no issue setting this up on a “non-certified” PC – there is no easy information out there that confirms this except this article!
What is a “certified tap device”?
Great blog, unfortunately it looks like you need the Win 10 Enterprise IoT. I tried with different versions of Win 10 Enterprise and the script wouldn’t take it.
Yep, same here. Anyone got a workaround?
When I try this it is keep saying the size of the OS should be same.
It keep saying you must supply an IOS that matches the exact characteristics above ( which is giving the windows version details
asking for IOS path( should I download another windows?
For those that are getting the OS issue when it comes to the script, I edited the PowerShell script.
Around line 200 it’s when it’s checking the ISO.
I commented out the False and added a true. I did this for the Iso.Length check and the Get-FileHash check.
Change from
return $false
Change to
return $true
#return $falst