Microsoft Teams Room management via Intune - Microsoft Community.Managing a Microsoft Teams Room (MTR) Device with Intune – Part 1 – Theme – Blog –
Looking for:
- Managing Microsoft Teams Rooms with Intune - Microsoft Tech Community |
Managing microsoft teams rooms with intune - managing microsoft teams rooms with intune. Managing a Microsoft Teams Room (MTR) Device with Intune – Part 1 – Theme
Teams Rooms comes with a specially configured Windows 10 image supplied by the original equipment manufacturer OEM.
Successful installation and deployment of Teams Rooms requires preparation, such as account provisioning and a device deployment and enrollment strategy. For detailed information to help you plan your Teams Rooms deployments, see Deployment overview - Microsoft Teams Rooms. Mobile device management MDM enrollment is not part of the default installation process for Teams devices. Windows Autopilot enrollment is not supported. There are two methods for enrolling Teams Rooms Windows devices in Intune.
Our recommended method is to use bulk enrollment, which allows you to also set up the device in shared device mode. Please note that these steps must be done manually, and you will need to give passwords to local technicians. From a license perspective, everything you need to register the device in Azure Active Directory Azure AD and enroll it in Intune is already covered by the Microsoft Teams Rooms licenses. Your organization might already have unmanaged Teams Rooms Windows devices in operation that are set up with local user accounts.
The local account is used to perform an automated sign in to Windows, while the Teams app on these devices is using the Azure AD Teams resource account to sign in. There are two options for registering and enrolling these devices. The first option is to use a resource account to register and enroll the device.
The second and preferred option is to create a provisioning package with Windows Configuration Designer and apply this to a Teams Rooms device. This will restart the device and apply the settings for example, a computer name , and join it to Azure AD.
This helps to identify which devices to apply Teams Rooms-related settings and policies to, and will handle them as a group, separate from other Windows devices. To learn more about Teams device enrollment and policies, see the blog post Managing Microsoft Teams Rooms with Intune.
Screenshot showing a dynamic membership rule with the following rule syntax: device. Check if the computer name follows a standard. Using a resource account to register Teams Rooms devices is a manual process. On the device user interface, select More … and then select Settings. Image of the Teams UI showing the "More" option with an ellipsis icon. Image of the Teams UI showing the "Settings" option with a gear icon. In the Settings menu, choose Windows Settings and you will be prompted to sign in with an Administrator account again.
Save and exit Teams. Image of the Settings menu in Teams, showing the "Windows Settings" option on the bottom left. From the Windows Start menu, open Settings , select Accounts , and then select Access work or school.
On the Set up a work or school account dialog, under Alternate actions , select Join this device to Azure Active Directory. A screenshot showing the "Microsoft account - Set up a work or school account" pop-up, with "Join this device to Azure Active Directory" selected at the bottom.
Sign in with the resource account credentials. Keep in mind that the resource account is added to the local machine and uses Administrator credentials. However, in Azure AD the user does not have any rights. A screenshot of the "Make sure this is your organization" pop-up, showing "User type: Administrator" to confirm you are signed in with Administrator credentials. We used a user account for enrollment, so the device is mapped to the resource account, as we can see in the Primary user field.
An image of the device "Overview" page in the Microsoft Endpoint Manager admin center, showing the "Primary user" field. Typically, these types of devices are considered shared devices, so you should manually remove the primary user. Select Properties, and then select Remove primary user and select Save at the top of the page. A benefit of using a DEM account over a resource account is that the DEM account can only enroll devices and will not have any rights to access mailboxes, calendars etc.
An image of the device "Properties" page in the Microsoft Endpoint Manager admin center, showing the option to "Remove primary user". An image of the warning message that you will get if you choose to remove the primary user: "Removing the primary user of a device configures it to operate in shared mode. In this mode, users, including the previously assigned primary user, can no longer self-service this device in the Company Portal.
Learn more [link]". At this point, we have successfully enrolled Teams Rooms in Intune. A screenshot of the Windows Configuration Designer UI that has different options to create different types of provisioning packages, or open a recent project. For our example, we select Provision desktop devices to create a new project, add a name, the project folder path, and an optional description, and then select Finish.
An image of the New project page in Windows Configuration Designer, where you add a project name, browse for the project folder, and add a description. In the package definition, you can specify some rules for the computer name.
There are two areas selected: the "Device name" field and the "Configure devices for shared use" section, with the toggle set to "No". Select Next. A screenshot of the "Set up network" page from the left menu in Windows Configuration Designer, with the "Set up network" toggle set to "Off".
You can use a DEM account, or any other account that has rights to gather the bulk token. During the enrollment, a new account will be created. Note the token expiration date in the Bulk Token Expiry field and select Next.
In Intune, we see the new, corresponding enrollment account that Windows Configuration Designer created. Note : The account that was used for the token request is not stored in the package.
A cropped image of the package as a new profile in Intune the Endpoint Manager admin center. For our example, we do not need to add any apps and there are no certificates, either.
Select Next to continue to the Finish page, review the summary, and then select Create to generate the package. A cropped image of the Finish page, showing the "copied to" location of the new package we just created.
An image of the package file in a local directory. From the Windows Start menu, select Settings and then sign in with a local Administrator account if you are not already signed is as a local Admin. Screenshot of the Windows Settings "Access work or school" menu, with the option "Add or remove a provisioning package" selected. A screenshot of the Windows Settings "Provisioning packages" window with the option "Add a package" selected. An image of the User Account Control pop-up dialog that says "Do you want to allow this app to make changes to your device?
A dialog opens, confirming that the package is from a trusted source. Additionally, it shows you the information about the changes that will be made to the system. To continue with the installation, select Yes, add it. An image of the dialog "Is this package from a source you trust? A screenshot showing the dialog "You're about to be signed out: Windows will shut down in 1 minute". Note: If you install a provisioning package on a device which is already in use, but not enrolled in Intune, it does not reset the system.
Windows applies the new settings, renames the computer, and joins the device to Azure AD, if specified. Furthermore, enrollment accounts used by the provisioning process do not assign a primary user for the device. The only way to enroll a new Teams Rooms device during setup is to use a provisioning package. You can use the package we built in our example and copy it to a USB drive in the root folder.
Setup will find the file and will continue with the enrollment. For more information, see Apply a provisioning package. Important: Windows Autopilot enrollment is not supported for Teams Rooms devices. If you have completed a new installation or have enrolled an existing device with a provisioning package, the User Account Control dialog will not show the local Administrator account anymore in your Teams Rooms settings.
For example, you will sign in with the account. There are several ways to enroll Teams Rooms Windows devices in Intune. However, instead of using these accounts and the manual steps they require, you can use a provisioning package to enroll Teams Rooms devices in Intune. If you do decide to enroll Teams Rooms devices with a resource account, remember that the account still has resource access to certain services.
For new installations of Teams Rooms, you can apply a provisioning package during the OOBE phase of the setup process. After completion, the device is already enrolled in Intune. We hope this post helps you better understand the different options for enrolling Teams Rooms devices in Intune. Keep in mind that we recommend using a provisioning package and a dedicated account for enterprise installations and registrations with minimal interaction.
If you have any questions or feedback, reply to this post or reach out to IntuneSuppTeam on Twitter. You must be a registered user to add a comment. If you've already registered, sign in.
Otherwise, register and sign in. Products 68 Special Topics 42 Video Hub Most Active Hubs Microsoft Teams. Security, Compliance and Identity.
Microsoft Edge Insider. Microsoft FastTrack. Microsoft Viva. Core Infrastructure and Security. Education Sector. Microsoft PnP.
Managing microsoft teams rooms with intune - managing microsoft teams rooms with intune. Managing a Microsoft Teams Room (MTR) Device with Intune – Part 3 – Configuration Profiles
Managing Teams Meeting Rooms with Intune - Microsoft Partner Community - Create Intune app protection policies
Note: This post was updated September 14th with the latest information and screenshots. Our MTR will need a room account created for it within Office The simplest and most cost effective is to license your MTR with a meeting room license.
This license grants the device:. Again, there are a number of ways to achieve this. The easiest is to apply a Microsoft E5 license to the administrator, or purchase a separate Intune license. You can even apply a 30 day M E5 trial license. Note that if the room only has a single display, by default the right hand side of the entire image will be displayed on the in-room displays.
Dual display rooms will display the full image stretched across both displays. You may wish to add information that users within the room may find useful such as some basic info on using the room, and the helpdesk number to call if there are any issues.
Now that we have our background image file, and SkypeSettings. We need a way of getting our SkypeSettings. Note: A previous version of this post included the below script. This script no longer works, so please use the script above instead.
Note: Any time you make a change to the script, you MUST change the filename of the script so that Intune knows the file has changed, and to re-run it on the MTR device again.
This extension will then automatically run the PowerShell script, pulling down the SkypeSettings. XML and mtr-wallpaper. 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. Expanding the keys under Policies , you can drill down and see the current status ResultDetails of your PowerShell script. In the above example, we can see that the script experienced an issue downloading files.
The DownloadCount shows the number of times the script attempted to run 3 in the above example. A script will run once per check-in period. If the script successfully runs, it will never run again. If the script fails, it will retry up to 3 times before failing and stopping forever. We can force a re-run of the above script by updating the DownloadCount to 0 , and setting Result to blank and then restarting the Intune Management Extension service.
Note though that this will only re-run the currently downloaded script. Managing your MTR deployment via Intune is straightforward, and enables you to have greater control of the end user experience. This site uses Akismet to reduce spam. Learn how your comment data is processed. A great article. Am struggling to understand whether we need a specific Intune compliance policy for MTRs and what to set.
In addition what settings to apply in configuration policies for e. Do you still need an E5 license for these?
I found that just the Microsoft Teams Room License provides the device everything it needs. Or is the E5 a prerequisite for Intune? The license includes teams and intune. Search Search for:. Setting up an Azure storage account We need to set up a Storage Account in Azure to host our XML settings file and customised desktop background image.
Tip: browse to www. This group should contain each of your MTR device computer names. When ready, click Add to add your script. If you have enabled automatic enrollment for all devices, your MTR will be automatically enrolled in Intune too.
Final Thoughts Managing your MTR deployment via Intune is straightforward, and enables you to have greater control of the end user experience. Notify of. Oldest Newest Most Voted. Inline Feedbacks. Amazing article boss!! I wish I had found this last month.
Great work!! Craig Chiffers. Reply to Mark. Stay tuned! Eric Reynolds Palau. Reply to Eric Reynolds Palau. Would love your thoughts, please comment.
Comments
Post a Comment