Bryce,
Sorry, I'm a bit slow on the uptake. Mistake #1 was not realizing that PTREE needed to be installed on clients. Must admit, didn't test your implementation of TLIST on my DC. Then Shawn's post of testing where KIX32.EXE is run from threw me. It matters not where it runs from but rather that it's a child of the logon process.

Since I'm not a programmer, I could be way off base, but what about MSMQ?

quote:

MSMQ Triggers
Server-only: This tool is included in the Windows 2000 Server Resource Kit only.


--------------------------------------------------------------------------------

MSMQ Triggers is Message Queuing application that allows you to associate incoming messages in a queue with functionality in a COM component or standalone .exe. As such, business rules can be invoked in response to such messages without any additional programming.

MSMQ Triggers works with Message Queuing for Microsoft® Windows® 2000 and MSMQ 1.0 for Microsoft® Windows NT® version 4.0.

MSMQ Triggers Concepts
Triggers are associated with specific queues on a computer and are invoked every time a Message Queuing message arrives at such queues. A trigger is comprised of one or more rules. These rules are defined by actions that will be invoked when all conditions associated with a rule are true.

A trigger is an automatic action taken in response to a message event. In the context of MSMQ Triggers, an event is defined as one or more conditions being satisfied with respect to a message arriving at a queue. The collection of all triggers on a particular computer is called the trigger set.

A condition is a test that is applied when a message arrives at a monitored queue. The condition can test for a property of a message only. A condition is always paired with an action.

An action is an executable behavior that is taken when a condition is true. An action can be expressed as an executable and argument list; or, a COM component, method, and argument list. Arguments are also called parameters.

A rule is an action-condition pair. A rule describes an action that will be taken when a specific condition is true. The collection of all rules (for all triggers) on a particular computer is called the rule set. A default rule handler, IMSMQRuleHandler, is used to test the condition and implement the action for a rule. This is the only supported rule handler.

An action is an executable behavior that is taken when a condition is true. An action can be expressed as an executable and argument list; or, a COM component, method, and argument list. Arguments are also called parameters.

A rule is an action-condition pair. A rule describes an action that will be taken when a specific condition is true. The collection of all rules (for all triggers) on a particular computer is called the rule set. A default rule handler, IMSMQRuleHandler, is used to test the condition and implement the action for a rule. This is the only supported rule handler.

The MSMQ Triggers Service reads messages from a monitored queue, that is, the service looks at such messages. Messages are not removed from queues by this service. It should be noted that another Message Queuing application may open the queue and remove messages before the MSMQ Triggers Service can looks at the queue.



The downside I see with WAITFOR is the inability to pass anything but the sending computer name (and trigger name). If there's a way to send more with MSMQ, it would cut down on back-and-forth chatter and the need to pass info through a file.

One question on RCMD. Can it be pushed from the server?

_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.