Looking for:
Managing a Microsoft Teams Room (MTR) Device with Intune – Part 1 – Theme – Blog – . |
Microsoft teams rooms intune management -
An additional tip is to name Teams Room devices with a prefix that allows devices to be grouped dynamically. You can rename devices with either a Windows 10 configuration policy or manually per device in Intune. Depending on your current scenario, there are several other enrollment options available:. For more details about available enrollment methods, see Intune enrollment methods for Windows devices.
Recommendation: Use Windows configuration profiles to configure device settings that you need to change beyond the shipped defaults. The following Windows 10 Configuration Policy types may be used with Windows 10 based meeting room devices:. Check for supported hardware here. Learn more about available configuration policies here: Create a device profile in Microsoft Intune.
Compliance policies Recommendation: Use compliance policies to achieve the desired security level for your Teams devices. You can use compliance policies on your Teams Room devices. Make sure to create the appropriate exclusions for any existing Windows 10 compliance policies that are currently deployed in your organization to All devices.
For example, you may have configured the setting Maximum minutes of inactivity before password is required in a policy for all Windows 10 desktop devices but this would result in a poor meeting room experience if applied to Teams Room devices. If you currently have Windows 10 compliance policies deployed to large groups of devices, make sure you use the Exclude group feature so that you can target a more specific compliance policy for the Teams Room devices.
For detailed guidance, see Use compliance policies to set rules for devices you manage with Intune. Conditional Access policies with only location-based conditions can be applied to Microsoft Teams Rooms accounts at this time. Microsoft is currently working on updates that will allow additional conditions to be set, such as device compliance. Then you can use the dynamic group feature to group together all devices that start with MTR. The reason for device-group assignment is that Teams Room devices sign in to Windows with a local user account instead of an Azure AD user account and during sync with Intune, would not request any user-assigned policy.
As always, we want to hear from you! Room inventory tracking with a bulk export option that lists room devices, peripherals, makes, and models.
Easy onboarding with self-enrollment of room devices to the Microsoft Teams Rooms managed service. Customer portal for managed service capabilities, insights, administrative settings, and room group management. Application, operating system, peripheral and firmware health monitoring.
Automated incident detection for issues affecting meeting experiences due to issues such as peripheral health. Health overview of the entire room real estate and incidents through the Microsoft Teams Rooms managed service portal. Automated diagnostics and auto-remediation where applicable. Service Now integration for incident coordination. Automated meeting application and firmware update orchestration based on customer configurable deployment rings. Incidents related to the meeting room app, room devices, and peripherals are included in Microsoft Teams Rooms managed service support.
Customer-initiated tickets: 3 business days System-initiated tickets: 15 business days. Issues related to another Microsoft product outside the scope of the Microsoft Teams Rooms managed service are directed to the appropriate support team.
In some cases, you may be responsible for engaging directly with your OEM. Investigation and guidance for Microsoft Teams Rooms Windows configuration including Microsoft Teams Rooms app settings, first-party network configuration, first-party software setup, and recommended power settings and configuration.
Any third-party software configurations and investigations that aren't directly part of the Microsoft Teams Room app. Also, any OEM-specific configurations that require configuration outside of first-party windows, or Microsoft Teams Room app settings.
The Intune management extension agent checks with Intune once every hour and after every reboot for any new scripts or changes. If the script fails, the Intune management extension agent will attempt to retry the script three times for the next 3 consecutive Intune management extension agent check-ins. One of the most common issues that can occur is that the Intune management extension agent does not install on the MTR.
To solve this problem, first ensure the device is both Azure-AD joined, and enrolled correctly in Intune. Be sure that your SkypeSettings. XML file contains the correct file name and extension for your wallpaper file, and that your PowerShell script contains the correct URL to download the file from your Azure storage account. Check too that you can browse to the storage account from the MTR. Managing your MTR deployment via Intune is straightforward, and enables you to have greater control of the end user experience.
For more Microsoft Teams news check out our resource centre. Chiffers, C. Check out more great Microsoft Teams Content here or join our mailing list to stay up to date. Forgot Password? Enter something special:.
Not a member yet? Create a free account Sign Up. With over 2, eBooks, webinars, presentations, how to videos and blogs. Features update, Quality updates or Rings? Craig Chiffers. Reply to ChunBao. Thomas Engler. Last edited 5 months ago by Thomas Engler. Reply to Thomas Engler. Reply to Roger. Would love your thoughts, please comment. The number of days to defer quality security updates and bug fixes etc updates before installing them.
The number of days to defer feature new versions of Windows 10 updates before installing them. The number of days you can uninstall a feature update on an MTR before the files are removed.
Comments
Post a Comment