Managing Teams Meeting Rooms with Intune - Microsoft Partner Community - Deliver better hybrid meeting experiences
Looking for:
Teams meeting rooms intune - |
- Managing Teams Meeting Rooms with Intune - Microsoft Partner Community
- How to enroll Microsoft teams rooms devices into Intune - Mindcore Techblog
This site uses Akismet to reduce spam. Learn how your comment data is processed. Search Search for:. Welcome to part 3 of managing Microsoft Teams room devices within Intune. Should I create configuration profiles for my MTRs? What are the recommended profiles to configure for an MTR?
Administrative Templates Yes — Although I would not recommend this. Certificates Yes — if required within your environment. Note it is not a feature mapping between Standard and Basic and Premium and Pro. Basic is something new. Pro removes the Microsoft people-based managed service team but will add new features too. There are important changes to understand. With Pro, you are getting more functionality than what Microsoft Teams Rooms Standard offers, especially around management, but you now must move up to Pro to maintain all features at the end of your contract term.
A lot of functionality has been added to Microsoft Teams Rooms since the Microsoft Teams Rooms Standard licence was introduced many years ago. Any existing licences will be valid until the contract time ends typically a year from the initial purchase if buying directly from Microsoft. Larger customers with volume licence agreements will be able to continue using and buying Microsoft Teams Room Standard licences until their licence agreement expires.
However, most new features moving forward will not come to Standard or Premium, only Pro. So Microsoft will be encouraging you to look at Pro. Standard will not lose any features it already has today.
Look out for more feature announcements at the upcoming Microsoft Ignite event I will cover all the new feature news in my monthly email update here. For customers without an enterprise agreement, who buy direct from Microsoft or a CSP, you will not be able to buy new Microsoft Teams Rooms Standard or Premium licences; for new rooms, you will have to use either Basic or Pro licences.
Once your licence term expires for your existing licences, you must move to Basic or Pro. Microsoft Teams Rooms Pro includes the Teams Phone licence, which is the ability for the room to also be a Phone, but you will need to add a phone number and connectivity via Microsoft Calling plan, Operator Connect or Direct Routing.
Note this does not mean it does not have PSTN dial in and out for meetings. That feature is called PSTN Audio Conferencing and is related to the person who schedules the meeting having that licence. Yes, you can if you want, but the functionality will be different for the users which might be confusing.
More importantly, the management and admin experience will be different for the Rooms. You will be capped to 25 of these licences per tenant.
If you have a use case for Panels without Microsoft Teams Rooms, a low-cost i. This is a corner case. E licences are not for shared devices. 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.
Comments
Post a Comment