Aspera ForceScan Utility for Windows Hot Folders on Network Shares


Client, Point to Point, Enterprise Server or Connect Server 3.4.6+ DO NOT NEED FORCE SCAN: asperasync implements a periodically configurable rescan of the hot folder

This article does not apply for Client, Point to Point, Enterprise Server or Connect Server 3.4.6 and higher


The attached script (force_scan.bat) can be implemented on a Windows Aspera installation (Client, Point to Point, Enterprise Server or Connect Server) to force the scan of a hot folder. This is often utilized when the source for a hot folder is on a network share and content is added to that folder from processes or users from systems other than the Aspera Server. In these instances the file system notifications are not sent to the Aspera Server and the hot folder service would not know that new content is available to be sent.

In the attached zip file is a batch file (force_scan.bat) and a network utility, netcat (see This is the complete package. We have also included a copy of just the script (force_scan.bat) for those environments with strong Intrusion Detection or attachment filtering software that will not permit the download of nc.exe. If you are unable to download the zip file you will need to get a copy of the netcat utility from another source.

The batch file, force_scan.bat, is configured to run on 64 bit Windows. If you are using a 32 bit version of Windows please edit the script with the editor of your choice and uncomment the first "SET ASPERASYNC_PORT_FILE" line and comment out the second "SET ASPERASYNC_PORT_FILE"


Original (64 bit Windows) :

::SET ASPERASYNC_PORT_FILE="C:\Program Files\Aspera\Enterprise Server\var\run\asperasync.port"
SET ASPERASYNC_PORT_FILE="C:\Program Files (x86)\Aspera\Enterprise Server\var\run\asperasync.port"


Changed to 32 bit Windows:

SET ASPERASYNC_PORT_FILE="C:\Program Files\Aspera\Enterprise Server\var\run\asperasync.port"
::SET ASPERASYNC_PORT_FILE="C:\Program Files (x86)\Aspera\Enterprise Server\var\run\asperasync.port"


It is also assumed that the netcat utility, nc.exe, is in the same directory as the script and is called nc.exe. If your environment differs update the variable to reference the location of nc.exe in your environment.



Also, please note:

  1. User running the script needs some additional permissions (such as logon as a batch job, etc.) so the account needs to be an administrator on the machine running asperasync.exe.
  2. The force_scan.bat file, the netcat executable (nc.exe) and the folder containing them should be owned by the user running the script (otherwise job fails when running through the Windows task scheduler, even if it may succeed as a command line run).
  3. In the Task Properties->Action->Edit tab, the field "Start in (optional)" field must be populated with the directory the file lives in.


This ForceScan batch script is implemented by creating a Windows Scheduled Task at the frequency of your choice. For information on creating a scheduled task refer to



Powered by Zendesk