I have done this remotely probably about 30 times, on locations that are half way around the world from me and I did not have out of band access if it had gone wrong. Fortinet will tell you that you need to have a serial connection into the firewall with OOB access if you want to upgrade the firmware remotely, that' s their stance. Its a gamble doing it remotely without having OOB serial access, but I have never had a problem with either upgrading the firmware or rolling back the firmware and that is on both stand alone firewalls and HA pairs. Its going to come down to your choice. Good luck.
I mean access a customers fortigate remotely and update...
i' d like recommend follow updates path in those cases. i.e.: if you' ve a unit with a complex configuration running 2.80 don' t expect a smoothly upgrade if you go direct to 3.0 MR7 ....these kind of things
most of my customers are: FG50B FG60 FG60B what firmware version is recomended? I go to support site, assume newest should always be downlaoded? the images in: ftp://support.fortinet.com/FortiGate/v3.00/MR7/MR7_Patch_2/
Hi, I update firmware remotely very regularly on the FG60B' s with out any issues. I would recomend that use the USB Loader facility and take a backup of the config onto the key before you carry out the update. We' ve never had any issues. Rich
I only had one issue, where the unit did not come back online after upgrading. Luckily in the AM, the users just recycled the power and it came back. To be fair, this unit is HAMMERED with use, so a prior reboot before the upgrade would probably have cleared the memory for a smooth upgrade. Other than that, I have upgraded all my FWF60Bs and FWF60AMs remotely without issue. Even the one that flaked out, I was later able to remotely upgrade without a problem.
very old firmware will do upgrading without clear memory first. However the newer firmware, I think v3.0 MR5 or later but not sure, does kill all other daemons to clear memory before upgrading.