Iphone

We use Outlook as part of Office 2003 running around Exchange 2003 with roughly 90 mailboxes.

We recently invested in an application which has been deployed via group policy to around 80 users which access Outlook to send emails to clients.

However during this process we get the usual 'A program is trying to access...' warning, the user then has to click 'Allow' and 'Yes which when trying to mail 40+ clients can be quite frustrating.

I have seen several applications which basically answer yes but do not want to deploy such an app to 80 users.

Is there a way of disabling this warning via group policy or exchange system manager?

Iphone

I can't answer the question definitively. I've read several Microsoft pages that describe/document the security template. Some of them seem to be saying that the template does control whether an external application (i.e. not an add-in, form code, or VBA procedure, all of which run from inside Outlook) can execute restricted commands/procedures without causing the security dialog to pop up. Others, like the one I cited a couple of posts back appear to be saying that the security template only governs code running inside Outlook and that external programs are always subject to the security restriction. I cannot find any source that clearly states whether the template applies to external code. In the absence of a clear statement one way or the other, we are left to make an educated guess. If the template does in fact allow external external code to run free of any security constraint, then that is the equivilent of Microsoft never having applied any security to Outlook at all. We'd be back where we were before the security patch was issued for Outlook 2000. Any code, malicious or otherwise, would have free reign to access and send mail without any knowledge of the user at the computer. The very reason that Microsoft introduced the security patch to begin with. In my opinion, it doesn't seem likely that Microsoft would go to all the effort knowing that the pop-up security dialog would annoy everyone and they'd probably just apply the template and turn all security off. Then I look around at products like Click-Yes and Outlook Redemption. Both were written specifically to get around the security Microsoft had introduced with the security patch for Outlook 2000 and then made integral to the product in 2002 and beyond. Necessity being the mother of invention, why would the authors of these programs take the time to create them if the security template could simply allow all code to run unfettered? Of course they could have been targeting the non-Exchange Outlook users, and Redemption could have been created to give individual programs the ability to circumvent security without having to remove it altogether.

Although the security template applies to Outlook, it is really more of an Exchange issue and I freely admit that Exchange isn't my strong suit. I've never had the opportunity to test it and therefore cannot say whether it will solve your problem or not. Assuming that it does, then please keep in mind that it appears as if it would be removing all security constraints, allowing any external code to access and send on your behalf, not just that one program.