IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

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

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

Environment

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

Objective

To run the DeleteOrphanedNames<Version>.bat file

Resolution

  1. Login to the App Control database server
  2. Backup the DAS database:
  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 Notes

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

Related Content


Labels (1)
Tags (2)
Was this article helpful? Yes No
0% helpful (0/1)
Article Information
Author:
Creation Date:
‎09-09-2020
Views:
1624
Contributors