[SOLVED] Package tis-microsoft-teams
Published: September 1, 2020 - 12:24 PM
Good morning,
Several topics have already been posted on this forum regarding the package tis-microsoft-teams suggested in the repository. I preferred to create a new topic to discuss several questions I have.
1) In this package, Microsoft Teams is installed using the MSI file and the argument ALLUSER=1 (without the "S").
This argument is used only in VDI environments.
Therefore, in order to install Teams on a classic (non-VDI) environment, keys (VMware, Citrix) are added to the registry and trick the installer into thinking it is on a VDI environment.
Why was this approach preferred rather than using the MSI with the arguments (OPTIONS="noAutoStart=true" ALLUSERS=1) which work in both VDI and non-VDI environments?
This would also avoid file manipulation setup.json to disable Teams from automatically starting when logging in.
2) In the current package, I may have missed something, but could there be a problem with the function session_setup().
The current version of Teams is retrieved into a variable (user_app_version) from the registry but does not appear to be used subsequently. A condition would be missing:
THANKS,
Sincerely.
Several topics have already been posted on this forum regarding the package tis-microsoft-teams suggested in the repository. I preferred to create a new topic to discuss several questions I have.
1) In this package, Microsoft Teams is installed using the MSI file and the argument ALLUSER=1 (without the "S").
This argument is used only in VDI environments.
Therefore, in order to install Teams on a classic (non-VDI) environment, keys (VMware, Citrix) are added to the registry and trick the installer into thinking it is on a VDI environment.
Why was this approach preferred rather than using the MSI with the arguments (OPTIONS="noAutoStart=true" ALLUSERS=1) which work in both VDI and non-VDI environments?
This would also avoid file manipulation setup.json to disable Teams from automatically starting when logging in.
2) In the current package, I may have missed something, but could there be a problem with the function session_setup().
The current version of Teams is retrieved into a variable (user_app_version) from the registry but does not appear to be used subsequently. A condition would be missing:
Code: Select all
if Version(user_app_version) < Version(package_version):
# Killing app before making changes
killalltasks('Teams.exe')
...
Sincerely.