Looking for:

How to make Zoom or Microsoft Teams work in your VDI infrastructure

Click here to Download

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

It appears that Microsoft are now starting to do something about it. Microsoft have recently released this article which includes download links to the x64 and x86 versions of teams and a specific command line to run in order to install Teams as a VDI friendly product.

I wanted to have a look at this executable and see how it installed. In order to find out a bit more about the teams installer I broke open process monitor and ran the command line without having preinstalled any typical VDI agent packages into a windows 10 instance.

Looking into the process monitor logs it appears that the teams installer looks for specific VDI agent based registry locations to determine whether it will install or not. These reg keys are obviously associated with the two big VDI vendors however if you are using another vendor again you may be out of luck for now.

If a VDI agent is not installed then the installer looks for these keys only and then fails the install however if the VDA is installed it also looks for quite a few other keys so at the moment its not a case of creating a single key to fool the installer.

The change to MSI package are certainly welcome and a good initial step in providing a machine based install for Microsoft Teams which hopefully will also migrate across to the other apps that are guilty of the same behaviour cough OneDrive. The following diagram provides an overview of the architecture. If you currently run Teams without AV optimization in VDI and you use features that are not supported yet for optimization such as Give and take control when app sharing , you have to set virtualization provider policies to turn off Teams redirection.

This means that Teams media sessions won’t be optimized. For steps on how to set policies to turn off Teams redirection, contact your virtualization provider. We recommend that you evaluate your environment to identify any risks and requirements that can influence your overall cloud voice and video deployment.

To learn more about how to prepare your network for Teams, see Prepare your organization’s network for Teams. The chat and collaboration experience works as expected. When media is needed, there are some experiences that might not meet user expectations on the Chrome browser:. If your organization wants to only use chat and collaboration features in Teams, you can set user-level policies to turn off calling and meeting functionality in Teams.

You can set policies by using the Teams admin center or PowerShell. It up to a few hours for the policy changes to propagate. If you don’t see changes for a given account immediately, try again in a few hours. Calling polices : Teams includes the built-in DisallowCalling calling policy, in which all calling features are turned off. Assign the DisallowCalling policy to all users in your organization who use Teams in a virtualized environment.

Meeting policies : Teams includes the built-in AllOff meeting policy, in which all meeting features are turned off. Assign the AllOff policy to all users in your organization who use Teams in a virtualized environment. To assign the DisallowCalling calling policy and the AllOff meeting policy to a user:.

If you have an existing implementation of Teams on VDI with chat and collaboration in which you had set user-level policies to turn off calling and meeting functionality, and you’re migrating to Teams with AV optimization, you must set policies to turn on calling and meeting functionality for those Teams on VDI users.

You can use the Teams admin center or PowerShell to set and assign calling and meeting policies to your users. It can take some time a few hours for policy changes to propagate. If you don’t see changes for a given account immediately, try again after a few hours. Calling polices : Calling policies in Teams control which calling features are available to users. Teams includes the built-in AllowCalling calling policy, in which all calling features are turned on. To turn on all calling features, assign the AllowCalling policy.

Or, create a custom calling policy to turn on the calling features that you want and assign it to users. Meeting policies : Meeting policies in Teams control the types of meetings that users can create and the features that are available to meeting participants that are scheduled by users in your organization. Teams includes the built-in AllOn meeting policy, in which all meeting features are turned on. To turn on all meeting features, assign the AllOn policy.

Or, create a custom meeting policy to turn on the meeting features that you want and assign it users. To assign the AllowCalling calling policy and the AllOn meeting policy to a user:. When users connect from an unsupported endpoint, the users are in fallback mode, in which AV isn’t optimized.

To disable fallback mode, set the value to 1. To enable audio only, set the value to 2. If the value isn’t present or is set to 0 zero , fallback mode is enabled. Teams VDI policies are available in the Teams module. These policies are active and enforced on non-optimized VDI environments.

We’re working on adding calling and meeting features that are currently only available in non-VDI environments. These might include more admin control over quality, additional screen sharing scenarios, and advanced features recently added to Teams. Contact your Teams representative to learn more about upcoming features. This is a known issue with Citrix VDA versions and Then, restart VDA. Skip to main content. Yes No. Sorry this didn’t help. Thanks for your feedback. Choose where you want to search below Search Search the Community.

Search the community and support articles Microsoft Teams Teams for business Search Community member. Hello, We currently use persistent VDI’s and are looking to switch to non-persistent for some users. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

 
 

– Microsoft teams installer vdi – microsoft teams installer vdi

 

Installation has failed: Cannot install for all users when a VDI environment is not detected. Jgq85 You have to manually create the following registry key before Teams will let you install in per machine mode. You just have to Download Teams to your downloads folder then run the below commands. Thanks for sharing patrickkoehler ,. By the way, now Microsoft Teams is now available in preview for Windows Virtual Desktop media optimization.

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. AI and Machine Learning. Microsoft Mechanics. Healthcare and Life Sciences. Small and Medium Business. Internet of Things IoT. Azure Partner Community. Microsoft Tech Talks. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs.

Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Did you mean:. Sign In. I’m using the Machine Installer msi same as I deployed to regular computers.

Is there a clear direction to get Teams on there? Steve Burkett. Brian Charles. Mahmoud A. Dear Jgq85 , You just have to Download Teams to your downloads folder then run the below commands. Hi Mahmoud A. Atallah , regarding the Teams installation on WVD, there are maybe more topics as well to consider. Cheers, Patrick. Education Microsoft in education Office for students Office for schools Deals for students and parents Microsoft Azure in education.

 

– Deploy Microsoft Teams with Microsoft Apps – Deploy Office | Microsoft Docs

 

We currently use persistent VDI’s and are looking to switch to non-persistent for some users. The issue we are running into is that Teams can’t be installed on the template, since it is user specific. We can run a script that installs Teams upon login, but it has to run at every login on the non-persistent VDI’s otherwise Teams won’t work. We don’t want to have to install it every time a user logs in.

Is there a way to deploy Teams on the VDI tempalte in a non-persistent VDI environment so that it works for all users who login without a fresh install? Was this reply helpful? Yes No. Sorry this didn’t help. Thanks for your feedback. Choose where you want to search below Search Search the Community. Search the community and support articles Microsoft Teams Teams for business Search Community member. Hello, We currently use persistent VDI’s and are looking to switch to non-persistent for some users.

This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Here it has been approved on your side.

About how Teams work in non-VDI, we have little information regarding this. As you mentioned that you can have a script to get it done, you can contact Microsoft MSDN forum which mainly focuses on the development related issues for help. On another hand, any customer who have the similar experience is welcomed to share something here. Regards, Alan. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site.

This site in other languages x.

 
 

Leave a Reply

Your email address will not be published. Required fields are marked *