App Control: How to Create Test Environment
search cancel

App Control: How to Create Test Environment


Article ID: 286805


Updated On:


Carbon Black App Control (formerly Cb Protection)


Replicate the items necessary to create a separate but identical environment specifically for testing


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


Warning: Using the same Reputation (SRS) Key on multiple Server installations will cause issues.

If the Test Environment requires syncing with the Reputation Service please be sure to also request an additional Reputation Key from the Account Team.

  1. Work with the Account Team to request the existing App Control Server license be split using from the New Instance Request form.
    NOTE: The same Reputation Key cannot be used on multiple Server installations. If a new Reputation Key is required, please be sure to request one.
  2. Make a full backup the DAS database and move it to the new SQL Server.
  3. Restore the DAS database to the new dedicated SQL instance to be used as the test environment
    1. Open Microsoft SQL Server Management Studio
    2. Right click on 'Databases' > Restore Database
  4. Regenerate the key for App Control Server via Microsoft SQL Server Management Studio:
    1. Expand Databases > Expand DAS > Expand Programmability > Expand Stored Procedures
    2. Right click on dbo.RegenerateParityCenterKey > Click Execute Stored Procedure > Click OK
  5. 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.
  • 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.