By default, Web beacons and HTML forms are set to “UserFilterChoice”, which means that they are blocked, but the user can unblock them if needed.
If you are a strict administrator or your company policies force you to block the beacons, you can do so with exchange shell.
The parameter which defines the behaviour is “FilterWebBeaconsAndHtmlForms” and we have three values.
- UserFilterChoice – Blocks, but user can unblock
- ForceFilter – Blocks all.
- DisableFilter – Allows all.
In order to block beacons forcefully and not give the end user the option to unblock, run the following cmdlet,
Set-OWAVirtualDirectory –identity “OWA (Default Web Site)” –FilterWebBeaconsAndHtmlForms ForceFilter
No comments:
Post a Comment