- Managing microsoft teams rooms with intune

Looking for:

Managing microsoft teams rooms with intune. ANZ Modern Desktop Community 

Click here to DOWNLOAD

   

 

Managing microsoft teams rooms with intune -

 

Finally output folder is the folder that we need to provide where the intunewin file will be successfully created. After running the above command finally we see the. Also more importantly it creates installsync. This is the main cmd that starts the installation, sets the error state if it finds any and then exit the installation.

Now we have created the required installation media now we need to create the Intune Apps Policy to target them to the required room systems. Navigate to Intune — select all apps — Add new app type and select Windows app win In the app description we can provide a name and description as per our requirement.

Once after the file is successfully uploaded we receive a confirmation notification message like below;. With Microsoft Intune we are able to install the Logisync App Deployment in an automated way without any hassle. Apps can only be installed in the device context if they are supported by the device and the Intune app type. Device context installations are supported on Windows 10 desktops and Teams devices, such as the Surface Hub.

Like Like. Do you know how to register these systems to Sync portal if we cannot find it? You are commenting using your WordPress. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. This site uses Akismet to reduce spam. Learn how your comment data is processed. Click here to buy your copy of the book - Reimagine remote working with Microsoft Teams.

Email Address:. I can be contacted through email sathish ezcloudinfo. It can be downloaded from this github website Then create installsync. Navigate to Intune — select all apps — Add new app type and select Windows app win 32 Now we need to select the app that we have created which is logitechprovisionstub. In the next screen in add app section use the install command installsync. And after few times if the installation is successful we can see the below message.

And the device installation status is also showing successful. When logging into the system could see that the Logitech services are installed and running. Share this:. Like this: Like Loading Evolvous March 2, at am Reply. Great Share!

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. Windows Information Protection Not recommended Once you have selected the template you wish to configure give the template a meaningful name Configure the profile Assign the profile to your MTR device group and click create.

Click OK to save the changes. Click Next , and skip assigning Scope Tags. Sit Save to save the rule. Now you need to wait an hour for the MTR to do its hourly check-in with Intune, download the scripts and apply them!

This is easily done via Powershell Create a.

 

Managing microsoft teams rooms with intune -

 

As Microsoft and their certified device partners gear up to bring more native Microsoft Teams IP Phones to the market the management and customization of the device experience is also being expanded upon. This article introduces the current capabilities of a new PowerShell cmdlet created specifically to manage the user experience of these devices. That cmdlet only controls a single globally-applicable set of parameters though, so it was not possible to create different sets of behaviors which could be applied to different groupings of phones.

At the time of posting this article Microsoft has not yet published any official documentation for this cmdlet, but the functionality is already present in Office tenants. The most obvious change between the Skype IP Phone functionality and the what now exists for Teams devices is there is also a New -CsTeamsIPPhonePolicy cmdlet which allows the creation of custom policies in addition to the default global policy which can be modified if desired.

This addresses a long overdue customer request to assign unique parameter values to different categories of phones, be it by location, department, use-case, etc. Alongside this cmdlet is the requisite Grant -CsTeamsIPPhonePolicy cmdlet which is used to assign custom policies to individual user accounts. Currently there is a very limited set of parameters available to actually control phone behavior, but the groundwork has been laid to start defining unique policies and then assigning these polices to user accounts to control their IP phone experiences.

To take a closer look at this new capability launch PowerShell and import the Skype for Business Online module if installed as outlined in numerous articles like this. Users can only be assigned to user policies and cannot explicitly be assigned to a global policy; assigning them to a null policy will return them to the default behavior of adhering to the global policy. The next step into investigating the configuration would be to take a look at the default Global policy.

The default configuration in all Office tenants should simply return a single Global policy with the parameters shown above. As previously mentioned, the list of configurable parameters in these policies are currently quite limited. In fact, at the time this article was written there are only two behaviors which can be controlled: the primary client experience via the sign in mode, and the inclusion of the Search function on Common Area Phones.

As best practices typically dictate it is generically recommended to leave the default global parameters as they are and create new user policies to customize any behavior. Be aware that the only available policy types here are global and user , so if there is a behavior which would be deemed desirable for all users then it would be easier to manage this change at the global level then having to manually add every new user account in the tenant to a specific user policy.

Now that some parameter values have been discovered the piece to uncover is what are the possible configuration options for these settings? A simple way to find that out in PowerShell is to attempt to set a parameter to an obviously invalid value and when the cmdlet fails the error response will return the list of accepted values. What the SignInMode parameter controls is essentially the overall user experience on the Teams device Android client.

There are three different options which provide three unique interfaces targeted at three specific, common use-cases: regular users, shared meeting rooms, and common areas. The available parameter values are as follows:. The UserSignIn setting provides the full client experience which is typically targeted for regular phone users. Unless any changes are applied to the tenant using the cmdlets and guidance in this article then all user accounts signing into all Teams IP phones will receive this experience as the default global policy is set to this value.

The latest phone software no longer prompts the user during sign-in to select if they want a Personal or Shared experience as outlined in a past article. The account type which is signing into the phone does not matter, so whether it is a user mailbox or room mailbox or if it has been enabled in Skype for Business using the CsMeetingRoom cmdlet set is irrelevant.

Additionally, the type of Office license applied to the account has no effect here either. Thus, an account configured as a room mailbox and assigned a Common Area Phone license which is a bad idea for other reasons will still show the full client experience when signing into a Teams phone in this example tenant based on the fact that only the single global policy exists which is set to UserSignIn mode.

In short, the overall client experience is controlled only by this PowerShell policy, and nothing else. Note that the screenshots above are using the Dark Theme option, which is not the default appearance. This setting is meant to be used on phones which are located in conference rooms where the primary use case is joining scheduled meetings. In order to utilize this mode on a phone a new user policy must be created so that it can be assigned to the user account which will be signed into the phone.

When logging into a Teams phone using this account the interface will default to showing only the Calendar view, and the Dial button if the account is Enterprise Voice enabled with the requisite Phone System licensing.

The Search button is still available, but the Call Park button has been removed. The following screenshots where taken from a Poly Trio using the account which was added to the Meeting Room policy in the previous steps. This setting provides to most restrictive user experience intended for phones in common areas which may even be placed in public area.

In order to utilize this mode on a phone another new user policy should be created so that it can be assigned to other user accounts. When logging into a Teams phone using this account the only the dial pad will be displayed along with the Call Park button.

The Search function can selective be hidden or shown via the other setting in the policy. Once the policy change is picked up by the phone it should display the Search button. About Jeff Schertz Site Administrator. Thank you Jeff for the detailed information! So this has answered so many questions about the latest firmware for the Poly Trios.

However, after setting this policy on a specific account and restarting the phone, the Shared experience is not what is set.

What else has to be done? As with anything in Teams give it at least overnight before you give up. That being said I just tested on an account after around 2 hours and the Trio is in Meeting sign-in mode as expected. Applied the policy, waited about 3 hours, and finally a phone and account that work as intended. Yes, the Trio should appear under Devices appear in the Teams Admin Center, but this might not be in your tenant yet as the phone management solution is rolling out in Teams.

Hi, is there any way to get my exchange contacts to the ipphone, to names instead of the numbers? Based on what standard is this error prompt thrown? Is there a way to allow rooms set to use MeetingSignIn to still allow the user to view the meeting comments? We still use Zoom heavily which puts all the dial information in the meeting comments. Joel, no. It appears that in the Meeting Room view the calendar items cannot be opened like they can in User mode.

It seems that only Teams Join and Skype Call meetings are actionable on the phone. Hopefully Microsoft addresses this an update as it seems a bit crippling. Awesome write-up! I am running Native mode and it requires Microsoft Intune to work. Does your implementation include Intune, and if not how did you bypass that? Also my only issue seems to be getting the Meeting tab up and running, I can only see the magnifying glass in Shared mode and Calls and voicemail in Personal mode.

Any help would be appreciated. Great column by the way. Are you receiving a specific error? You have no idea how much this single article has saved dozens of hours of experimenting on my end Jeff, thank you very much. No, other than the options provided in the Teams Admin Center for managing devices via configuration profiles which are very basic at the moment.

It was my Poly Team that found this blog and helped me. I can successfully enter a phone number and hit the dial button and it makes a phone call.. It can also receive calls. Just no dialtone. I have a Yealink CAP configured now but users do not remember phone numbers anymore.

No, the Common Area Phone interface on the Teams phone client does not provide contacts or favorites. You can leave the Search function so users can search the directory, but to have a list of contacts shown the user signed into the phone would need to be reverted to the User sign-in mode. That would not likely be ideal though as the Call history, Calendar and Voicemail tabs would be shown. This is a great write up. I used it to configure the meeting room policy and applied to my CP phones.

Do I need to give it different licensing or is there something in a config? If the user account had previously been setup as a user mailbox and had a license which included Exchange Online licensing then assigning the Meeting Room license to that account would disable the user mailbox. Thank you sir for sharing your wisdom. Thank you Jeff on a great article. Thank you on your reply. I have Poly phone and as soon as I click sing on it gives an error certificate is missing.

I understand it requires company portal to be installed or something as per the guide but how to do that one physical poly phone or what is the work around. As far as I know this change was not communicated, documented or published anywhere. TeamsIpPhonePolicies are now license driven. A little over a week ago we started receiving feedback from users that their phones were now only showing the dial pad. If you have the correct licensing then the policy should be fine.

I pinged one of my contacts at Microsoft and they confirmed this change did happen last week. The change actually occurred with Update 2A which was released back on June 10th. Microsoft appears to a be making it easier to provide the CAP UI to accounts without administrators needing to create and manage phone policies by simply looking at the license while also b limiting the ability for customers to use the cheaper CAP license for anything other than the standard CAP phone experience.

Hopefully Microsoft will add some level of contact or Favorite integration in the CAP UI for the basic speed dial capabilities which many desire. Unless that happens though then a user license will need to be applied to the account to regain access to the UserSignIn mode.

Thanks for the additional information Jeff! Yeah, my client falls into that category of using a CAP Lic and UserSign in and now this is causing major pain for end users working across branch locations. Do you know if it is a current known limitation that added external contacts PSTN , while visible as speed dials for outgoing calls on the Desk Phones, are not recognised on Teams Desk Phones nor on incoming calls when ringing or in call history?

Just the PSTN number shows up. Very annoying! It shows up correctly on Teams Desktop Client. The -SearchOnCommonAreaPhoneMode feature is flawed, all this policy does is remove the search icon from the top right corner of the display, there are 3 other ways to search the GAL if you have a speed dial, no speed dial and there are 2 ways to search the GAL with the policy set.. I will post another update when my ticket has been resolved and the search is no longer available.