App Control: How to Run Filename Pathname Reseed .bat File
App Control Server: 8.0 - 8.6
Microsoft Windows Server: All Supported Versions
To run the FilenamePathnameReseed<Version>.bat file
Login to the App Control database server
Confirm there is a recent full backup of the das database
Execute the 'FilePath_Pruning_Scope_AllVersion.sql' script
Results will validate percentage of orphaned files/paths
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"
Double click the FilenamePathnameReseed_X.X.X.bat
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)
Let the .bat script complete.
Once complete, copy the output from the command window into a text file and save it.
Restart the "Carbon Black App Control Reporter" and "Carbon Black App Control Server" services in services.msc
Rerun the 'FilePath_Pruning_Scope_AllVersion.sql'
Provide the results of step 3, 10, and 12 to Carbon Black Support.
Do not use this script without the help from Carbon Black Support.
A new version of this script is required for versions 8.7 and higher
Cancelling the reseed after starting will leave the database severely corrupted and require a restore. Contact Support if any questions or concerns come up.
If Unified Management server is in use, navigate to the https://<UMServer>/support.php page on the UM Master and at the bottom of the page uncheck the Validate Rules checkbox
FilenamePathnameReseed_X.X.X.bat is version specific, ensure the proper version is being ran
FilePath_Pruning_Scope_AllVersion.sql is not version specific
Due to the creation of temporary tables, please verify that there is at least twice the free space of the current DAS database size.Not doing so will result in database corruption and require a restore.
This process is time consuming and can take anywhere from a few hours to several days in some scenarios.