For one of our core application that was running on windows server 2003, we have decided to move the same to windows server 2008 R2 enterprise. Our application extensively uses Com, com+ and dcom architecture.
Issue
One of the DCOM object(abc.exe) running on server(w2008R2 enterprise) is initiated by Client. The client can be either windows xp or windows server 2003. The abc.exe is registered in win2008R2 enterprise server with below set of properties
a) Identity - Interactive User
b) Remote Access - Allowed to all users
When the server(Windows server 2008 R2 enterprise) is in connected mode i.e when we connect to server using remote desktop services, and if we initiate abc.exe from client machine then it is successfully get invoked.
However, if the server(windows server 2008R2 enterprise) is in disconnected mode i.e. when the terminal services session is disconnected, and if we initiate same abc.exe from client machine then we are getting 'can't get requested object' error in client machine.
What i believe is there is some setting which is stopping the object to be initiated when the server is in disconnected mode.
Can someone help me out and tell what can be the possible setting related to Remote Terminal server that is stopping for the component to be initiated while it is in disconnected mode?
Any help is much appreciated.
Thanks,
Sunny