admpack

  • Thread starter Thread starter J.P.
  • Start date Start date
J

J.P.

Is there any way at all to use the OutlookSecurity.oft form in Outlook
without exchange server? We do no use exchange server and we aren't
going to (and I expect many others feel the same way) which makes me
wonder why on earth you can't customize the object model guard in
Outlook XP without it. There has to be some way to work with Outlook
other than a 3rd party extended mapi wrapper, coding around extended
mapi ourselves, and an 'automagic click make dialog disapear'
background process on the workstations. We have some very simple
macro's to run through the rules wizzard on certain employees clients
and it's turned into a nightmare. If anyone can provide some useful
information that doesn't require us implementing exchange server or
depending on 3rd party products that we don't already use I would
greatly appreciate it!

Thanks in advance,
J.P.
 
Sorry, but you will have a very long wait for an answer based on your
criteria.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, J.P. asked:

| Is there any way at all to use the OutlookSecurity.oft form in Outlook
| without exchange server? We do no use exchange server and we aren't
| going to (and I expect many others feel the same way) which makes me
| wonder why on earth you can't customize the object model guard in
| Outlook XP without it. There has to be some way to work with Outlook
| other than a 3rd party extended mapi wrapper, coding around extended
| mapi ourselves, and an 'automagic click make dialog disapear'
| background process on the workstations. We have some very simple
| macro's to run through the rules wizzard on certain employees clients
| and it's turned into a nightmare. If anyone can provide some useful
| information that doesn't require us implementing exchange server or
| depending on 3rd party products that we don't already use I would
| greatly appreciate it!
|
| Thanks in advance,
| J.P.
 
Is there any way to allow macro's that are executed by the rules
wizzard to execute without the dialog box that allows access for a
maximum of 10 minutes?

Solutions I have already reviewed:
- 3rd party wrappers around extended mapi
- Write an add-in ourselves using extended mapi
- Use exchange server and a security policy
- ClickYes application mentioned in many similar posts about this issue

What I would like to do is to be able to use the security policy stuff
that comes with admpack without exchange server. We do not run exchange
server and we have no intentions to run it. If that is not possible,
I'm wondering if there is any other possible way to get around the "...
accessing adress book ..." dialog box that pops up when our macros
execute other than writing something in C++ around extended mapi, using
a 3rd party extended mapi wrapper (Redemption) or a hack solution like
ClickYes.

I'm sorry for knocking all the common solutions but they aren't
acceptable just to make use of some 15 line macro's that cause the
security dialog to appear. If there is any other way I would greatly
appreciate some information about it.

J.P.
 
Is there any way at all to use the OutlookSecurity.oft form in Outlook
without exchange server?
No.

There has to be some way to work with Outlook
other than a 3rd party extended mapi wrapper, coding around extended
mapi ourselves, and an 'automagic click make dialog disapear'
background process on the workstations.
Click to expand...

There once was a way, and viruses took advantage of it to the extent that entire mail systems were brought to their knees. Perhaps you don't remember the spring of 1999.
I'm sorry for knocking all the common solutions but they aren't
acceptable just to make use of some 15 line macro's that cause the
security dialog to appear. If there is any other way I would greatly
appreciate some information about it.
Click to expand...

Outlook VBA macros? Then your other solution is to upgrade to Outlook 2003, which "trusts" the Outlook object model for VBA use without triggering security prompts for objects derived from the intrinsic Application model in VBA.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Back
Top