I've successfully established Remote connections to our servers
using 24x7RemoteControl COM objects, however I was depending on
the ConnectedToRemote property of the 24x7RemoteControlCOM object
before closing the session.

I'm reading no values for this property, so my CloseSession calls
were never executed. Does this leave sessions open? Though I have
been setting my COM object to NOTHING before exiting my application.

In other words, do I leave orphaned open sessions if I don't call the CloseSession
method, even if I set my 24x7 COM object to Nothing?

Thanks!

P.S.

I've tested the 24x7COM Object itself, and that appears to be
the correct boolean value for whether there is a connection or not.

: I've successfully established Remote connections to our servers
: using 24x7RemoteControl COM objects, however I was depending on
: the ConnectedToRemote property of the 24x7RemoteControlCOM object
: before closing the session.

: I'm reading no values for this property, so my CloseSession calls
: were never executed. Does this leave sessions open? Though I have
: been setting my COM object to NOTHING before exiting my application.

: In other words, do I leave orphaned open sessions if I don't call the
: CloseSession
: method, even if I set my 24x7 COM object to Nothing?

: Thanks!

The com object should automatically close session when it is being destroyed (set to nothing). You can easily check it if you enable the tracing feature on the client. I nthe trace you can then see messages like the following

DPB02 Connection(07FA07C0): DisconnectServer: ... (00000000)
DPB02 Connection(07FA07C0): DisconnectServer: SUCCEEDED (00000000)
DPB45 SessionId (00FD47B0): Release Object: instanceId(00000088)

: P.S.

: I've tested the 24x7COM Object itself, and that appears to be
: the correct boolean value for whether there is a connection or not.