Looking for:
Deployment guide for Webex App for Virtual Desktop Infrastructure (VDI) - Cisco. |
Webex teams vdi download - webex teams vdi download.Welcome to Cisco Community
Webex teams vdi download - webex teams vdi download. Deployment guide for Webex App for Virtual Desktop Infrastructure (VDI)
Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.
Learn more about how Cisco is using Inclusive Language. The steps include what you need to do on the hosted virtual desktop HVD environment and what users need to do on their thin clients. To prepare for your users wanting to access the Webex App remotely from thin client devices, set up the Webex App on the centralized hosted virtual desktop HVD environment. In Control Hub, you can use an organization-level setting to either enable or disable VDI optimization and detection for your Webex App users.
By default, the setting is enabled. Thin clients are typically lightweight or repurposed computers that users use to establish a remote connection with a centralized HVD server where Webex App is hosted. For full featured meetings with the Webex App , you or your users must install two separate VDI plugins on a thin client.
To prepare for your users wanting to access the Webex App remotely from thin client devices, set up Webex App on the centralized hosted virtual desktop HVD environment. If your organization has its own download site that includes your site-specific Webex App , go to that site and download your organization-specific version. If you use auto-upgrade, we recommend that you move your Control Hub organization to the slow channel. For more information, see Upgrade Management in this guide.
See the following table for explanations of the arguments that you can use when installing Webex App in a VDI environment. For information about user preferences and how to preserve them, see User preferences. This is useful in a shared environment typically non-persistent VDI.
Use this option if you prefer to manually maintain upgrades. The argument does not affect a non-VDI environment. If using this option, ensure that your organization is configured for slow channel. When installing the bundled components for Webex App, if you have administrative privileges, you can use this argument to lock the version of the app that is used to join meetings, if the version is compatible with the site version. WebView2 is required for proper operation of Webex.
See User preferences for more information. Users may be in a Citrix environment and not have the thin client installed or the virtual channel is disconnected. We support this scenario with fallback to a non-virtual Webex App installation. In this mode, the app shows a warning that the quality of video may be affected. Once the virtual channel is connected, the app can change to VDI mode.
Use this table to understand the different installation combinations and how they affect media optimization for Unified CM, Webex Calling, and calls on Webex App. The roaming database contains all user credentials and preferences, encrypted using AES As a VDI customer, you should always back up the above folder, so that user credentials and preferences are maintained across VDI sessions. Users access the Webex App through a virtualized Windows environment. Walk through the deployment steps in the Azure admin portal to create the host pool, virtual machines, and related settings.
A host pool is a collection of VMs that offer a similar service. Azure indicates when the virtual environment is ready. For specific deployment steps, see the Microsoft documentation on getting started with AVD. This setting applies across your organization, unlike the installation parameters which affect your deployment at the server level. If you're unable to install the VDI plugin for your users, walk them through these steps on their thin client devices.
If you're running a bit or bit environment with VMware, make sure you download and install the VDI client that matches the VMware environment. Webex App needs to be installed on your central HVD environment. Double-click the msi file that you downloaded. To complete the installation, click Finish. Optional If you or users are manually installing the two plugins for full featured meettings, follow the steps in Install Webex Meetings VDI plugin on thin client systems.
You can find the version numbers on the download page. Webex Meetings VDI as a standalone plugin is released every month, but this bundled plugin installer is release bimonthly. Double-click the exe file that you downloaded.
Read the welcome screen, which covers the plugin versions that are included in the installer, and then click Next. For Webex App to function properly for your users, you must use the official thin client plugin from the download site. To confirm, the Health Check shows a connected status for the Virtual Channel. Create an image for the thin clients. On the thin client, install the Webex App VDI plugin; enter your password at the authentication prompt.
After you click Install, the Ubuntu Software Center locates and installs the dependency libraries, and then installs the Webex App Client. Deploy the image to the thin clients. For more information about how to create an image or how to update the thin client, see the Elias documentation available from the Unicon website.
Under the registry, enable the vdciscoteams parameter. Because of this third-party integration, you must contact Dell for technical support. For more information, see the Dell Wyse ThinOS documentation for your supported release; the "Supported packages" section of their release notes mentions the version of the Webex VDI plugin that's supported. See the software download page to get a copy of the OS installation package. Because of this third-party integration, you must contact 10ZiG for technical support.
For more information, see the 10ZiG page for your specific thin client. For Webex App to function properly for your users and be optimized for VDI, you must use the thin client build. For full featured meetings with Webex App , you or your users must either install the bundled VDI plugin or the two separate VDI plugins on a thin client. You cannot use the bundled VDI plugin package on Linux thin clients. For Linux, you must install the separate VDI plugins.
Install only the Webex app in the HVD environment. No other apps are required. Make sure you follow the Full-featured meetings requirements. Install the Webex app VDI plugin for the supported thin client platform:. For feature limitations for each release, see the release notes.
With per-machine installation, automatic updates are disabled. This means that to update the Teams app, you must uninstall the current version to update to a newer version. With per-user installation, automatic updates are enabled.
Keep the Teams desktop app in your VDI environment up to date. Teams desktop app versions with release dates that are more than 90 days older than the current version's release date aren't supported. Unsupported Teams desktop app versions show a blocking page to users and request that they update their app. For most VDI deployments, we recommend you deploy Teams using per-machine installation.
To update to the latest Teams version, start with the uninstall procedure followed by latest Teams version deployment. For Teams AV optimization in VDI environments to work properly, the thin-client device must have access to the internet. If internet access isn't available at the thin-client device, optimization startup won't be successful.
This means that the user is in a non-optimized media state. In a dedicated persistent setup, users' local operating system changes are retained after users log off.
For persistent setup, Teams supports both per-user and per-machine installation. In a non-persistent setup, users' local operating system changes are not retained after users log off. Such setups are commonly shared multi-user sessions. VM configuration varies based on the number of users and available physical server resources. For a non-persistent setup, the Teams desktop app must be installed per-machine to the golden image.
This ensures an efficient launch of the Teams app during a user session. Using Teams in a non-persistent setup also requires a profile-caching manager for efficient Teams runtime data synchronization. Efficient data synchronization ensures that the appropriate user-specific information such as a user's data, profile, or settings is cached during the user's session.
Make sure data in these two folders are synced:. A roaming folder or, if you are using folder redirection, a caching manager is required to ensure that the Teams app has the runtime data and files required to run the application. This is necessary to mitigate network latency issues or network glitches, which would otherwise cause application errors and a slow experience due to unavailable data and files.
There are a variety of caching manager solutions available, such as FSLogix. Consult your caching manager provider for specific configuration instructions. Excluding these items helps reduce the user caching size to further optimize your non-persistent setup. Before you deploy Teams through Microsoft Apps for enterprise, you must first uninstall any pre-existing Teams apps if they were deployed using per-machine installation.
Teams through Microsoft Apps for enterprise is installed per-user. Teams is also being added to existing installations of Microsoft Apps for enterprise.
Microsoft Apps for enterprise doesn't support per-machine installations of Teams. To use per-machine installation, you must exclude Teams from Microsoft Apps for enterprise.
To learn more about Teams and Microsoft Apps for enterprise, see How to exclude Teams from new installations of Microsoft Apps for enterprise and Use Group Policy to control the installation of Teams. At this point, the golden image setup is complete. This process adds a required registry key to the machine that lets the Teams installer know it is a VDI instance.
Without it, the installer will error out, stating: "Installation has failed. Cannot install for all users when a VDI environment is not detected. All users can then uninstall Teams if they have admin credentials. PowerShell script : You can use the Teams deployment cleanup PowerShell script to uninstall Teams and remove the Teams folder for a user. Run the script for each user profile in which Teams was installed on the computer.
There are a variety of virtualized setup configurations, each with a different focus for optimization. For example, a configuration might focus on user density.
When planning, consider the following to help optimize your setup based on your organization's workload needs. In addition to chat and collaboration, Teams on VDI with calling and meetings is available with supported virtualization provider platforms. Supported features are based on the WebRTC media stack and virtualization provider implementation. 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.
No comments:
Post a Comment