Discovery pattern with deletion strategy for "tracked file" not deleting once the file is gone on the target device.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Description Customer can configure File Tracking on a specific pattern, in these case for Windows - OS Servers. Once the file is gone on target he has set the strategy to Deletion. But when discovery is run, it doesn't delete those files. This KB address how the deletion strategy works and when. Please review the additional information. Procedure Navigate to the sa_pattern.LISTOpen the pattern where you want to set the strategy forIn this case, the field is "Tracked Files" and set this strategy to Delete Applicable Versions All versions. Additional Information The way deletion strategy works is by comparing the previous discovery result for a given device with the current one, and the defined deletion strategy is executed based on the delta. So, if in previous discovery device X was discovered, and in the current one it's missing, and deletion strategy defined to be "Delete", then the device is deleted. On the same note, if it's defined to be "Keep", then the device is kept in the CMDB. The deltas are being calculated only between two consecutive discoveries. So, if now I take the same device X, which was kept in the CMDB based on its deletion strategy, and now I change it to "Delete", it won't be deleted on the next discovery since it has already been missing from the previous one. So, in this specific case, you should remove the file manually. In the future, if you have any files on Windows Server that are currently still being discovered, once they're removed from the machine they'll be removed from the CMDB as well, as expected.