Creating a New Test Environment
search cancel

Creating a New Test Environment

book

Article ID: 286805

calendar_today

Updated On:

Products

Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

Steps to create a new App Control environment from an existing Server License.

Environment

  • App Control Server: All Supported Versions
  • Windows Server: All Supported Versions
  • Microsoft SQL Server: All Supported Versions

Resolution

  1. Acquire the relevant Server License (.lic) file:
  2. If duplicating the existing environment for testing:
    1. Make a full backup the DAS database and move it to the new SQL Server.
    2. Restore the DAS database to the new dedicated SQL instance to be used as the test environment
      • Open Microsoft SQL Server Management Studio
      • Right click on 'Databases' > Restore Database
    3. Click New Query and execute to generate a new App Control Server ID: 
      use das; exec dbo.RegenerateParityCenterKey;
Warning: Failure to generate a new App Control Server ID will cause mixing up of file data from 2 or more App Control servers being sent to the Reputation services backend, which could result in invalid reputation trust and threat scores being reported back.
  1. Install App Control Server as outlined in Server Documentation > Server Installation Guide on VMware Docs.

Additional Information

  • The Server Address/hostname for the test environment MUST be different. During Server install a notifier will appear; please accept the change.
  • If installing App Control Server on a different partition than what was used in production, notifier will appear during the install for the test lab. Click OK to use the new partition.
  • None of the production endpoints will connect to this lab server since the lab server has a different Server Address.
  • Accept all the defaults.
  • When lab server is installed, it will be using the copy of the DAS database and rules and policies will be similar to production environment
  • Machines from production environment will show in the test lab's Console, but will be disconnected
  • If Agents from Production are going to be moved to the Test Environment then a SAN certificate with the Test Servers name will need to be created
  • SetServer could be used to move individual machines to the Test Environment
  • Any Agent that is installed for the Test Environment cannot be moved to the Production Environment, and would need to be uninstalled from the Test Environment then installed using the Production Environment Agent.
Powered by Wolken Software