![]() 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 |