Hi Petri-X,
Although proxy servers are not generally recommended for real time communication devices, you can connect up to a proxy with these settings:
In the Microsoft Teams Rooms UI, click on the Settings gear icon where you'll be prompted for the local Administrator password on the device (the default password is sfb).
Tap on Settings followed by tapping on the Go to Windows button and then tapping on the go to Admin Sign In button and then clicking the Administrator button (if the computer is domain joined choose Other User, then use .\admin as the user name).
In the Search Windows box bottom left type in regedit (either long press the screen or right click and choose Run as administrator).
Click on the HKEY_USERS folder (you'll see a list of machine user SIDs) ensure the root folder HKEY_USERS is selected.
Click on File and then choose Load Hive.
Browse the to the C:\Users\Skype folder and type in the File name box NTUSER.dat and press the open button
You'll be prompted for a Key Name for your newly loaded Hive; type in Skype (you should now see the registry settings for the Skype User).
Open the Skype key and browse to HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings then ensure these settings are entered:
[HKEY_USERS\Skype\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
"MigrateProxy"=dword:00000001
"ProxyEnable"=dword:00000001
"ProxyServer"="xx.xx.xx.xx:8080"
If ProxyServer doesn't exist you may have to add this key as a string, change the xx.xx.xx.xx:8080 to the ip/host and port of your Proxy server.
Once you are finished making your changes highlight the Skype User key (root folder for Skype) and choose unload Hive from the Registry file menu (you'll be prompted for confirmation - select Yes ).
You can now close the registry editor and type logoff into the Windows search box.
Back at the sign-in screen, choose the Skype user. If all the previous steps were successful, the Microsoft Teams Rooms device will sign-in successfully.
As for the logs, there are a number of signing logs that are worth checking:
Under C:\users\skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalState\Tracing\
- msoidtrace{<long guid>}.txt
and C:\users\skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalCache\Roaming\Microsoft\Teams\
- Logs.txt
You can run the PowerShell command to collate them all into a single ZIP file to analyse later:
powershell -ExecutionPolicy unrestricted c:\rigel\x64\scripts\provisioning\ScriptLaunch.ps1 CollectSrsV2Logs.ps1
It would be worth checking conditional access for Teams and also if you have any 3rd party MFA enable for that account.
Thanks,
Dan