3/26/2020 Citrix Installer For Windows 10
As of August 21, 2020 ShareFile Desktop App for Windows up to version 1.18 will begin deprecation. The upgrade path is to update the tool to Citrix Files for Outlook 6.X or higher. Deprecation may take several weeks to complete and the tool may still be temporarily available for some users during this process. If a user-installed instance of Citrix Receiver for Windows exists on the system and an administrator installs Citrix Receiver for Windows on the same system, there will be a conflict. Citrix recommends that you uninstall all user-installed instances of Citrix Receiver for Windows before installing Citrix Receiver for Windows as an administrator.
![]() Applicable Products
Information
Contents
System Requirements
Available Localization Install and Configuration Basic Operations Icon Overlays Accessing Dashboard Settings Menu Group Policy Definitions - Now in Citrix Product Documentation. Known Issues - Now in Citrix Product Documentation. Citrix Files allows you to access your files in ShareFile directly through a mapped drive providing a native Windows Explorer experience. Files are downloaded only when accessed and temporarily stored on your computer. Changes made to the files are automatically saved back to ShareFile cloud. You can also access additional functionality through the Windows right-click context menu and perform operations such as Sharing or Requesting of files.
|
Operations | Description |
Open and Edit | Open a file in your S: drive, make some edits and save. Your changes will automatically be saved back to your Citrix Files account. |
Upload | Drag a file or folder to the S: drive to upload. You may also perform a copy and paste to upload a file or folder. |
Download | Drag a file or folder from the S: drive to your desktop or any other folder to download. You may also perform a copy and paste of files and folders to download. |
Delete | Drag a file or folder to the trash. Although you will be warned that the file will be permanently deleted, items will be available in Citrix Files’s Recycle Bin. |
New Folder | Creates a new folder in your ShareFiles account. |
Right Click Context Menu
Citrix Files integrates with the Windows Explorer context menu to give the application access to additional Citrix Files options. Right click on a file or folder inside your S: to view the context menu options:Menu Option | Description |
---|---|
Share options |
Available when you right click on a file or folder.
|
Request Files |
Available when you right-click on a folder, or within a folder when no files are selected.
|
Open in Website |
Opens up your default browser to the current folder location on the Citrix Files website.
|
View Details | View advanced details of a file including file properties, previous versions, and notes. |
Check Out | Check out a file. If the file is already checked-out, the Check-in option will appear. |
Upload | Upload files or folders directly from your computer. Use this option if uploading a large file or a large number of files. |
Download | Download files or folder to a specific location on your computer. Use this option if downloading a large file or a large number of files. |
Add to Favorites | Add a file or folder to your Favorites folder. If a file or folder is already a Favorite, you will have the option to remove from Favorites. |
Refresh Content | Manually refreshes the contents of a folder. Note: Folder contents should update automatically as remote changes are made, but you can use this function if you need to refresh manually. |
Manage Folder Permissions | Allows you to manage access permissions for a folder. You can add/remove users to that folder or limit which operations they are allowed to perform. This context menu option is only available on Folders. |
Icon Overlays
Files and Folders will have an icon overlay representing the status of that item. The following defines what each icon overlay represents:
Online-only files / folders don’t take up space on your computer. You see a cloud icon for each online-only file / folder in File Explorer, but the file / folder doesn’t download to your device until you access it. You can’t open online-only files / folders when your device isn’t connected to the Internet.
|
Mixed state Folder occurs when you have some items within it are mixed across online-only, always offline and/or cached.
When you open an online-only file, it is download to your device and becomes a cached file. You can open cached files anytime, even without internet access. If you need to free up space, you can change the file back to online only. To do so just right-click the file and select ‘to be set’ or go to the Citrix Files dashboard – settings – free up space
|
Only files or folders that you mark as “Make available offline” will have a green circle with the white check mark. These files or folders are downloaded to your device and are available offline. The bring these files or folders back to online-only, you need to right-click on the file or folder and select “Make available online”
|
Sync (upload / download) is in progress
|
The file is currently checked out
|
Accessing the Dashboard
You can access the dashboard by left clicking on the Citrix Files system tray icon. The dashboard will show you recently uploaded files. You can also access your Settings and other options by clicking the (…) in the top right corner of the dashboard.Settings Menu
Access the Settings menu from the dashboard or by right-clicking on the Citrix Files for Windows System Tray icon.Menu Option | Description |
---|---|
Log Out | Logs you out of your Citrix Files account. Cached files will be deleted. |
Launch on Startup | Determines whether the application should launch automatically after logging onto the computer. |
Reset App Settings |
Restores the app settings such as share options to their original, default values.
|
Enable beta Features | If your admin has enabled Desktop Apps Betas, then this setting will appear to allow you to enable Betas on this device. |
Drive Location | Uses S: as the default drive letter, but can be changed to other drive letters which are currently not in use. |
Drive Space | Clicking 'Free Up Space' will move any cached files to an online-only experience. Note, if using the Offline Access Beta, this setting will not move any files or folders you brought offline to an online only experience |
Share Options | Configure share options including notifications and security options. |
Cache size default is 5GB. This can be modified by your administrator via GPO.
Free Up Space
In the Citrix Files for Windows Settings UI, end users have the ability to Free Up Space. When clicked, Citrix Files for Windows will move any cached files
to an online-only
experience.
Note:
It will not move any files or folders you brought offline to an online only experience
to an online-only
experience.
Note:
It will not move any files or folders you brought offline to an online only experience
Upon clicking, Free Up Space a native notification will inform you how much space was freed.
Group Policy definitions and information is now in Citrix Product Documentation.
Updated list is now in Citrix Product Documentation.
Additional Resources
- CTX119253 - Language Support for Citrix Products
- Citrix Files for Windows: Group Policy Definitions
- Citrix Files for Windows: Known Issues
Disclaimer
Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.
-->
This article describes the requirements and limitations for using Microsoft Teams in a virtualized environment.
What is VDI?
Virtual Desktop Infrastructure (VDI) is virtualization technology that hosts a desktop operating system and applications on a centralized server in a data center. This enables a fully personalized desktop experience to users with a fully secured and compliant centralized source.
Microsoft Teams in a virtualized environment supports chat and collaboration, and with the Citrix platform, calling and meeting functionality are also supported.
Teams in a virtualized environment supports multiple configurations. These include VDI, dedicated, shared, persistent and non-persistent modes. Features are in continuous development and are added on a regular basis, and functionality will expand in the coming months and years.
Using Teams in a virtualized environment may be somewhat different from using Teams in a non-virtualized environment. For example, some advanced features may not be available in a virtualized environment and video resolution may differ. To ensure an optimal user experience, follow the guidance in this article.
Teams on VDI components
Using Teams in a virtualized environment requires the following components.
- Virtualization broker: The resource and connection manager to the virtualization provider, such as Azure
- Virtual desktop: The Virtual Machine (VM) stack that runs Microsoft Teams
- Thin client: The endpoint that the user physically interfaces with
- Teams desktop app: This is the Teams desktop client app
Teams on VDI requirements
Virtualization provider requirements
The Teams desktop app was validated with leading virtualization solution providers. With multiple market providers, we recommend that you consult your virtualization solution provider to ensure minimum requirements are met.
Currently, Teams on VDI with audio/video (AV) optimization is certified with Citrix. Review the information in this section to ensure both Citrix and Teams requirements are met for proper functionality.
Partners certified for Teams
The following partners have virtual desktop infrastructure solutions for Teams.
Partner | Partner solution |
---|---|
Citrix Virtual Apps and Desktops |
Citrix Virtual Apps and Desktops requirements
Citrix Virtual Apps and Desktops (formerly known as XenApp and XenDesktop) provides AV optimization for Teams on VDI. With Citrix Virtual Apps and Desktops, Teams on VDI supports calling and meeting functionality in addition to chat and collaboration.
You can download the latest version of Citrix Virtual Apps and Desktops here. (You'll need to sign in first.) The necessary components are bundled into the Citrix Workspace app (CWA) and Virtual Delivery Agent (VDA) by default. You don't need to install any additional components or plugins on CWA or the VDA.
For the latest server and client requirements, see this Citrix website.
Install or update the Teams desktop app on VDI
You can deploy the Teams desktop app for VDI using a per-machine installation or per-user installation using the MSI package. Deciding on which approach to use depends on whether you use a persistent or non-persistent setup and the associated functionality needs of your organization.For a dedicated persistent setup, either approach would work. However, for a non-persistent setup, per-machine installation is required for Teams to work efficiently. See the Non-persistent setup section.
With per-machine installation, automatic updates is 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 is enabled. 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 endpoint must have access to the internet. If internet access isn't available at the thin client endpoint, optimization startup won't be successful. This means that the user is in a non-optimized media state.
Dedicated persistent setup
In a dedicated persistent setup, users' local operating system changes are retained after users log off. For persistent setup, Teams support both per-user and per-machine installation.
The following is the recommended minimum VM configuration.
Parameter | Workstation operating system | Server operation system |
---|---|---|
vCPU | 2 cores | 4,6, or 8 It's important to understand the underlying non-uniform memory access (NUMA) configuration and configure your VMs accordingly. |
RAM | 4 GB | 512 to 1024 MB per user |
Storage | 8 GB | 40 to 60 GB |
Non-persistent setup
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 box resources.
For a non-persistent setup, the Teams desktop app must be installed per-machine to the golden image. (To learn more, see the Install or update the Teams desktop app on VDI section). This ensures an efficient launch of the Teams app during a user session. Using Teams with a non-persistent setup also requires a profile caching manager for efficient Teams runtime data sync. This ensures that the appropriate user-specific information (for example, user data, profile, and settings) are cached during the user session. There are variety of caching manager solutions available. For example, FSLogix. Consult your caching manager provider for specific configuration instructions.
Teams cached content exclusion list for non-persistent setup
Exclude the following from the Teams caching folder, %appdata%/Microsoft/Teams. Excluding these help reduce the user caching size to further optimize your non-persistent setup.
- .txt files
- Media-stack folder
Office 365 ProPlus considerations
Consider the following when you deploy Teams with Office 365 ProPlus on VDI.
New deployments of Teams through Office 365 ProPlus
Before you deploy Teams through Office 365 ProPlus, you must first uninstall any pre-existing Teams apps if they were deployed using per-machine installation.
Teams through Office 365 ProPlus is installed per-user. To learn more, see the Install or update the Teams desktop app on VDI section.
Teams deployments through Office 365 ProPlus updates
Teams is also being added to existing installations of Office 365 ProPlus. Since Office 365 ProPlus installs Teams per-user only, see the Install or update the Teams desktop app on VDI section.
Using Teams with per-machine installation and Office 365 ProPlus
Office 365 ProPlus doesn't support per-machine installations of Teams. To use per-machine installation, you must exclude Teams from Office 365 ProPlus. See the Deploy the Teams desktop app to the VM and How to exclude Teams deployment through Office 365 ProPlus sections.
![Citrix receiver installation windows 10 Citrix receiver installation windows 10](/uploads/1/2/7/2/127215029/557872428.png)
How to exclude Teams deployment through Office 365 ProPlus
To learn more about Teams and Office 365 ProPlus, see How to exclude Teams from new installations of Office 365 ProPlus and Use Group Policy to control the installation of Teams.
Deploy the Teams desktop app to the VM
-
Download the Teams MSI package that matches your VDI VM operating system using one of the following links:The minimum version of the Teams desktop app that's required is version 1.2.00.31357. (PSTN hold is not supported in earlier versions.)
-
Install the MSI to the VDI VM by running one of the following commands:
-
Per-user installation (default)This is the default installation, which installs Teams to the %AppData% user folder. At this point, the golden image setup is complete. Teams will not work properly with per-user installation on a non-persistent setup.
-
Per-machine installationThis installs Teams to the Program Files (x86) folder on a 64-bit operating system and to the Program Files folder on a 32-bit operating system. At this point, the golden image setup is complete. Installing Teams per-machine is required for non-persistent setups.The next interactive logon session starts Teams and asks for credentials.
-
-
Uninstall the MSI from the VDI VM.There are two ways to uninstall Teams:
-
PowerShell script (recommended):You can use this PowerShell script to clean up Teams from target machines or users. It should be executed for every user on a targeted machine.
-
Command line:This approach removes Teams, yet prevents re-installation of Teams. Run the following command:This uninstalls Teams from the Program Files (x86) folder or Program Files folder, depending on the operating system environment.
-
Teams on VDI performance considerations
There are variety of virtualized setup configurations, each with a different focus for optimization. For example, user density. When planning, consider the following to help optimize your setup based on the workload needs of your organization:
- Minimum requirement: Some workloads may require a setup using resources that are above the minimum requirements. For example, workloads for developers who use applications that demand more computing resources.
- Dependencies: These include dependencies on infrastructure, workload, and other environmental considerations outside the Teams desktop app.
- Disabled features on VDI: Teams disables GPU-intensive features for VDI, which can help improve transient CPU utilization. The following features are disabled:
- Teams CSS animation
- Giphy auto-start
Teams on VDI with calling and meetings
In addition to chat and collaboration, Teams on VDI with calling and meeting support is available with Citrix-based platforms. Supported features are based on the WebRTC media stack and Citrix-specific implementation. The following diagram provides an overview of the architecture.
These calling and meeting features are not supported:
- Enhanced emergency services
- HID buttons and LED controls between the Teams app and devices
- Background blur and effects
- Broadcast/live events
- Location-Based Routing (LBR)
- Call park
- Call queue
Important
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 Citrix 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, see this Citrix website.
We're working on adding calling and meeting features that are currently only available in non-VDI environments. These may include more admin control over quality, additional screen sharing scenarios, and advanced features recently added to Teams. Contact your Teams representative to learn more about upcoming features.
Network requirements
We recommend that you evaluate your environment to identify any risks and requirements that can influence your overall cloud voice and video deployment. Use the Skype for Business Network Assessment Tool to test whether your network is ready for Teams.
To learn more about how to prepare your network for Teams, see Prepare your organization's network for Teams.
Migrate from Skype for Business on VDI to Teams on VDI
If you're migrating from Skype for Business on VDI to Teams on VDI, besides the differences between the two applications, there are some differences when VDI is also implemented. Some capabilities that aren’t currently supported in Teams VDI that are in Skype for Business VDI are as follows:
- Control of VDI calling experiences with policies for limiting media bitrate
- Per-platform policy to disable some AV features in VDI
- Give and take control when app sharing
- Screen share from chat without audio
- Simultaneous video and screen sharing send and receive
Teams on Chrome browser versus Teams desktop app for VDI
Teams on Chrome browser doesn't provide a replacement for the Teams desktop app for VDI with AV optimization. The chat and collaboration experience works as expected. When media is needed, there are some experiences that may not meet user expectations on the Chrome browser:
- The audio and video streaming experience may not be optimal. Users may experiences delays or reduced quality.
- Device settings aren't available in browser settings.
- Device management is handled through the browser and requires multiple settings in browser site settings.
- Device settings may also need to be set in Windows device management.
Teams on VDI with chat and collaboration
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. This feature level doesn't require Citrix Virtual Apps and Desktops.
Set policies to turn off calling and meeting functionality
You can set policies by using the Microsoft Teams admin center or PowerShell. It can take some time (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.
Assign policies using the Microsoft Teams admin center
To assign the DisallowCalling calling policy and the AllOff meeting policy to users, follow these steps:
- In the left navigation of the Microsoft Teams admin center, go to Users.
- Select the user by clicking to the left of the user name, and then click Edit settings.
- Do the following:
- Under Calling policy, click DisallowCalling.
- Under Meeting policy, click AllOff.
- Click Apply.
To assign a policy to multiple users at a time, see Edit Teams user settings in bulk.
Or, you can also do the following:
- In the left navigation of the Microsoft Teams admin center, go to the policy you want to assign. For example:
- Go to Voice > Calling policies, and then click DisallowCalling.
- Go to Meetings > Meeting policies, and then click AllOff.
- Select Manage users.
- In the Manage users pane, search for the user by display name or by user name, select the name, and then click Add. Repeat this step for each user that you want to add.
- When you're finished adding users, click Save.
Assign policies using PowerShell
The following example shows how to use the Grant-CsTeamsCallingPolicy to assign the DisallowCalling calling policy to a user.
To learn more about using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.
The following example shows how to use the Grant-CsTeamsMeetingPolicy to assign the AllOff meeting policy to a user.
To learn more about using PowerShell to manage meeting policies, see Set-CsTeamsMeetingPolicy.
Migrate Teams on VDI with chat and collaboration to Citrix with calling and meetings
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 Citrix with AV optimization, you must set policies to turn on calling and meeting functionality for those Teams on VDI users.
Set policies to turn on calling and meeting functionality
You can use the Microsoft Teams admin center or PowerShell to set and assign calling and meeting policies to your users. It can take some time (a few hours) for policy changes to propagate. If you don’t see changes for a given account immediately, try again after a few hours.
Calling polices: Calling policies in Teams control which calling features are available to users. Teams includes the built-in AllowCalling calling policy, in which all calling features are turned on. To turn on all calling features, assign the AllowCalling policy. Or, create a custom calling policy to turn on the calling features that you want and assign it to users.
Meeting policies: Meeting policies in Teams control the types of meetings that users can create and the features that are available to meeting participants that are scheduled by users in your organization. Teams includes the built-in AllOn meeting policy, in which all meeting features are turned on. To turn on all meeting features, assign the AllOn policy. Or, create a custom meeting policy to turn on the meeting features that you want and assign it users.
Assign policies using the Microsoft Teams admin center
To assign the AllowCalling calling policy and the AllOn meeting policy to users, follow these steps:
- In the left navigation of the Microsoft Teams admin center, go to Users.
- Select the user by clicking to the left of the user name, and then click Edit settings.
- Do the following:
- Under Calling policy, click AllowCalling.
- Under Meeting policy, click AllOn.
- Click Apply.
To assign a policy to multiple users at a time, see Edit Teams user settings in bulk.
Or, you can also do the following:
- In the left navigation of the Microsoft Teams admin center, go to the policy you want to assign. For example:
- Go to Voice > Calling policies, and then click AllowCalling.
- Go to Meetings > Meeting policies, and then click AllOn.
- Select Manage users.
- In the Manage users pane, search for the user by display name or by user name, select the name, and then click Add. Repeat this step for each user that you want to add.
- When you're finished adding users, click Save.
Assign policies using PowerShell
The following example shows how to use the Grant-CsTeamsCallingPolicy to assign the AllowCalling calling policy to a user.
To learn more about using PowerShell to manage calling policies, see Set-CsTeamsCallingPolicy.
The following example shows how to use the Grant-CsTeamsMeetingPolicy to assign the AllOn meeting policy to a user.
To learn more about using PowerShell to manage meeting policies, see Set-CsTeamsMeetingPolicy.
Known issues and limitations
Client deployment, installation, and setup
![Login Login](/uploads/1/2/7/2/127215029/249614461.png)
- With per-machine installation, Teams on VDI isn't automatically updated in the way that non-VDI Teams clients are. You have to update the VM image by installing a new MSI as described in the Install or update the Teams desktop app on VDI section. You must uninstall the current version to update to a newer version.
- Teams should be deployed either per user or per machine. Deployment of Teams for concurrent per user and per machine is not supported. To migrate from either per machine or per user to one of these modes, follow the uninstall procedure and redeploy to either mode.
- MacOs and Linux-based clients are not supported by Citrix at this time.
- Citrix doesn't support the use of explicit HTTP proxies defined on an endpoint.
Calling and meetings
- Interoperability with Skype for Business is limited to audio calls, no video modality.
- Dual Tone Multi Frequency (DTMF) interaction with telephony systems is currently not supported.
- Joining Teams meetings as an anonymous user isn't AV-optimized. The user can join the meeting and have a non-optimized experience.
- Only a single incoming video stream is supported in meetings or group calls. When multiple people send video, only the dominant speaker's video is shown at any given time.
- Incoming and outgoing video stream resolution is limited to 720p resolution. This is a WebRTC limitation.
- Only one video stream from an incoming camera or screen share stream is supported. When there's an incoming screen share, that screen share is shown it instead of the video of the dominant speaker.
- Outgoing screen sharing:
- Application sharing is not supported.
- Give control and take control:
- Not supported during a screen sharing or application sharing session.
- Supported during a PowerPoint sharing session.
- High DPI scaling on CWA is not supported.
For Teams known issues that aren’t related to VDI, see Known issues for Teams.
Troubleshooting
Troubleshoot Citrix components
For information on how to troubleshoot VDA and CWA issues, see this Citrix website.
Related topics
![](/uploads/1/2/7/2/127215029/563973157.jpg)
Comments are closed.
Author
Write something about yourself. No need to be fancy, just an overview.
Archives
December 2022
November 2022
March 2020