次の方法で共有

Session 0 isolation, COM and COM+

  • [アーティクル]

Session 0 isolation is not limited to NT services. It also applies to COM+ server applications and COM out-of-process applications running under anything else than the interactive user. So all problems related to services living in a different Terminal Server session from the first logged in user now also apply to dllhost processes (COM+ or surrogated COM dlls) and COM server applications.   

 

Maarten

Comments

  • Anonymous
    December 07, 2006
    Hi, I understand the reasons behind the Session 0 isolation issues and services - services interacting with the desktop without the appropriate priviledges causes issues. And the COM/COM+ out process issues makes sense as well. The question is; how can detect whether a COM object is going to be out of process? Can we just look for remote server names in the AppID string? And to resolve the issue can just set the Impersonation levels to Delegate? Any more information on this topic would be much appreciated. Note: I have already read the Services Guide for Vista cheers, g