When installing ffastrans service from unc path so we can run a farm, opening ffastrans from a local dir (e.g. z:) would mess up the config file by rewriting the new installation path into it.
Proposed solution: when opening ffastrans.exe, check if it was started from the same path as seen in config and if not, propose to open the correct start link or such
Add UNC installations sanity check
Add UNC installations sanity check
emcodem, wrapping since 2009 you got the rhyme?