Microsoft Teams Client v2 - Requirements and changes

SphereShield Versions:

1- Bastion 2.0.9.0 and above

Copy the new bastion.exe and replace it with the old one, then in bastion.xml add the following host to the host’s list in the forward listener:

The certificate used in Bastion.xml needs to have this extra host in SAN (If you are using AGAT certificate, then use Teams8.pfx)

2- TeamsProtector 1.7.1.3 and above

Copy the new TeamsProtector.dll and replace it with the old one, we also need to copy the following new files TeamsProtector2.js and calling_electron_bundle.js and paste them into the same directory of the fw_proxy.

3- PAC file

Modify the PAC file and add the following line:

Configure the workstation to run with the proxy (PAC) and then install the new Teams client.

If new Teams was installed before AGAT proxy

If you already have the new Teams client on your desktop before having AGAT proxy configured, please do the following after configuring AGAT proxy:

Reset Teams

1. Search for “Apps & Features” in Windows search bar

Open

2. Click on “Advanced Options” in Microsoft Teams (work or school)

Open

3. Scroll down and click on Reset

4. Sign in to Microsoft Teams to get script injections from AGAT CDN