What user rights are required to run RemoteExec?
To remotely run a program, the Windows NT user account needs to have full administrative rights on both computers except if the same Windows NT user is logged on on the two computers.

Do I need to install an agent on the remote computers?
No. No remote user agents are required in order to use RemoteExec.

Does RemoteExec work with remote Windows 9x computers?
No, RemoteExec does not work on Windows 9x system.

Are protocols other than TCP/IP supported?
Yes, RemoteExec can work on all protocols supported by DCOM including NetBeui, NWLink?

What are the required conditions to execute remotely a task on a computer?
    1. The registry of this computer should be accessible remotely from your administration console (using regedit or regedt32).
    2. The administrative share \\ComputerName\admin$ should be accessible from your administration console.

If that's not the case, you should check the following points:
    1. Have you the administrative rights on the remote computer?
    2. Is the service server running on the remote computer?
    3. Is the administrative share on the remote computer Windows NT directory (ADMIN$) enabled?
    4. Can you resolve the name of the remote computer from your administration console? (Check this with the command line "ping computername".)
If not, you have a WINS or a DNS problem.

RemoteExec returns the status: "Failed to initialize" and the error message: "Network path not found".
If you have routers between the two computers, ensure that the RPC protocol is correctly routed.

How can I execute a program on a remote computer located in a workgroup or in a foreign domain?
You need to create the same administrator account (login and password) on the remote computer and on the local computer and execute RemoteExec locally under this account.