App Control: How to Run Delete Orphaned Names .bat File

Products

• Carbon Black App Control (formerly Cb Protection)

Issue/Introduction

To run the DeleteOrphanedNames<Version>.bat file

Environment

• App Control Server: 8.0-8.6
• Microsoft Windows Server: All Supported Versions

Resolution

1. Login to the App Control database server
2. Backup the DAS database:
   • https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/create-a-full-database-backup-sql-server?view=sql-server-ver15
3. Execute the 'FilePath_Pruning_Scope_AllVersion.sql' script
   • Results will validate percentage of orphaned files/paths
4. Open Services.msc
5. Stop the "Carbon Black App Control Reporter" and "Carbon Black App Control Server" services in services.msc
   • These services were formally named "CB Protection Reporter" and "CB Protection Server"
6. Extract 'FilePathNamePruningBat_X.X.X.zip'
7. Double click the DeleteOprhanedNames_X.X.X.bat
8. Script will prompt for name of the SQL server.
   • This needs to match how it is seen in the Objects Panel of the SQL Server Management Studio, e.g, Instance\Servername Note: if unsure then open SSMS, right-click on the top tree node > properties > (copy and paste what's in the 'name' field) 
9. Let the .bat script complete.
10. Once complete, copy the output from the command window into a text file and save it. 
11. Restart the "Carbon Black App Control Reporter" and "Carbon Black App Control Server" services in services.msc
12. Rerun the 'FilePath_Pruning_Scope_AllVersion.sql'
13. Provide the results of step 3, 10, and 12 to Carbon Black Support.

Additional Information

Warnings: 

• Do not use this script without the help from Carbon Black Support.
• FilePathNamePruning.bat is version specific. 
• FilePath_Pruning_Scope_AllVersion.sql is not version specific
• Cancelling the script after starting will leave the database severely corrupted and require a restore. Contact Support if any questions or concerns come up.
• Due to the creation of temporary tables, please verify that there is at least twice the free space of the current DAS database size
• This process can take several hours depending on database size