Unless there is a business mandate to allow it for wanted tracking purposes, I would leave it as is. I also wouldn't enforce it, unless its a recurring issue that increases your support costs.
Some people just like to complain about every little thing that doesn't work exactly how they expect it to - as if life is to be perfect for them. Those people are best to be ignored, until they become a problem that effects your own performance metrics. -- Espi On Tue, Oct 28, 2014 at 7:27 AM, Kennedy, Jim <[email protected]> wrote: > So in Exchange 2010 OWA web beaconing is blocked by default with a user > choice. Just had a user complain about that......my gut reaction is to leave > it > as is. Let them decide, but reality is they probably always just click on > allow anyway. > > > > How does the collective handle this in OWA? Looking for opinions. >
