Security updates for SP1

Version 8.2 SP1 includes the following security updates:

Creating an alternate user name for a Windows agent

When the RSCD agent runs on a Windows machine, it runs by default under the user name BladeLogicRSCD. The following procedures explain how to create an alternate user name for Windows agents. Defining an alternate name can resolve a problem in which the BladeLogicRSCD user becomes locked on domain controllers.

To create an alternate user name on a single domain controller

Use this procedure if only one domain controller is running in a Windows domain.

  1. On a domain controller, add the registry key \HKEY_LOCAL_MACHINE\SOFTWARE\BladeLogic\RSCD Agent\BladelogicRSCDUser as a string value. For the value of the new registry key, enter a user name for the agent.
  2. Stop the agent on the domain controller. See Starting and stopping the RSCD agent.
  3. Delete the BladeLogicRSCD user and its home directory.
  4. Restart the RSCD agent.

To create an alternate user name on multiple domain controllers

Use this procedure if multiple domain controllers are running in the same Windows domain.

  1. On the first domain controller, add the registry key \HKEY_LOCAL_MACHINE\SOFTWARE\BladeLogic\RSCD Agent\BladelogicRSCDUser as a string value. For the value of the new registry key, enter a user name for the agent.
  2. Stop the agent on this domain controller. See Starting and stopping the RSCD agent.
  3. Start the agent on this domain controller.
  4. Wait until the new user name replicates to other domain controllers, or force replication to those domain controllers.
  5. Using the procedure described in the first step, add the registry key on the other domain controllers in the Windows domain.
  6. Stop and start the BladeLogic RSCD Agent service on the other domain controllers.
  7. After all domain controllers are using the new user name, delete the default BladeLogicRSCD user account and delete its home directory on each domain controller.

SOCKS proxies and Network Shell proxy servers

If you are using SOCKS proxies, Application Servers should be configured to route traffic to Network Shell proxy servers. Using a Network Shell proxy server prevents issues that can occur when any type of action causes files to be copied from a server behind one SOCKS proxy to a server behind another SOCKS proxy.

For information about Network Shell proxy servers, see Setting up a Network Shell proxy server. For information about SOCKS proxies, see Setting up communications with remote servers.

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

Comments