Running Remote Automation Using AUTOCLIK and AUTODRIV
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
The latest version of this topic can be found at Running Remote Automation Using AUTOCLIK and AUTODRIV.
AUTOCLIK is a simple Automation server sample application that you can use as a base from which to learn more about Remote Automation. AUTODRIV is a simple Automation client application that drives AUTOCLIK. You can use them to demonstrate Remote Automation.
To install AUTOCLIK.EXE on two machines and drive it using Remote Automation
Install the AUTOCLIK sample application onto your development machine.
Build AUTOCLIK.EXE.
Run AUTOCLIK.EXE in standalone fashion and then shut it down. This will register it as an Automation server.
Copy AUTOCLIK.EXE to a remote machine, run it there, and then shut it down.
Run AUTODRIV.EXE on the local machine and verify that running it starts AUTOCLIK.EXE. To find out more about AUTODRIV.EXE, see AUTOCLIK.
On the remote machine, start AUTMGR32.EXE (Automation Manager).
On the remote machine, start RACMGR32.EXE (Remote Automation Connection Manager).
In the Remote Automation Connection Manager, select AutoClik.Document from the OLE Classes list.
Choose a system security policy from the Client Access tab to grant client access to AutoClik.Document.
On the local machine, start RACMGR32.EXE and select AutoClik.Document from the OLE Classes list.
From the Server Connection tab, choose both the network address of the remote machine and the appropriate network protocol.
With AutoClik.Document still selected in the OLE Classes list box, choose the Remote command from the
Registermenu.On the local machine, run AUTODRIV.EXE or the equivalent AUTOCLIK.MAK Visual Basic project if you want to have a Visual Basic, rather than an MFC, client.
On the remote machine, you should now be able to see AUTOCLIK executing commands initiated from the local client.