Microsoft Teams optimization not working for self-hosted Citrix Workspace app for Chrome OS users
book
Article ID: CTX331648
calendar_today
Updated On:
Description
Users who meet all below conditions
- use self-hosted/repackaged versions of Citrix Workspace app for Chrome OS from their own enterprise admin consoles AND
- have updated to Chrome OS Version 96 and above, AND
- have enabled Microsoft Teams optimization AND
- are on version 2111 of Citrix Workspace app for Chrome OS
see Microsoft Teams is unoptimized within the virtual desktop and the Microsoft Teams virtual app.
Users who meet all below conditions
- use self-hosted/repackaged versions of Citrix Workspace app for Chrome OS from their own enterprise admin consoles AND
- have updated to Chrome OS Version 96 and above, AND
- have enabled Microsoft Teams optimization AND
- are on versions older than 2111 of Citrix Workspace app for Chrome OS
will see screen sharing/joining meetings/calls not connecting from Microsoft Teams within virtual desktop/virtual app
Resolution
Customers who are repackaging/self-hosting Citrix Workspace app for Chrome OS will need to follow the steps below :
1. Sign up for the Origin Trial
here.
2. Click on Register. You will see the interface as in the snapshot below. In the field ‘Web Origin’ enter
chrome-extension://{app-id}. Here replace
app-id with the id of self-hosted Citrix Workspace app for Chrome OS. Tick all the checkboxes and click
Register.
3. . Once you complete the registration, you will immediately receive a valid token that needs to be copied.

4. Go to Citrix Workspace app for Chrome OS code downloaded from Citrix downloads.
- If you’re on a version older than 2111 of Citrix Workspace app for Chrome OS, then Unzip and access SessionWindow.html located in ChromeApp/src folder and paste the following under the <head> tag of SessionWindow.html.Here replace ‘TOKEN’ with the Token copied in Step 3.
- <meta http-equiv="origin-trial" content="TOKEN">
- If you’re on a version 2111 or later of Citrix Workspace app for Chrome OS, then Unzip and access SessionWindow.html located in ChromeApp/src folder. You will find the <meta> tag where you can replace the existing token with the Token you copied in Step 3<meta http-equiv="origin-trial" content="TOKEN">
Was this article helpful?
thumb_up
Yes
thumb_down
No