Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Delete old files in Serv-U

Delete old files in Serv-U

Table of contents

Updated October 6, 2016


Some users may want to remove files after uploading or downloading.


All Serv-U versions


  1. If you do not already have them, create a local folder for Serv-U batch files and a local folder for Serv-U logs.
  2. Create a batch file named deletefileafterdownload.bat in your Serv-U batch file folder. Copy/paste this text in:
    time /t >> D:\local\ServU_One\Log\DeleteFileAfterDownload.log
    echo Deleted %1 >> D:\local\ServU_One\Log\DeleteFileAfterDownload.log
    del %1 >> D:\local\ServU_One\Log\DeleteFileAfterDownload.log
  3. Before you save the batch file, change the log path ("D:\local\ServU_One\Log") to your Serv-U log path.

    Do not worry about creating the "DeleteFileAfterDownload.log" file. When Serv-U runs this batch file, it will be done automatically.

  4. Create a new domain-level event called "Delete File After Download".

Event type: File Download
Event Name: Delete File After Download
Enable Event: Checked
Description: (write which folders this applies to)
Action: Execute Command
Executable Path: (full path of deletefileafterdownload.bat)
Command Line Parameters: $LocalPathName
Completion Wait Time: 0

5. Flip to the "Event Filters" tab on your new event and add an Event Filter:

Name: Just Folders Named (whatever your folder criteria are)
Logic: (doesn't matter if you only have one filter rule)
Filter Enabled: Checked
Description: (optional)
Variable: $PathName
Comparison: = (is equal to)
Constant = *dad* (change as necessary; just "*" will match all)
Data Type = (abcd) string

6. Test the process:

a. Sign on as an end user.
b. Download a file from a folder that should trigger the event.
c. Check that the event firing was noted in the Serv-U domain log, and also check that a new "Deleted (filename)"     entry appeared in the DeleteFileAfterDownload.log file. Also, refresh your directory listing in the client you used     to perform the download to verify that the file is gone.
d. Now download a file from a folder that should NOT trigger the event and check that the event did not fire.



Last modified