yea that is what this thread is about.

What i would really like to do is use some type of COM object to do a query from the server to the client to see if a kix generated request came from the logon script or not.

Ptree looks like it will fit the bill, but ptree has to be installed on the remote client in order to use it (not a big problem). The big problem with ptree is it will not work on a NT computer, and that is a show stopper.

So my current plan of attack is to use tlist.exe (see above) and squirt a kixscript to the remote computer via the rcmd service.

RCMD will have to installed very much like suss.exe... but this is not a problem.

The "squirted" script (logonscript_verification) will then verify the status of the request (logon script or not).

If the logonscript_verification process is ok, the server is notified that the X software install request is a valid request and to start the X software install via the RCMD.

Anything ran via the RCMD command would automatically inherit Admin rights.

hopefully... when the dust clears.... we will have a poor-man's SMS

a secure way to remote install software on a NT/Win2k workstation. With out the risk of using SU, username, and password hardcoded in a script.

Bryce