Creating a New Test Environment

Carbon Black App Control (formerly Cb Protection)

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

WARNINGS:

Failure to generate a new App Control Server ID will cause file data from multiple App Control Servers being sent to the Reputation services backend.
- This could result in invalid Reputation Trust and Threat Scores being reported back to the related App Control Servers.
The Server Address/hostname for the Test Environment MUST be different than the Production Environment.

Obtain the relevant Server License from the Support Portal
- While it is best practice to have a unique Server License for each App Control Server, the same Server License can be used for multiple installations.
- The total endpoint count across all Server installations must not exceed the total licensed quantity.
- Contact Global Customer Care Team for assistance with Server License modification (date, quantity, etc)
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;
```
Install App Control Server as outlined on App Control Tech Docs > Server > Server Installation Guide.

During the installation with a restored/copied database from a Production Environment
- A notification may appear about detecting changes, accept the changes.
- Using a copy of the Production Environment's database will have a copy of all Rules and Policies in the Test Environment.
- Production Machines will show in the Test Environment Console as Disconnected and can safely be deleted from the Test Environment.
If Production Agents are to be moved to a duplicated Test Environment:
- Utilize a Subject Alternative Name with the Communication Certificate.
- Update the Server Address for the relevant Agents with the setserver command.
- This must be done shortly after initially creating the Test Environment.
Agents in the Test Environment cannot be moved back to the Production Environment
- The environments will begin to quickly differ with small changes to the overall structure.
- Agents cannot be moved from the Test Environment to Production without uninstalling the Test Environment Agent.