The problem is this only works if the user who originally installed Teams is currently logged in. Once everythign is removed, it re-runs the The script removes the Teams Machine-Wide Installer and then attempts to remove it again using the Execute-ProcessAsUser. To circumvent this issue, I scripted an installer with the PowerShell Application Toolkit. Basically all that's left in the directory is a folder called "current". Now Teams is being re-installed, and sometimes causing the files in %LocalAppData%\Microsoft\Teams to become unusable. But this has started to causeĪll kinds of problems. So we've changed our Deployment Type to System. But those issues have since been resolved. We originally deployed Teams Machine-Wide Installer from Configuration Manager as User because there were issues with the MSI early on. Does anyone know if the Teams Machine-Wide Installer is supposed to be deployed in the User or System context?
0 Comments
Leave a Reply. |