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.

Installing an RSCD agent (Windows)


This topic provides instructions for installing an RSCD agent on a Microsoft Windows computer other than a replicated domain controller.

To install on replicated domain controllers, see Installing-RSCD-agents-in-a-replicated-domain-controller-environment.

You can perform either:

  • Typical installation — Uses default settings for the location of the RSCD agent installation folder and log files, security preferences, and logging.
  • Custom installation — Lets you change the default settings.

To perform a silent installation of an RSCD agent, see Using-silent-mode-to-install-an-RSCD-agent-Windows.

Note

The RSCD agent for Microsoft Windows requires that the Server service is running in order to function correctly.

Before you begin

  • For a server to provide information about Windows Group Policy objects, the file secedit.exe must be installed on the server, and it must be included in the server's executable path.
  • If the server is a domain member or domain controller, confirm that the Net Logon service is enabled and running before installing the RSCD agent. The agent uses the Net Logon service to determine the domain and obtain information about the machine. If the server is not part of a Windows domain, the agent uses a different method for determining machine information. Additionally, the automation principal feature uses the Net Logon service to access domain user information so the automation principal can act as a domain user.

    Note

    If you subsequently remove the agent computer from the domain, you must also remove the Net Logon dependency (via the registry) and restart the agent. Otherwise, the agent will not start.

  • The patch analysis function of BMC Server Automation requires the Microsoft XML (MSXML) parser version 6.0 SP2 or later to be installed on the server on which the RSCD agent is installed. You can install the RSCD agent on a computer on which MSXML is not installed, but patch analysis does not function correctly until MSXML 6.0 SP2 or later is installed.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, you must either:

To enable patch deployment on Windows servers where a version 8.2.0 agent is installed, additional steps may be required. See Enabling-deployment-on-Windows-servers. This requirement was eliminated for agents running version 8.2.1 or later, as described in Agent-installation-and-default-treatment-of-the-Windows-Administrators-group.

To install an RSCD agent

  1. Navigate to the directory containing installation files and run the installation program for the RSCD agent. Different installers are provided for 32-bit and 64-bit Windows. (Installation program names follow the convention: RSCDversion-platform.)

    Note

    The installation program might display a message telling you to reboot. You must reboot the computer and then run the installation again.

  2. Accept the license agreement and click Next.
  3. Select a setup type for the installation. Then click Next.
    • Typical — Uses a "ready to install" setup with default settings for:
      • RSCD agent installation folder. The default is C:\Program Files\BMC Software\BladeLogic\RSCD
      • Security preferences defined in the secure, exports, and users.local configuration files
      • Location of agent log files. The default is C:\Program Files\BMC Software\BladeLogic\RSCD
      • Secure log files (enabled)
      • Logging of remote keystrokes (enabled)
    • Custom — The installation program displays windows on which you can change the default installation settings. For information about these settings, see Worksheet-for-installing-the-RSCD-agent-Windows.
  4. On the Ready to Install window, click Install.
  5. To complete the installation, click Finish.

The installation program starts the RSCD agent.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*