Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Setting up a PsExec server

To use the Agent Installer to install agents on Microsoft Windows servers, you must first set up a PsExec server on a Windows server. A PsExec server functions as a proxy to execute psexec requests on agentless Windows hosts during agent installation.

To set up a PsExec server

  1. Using a Windows host, install an RSCD agent, version 8.2 or later.
  2. Using the BMC Server Automation Console, add the server to the Servers folder.
  3. Ensure that the agent is running and that you can browse the contents of the server.
  4. Download PsExec.
    You can download PsExec from http://technet.microsoft.com/en-us/sysinternals/bb897553.
    PsExec must be version 1.98 or later.
  5. Install PsExec according to the instructions from Microsoft. 
    PsExec must be installed in a directory that is specified in the %SystemRoot% environment variable (typically C:\Windows).

    To complete the PsExec server installation, run the server at least once and accept the EULA.
  6. If you are installing agents on Windows servers using a domain account, the account must be granted the Windows Logon as a batch job privilege on the PsExec server.  
    1. When an Agent Installer Job runs, the Application Server must access the PsExec server. 
      To accomplish this, the Application Server uses the account information defined in an automation principal that the remote host authentication specifies. 
      If the account information is a domain account, the account must be granted the Windows Logon as a batch job privilege on the PsExec server.
      For more information about defining automation principals, see Creating automation principals
    2. To access the Logon as a batch job setting, use the Control Panel on the PsExec server and go to Administrative Tools > Local Security Policy > Local Policies > 
      User Rights Assignment.
  7. To confirm that the PsExec server is functioning correctly, update the status of a remote host authentication that is based on the PsExec protocol. See Specifying or modifying information for remote host authentication.

Was this page helpful? Yes No Submitting... Thank you


  1. Andrew Hull

    It should be noted that version 2.2 of psexec DOES NOT WORK, because switches were removed or changed. Only versions between 1.98 and 2.11 work correctly.

    Jul 15, 2016 12:00
    1. Moiz Nalwalla

      Hi Andrew,

      The QA tested it on our systems and did not encounter any problems with this version.

      Can you shed some light on what use case you are using PsExec 2.2, and what is the exact issue you encounter, so that we can investigate further?

      Jul 28, 2016 09:02