I am currently testing the new Teams Client with VDI pooled machines and App Layering.
To install Teams in VDI i used the "teamsbootstrapper.exe -p - o MSTeams-x64.msix" in the OS Layer.
I can say that I've managed to get it to work with some workarounds, but I want to find a way to get everything working smoothly. The new Teams client is running, but the Add-in is not running in the user account. There is no Teams Outlook Add-in under %LocalAppData%.
I unpacked the MSIX Teams file with 7-Zip, where I found the Teams-Outlook-Addin MSI. I then installed the Add-in in a test user account (no admin privileges were needed). After that, I switched the registry key "LoadBehavior" under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect to 3. With this key, the Add-in runs in Outlook on startup.
Question
Sch1ll3
Hi,
I am currently testing the new Teams Client with VDI pooled machines and App Layering.
To install Teams in VDI i used the "teamsbootstrapper.exe -p - o MSTeams-x64.msix" in the OS Layer.
I can say that I've managed to get it to work with some workarounds, but I want to find a way to get everything working smoothly. The new Teams client is running, but the Add-in is not running in the user account. There is no Teams Outlook Add-in under %LocalAppData%.
I unpacked the MSIX Teams file with 7-Zip, where I found the Teams-Outlook-Addin MSI. I then installed the Add-in in a test user account (no admin privileges were needed). After that, I switched the registry key "LoadBehavior" under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect to 3. With this key, the Add-in runs in Outlook on startup.
Has anybody found a better way?
Link to comment
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now