====Running Drivers on Remote Systems====

Although it is not the recommended usage pattern, ARDI can run //remote drivers//. These are drivers that run on systems other than the ARDI server itself.

These are most often used when...

   * Your server is congested and is using too much network bandwidth or CPU.
   * You are running a Linux-based ARDI server and need to communicate to a system that only has a Windows-based driver.

A Linux version of the toolkit has not yet been made available, as most use cases have involved Windows servers.

===Installation Steps===

==Step 1: Install the Remote I/O Tools==

On a Windows system (this can be any standard OS - you do not require a Server edition), you will need to install the remote I/O tools. This installs the driver management framework (as well as dependencies, like Python and the ARDI driver toolkits). 

==Step 2: Install the Drivers==

You'll need to install the individual drivers you want to communicate with.

==Step 3: Add the Drivers to ARDI==

Next, you'll need to add new drivers to ARDI. Remember to include the //host name// in the driver configuration - this tells ARDI that the driver is located on a different host.