Has anyone followed this article yet? I have and so far it does install to that location but gives no process on how to actually get teams into the end users account once they login.
I have looked at kvm's blog and followed everything outlined in it. Unfortuantely, I am still having issue with getting Teams working in our Horizon 7.8 environment.
I installed Teams on our test image using this command "msiexec /I <path_to_msi> /l*v <install_logfile_name> ALLUSER=1 ALLUSERS=1". Created a snapshot and republished the pool. Additionally, I added the directories below to UEM to ensure they are cached:
- C:\Users\username\AppData\Local\Microsoft\IdentityCache (%localAppdata%\Microsoft\IdentityCache)
Upon logging into a desktop the first time, Teams attempts to start/run but a white box just appears on a screen and nothing happens. If I logout of the desktop and grab a new one, Teams seems to launch fine and work ok...for a while. When I logout of the desktop and then grab another one either later that day or the next day, Teams may or may not start.
However, if it does I will have the message at the top "We weren't able to connect. Sign in and try again." Also, the icons for the people (either names of initials) do not exist and the status of the user is not available. However messages do seem to come through.
We need to get this working as quickly as possible so any help is greatly appreciated.
Hi! A few weeks ago, I deployed a non persistent enviorment with Instant Clones, App Volumen Manager, Office 365 and Teams. With writiable volumes (use tempalte profile only) you can saved users credentials. Yo need to install Teams and Office 365 on the Master Image.
I have Teams installed on the image and I am using UEM for the settings and caching the credentials. What else do I need to do
Sorry, I forget this: you need to create this shortcut configuration on UEM or DEM server:
Shortcut name: Microsoft Teams
Arguments: C:\Users\%username%\AppData\Local\Microsoft\Teams\Update.exe --processStart "Teams.exe"
Start in: C:\Users\%username%\AppData\Local\Microsoft\Teams
Icon Path: C:\Users\%username%\AppData\Local\Microsoft\Teams\app.ico
Icon index: 0
Check run asynchronously
I not used DEM Server to cached the users credentials, I used App Volumes writiable.
The shortcut you are creating is for a user-installed teams setup, not a machine-wide teams setup. If you install teams correctly using both ALLUSER=1 ALLUSERS=1 switches, there will be no teams.exe in the userprofile, but only in c:\program files (x86)\microsoft\teams\
If you have teams.exe in both userprofile and program files folder, you'll start getting teams crashes because the teams in userprofile will update itself and won't be the same version of the teams installed in program files anymore. Trust me, I've been there, it's a lot of work to get that right afterwards. Certainly on non-persistent VDI, you should not let users install Teams in their userprofile!
RachelW Concerning the DEM config, I can't help you, because we don't use it. We use FSLogix to store our profiles and that works very smooth.
I obtained that command from this article from Microsoft (Teams for Virtualized Desktop Infrastructure - Microsoft Teams | Microsoft Docs). The install command I posted regarding the install was from this article - per-machine, non-persistent desktop. I am a little confused as to your comment about it being per-user instead of per-machine. Can you help me understand what you mean?
When a user logs into your virtual desktop the first time, are they prompted to enter credentials? Currently, we are being prompted the first time and then after that it does not. Do you know how to not have it prompt the user and just use their credentials of the machine they are logged into?
Don't worry, I was confused too when I found out I installed it wrong...
Using the MSI switch ALLUSERS=1 the MSI package will install a teams.exe in c:\program files (x86)\microsoft\teams and create a registry RUN key in HKLM so that everytime a user logs on, that teams.exe is started. In fact, that teams.exe is not the Teams executable, but a teams setup, that will install the Teams package in the userprofile (%appdata%\microsoft\teams\...).
Problem with this setup, is that there will be a full teams setup in each userprofile that logs on to the server/vdi!
Another problem with this setup, is that every user will be able to update the teams installation in their userprofile and this will lead to teams crashes when the teams setup in c:\program files (x86)\... is a different version than the one installed in the userprofile. (we found out the hard way. All was fine for about 3 weeks, and then suddenly users started complaining their teams crashed when they started a video call)
However, if you setup the MSI with ALLUSER=1 ALLUSERS=1 Teams will effectively be installed in c:\program files (x86)\microsoft\teams and run from there. Only user data will be stored in the userprofile and the users will also NOT be able to update the teams installation (to update it, you have to uninstall and reinstall the latest version with the same switches on the master image).
This is also the preferred way to go when using non-persistent desktops. Users will not be able to update their teams installation and when they try to download teams and install it, it will just start the already installed teams from c:\program files (x86)\... but not actually install anything because it sees it's already there.
Hopefully this clears out some confusion :-)
Another question I have is this....like I said we are using UEM and I noticed the Microsoft Teams Archive file is rather large - 40 MB compressed. What can be done to reduce the size of that file? I just spent weeks getting the Chrome profiles reduced to a decent size and now the Teams profiles are large.
Any suggestions are appreciated.
Here's a link to the Teams guide + DEM attached is a Teams.zip which i havent full tested yet, but it looks promising. I think it's in this post here somewhere.
p.s If you have a link to a promising guide on how to reduce the chrome settings please message me. ^^
1 person found this helpful
**Disclaimer, we don't use the latest version currently in production but I have tested this on a newer version but definitely not the latest version.
This is what I've determined needs to be captured under the Teams folder. These are the bare minimum from what I can tell that need to be captured, but this causes the index and cache to be rebuilt every time the user logs in. If you have low-performance VMs then you may want to consider capturing those folders as well but experiment with it.
This creates about a 200-300 kb zip file. The biggest contributor is the dictionaries file.
I've also spoken with Microsoft support and they also recommend capturing these settings as these are the location in which the AAD credentials are stored:
And making the following reg edits:
- Modify the added registry key HKCU\Software\Microsoft\Office\16.0\Common\Identity\DisableADALatopWAMOverride to 0 instead of 1
- Modify the added registry key HKCU\Software\Microsoft\Office\16.0\Common\Identity\DisableAADWAM to 0 instead of 1
- Add the following registry value: HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin\BlockAADWorkplacejoin , set value to 1
A big factor in capturing Teams seems to really be how your Office 365 environment is set up.
We use ADConnect to sync AD to AAD.
We do not do SSO, so the user auths in Office 365 directly.
We do use password sync both to and from Azure AD.