We already covered this in part #1 of this series, but lets reiterate that it is crucially important to install Teams correctly for the environment. Key action #3 – implement suitable timeout and disconnection policies within the customer environment Teams installation and configuration Installation A thorough discussion of disconnection and timeout policies within RDSH or VDI environments is provided here – There are a number of factors to consider when deploying these policies, namely around understanding how users make use of the system, and this understanding will drive the policies that you implement. Around this, it can be useful to set up robust timeout and disconnection policies to prevent users from experiencing this issue. It is also worth noting that when users disconnect sessions rather than logging out, the Citrix HDX virtual channel that handles Teams can disconnect and not re-establish properly. Key action #2 – educate users in basic Teams troubleshooting, with supporting documentation as necessary Session disconnections Exiting Teams correctly by right-clicking the notification area icon and choosing “Quit” can help with many issues. Many problems that users encounter within Teams can be resolved by learning some basic troubleshooting techniques. Key action #1 – set user expectations as to differences between the desktop and VDI versions of Teams, provide roadmap to support this User self-help It can be useful to share this either with users or support personnel ( ) Citrix publish a roadmap of CVAD features that can sometimes provide an insight into when Teams features will “catch up” with the desktop version. Setting the user expectations around what is possible or limited within the VDI version of Teams can help to head off these issues. Unawareness of these limitations can often convince the users that Teams is “broken” and lead to helpdesk calls. Feature parity lags quite starkly between the two, with the “VDI” version the poorer relation.įeatures such as “background blur” and the Gallery View are commonly called out by users who move to the VDI version of Teams and are already familiar with the desktop version. It is important to note that there is a noticeable discrepancy between the traditional “desktop” version of Teams and the “VDI” version of Teams that is commonly used in RDSH or virtual desktop environments. The following key points should allow Teams to operate in an optimal mode that provides the best user experience. Ensuring that all users have an optimal experience that does not impact other users on the shared platform and/or shared hypervisor fabric is of paramount importance. When using Windows Server RDSH instances/Windows 10 Multi-User instances and/or Windows client VDI instances, there are implications for performance and user density given the shared nature of RDSH/Win10 MU platforms, and/or the shared resource nature of Windows client VDI. I’m sure we all know what Teams is by now, no introductions required! □
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |