[RESOLVED] tis-microsoft-teams

WAPT user CN · April 17, 2020 - 12:42

Hello,

I need to install Teams on several PCs for all users who will be logging in. I downloaded your package (thank you!), updated the MSI, and uploaded everything to my server. The package installed on one machine without any errors. So far, so good.

However, the installation doesn't start when users log in. The installer (teams.exe) is located in "C:\Program Files (x86)\Teams Installer" along with a setup.json file that contains only this:

{"noAutoStart":false}.

The registry does contain HKLM\Software\Microsoft\Windows\CurrentVersion\Run\Teams with the value:

"%ProgramFiles%\Teams Installer\Teams.exe --checkInstall --source=[SOURCE]".

However, I have Windows 10 64-bit, and therefore %ProgramFiles% corresponds to "C:\Program Files".

Is it normal that it installed teams.exe in the x86 directory?

Thank you

, Mathieu

WAPT user CN · April 17, 2020 - 12:50

I forgot to mention:

1/ Teams deployed on a 64-bit Windows 10 machine;
2/ Server running Debian 9.12;
3/ Console also running on a 64-bit Windows 10 machine.

April 20, 2020 - 1:46 PM

Actually, the directory where the teams.exe binary is stored isn't very important (Program Files or Program Files (x86)), but the environment variable must point to the correct one! The WAPT agent runs in 32-bit (to have the same agent on x86 and x86_64), so the program files variable will always point to c:\program files (x86). The setuphelpers have several functions for this: programfiles (which depends on the binary that calls it), programfiles64, and programfiles32, to specify in a more deterministic way which directory to point to. It's very likely there's an error at this point in the script.

Regards,

Denis

knpc · July 2, 2020 - 5:52 PM

Hello,

did you find out what was causing your problem because I have exactly the same issue?

Thanks

, Knpc

alex_30 · July 9, 2020 - 9:42 AM

Hello,

I'm having the same issue. I downloaded the tis-microsoft-teams 1.3.0.13565-20 x64 package from the WAPT Store,
but it won't install on my Windows 7 x64 machine.
Does anyone have a solution?

WAPT version: 1.7.4
Server OS: Windows Server 2019 Standard
Administration machine OS: Windows 7 x64

jpele · July 10, 2020 - 6:19 PM

Hello,

I've updated the Teams package. It now installs in the system environment and cleanly uninstalls any version installed in the user environment. There shouldn't be any more problems.

Regards,
Jimmy

alex_30 · July 21, 2020 - 4:02 PM

Hello,

thank you, I will test it and give you feedback.
However, I have another question beforehand.
From what I understand, the package was created for a virtualized environment, but in my case, it's a physical machine, so I just need to comment out the 3 lines:
registry_set(HKEY_LOCAL_MACHINE,r'SOFTWARE\VMware, Inc.\VMware VDM\Agent','','')
registry_set(HKEY_LOCAL_MACHINE,r'SOFTWARE\Citrix\PortICA','','')
registry_set(HKEY_LOCAL_MACHINE,r'SOFTWARE\Microsoft\Teams','IsWVDEnvironment',1,type=REG_DWORD)

Is that correct?

jpele · July 22, 2020 - 10:57

Hello,

it's actually the opposite. If you're in a "WVD/VDI" environment, it's best not to manipulate these registry keys. They're added because they're required to allow installation in a system environment on a "non-VDI" machine.

Therefore, I suggest you refrain from commenting.

Sincerely,
Jimmy

alex_30 · July 22, 2020 - 3:19 PM

Thank you for your feedback, I will test it and keep you updated

alex_30 · July 31, 2020 - 11:10

Hello,

sorry for the slightly late reply.
I was able to deploy the package on a Windows 7 32-bit machine.
The installation worked, however, every time Teams starts, a security pop-up appears: [
attachment=0]teams_32_pop_up_secu.png[/attachment]

I think this is related to the fact that our users are not administrators of their machines.