User Profile
kmass-llc
Copper Contributor
Joined Apr 06, 2021
User Widgets
Recent Discussions
- 24KViews0likes0Comments
Re: Teams Version history
I have the same question. Without the version history, we are spinning our wheels trying to maintain Teams in a WVD environment. Here is why: - According to https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#install-or-update-the-teams-desktop-app-on-vdi, Teams cannot self-update in a WVD environment, we have to uninstall the old one and install the new one. - The https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm doesn't tell you the version number, and always has the same file name. So you have to conduct your own version control to be able to uninstall the old one (because the uninstaller expects the MSI file to have the same name and path as when it was installed) and to reinstall the new one that you intend. The versions I downloaded in February, March, and April all have different file sizes and modified dates in the file details, but when installed all claim to be version 1.4.00.2781. So I don't know if I should have just kept the January version. - Even with careful version control, uninstall and resinstall can fail on some WVD hosts, even using the https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d. These factors together create a situation that is both a time waster and a security issue, the latter because it drives my customers to use Teams on personal systems instead of the company system that is more secure, but might or might not have Teams installed on it.37KViews0likes4Comments
Recent Blog Articles
No content to show