Hi there...
I have developed a COM+ DLL (VB.NET) which I have registered via Component Services to perform some functions under the Local System Account.
I want to call the methods on my COM+ dll and use them to launch processes, elevating the interactive users rights.
I have finished the code for all of this, however when I debug/launch my application, .NET seems not to use the DLL in COM+ (I have run FileMon on it) and doesn't run the processs as System, rather under my credentials.
If I perform a similar function in VBScript, the process is launched under the system account.
This will launch cmd shell under my credentials.
Can anyone explain why?
thanks in adv...
I have developed a COM+ DLL (VB.NET) which I have registered via Component Services to perform some functions under the Local System Account.
I want to call the methods on my COM+ dll and use them to launch processes, elevating the interactive users rights.
I have finished the code for all of this, however when I debug/launch my application, .NET seems not to use the DLL in COM+ (I have run FileMon on it) and doesn't run the processs as System, rather under my credentials.
If I perform a similar function in VBScript, the process is launched under the system account.
Code:
VBSCRIPT:
Set obj = CreateObject("Object.Interface")
obj.InvokeProcess(cmd, "")
[code]
this will launch a cmdshell under the system account.
[code]
VB.NET
'Added Reference to myDLL.DLL
IMPORTS myCOM = myDLL
dim obj as object = new myCom.Interface
obj.InvokeProcess(cmd, "")
Can anyone explain why?
thanks in adv...