Upgrade reboot delay consequences?

[Campbell IT 4]

We have about 20 Windows 2012 R2 servers that are running version 7.0 that need to be upgraded to 7.3 before the upcoming EOL date. Scheduling downtime for these servers is a challenge. If we push the upgrades to these servers without rebooting, what are the consequences of delaying the reboot? Will they be totally unprotected until the reboot? Any other issues we should be concerned about? Thanks.

[Marcos 5,735]

If I remember correctly, the whole communication protocol was changed in v7.3 so without rebooting the machine after the upgrade may cause protection to stop working. Please keep in mind that v7.3 will lose full support this month:

https://support-eol.eset.com/en/policy_business/product_tables.html

[Campbell IT 4]

15 hours ago, Marcos said:

If I remember correctly, the whole communication protocol was changed in v7.3 so without rebooting the machine after the upgrade may cause protection to stop working. Please keep in mind that v7.3 will lose full support this month:

https://support-eol.eset.com/en/policy_business/product_tables.html

Terrific. Honestly, the constant upgrades are getting tiresome. It's almost a full time job to keep up with ESET upgrades.

[Marcos 5,735]

45 minutes ago, Campbell IT said:

Terrific. Honestly, the constant upgrades are getting tiresome. It's almost a full time job to keep up with ESET upgrades.

I would probably not call program updates once per 3 years constant updates. If you take a look at https://support-eol.eset.com/en/policy_business/product_tables.html, version 7.3 was released in Dec 2020, full support ends after 1,5 year with EOL to reach in June 2024, ie. after 3,5 years. Plus there's a possibility in certain cases to purchase additional limited support for specific module updates.

Moreover, upgrades via uPCU are seamless since they install only after the next restart of the machine and another restart should not be required.