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:
<host>statics.teams.cdn.office.net</host>
The certificate used in Bastion.xml needs to have this extra host in SAN (If you are using AGAT certificate, then use Teams8.pfx)
*.teams.cdn.office.net
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:
"statics.teams.cdn.office.net"
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
Search for “Apps & Features” in Windows search bar
Click on “Advanced Options” in Microsoft Teams (work or school)
Scroll down and click on Reset
Sign in to Microsoft Teams to get scripts injections from AGAT CDN
User Notifications: The original SphereShield pop-up is not yet supported in Microsoft Teams v-2. If you need user notifications you can setup IM notifications:
For Ethical Wall: If you need incoming block notifications to users who violates EW, configure Maintenance Service send IM to users who violate the rules.
For Ethical Wall on prem: Data Collaboration and Present Desktop were merged to Data Collaboration
Run this query on database: update [FEDERATION_POLICIES] set ALLOW_DATA_COLLABORATION = ALLOW_DESKTOP_SHARING