So if I log on to another XenApp server – even one without the “Machine-Wide Installer” installed, Teams is still available for use.
#Citrix xenapp 6.5 policy not applying install#
The install (which is around 400MB to start with, and rapidly increases) will now follow the user because it is installed fully into the user profile. It also drops an auto-start entry into the Registry, at HKCU\Software\Microsoft\Windows\CurrentVersion\Run, which points to the same executable as above with some slightly different parameters It spits out the Teams install into the user’s local profile, rather than anywhere in system areasĪ desktop shortcut is written to the user’s profile (%USERPROFILE%\Desktop), with the target pointing to %LOCALAPPDATA%\Microsoft\Teams\Update.exe –processStart “Teams.exe”Ī Start Menu shortcut is written to the user’s profile (%USERPROFILE%\Microsoft\Windows\Start Menu\Programs\Microsoft Corporation) which also points to %LOCALAPPDATA%\Microsoft\Teams\Update.exe –processStart “Teams.exe” as the target So when any user logs on to the machine, the executable from the c:\Program Files (x86)\Teams Installer folder runs, which triggers some more actions, namely:. This executable is auto-triggered at every user logon by an entry in the HKLM\Software\Wow643Node\Microsoft\Windows\CurrentVersion\Run area of the Registry which is also dropped by the Machine-Wide Installer When you run this, it creates a folder in C:\Program Files (x86) called Teams Installer, and in there you will find two files only But for those of us who manage XenApp and XenDesktop in non-persistent environments, Teams is a hideous glimpse of an application that Microsoft is so determined to dump onto every user that it possibly can, that it simply bypasses all the norms we’ve become used to, in the same way that Chrome and DropBox both can.įirstly, when you download the Teams MSI (or, to give it the proper name, the “Teams Machine-Wide Installer”), you don’t actually install Teams when you run it. Teams is going to put a bullet in the head of Skype for Business, eat Slack’s lunch, and be the face that launched a thousand Microsoft 365 subscriptions. Yes, that’s exactly how I feel after digging through the mess that is the guts of Microsoft Teams.
![citrix xenapp 6.5 policy not applying citrix xenapp 6.5 policy not applying](https://image.slidesharecdn.com/syn406citrixgrouppolicyarchitectureandtroubleshootingforxenappandxendesktop-140515161932-phpapp01/95/syn406-citrix-group-policy-architecture-and-troubleshooting-for-xenapp-and-xendesktop-1-638.jpg)
![citrix xenapp 6.5 policy not applying citrix xenapp 6.5 policy not applying](https://i1.wp.com/www.virtuallyimpossible.co.uk/wp-content/uploads/2013/03/Publishing_Applications_with_Citrix_XenApp_6.5_001.png)
#Citrix xenapp 6.5 policy not applying series#
For updated information on Teams deployment on Citrix or other VDI/RDSH platforms, please see this series of articles. Teams is Microsoft’s new Skype and Slack-killer.