COM from a process server starts multiple instances

How to make the local COM server work under a common account (the local system will be good)? The RunAs documentation seems to be unique to DCOM and does not work locally.

The problem I am facing is that my CoCreateInstance is called from processes running on different desktop computers, and SCM in this scenario wants to start a new server for each desktop, I only need one instanse - how it was designed!

+5
source share
1 answer

What you are describing is a system service, not a COM server. The COM server is designed to work under any session, and not under "session 0" (services) or with any session. If you need something that works only under 1 session and has global access to everything else, you should use the Windows service, not the COM server.

If you need an aspect of the COM server for another reason, but you want to share resources around the world or still have a “one process” that controls everything you need ... you can link your COM server to your service, using any IPC method you prefer.

, " " - EXE , , COM- , EXE/app, , , , , . EXE COM- EXE OLE/COM, EXE . , Microsoft Word Outlook COM-. outlook.exe COM-, , , .

0

All Articles