Prev: Terminal Server did not install successfully
Next: Windows Terminal Server Desktop Enumeration
From: Serge Podbyj on 15 Dec 2008 09:29
Hello,

I am using Session-to-Session Activation with a Session Moniker as described
in the MSDN article
(http://msdn.microsoft.com/en-us/library/aa383539(VS.85).aspx). The moniker
string is "Session:Console!clsid:[class id]" or
"Session:[digits]!clsid:[class id]" but the COM-server always activates in
the session 0 (which is not a console session or the session specified in the
moniker string). On Windows 2003 the same code works fine.

Any ideas?
From: Serge Podbyj on 16 Dec 2008 06:28
I have researched a little bit further.

The issue is not related to Vista (sorry). Session-to-Session Activation
always starts a COM-server in the session 0 if I select in DCOMCNFG to run a
COM-server as a specific user. If I select in DCOMCNFG to run a COM-server as
an interactive user Session-to-Session Activation works but I cannot access
the console session if no user logged in. How to do that? I need a COM-server
to be started always in the console session.
 | 
Pages: 1
Prev: Terminal Server did not install successfully
Next: Windows Terminal Server Desktop Enumeration