I had an odd one trying to using the CLI on windows to upgrade Otto - I even tried the manual method of uninstalling and reinstalling, but kept getting error that it wasn’t a valid application.
I copied the uninstaller off another windows server and then was able to run the CLI on this server. But noticed the same issue that the uninstaller is 0kb
Hey Stephen,
I believe the uninstaller is a symlink to the Uninstaller.dat, which is why its 0 KB. That’s probably why copying it broke it. Did you hit an issue running it manually or was there an error on the CLI install? Could you share the error?
-Kyle
This is what it looks like on a windows (ottomattic) server.
When i tried to uninstall / reinstall if it fails on the client’s on prem server.
Even the CLI fails to run. Last time I ran it installed properly but corrupted the uninstaller.
it may be due to threat locker they are running
threat locker is a good bet, I haven’t seen that before so it might be removing the uninstaller as a detected threat? We’ve had similar problems with NSSM on some servers
-Kyle
Thank you for giving us a call earlier. I remoted into the App Server and saw that Threatlocker appeared to be blocking the new update for OttoFMS. I reached out to my team about getting it unblocked, but our agent was reporting that there might be a virus inside of the installer. Please allow us a little bit of time for us to sort this out, and we will reach back out to you once we have cleared the installer.
Do you think setting on their end are too restrictive?
