Microsoft Teams.zip

Microsoft Teams.zip

Attachments
Comments

The DirectFlex trigger needs to be modified in this .ini

REF:   DirectFlexPath=c:\users\pim\appdata\local\microsoft\teams\update.exe

How do you add variables to the DirectFlex path?

Teams now offers an MSI installer for all users:

Install Microsoft Teams using MSI | Microsoft Docs

Have not tested, but this is part of the documentation, I suspect the UEM config file stays the same.

"The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of Teams application will be installed in that user's appdata folder. If a user already has the Teams app installed in the appdata folder, the MSI installer will skip the process for that user."

DirectFlexpath has been updated to

DirectFlexPath=%LOCALAPPDATA%\microsoft\teams\current\teams.exe

For non-persistent machines without roaming profile you have to configure the following:

[IncludeFolderTrees]

<LocalAppData>\Microsoft\Credentials

<LocalAppData>\Microsoft\Teams

<LocalAppData>\Microsoft\TeamsMeetingAddin

<LocalAppData>\SquirrelTemp

<AppData>\Microsoft\Teams

<AppData>\Microsoft Teams

<AppData>\Teams

Implemented and tested today ...

Newer version see below!!!

I have got it to copy the Teams profile over, but it always asks for the user to log in. It remembers the user but not the fact they were logged in, so they have to enter their password each time.

Problems with the Teams Outlook add-in?

By excluding the file "storage.json" the Outlook Teams add-in does now work each time the user logs in to a new non-persistant and non-dedicated desktop. Before changing this setting, we got always the message that the user has to sign out and in again into teams which doesn't resolve the issue. So the Teams add-in works now as expected and the users doesn't have to sign in each time to teams (only users without uem profile once).

Hope this helps.

Here's our config for VMware UEM/DEM:

[IncludeFolderTrees]

<LocalAppData>\Microsoft\Credentials   <-- it's possible that this line is not needed when using multi-factor authentication

<LocalAppData>\Microsoft\Teams

<LocalAppData>\Microsoft\TeamsMeetingAddin

<LocalAppData>\Microsoft\TeamsPresenceAddin

<LocalAppData>\SquirrelTemp

<AppData>\Microsoft\Teams

<AppData>\Microsoft Teams

<AppData>\Teams

[ExcludeFolderTrees]

<AppData>\Microsoft Teams\logs

<AppData>\Microsoft\Teams\Application Cache

<AppData>\Microsoft\Teams\Cache

<AppData>\Microsoft\Teams\tmp

[ExcludeFiles]

<AppData>\Microsoft\Teams\logs.txt

<AppData>\Microsoft\Teams\lockfile

<AppData>\Microsoft\Teams\storage.json

_______________________________________________________________________________________________________________________

Message Text (German):

Sie müssen sich bei Teams ab- und wieder anmelden, um eine Besprechung planen zu können. Wenn das Problem fortbesteht, wenden Sie sich bitte an Ihr Supportteam.

Message Text (English):

Sorry, you need to sign out of Teams and sign in again before you can schedule your meeting. If the problem persists, please contact your support team.

What version of Teams are you using? Also machine or user-based install?

Version is: 1.2.00.24753 (64-bit)

It is machine based install.

Are you sure? For me, the machine wide install (ALLUSER=1) doesn't create these folders:

<LocalAppData>\Microsoft\Teams

<LocalAppData>\Microsoft\TeamsMeetingAddin

<LocalAppData>\Microsoft\TeamsPresenceAddin

<LocalAppData>\SquirrelTemp

As of an hour ago i have got it working...

I added the following:

[IncludeRegistryTrees]

HKCU\Software\Microsoft\Office\Teams

I have followed the setup from this thread (including the registry inclusion above), however I get one of the two outcomes below:

If I exclude the storage.json file the Outlook Teams add-in works, but the user is asked to enter their password to login to Teams on every login.

If I don't exclude storage.json Teams automatically logs in, however the Outlook Teams add-in doesn't work.

Has anyone been able to get Teams to automatically login AND get the Outlook Teams add-in working with federated O365?

I too get this exact same outcome, with these exact settings.  Thank you to everyone that is putting in the work to figure this out as Microsoft keeps throwing curve balls at us each update.

FYI i have been working on this a ton today and I decided to un-exclude the storage.json file and I was able to auto sign-in and also had my outlook plugin.

this is our Config

[IncludeRegistryTrees]

HKCU\Software\Microsoft\Office\Teams

[IncludeFolderTrees]

<LocalAppData>\Microsoft\Credentials

<LocalAppData>\Microsoft\Teams

<LocalAppData>\Microsoft\TeamsMeetingAddin

<LocalAppData>\Microsoft\TeamsPresenceAddin

<LocalAppData>\SquirrelTemp

<AppData>\Microsoft\Teams

<AppData>\Microsoft Teams

<AppData>\Teams

[ExcludeFolderTrees]

<AppData>\Teams\logs

<AppData>\Microsoft\Teams\media-stack

<AppData>\Microsoft\Teams\Service Worker

<AppData>\Microsoft\Teams\Application Cache

<AppData>\Microsoft\Teams\Cache

<AppData>\Microsoft\Teams\tmp

[ExcludeFiles]

<AppData>\Microsoft\Teams\logs.txt

<AppData>\Microsoft\Teams\lockfile

#<AppData>\Microsoft\Teams\storage.json

Thanks for chiming in j.ervolino, however unfortunately this doesn't resolve my issue and I'm not sure why Smiley Sad

Your config works for the next login, however for subsequent ones I go back to having the Teams Outlook plugin issue. We use Office 2016 and run federated O365. What do you run? Does yours work consistently for all subsequent logins? Do you run the Teams machine wide installer?

I have the outlook addin working, but the auto login has stopped working since the last update of Teams. We are using outlook 2016 and local exchange server.

We are much the same federated AD through Azure sync, only difference is Office 2013 for us not 2016, one thing I have done is I used UEM ADMX template and pushed the outlookadin to load for everyone, snapshot of those settings is below.

I opened a ticket with Microsoft and they stated that you should also be tracking:

[IncludeFolderTrees]

<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

I added the following:

[ExcludeFolderTrees]

<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\TempState

<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Temp

In my testing it works but I haven't had a chance to do full-blown testing.

I had to add this line to [Included Folders]

<LocalAppData>\Microsoft\IdentityCache

Works like a champ now.

Hello,

We're using the Teams per machine system Wide Installer ver. 1.3.0.13565, Instant Clones and DEM 9.9. I have tried every setting listed in this thread and still getting the following screens (in order) when starting Teams for every user at every login. We are using Federated O365 with Office 2016.

I'm guessing this is not "expected behavior." Has anyone gotten this working?

Teams Config File in DEM

[IncludeFolderTrees]

<LocalAppData>\Microsoft\IdentityCache

<LocalAppData>\Microsoft\Teams

<LocalAppData>\Microsoft\TeamsMeetingAddin

<LocalAppData>\Microsoft\TeamsPresenceAddin

<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

<LocalAppData>\SquirrelTemp

<AppData>\Microsoft\Teams

<AppData>\Microsoft Teams

<AppData>\Teams

[ExcludeFolderTrees]

<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\TempState

<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Temp

<AppData>\Microsoft Teams\logs

<AppData>\Microsoft\Teams\Application Cache

<AppData>\Microsoft\Teams\Cache

<AppData>\Microsoft\Teams\tmp

[ExcludeFiles]

<AppData>\Microsoft\Teams\logs.txt

<AppData>\Microsoft\Teams\lockfile

<AppData>\Microsoft\Teams\storage.json

I've been going through almost the same scenario with Microsoft Support. I'm not 100% out of the woods yet, but I think the key to success in bypassing MDM enrollment is to set these two reg keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin\autoWorkplaceJoin=dword:00000000

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin\BlockAADWorkplaceJoin=dword:00000001

I would also recommend upgrading your Teams client, if you can.

Thanks doddsington​, this worked like a charm!

In our environment we install Teams like this

msiexec /i Teams_windows_x64.msi OPTIONS="noAutoStart=true" ALLUSERS=1 ALLUSER=1

Our DEM :

 

[IncludeRegistryTrees]
HKCU\Software\Microsoft\Office\Teams
HKCU\Software\Microsoft\Tracing\WPPMediaPerApp\Teams

[IncludeFiles]
<AppData>\Microsoft\Teams\desktop-config.json
<AppData>\Microsoft\Teams\settings.json

[IncludeFolderTrees]
<AppData>\Teams
<AppData>\Microsoft\Teams
<LocalAppData>\Microsoft\IdentityCache
#<LocalAppData>\Microsoft\Teams
#<LocalAppData>\Microsoft\TeamsMeetingAddin
#<LocalAppData>\Microsoft\TeamsPresenceAddin
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
<LocalAppData>\SquirrelTemp
<AppData>\Microsoft Teams\Backgrounds\Uploads

[ExcludeFolderTrees]
<AppData>\Microsoft\Teams\logs
<AppData>\Microsoft\Teams\Application Cache
<AppData>\Microsoft\Teams\ai_models
<AppData>\Microsoft Teams\Backgrounds
<AppData>\Microsoft\Teams\Cache
<AppData>\Microsoft\Teams\Code Cache
<AppData>\Microsoft\Teams\CodeCache
<AppData>\Microsoft\Teams\Dictionaries
<AppData>\Microsoft\Teams\GPUCache
<AppData>\Microsoft\Teams\Service Worker
<AppData>\Microsoft\Teams\Service Worker\CacheStorage
<AppData>\Microsoft\Teams\Service Worker\ScriptCache
<AppData>\Microsoft\Teams\[MATCHALL]\Media-stack
<AppData>\Microsoft\Teams\media-stack
<AppData>\Microsoft\Teams\meeting-addin\Cache
<AppData>\Microsoft\Teams\skylib
<AppData>\Microsoft\Teams\tmp
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Temp
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\TempState
<LocalAppData>\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Tokenbroker\Accounts

[ExcludeIndividualFolders]
<AppData>\Microsoft Teams\Backgrounds

[ExcludeFiles]
<AppData>\Microsoft\Teams\lockfile
#<AppData>\Microsoft\Teams\storage.json
<AppData>\Microsoft\Teams\*.txt
old_logs_*.txt
logs.txt
LOG
LOG.old
*.log
*.txt

 

All of these base on MS Artikels
https://learn.microsoft.com/de-de/microsoftteams/msi-deployment

https://learn.microsoft.com/de-de/microsoftteams/teams-for-vdi

 

Version history
Revision #:
1 of 1
Last update:
‎09-27-2017 01:14 PM
Updated by: