"Billy Bob" <wh*@microsoft.comwrote in message
news:er****************@TK2MSFTNGP03.phx.gbl...
Hi
I tried that and it does start the process, but there is one problem with it. I've
downloaded this code from MSDN and it works
....http://msdn2.microsoft.com/en-us/lib...97(VS.71).aspx but wanting to start the
Asyncremoteclient.exe on the remote machine, so I tried that via the WMI script but for
some reason, even though the app starts and appears in taskman it never communicates with
the server.exe unless I manually go to the remote client pc and type in
remoteasyncclient.exe myself.
Do network apps not start via a remote process?
What you are trying does not work in general on Windows. The remote process runs in a
restricted security context, it does not run in the context of an interactive logon account
(if any), it runs in the security context of the remote WMI service and by default it's
impersonating the initiator (the WMI client). What does it mean to the application that was
started? First, this application has no way to interact with the user, even when it's a
console application, the output will go to a non visible desktop and there is no way to read
from the keyboard. Second, the "environment" is the one inherited from the Service that
launched the program, that means that variables like the home directory and current working
directory are not what you might expect, the profile loaded is not a user profile but a
service profile, so applications who expect this profile to be loaded will fail miserably.
Or otherwise stated, what you are trying is a no no in Windows, all you can do is use Remote
Destop or Terminal Services to start a remote interactive session and launch your
application from the command windows.
Willy.