Did you find a solution for this problem???
With kind regards
I'm having the same problem, via app volumes I can not capture microsoft teamm, I got a microsoft msi to mass install and put in the parent image. When you start the virtual desktops it installs microsoft teams but gets a white screen. Follow the teams logs Were you able to solve it?Thanks,Ricardo lins
Our solution for deploying Teams is to package it with Thinapp and delivery it in an appstack. So far its been solid for the last 3 months.
Here is a guide on using thinapps with app volumes.
Could you post the recipe for it? Teams has two installers and both are reportedly pretty unreliable.
Can you explain how you are capturing Teams with Thinapp? We are having a tough time getting the ThinApp to capture without .dll errors thrown.
Anyone had progress with this?
The one thing I had to do to get it to work is to black list the executables (ex. teams.exe) from directflex. It was crashing with the .dll problem until I did that.
See this article on blacklist.xml configuration.
When creating the package, don't use the .msi installer. You need to use the .exe installer that installs the app to the users appdata.
Hmmm.. Teams, interesting subject..
We needed to package this as well for our users and the very very short story is it won't work with Appvolumes Appstacks due to the simple fact that Appstacks do NOT hold user Appdata information. Apparently the application is being installing into the %APPDATA%\Local\Microsoft\Teams even if you distribute using SCCM or any other tool
The half ass witted solution provided by M$ is to copy the installer file into the Program Files directory and let it be installed during logon (see Install Microsoft Teams using MSI via SCCM | Microsoft Docs ). I'm not quite sure which clown at Microsoft came up with this solution be should be fired on the spot!!
Long story short. The only way to get this to work in VDI is by either using the web version or use the writable with profile in it because the UIA only will not capture the profile folders.
If you install it during logon you will end up with a very high CPU usage during every logon from a user..
And oh yeah, the updater is located within the installer which means you don;t have any control on what version of Teams a user is using.. If the application fails the only thing that you can do is remove the writable altogether...
Good move Microsoft.. Those MacBooks are getting more interesting by the day...
After this full rant.. It does seem that Teams works with Appvolumes 2.15, my guess is that the HookInjectionWhitelist setting does haev soemthing to do with that as teams.exe is one of the items ion that list.