Configuration of VmgCtxTeamsTest

Microsoft Teams in a virtual environment supports, by default, calling and meeting functionality in addition to chat and collaboration chat. The Citrix® HDX™ Optimization for Microsoft® Teams offers clear, crisp 720p high-definition video calls @30 fps, in an optimized architecture. Virtual application users can seamlessly participate in audio-video or audio-only calls to and from other Teams users, Optimized Teams’ users and other standards-based video desktop and conference room systems. Likewise, Microsoft relies on the Workspace app WebRTC (Web Real-Time Communication) media engine for acquiring, capturing, and processing the media. WebRTC media engine enables web browsers and virtual applications to directly share video, audio, and data during the sessions. Without proper consideration and design for optimization, virtual application users will likely find the Microsoft Teams experience to be subpar. Therefore, it is important for administrators to continuously check whether the Microsoft Teams application installed on the target server is optimized or not. The VmgCtxTeamsTest helps administrators in this regard!

This test continuously monitor the target virtual server and reports whether the Microsoft Teams application is installed or not. If the Microsoft Teams application is installed on the target server, then, this test will also reveal the optimization status of the Microsoft Teams application and the number of sessions during which the Microsoft Teams has used WebRTC media engine to create a connection and transfer data and/or media among users.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the nick name of the Cloud Desktops component for which this test is to be configured.

• Specify the port at which the specified host listens to in the PORT text box. By default, this is NULL.

• To obtain the ‘inside view’ of performance of the cloud -hosted Windows desktops - i.e., to measure the internal performance of the Windows virtual desktops - this test uses a light -weight eGVMAgent software deployed on each of the desktops. Accordingly, Inside View Using parameter is by default set to eGVMAgent (Windows).

• Report Powered OS flag is relevant only for those tests that are mapped to the Inside View of Desktops layer. If this flag is set to Yes (which is the default setting), then the ‘inside view’ tests will report measures for even those Windows virtual desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_virtualdesktopname. On the other hand, if this flag is set to No, then this test will not report measures for those Windows virtual desktops to which no users are logged in currently.

• Report By User flag is set to Yes by default. The value of this flag cannot be changed. This implies that the virtual machines in VDI environments will always be identified using the login name of the user. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename.

• Since this test runs for a ‘Cloud Desktops’ component, Is Cloud VMs flag is set to Yes by default.

• To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.