The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Creating remote runspaces


Windows PowerShell commands that take a ComputerName parameter can be run on any computer that runs Windows PowerShell. To run commands that do not take a ComputerName parameter, you can use WS-Management to configure a runspace that connects to a specified computer, and run commands on that computer.

To create a runspace that connects to a remote computer, you create a WSManConnectionInfo object. You specify the target endpoint for the connection by setting the ConnectionUri property of the object. You then create a runspace by calling the CreateRunspace method, specifying the WSManConnectionInfo object as the connectionInfo parameter.

The following example shows how to create a runspace that connects to a remote computer. In the example, RemoteComputerUri is used as a placeholder for the actual URI of a remote computer.

namespace Samples
  using System;
  using System.Collections.ObjectModel;
  using System.Management.Automation;            // Windows PowerShell namespace.
  using System.Management.Automation.Runspaces;  // Windows PowerShell namespace.

  /// <summary>
  /// This class contains the Main entry point for this host application.
  /// </summary>
  internal class RemoteRunspace02
    /// <summary>
    /// This sample shows how to create a remote runspace that 
    /// runs commands on the local computer.
    /// </summary>
    /// <param name="args">Parameter not used.</param>
    private static void Main(string[] args)
      // Create a WSManConnectionInfo object using the default constructor 
      // to connect to the "localHost". The WSManConnectionInfo object can 
      // also be used to specify connections to remote computers.
      WSManConnectionInfo connectionInfo = new WSManConnectionInfo();

      // Set the OperationTimeout property and OpenTimeout properties. 
      // The OperationTimeout property is used to tell Windows PowerShell 
      // how long to wait (in milliseconds) before timing out for an  
      // operation. The OpenTimeout property is used to tell Windows 
      // PowerShell how long to wait (in milliseconds) before timing out 
      // while establishing a remote connection.
      connectionInfo.OperationTimeout = 4 * 60 * 1000; // 4 minutes.
      connectionInfo.OpenTimeout = 1 * 60 * 1000; // 1 minute.

      // Create a remote runspace using the connection information.
      //using (Runspace remoteRunspace = RunspaceFactory.CreateRunspace())
      using (Runspace remoteRunspace = RunspaceFactory.CreateRunspace(connectionInfo))
        // Establish the connection by calling the Open() method to open the runspace. 
        // The OpenTimeout value set previously will be applied while establishing 
        // the connection. Establishing a remote connection involves sending and 
        // receiving some data, so the OperationTimeout will also play a role in this process.

        // Create a PowerShell object to run commands in the remote runspace.
        using (PowerShell powershell = PowerShell.Create())
          powershell.Runspace = remoteRunspace;

          Collection<PSObject> results = powershell.Invoke();

          Console.WriteLine("Process              HandleCount");

          // Display the results.
          foreach (PSObject result in results)
                              "{0,-20} {1}",

        // Close the connection. Call the Close() method to close the remote 
        // runspace. The Dispose() method (called by using primitive) will call 
        // the Close() method if it is not already called.