Looking for:
Optimization for Microsoft Teams | Citrix Virtual Apps and Desktops 7 - MST to install Teams on regular Windows 10 |
- Teams for Virtualized Desktop Infrastructure - Microsoft Teams | Microsoft Docs
Discover best practices, product information, and IT tips that you can use to help your business. As a part of Covid precautions driving business trends, Microsoft Teams usage increased exponentially when the solution was added to the default Office suite and increased in functionality.
Usage of Teams in compared to was up around percent and holds steady as businesses worldwide continue to figure out how to best support their remote workers. At first glance, admins could believe Teams is a typical co llaboration tool, such as Citrix Podio, or a meetings app, such as Cit rix GoToMeeting.
It is possible for Teams to replace these tools. However, getting there requires significant pre-planning and implementation of additional Microsoft components. Managing Teams within a virtual desktop infrastructure VDI environment also requires some considerations. Install Location: Per-machine or Per-user? Endpoint Device. Citrix Optimization Feature. Is your VDI infrastructure or hardware making it difficult to use Teams?
Should I Install Per-machine or Per-user? A zero-day or a business enhancing feature released will be able to be introduced to the environment quickly. However, an environment breaking patch can also be released uncontrolled if installed per-user.
For example, Citrix optimization was only available when deploying on the system drive. But with a recent patch, this was no longer true, and Teams automatically switched to Citrix optimization mode, which has limited features. These types of issues result in a significant number of help desk calls until a workaround could be implemented. In early , it was recommended to install per-user as it allowed preventing Teams from auto-starting. This let users who were not interested in Teams not have it launch and reduced the infrastructure resource requirements of every user having a Teams session.
However, as Covid precautions stuck around and adoption drastically increased, it no longer made sense to allow per-user installs to persist and provide inconsistency in the environment.
The migration from per-user to per-machine is automatic. Microsoft will convert the install when a per-user logs into a per-machine image. We noticed that the Taskbar shortcut must be unpinned and repined as it still pointed to per-user install. Also, the Teams Outlook add-in pointed to the old per-user install and had to be fixed with a registry key update.
And finally, on rare occasions, the migration did not work successfully; In the session as an admin, Teams had to be uninstalled and then reinstalled. Pros and cons of per-machine and per-user installments:. How many end devices are needed is largely dependent on whether optimization will be enabled see section below. If unoptimized, the end-device is less important as most of the computation occurs in the VDI. H owever , all audio and webcam must still traverse the network to the VDI.
This can provide a wide disparity in end-user experience if a standard is not implemented. This increases outbound network load to the internet for your branch sites. Microsoft has worked together with virtual desktop vendors, such as Citrix and VMware, to implement an optimized mode of Teams. This enables H.
While significantly improved over , there are still feature limitations in the optimized version of Teams. It can be tempting to include the Teams app with the rest of the Office installation to gauge end-user interest. However, Teams uses Electron and Optimization, and some of those limitations require a VDI architect to consider unique design decisions compared to the rest of the Office suite.
The fast pace and complexity to implement Teams requires careful planning, design, and proper hardware prior to implementation to prevent data loss and performance degradation. Consider using a managed virtual desktop infrastructure provider to help your team avoid set-up and implementation errors, and keep Teams running smoothly for your entire remote workforce. To learn more, download the complete solution brief: Deploying Microsoft Teams.
Have VDI questions? Our Info sessions are always free. Schedule one for your team:. Capital View Center S. Whitehat Virtual Blog Discover best practices, product information, and IT tips that you can use to help your business.
There are three major design decisions for an admin deploying Teams for VDI: 1. Endpoint Device 3. Installing on the system drive prevents this scenario. Per-machine install prevents auto-updating, which allows proper QA of new Teams releases.
Most virtual desktop optimization clients recommend per-machine installs. Per-machine Cons: Teams updates frequently and bug fixes must be implemented often to keep up to date in the golden image.
Once a user launches Teams, they are unable to prevent auto-launch. Teams will always auto-launch and cannot be turned off by the user. Teams consumes all session resources to launch. This effectively means auto-launching is increasing your user logon times because the session will be unusable until Teams finishes launching.
Per-user Pros: Teams can be prevented from auto-launching by an admin by default and a user can toggle auto-launch on or off. This reduces login times as well as resource consumption for virtual machines. Teams stays current by automatically updating. Per-user Cons: Teams disk storage requirements multiplies by every user instead of the number of machines. Don't have time to read the entire article? Should I Leave on Optimization? Optimize Pros: Optimizing allows Teams to efficiently manage and redirect audio and video, improving performance while reducing server resource utilization.
Audio does not have to double hop between end-device, VDI, and Teams servers but instead goes directly to Teams servers. Also, audio and webcam video are not rendered in the VDI reducing resource utilization.
Mapping of audio and webcam devices functions more natively without leveraging VDI vendor technologies, such as Citrix HDX audio, which can be buggy. The pace with which versions are released provides a significant operational requirement to stay up to date. End-client agent versions must be released by vendor and then updated on the end-device. The Teams version in the VDI must also be updated if per-machine installed.
If thin-clients are used as end devices, the updates can be further delayed as the vendor agents are typically included as part of the thin-client OS. This means operations must validate and deploy new OS versions of thin clients as well as testing in VDI. Features are limited, as defined in section below. Unoptimized Pros: Almost the full feature set of Teams as compared to physical device install.
Teams functions the same way as all other conferencing tools, such as WebEx, reducing user confusion. Unoptimized Cons: Audio and video performance is reduced and heavily dependent on the end-device and VDI network stability.
Any latency or bandwidth issues are compounded due to the double hop between device, VDI, and Teams servers. Audio and video device instability causes users to have to restart Teams, and sometimes the VDI session itself, to continue working after crashing.
Leave Comment. Subscribe Our Blog. Most Popular. Whitehat Virtual Technologies. Search website Search Google. Healthcare Finance Manufacturing Retail. P:
No comments:
Post a Comment