PC Review Forums Newsgroups Microsoft Outlook Microsoft Outlook VBA Programming Trusted Application?

Reply

Trusted Application?

 
Thread Tools Rate Thread
Old 26-04-2004, 01:37 PM   #1
Neil Dittmar
Guest
 
Posts: n/a
Default Trusted Application?


Hello all,

I am coding an application in Visual Basic 6 that
will interact with certain items in Outlook 2003,
including contacts. I am aware that some of these
interactions will trigger a security dialog when
attempting to access. Is there a way for Outlook 2003
to "trust" an application (like a COM Add-In) on the
client side so that it does not produce security prompts?
It's also important to note that we are running in an
Exchange Server 2003 environment. Any help or suggestions
would be greatly appreciated.

Thanks,

Neil Dittmar
Software Developer
Aurora Information Systems
  Reply With Quote
Old 26-04-2004, 02:05 PM   #2
Sue Mosher [MVP-Outlook]
Guest
 
Posts: n/a
Default Re: Trusted Application?

Outlook 2003 trusts all properly constructed Outlook COM add-ins by default
*unless* you have also implemented the Outlook Security Settings folder on
the Exchange server by setting the client registry entry appropriately. If
that's the case, then the administrator will need to trust the COM add-in as
part of the settings on a security setting item. See
http://www.slipstick.com/outlook/esecup/admin.htm and
http://www.outlookcode.com/d/sec.htm

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"Neil Dittmar" <anonymous@discussions.microsoft.com> wrote in message
news:440301c42b8b$4e30b540$a301280a@phx.gbl...
> Hello all,
>
> I am coding an application in Visual Basic 6 that
> will interact with certain items in Outlook 2003,
> including contacts. I am aware that some of these
> interactions will trigger a security dialog when
> attempting to access. Is there a way for Outlook 2003
> to "trust" an application (like a COM Add-In) on the
> client side so that it does not produce security prompts?
> It's also important to note that we are running in an
> Exchange Server 2003 environment. Any help or suggestions
> would be greatly appreciated.



  Reply With Quote
Reply



Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off