On some systems (most notably, Server 2012, and Server 2012R2) we have observed that the Traverse maintenance scripts are unable to properly purge old netflow data from the system during nightly maintenance. This condition will also prevent users from deleting the data using file explorer, even when logged in as an administrative user, or local administrator.
Resolution of this is a straightforward task, although it involves a few specific steps.
First, we must set the Traverse Netflow Collector to run as the local Administrator account. This is accomplished by setting the service itself to logon as the Administrator account from the Windows Services snap-in. Open the Windows Services snap-in, choose the 'Traverse Netflow Data Collector', then right click and choose properties. When the properties tab is open, select 'Log on as: This Account' and fill the fields in with .\Administrator, and enter the proper password. Save the settings, and restart the service. This will ensure that moving forward, permissions will continue to be set properly for the files that Traverse stores your netflow data in.
Next, we need to reset the permissions of the data directory and all of the data files for the netflow subsystem. Open file explorer, and navigate to your Traverse home directory, then into apps\silk\ - in this example, we will be using the default of C:\Program Files (x86)\Traverse\apps\silk as our starting point.
Right click on the data directory, and choose properties. Click on the Security tab, and then click the Advanced button at the bottom.
In the next dialog, choose Change, for the Owner :
Choose the local machine as your location, and ensure that the local administrator is the account chosen (DO NOT use a domain admin here, it must be a local administrator) :
When you return to the Advanced Security Setting for the data directory, choose to 'Replace owner on subcontainers and objects' and also select 'Replace all child object permission entries with inheritable permission entries from this object' :
Press Apply, and the permissions will be fixed. You may now purge netflow data by hand, or simply wait for the nightly maintenance scripts to purge data for you.