https://community.sophos.com/sophos-xg-firewall/b/blog/posts/sophos-firewall-v18-5-mr2-is-now-available
Release Notes: https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_185_rn.html
"Old" V18.5 MR1 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/128960/sophos-firewall-v18-5-mr1-feedback-and-experiences/
"Old" V18.0 MR5 Thread: https://community.sophos.com/sophos-xg-firewall/f/discussions/127053/xg-firewall-v18-mr-5-feedback-and-experiences
Please review: https://support.sophos.com/support/s/article/KB-000043489?language=en_US
Installed and all our workstation Heartbeats are missing (after rebooting workstations).
Quite an issue as heartbeats are required for all workstation connectivity. Had to physically connect to the XG to put a temporary access rule in.
I think I may have solved this. Details are in a similar issue I had before when I had to re-register an XG in Sophos Central - https://community.sophos.com/sophos-xg-firewall/f/discussions/130861/how-does-heartbeat-work
For future reference and so I can anticipate this in advance, is it normal for new certificates to be generated for a firmware update, or is this specific to this firmware update?
This should not be the case and is not expected to break after the firmware update. Could you create a support case to get the sorted out?
__________________________________________________________________________________________________________________
I have passed on an Access ID via emmosophos so that devs can have a look at the logs.