Teams Rooms console

[dougmcneill]

Good afternoon all!

I've been able to create the install media for a teams room based off of this walkthrough. 

It's being installed on a Surface Pro 4, and will install from the media correctly, but when i go to finish the final steps, it asks to connected to a dock to finish, but i'm trying to configure it as a standalone system for testing. I've done some searching online, but I can't seem to find any information on that. 

Any thoughts or ideas? 

Thank you!

[#2 · Accepted solution]

Yeah! You need a doc: from the link:

Microsoft Teams Rooms relies on the presence of certified console hardware. Even a correctly created image containing the Microsoft Teams Rooms console app will not boot past the initial setup procedure unless the console hardware is detected. For Surface Pro based solutions, the Surface Pro must be connected to its accompanying dock hardware to pass this check.

See dock requirements here:

https://docs.microsoft.com/en-us/microsoftteams/room-systems/requirements

[#3]

@adam deltinger 

Thank you for the information, i was hoping there was a way around that, but it is what it is.

Enjoy your weekend!

Doug

[#4]

@dougmcneill As Adam said there's a device check that you can't avoid.

I would also point out that generally the first gen of Teams Rooms hardware that used a Surface Pro are somewhat obsolete, and you would be better looking at the fully integrated devices such as Lenovo, HP, Yealink, Logitech Tap. It's then just a case of taking out of the box and plugging it in. Better value and better installation options.

[#5]

@Steven Collier 

Configure a Microsoft Teams Rooms console

HI 

Could help me with this error. This error occurs when I try to prepare the installation media.

I do everything indicated in the instructions.

PS>TerminatingError(Invoke-Native): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Command '& robocopy /mir 'd:\SW\SW2\SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-2_MLF_X21-79647' 'F:\' /R:0 /xf install.wim' failed test '$_ -lt 8 -and $_ -ge 0' with code '11'."

See the LOG below:

**********************

Windows PowerShell transcript start

Start time: 20190604152529

Username: 

RunAs User: Administrator

Configuration Name: 

Machine: PC (Microsoft Windows NT 10.0.17134.0)

Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Process ID: 39944

PSVersion: 5.1.17134.590

PSEdition: Desktop

PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17134.590

BuildVersion: 10.0.17134.590

CLRVersion: 4.0.30319.42000

WSManStackVersion: 3.0

PSRemotingProtocolVersion: 2.3

SerializationVersion: 1.1.0.1

**********************

Transcript started, output file is C:\Users\Administrator\Documents\PowerShell_transcript.ICGUA-PC-541.xCBluz0D.20190604152529.txt

Script version 1.4.3

Downloading CreateSrsMedia...

done

Validating signature for update.ps1...

success.

919C06207B8A9C6B71423B7916AB61D3F6EF6DC7BD04AD4EC9CB172053B3317991E8274D1DC0F6335D27B8F4E299F7336FEE6F5966624F2A5815A7EB8293884E

68308

What type of customer are you?

What type of customer are you?

Please make sure you have all of the following available:

1. A USB drive with sufficient space (16GB+).

   The contents of this drive WILL BE LOST!

2. Windows 10 Enterprise media that matches your SRSv2 deployment kit.

   Enterprise customers can access Windows 10 Enterprise media from the Volume Licensing Service Center:

   http://www.microsoft.com/licensing/servicecenter

3. Any language pack (LP and/or LIP) files to be included.

   MPSA customers:         http://go.microsoft.com/fwlink/?LinkId=125893

   Other volume licensees: http://www.microsoft.com/licensing/servicecenter

Please do not continue until you have all these items in order.

Found deployment kit already downloaded.

Validating signature for SRSDeploymentKit-4.0.85.0.msi...

success.

Extracting the deployment kit...

done.

This deployment kit is built for Windows build 10.0.17134.1.

This deployment kit draws its drivers from %configsetroot%\AutoUnattend_Files\DistShare\Out-of-Box Drivers.

Please indicate what drivers you wish to use with this installation.

[ 0] Logitech SmartDock

[ 1] Crestron SR

[ 2] Polycom MSR

[ 3] Lenovo Hub 500

[ 4] LRS

[ 5] HP Slice 2.0

[ 6] Crestron Flex

[ 7] None

Selected option 0.

[ 0] Surface Pro 4

[ 1] Surface Pro (2017)

[ 2] Surface Pro 6

Selected option 2.

Downloading driver...

done

Validating signature for SurfacePro6_Win10_17134_1808507_3.msi...

success.

Extracting SurfacePro6_Win10_17134_1808507_3.msi...

done.

Identifying language packs...

... done identifying language packs.

Found update KB4340917 already downloaded.

Validating signature for windows10.0-kb4340917-x64_ed5f586fa9d7064d61e45c523f20ba7fc1ff142a.msu...

success.

WARNING: THIS IS YOUR ONLY CHANCE TO PRE-INSTALL LANGUAGE PACKS.

Because you are pre-installing an update, you will NOT be able to pre-install language packs to the image at a later point.

You are currently building an image with NO pre-installed language packs.

Are you ABSOLUTELY SURE this is what you intended?

WARNING: PROCEEDING TO GENERATE SLIPSTREAM IMAGE WITH NO PRE-INSTALLED LANGUAGE PACKS.

Reminder: all data on the drive you select will be lost!

[ 0] KINGSTON SA400S37240G

[ 1] JetFlash Transcend 16GB

Selected option 0.

Creating Enterprise media.

Creating UEFI-compatible media.

Using SRSv2 kit:       C:\Users\administrator\Downloads\SRSDeploymentKit-4.0.85.0.msi

Using driver packs:

    C:\Users\administrator\Downloads\SurfacePro6_Win10_17134_1808507_3.msi

Using Windows media:   d:\SW\SW2\SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-2_MLF_X21-79647

Using language packs:

Using updates:

    C:\Users\administrator\Downloads\windows10.0-kb4340917-x64_ed5f586fa9d7064d61e45c523f20ba7fc1ff142a.msu

Writing stick:         KINGSTON SA400S37240G

Formatting and partitioning the target drive...

done.

Copying Windows...

PS>TerminatingError(Invoke-Native): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Command '& robocopy /mir 'd:\SW\SW2\SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-2_MLF_X21-79647' 'F:\' /R:0 /xf install.wim' failed test '$_ -lt 8 -and $_ -ge 0' with code '11'."

>> TerminatingError(Invoke-Native): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Command '& robocopy /mir 'd:\SW\SW2\SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-2_MLF_X21-79647' 'F:\' /R:0 /xf install.wim' failed test '$_ -lt 8 -and $_ -ge 0' with code '11'."

>> TerminatingError(Invoke-Native): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Command '& robocopy /mir 'd:\SW\SW2\SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-2_MLF_X21-79647' 'F:\' /R:0 /xf install.wim' failed test '$_ -lt 8 -and $_ -ge 0' with code '11'."

**********************

Windows PowerShell transcript end

End time: 20190604152908

**********************

[#6]

Well, this sucks.  I was trying to do the exact same thing.  I have some Surface Pro 4s here that I can use and just wanted to test out the functionality.  Seems dumb that I'd have to go shell out hundreds or thousands of dollars before I even know if this is something we want to move forward with.

Anyone know of a trick to bypass the dock requirement or fake it out?  :)  I have the Microsoft Dock for the SP4 but that doesn't work either.  :(

[#7]

@Mike Boehm realistically you wouldn't get particularly close to the experience if the app just ran on a regular Windows device.

1. You couldn't connect your laptop and share it's screen without the HDMI-in capture card.

2. You wouldn't get the proximity join from your laptop or phone without the BLE Beacon

3. Dual front-of-room displays (it's not the same as how Surface dock does it)

4. Having enough powered USB ports to drive cameras, speakers etc.

5. Motion detection for power on/off

Microsoft TRS is a qualified combination of hardware and software that enables the same features on all devices, the device is just as much part of the solution as the software. Fundamentally there is little to see as its just simple, minimal, controls.

[#8]

@adam deltinger

Do you think I would be able to install the Teams Console on a Surface GO device? 

[#9]

No, see the supported devices here:

https://docs.microsoft.com/en-us/microsoftteams/room-systems/requirements

Adam

[#10]

@dougmcneill