Teams Rooms console, Windows version
Hello guys, I read this : https://docs.microsoft.com/en-us/microsoftteams/room-systems/console to configure a Teams console but honestly, it is really hard. I have not a Windows Enterprise version or Enterprise IOT, that is the main problem. In the company there are only 100 employees, and i have Windows Pro. There is no reason for me to buy a Volume license. And additional the Enterprise IOT, where can i get this? Is there any other way to build a Teams Rooms console? Is not really small-business-friendly. Cheers.
Get the all info for "Additional Information" attributes for all meeting rooms - PowerShell
Hi Tech Folks, I am trying to get the info audio, video, display, tags, etc. which is located under each meeting room or basically a resource which the type is Room. Exchange Admin Center --> Resources --> Select Any Meeting Room (TYPE:ROOM) --> Additional Information I used this command which is working fine and reveals everything about the room and its properties , but NOT those above info I m looking for: Get-Mailbox -Filter '(RecipientTypeDetails -eq "RoomMailBox")' | Select * | Format-list How can I get those Additional Attributes by that PS command? Any thoughts? Thanks for your inputs
Microsoft Teams Rooms console ( USB installation issues )
Hi everyone, I tried to follow this guide https://www.docs.microsoft.com/en-us/MicrosoftTeams/rooms/console, but i can not finished the last step that required me a specific Windows 10 ( A specific version of Windows 10 is required, and this version is only available to volume licensing customers. You can get a copy from the VLSC ). The question is : Why is the version of Windows 10 Ent VLSC the correct one compared to any other ? My own Win 10 Enterprise isn't enough ? And There is some way to avoid using VLSC ? Thanks in advanceAvailability of Staff and Resources (Rooms)
How can I manage that services can only be booked when at that a certain time a certain number of staff members and a room (managed as a resource within Office 365) are available? Basically, this is only about the cross checking of several outlook calendars. I cannot find the setting but please - these "features" are so basic that I really do not believe that Microsoft is so incapable or brazen not to offer them in a paid service.
Show guest users in Teams Rooms search
Hey folks, I have a question regarding Microsoft Teams Rooms devices in with guest users in my tenant: I have invited users from another M365 tenant into my AzureAD. When I start a session on my rooms device and want to add one of the external guest users, my device could not find them if I search them by name. It works, when I enter the whole SIP address, so I just want them to be searchable just with the display name without entering the whole address. Any ideas if there is a solution for this? Thanks in advance, SebastianDeploying Microsoft Teams Rooms via Autopilot in Self-Deployment Mode
Description: We are experiencing issues with deploying our Microsoft Teams Room (MTR) systems via Windows Autopilot in Self-Deployment Mode. Despite following the official Microsoft documentation (Autopilot Autologin for Teams Rooms), the device fails to complete the login process. Setup Details: Device: Certified Intel NUC, previously in use. OS Installation: Windows 11 Pro pre-installed. Autopilot Import: The device was successfully imported into Autopilot. Group Assignment: GroupTag "MTR-ConsoleName" has been correctly assigned. Dynamic Group: The device appears in the associated dynamic MTR group. Profiles and Assignments: Deployment Profile and Enrollment Status Page (ESP) are assigned to the device. Teams Room Update App: Deployed via Intune and assigned to the MTR group (also included in ESP). LAPS: Local Administrator Password Solution (LAPS) is active on the device. Teams Rooms Pro Console: The device appears in the console and has been assigned to a resource account with a Teams Room Pro license. Issue: After completing the deployment process, the device hangs on the login screen and cannot connect to the resource account. This prevents the self-deployment process from completing. Steps Already Taken to Resolve the Issue: The device has been completely removed from Intune and Autopilot and re-added. A custom device restriction policy was created to ensure the device is allowed. All Intune and Azure policies were reviewed and optimized to avoid conflicts. Despite these efforts, the issue persists. Questions: Are there specific requirements or limitations that we might have overlooked? Are additional settings or policies required to ensure the device connects to the resource account successfully? Could existing policies, such as LAPS, interfere with the login process? Are there any known issues related to Autopilot and Teams Room deployments, particularly for previously used devices? We urgently request your assistance in identifying and resolving this issue, as these MTR systems are critical for our operations. Thank you for your support!
