To update a SQL Anywhere 16.0 Network server -- which is at a deployed site -- with an EBF, do the .lic files that were deployed with the original installation need to be regenerated to match the new executables?

The site was originally deployed with a manual method: There was no Setup or MSI run there, and no registration key was entered there. Rather, the developer (who is responsible for the licences) just prepared and delivered to the site a folder structure "SQL Anywhere 16\Bin32" that contained all the .exe, .dll and .lic files with instructions for the local site admin to copy that folder to "C:\Program FIles (x86)\". Then the local admin ran dbsvc.exe with appropriate parameters to create and register the service running dbsrv16.exe.

Now, to deploy an update from an EBF using a similar method, would this work: Could the developer just extract the new .exe and .dll files from a downloaded EBF distribution into a similar folder structure, add in the prior .lic files, then send that folder to the deployed site as a clean reinstall? Or could the site even reuse the existing .lic files already deployed?

Or would the developer have to generate new .lic files upstream?