Citrix Arena

Introduction

Installation of Teams

Step 1

Download the MSI package. Click here

Step 2
You must uninstall the current version prior to the installation or update.

Method 01: Uninstall using a PowerShell script. Click Here

Method 02: 

Start CMD as an Administrator and start the uninstallation with the following command:

msiexec /passive /x [Path to MSI] /l*v [Path to uninstall_logfile]

Step 3

Start CMD as an Administrator and start the installation with the following command:
msiexec /i [Path_to_MSI] /l*v [Path to install_logfile_name] ALLUSER=1 ALLUSERS=1

Prior to the installation on WVD, add the following registry key

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Teams\IsWVDEnvironment]

 Type: REG_DWORD

 Value: 1

Note: This will install Teams to Program Files (x86) on 64-bit systems and Program Files folder on 32-bit systems.

-------------------------------------------------------------------------------------------------------------------------------------

Important (Citrix App Layering):

If you are using Citrix App Layering PortICA key needs to add to the following registry path before you start the Teams installation with ALLUSER=1

HKEY_LOCAL_MACHINE\SOFTWARE\Citrix

Or

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Citrix

------------------------------------------------------------------------------------------------------------------------------------

Changes to be made on user profile solutions

Remove the following path if you have excluded in your user profile solution.

• Roaming/Microsoft/Teams

Add the following folder paths to the exclude list- directories.

• %AppData%\Microsoft\Teams\Application Cache
• %AppData%\Microsoft\Teams\Cache
• %AppData%\Microsoft Teams\Logs
• %AppData%\Microsoft\Teams\media-stack
• %Localappdata%\SquirrelTemp
• %Localappdata%\Microsoft\Teams\Current\Locales
• %Localappdata%\Microsoft\Teams\current\resources\locales
• %Localappdata%\Microsoft\Teams\Packages\SquirrelTemp

Add the following file paths to the exclusion list - files

• %AppData%\/Microsoft/Teams/*.txt

Add the following files paths to the files to synchronize. In my case in only require EN. Add more locales which are suites for your environment.

• %Localappdata%\Microsoft\Teams\Current\Locales\en*.pak
• %Localappdata%\Microsoft\Teams\current\resources\locales\locale-en*

------------------------------------------------------------------------------------------------------------------------------------

Recommendations

Disabling Teams AutoStart

• Enable to prevent Microsoft Teams from starting automatically after installation policy under User Configuration\Policies\Administrative Templates\Microsoft Teams

Note: If you are unable to find the policy, you may be missing the latest ADMX files in your policy central store. Download the latest ADMX files for Office365 and copy them into the Policy definition folder under SYSVOL. 

------------------------------------------------------------------------------------------------------------------------------------

Microsoft Teams redirection (Citrix)

Enable Microsoft Teams redirection policy on Citrix Studio

Note that, in order to get this configured on your environment the following requirements should be met.

• Controller Version: Minimum version - Delivery Controller (DDCs) 1906.2
• VDA Version: Minimum version - Virtual Delivery Agents (VDAs) 1906.2
• Workspace App Version: Minimum version - Citrix Workspace app 1907 for Windows
• Support Server OSs: Windows Server 2019, 2016, and 2012 R2 (Standard and Datacenter Editions)
• Support Client OSs: Windows 10 64-bit, minimum versions 1607 up to 1909

By default, HDX optimization for Teams is enabled in the VDA and if you are using a supported Workspace app, the following registry key will be configured to 1 automatically.

When it comes to optimizing Teams, we need to consider some other requirements as well. Please refer the following articles for more information.

• Optimization for Microsoft Teams
• Multimedia policy settings
• Teams for Virtualized Desktop Infrastructure

I hope this helps! Please feel free to let me know if anything else needs to be added. Your suggestions and recommendation are welcome.

Thank You!

• Monitors
• Servers
• Services or a Service Group (I prefer a Service Group)
• vServer (Virtual Server).

Monitor

• Expand Traffic Management > Load Balancing > Monitors.

• Name the Monitor (as preferred). 
• Change the Type from the drop down to User.

• Go to Special Parameters tab.
• Change the Type from the drop down to nstftp.pl.
• Click Create.

Servers

• Expand Traffic Management > Load Balancing > Servers.

• On the right Click Add.

• Enter the Server Name.
• Enter the IP address of the server.
• Enter the comments as you wish to describe the server. (not a must)
• Click Create.

Service Group

• Expand Traffic Management > Load Balancing > Service Groups.
• On the right, click Add.

• Give the Service Group a striking name.
• Change the Protocol to TFTP.

• Click on “No Service Group Member” to add the Server objects.

• Change the selection to Server Based and then select the server objects. If you did not create the server object before, then enter the IP address of a PVS Server.
• Enter 69 the port.
• Click Create.

• Under Advanced Settings, Click Monitors.

• Click on No Service Group to Monitor Binding under Monitors section.

• Click on the arrow next to Click to select to select the Monitor.

• Select Monitor_PVS and Click Select.

• Then Click Bind.

• To verify if the Monitor is working Click on Server Group Members.
• Select a member server and then Click Monitor Details.

• The Last Response Should be Success – Probe Succeeded. Click Close twice.
• Click Done.

Load Balancing Virtual Server.

• Expand Traffic Management > Load Balancing > Virtual Servers.

• On the right, click Add.

• Name the vServer as you wish.
• Change the protocol to TFTP.
• Enter a new internal VIP.
• Enter 69 as the port.
• Click OK.

• Click on No Load Balancing Virtual Server ServiceGroup Binding under Services and Service Groups to add the Service Group or Service.

• Click on the arrow next to Click to select to select the ServiceGroup.

• Select the SVC_PVS Service Group and Click Select.

• Click Bind.
• Click Continue.
• Under Advanced Settings click on Method.

• Under Load Balancing Method Select ROUNDROBIN and Backup LB Method should be LEASTCONNECTION. Click OK.

• Verify if LB vServer appears in the up state.

DNS/DHCP

Optional

• Add a New A Host Record in the DNS. In this case, im using PVS as the name but it can be something as you like.

• At last, on the DHCP server configure the PVS Load Balancing vServer VIP address under Scope Option window Option 066 Boot Server Host Name.

• To verify this stop Citrix PVS TFTP service on one of PVS Server. Then Monitor_PVS on NetScaler as this detects if the service is down.
• Try to boot up the Target Device it should contact the TSPVS002 in this case.

• They grow uncontrollably. For example, when we add more applications and those settings are saved into the roaming profile. When we delete it from our system, it will still be in the Roaming Profile. This tends to be a big issue for the terminal servers as login time will increase after a while because profiles are growing and growing quite fast however they are never cleaned up! Or cleared! If a user has an issue we just delete the user profile and the user has to setup all the applications all over again.

• Profile Corruption – This is a common problem, almost happening more than once a day for my experience. If we delete 5 profiles for a day, the users who want to login will have to set up the icons and applications just the way they like it all over again, which is tedious and frustrating both for the user and those at the Service desk.

• Difficult to fix

• Slow – This is caused when because. When you login the whole profile will be copied into the Terminal server which is where u login and when you log off the profile will be copied back to the file share. Regardless of If your profile is 5MB, 1GB or 3GB or more…. It will slow down your login time.

• Susceptible to “last write wins” and resultant settings loss where application silos exist

• No Special modifications.
• Easy to implement.
• The user profile is accessible from any XenApp server.
• Settings are saved across sessions.