So now I've got another customer who is not quite willing to do this.
They can create the account, but the workstation running our application
must log on using a standard user account. They want our software
to "impersonate" the service account (assuming of course, that we have
the password for it). Our software actually gets spawned by a
master scheduling facility, so my thought was that I would do this by
using the API CreateProcessWithLogonW(). This call works, in that
it accepts the service account credentials and runs the MAPI app,
but then the MAPI code fails, with OpenMsgStore() returning
MAPI_E_UNCONFIGURED. (When logged in using the serivce account, the
same code works fine).
Would I need to use LogonUser() and/or ImpersonateLoggedOnUser() to
accomplish what I need? I would think this basically does the same
thing that CreateProcessWithLogonW() does.
--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
-
"Jeff McKay" <jeff....@comaxis.com> wrote in message
news:_bCdnZ-Wrsw1oonW...@supernews.com...
"Dmitry Streblechenko" <dmi...@dimastr.com> wrote in message
news:ea9S$ticKH...@TK2MSFTNGP04.phx.gbl...
--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
-
"Jeff McKay" <jeff....@comaxis.com> wrote in message
news:hdSdnWjnduoMAYnW...@supernews.com...