Terminal Services and Automation Servers

[Steve Hunt]

I have my own automation server (ActiveX EXE) created in
VB6 which I would like to run on the console session. I
would like to access this single ActiveX Server from
client apps running on both the console and thin client
sessions. However, although this works ok with console
apps, everytime I run a thin client app a new instance of
the ActiveX Server is created locally on the thin client
session!

How can I therefore access the ActiveX server running on
the console session from a thin client app via the COM
interface?

Many thanks

 

[Ivan Leichtling [MSFT]]

Steve -

You need to explore COM activation and launch security. Your COM app
has to be registered on the server is such a way that all users in all
sessions always get the same single instance of your interface.

I have my own automation server (ActiveX EXE) created in
VB6 which I would like to run on the console session. I
would like to access this single ActiveX Server from
client apps running on both the console and thin client
sessions. However, although this works ok with console
apps, everytime I run a thin client app a new instance of
the ActiveX Server is created locally on the thin client
session!

How can I therefore access the ActiveX server running on
the console session from a thin client app via the COM
interface?

Many thanks

This posting is provided "AS IS" with no warranties, and confers no rights