Reboot required

[m.novelli]

I forgot the biggest issue with this update... the reboot required by Microsoft C++ runtime this is a real pain that almost double the time needed for the update

(wait for Veeam Services to start after reboot, and then stop them again before running the update...)

Marco

[ChristineAlexa]

My biggest complaint ...

Forced reboot of clients, EVEN clients THAT WERE ONLINE AND ACTIVE with NO warning.
MANY users lost their work, and I had to listen to boss yell for an hour.

Please, Please, Please just set the reboot flags in the OS that annoy the user to reboot. It is pretty unacceptable to just force reboot with no warning on active users, logged in users.

[ChristineAlexa]

So, is there a way to make it stop at "Reboot Required", which I actually see some machines go through in the console, yet still auto-reboot.

[Gostev]

@Egor Yakovlev do you know?

[Egor Yakovlev]

That does look odd to me. We are talking about end user machines with Veeam Agents here, right? Protection Group settings got both auto-update as well as reboot checkboxes and follow these settings without any known issues. That is, agent should never update itself automatically if "Auto-update backup agents" checkbox is cleared, nor should it reboot itself if respectful checkbox for automatic reboot is cleared. More than that, even if you hit Upgrade Agent manually from VBR console, we will not reboot target machine automatically and session will state "reboot required" for you to conclude upgrade at suitable time.

[ChristineAlexa]

OK, so I am not imagining, the behavior is unintended and unexpected.

I'm wondering, I believe I checked the one checkbox at the end of the upgrade asking if you want to allow agents to be updated (don't remember exact verbiage).

I wonder if it unintentionally sets the reboot flag?
Or, if it's a combination of the above, PLUS a rescan. flips both flags (update + reboot) unintentionally?

I was expecting the behavior you described, that the machines should wait in "Reboot Required", until the client was rebooted intentionally.

Possibly the ideas above help in fuzzing this out...

[ChristineAlexa]

To follow up, just had it decide to auto-reboot again during uninstall, with users physically using the machines (including the machine I was using!!!)

Then it decided to reinstall from the workstations being in a protection group (and again, auto-reboot, without prompting on active users, including myself)

We are a 24 hr operation, things can't just "reboot" on their own with coordination or workers in mind.

I most likely lost my job over this, this time.

So thank you.

[Gostev]

That does look odd to me. We are talking about end user machines with Veeam Agents here, right? Protection Group settings got both auto-update as well as reboot checkboxes and follow these settings without any known issues. That is, agent should never update itself automatically if "Auto-update backup agents" checkbox is cleared, nor should it reboot itself if respectful checkbox for automatic reboot is cleared. More than that, even if you hit Upgrade Agent manually from VBR console, we will not reboot target machine automatically and session will state "reboot required" for you to conclude upgrade at suitable time.

This answer still stands. There are currently no known issues with this functionality, so it all depends on how you configure the Protection Group. If you see your Protection Groups not honoring their agent auto update settings then you should open a support case and let us investigate. Plus I'm sure there are many other apps running on your machine so Veeam can never be the only suspect.

[ChristineAlexa]

Gostev,
I figured out what happened. The DEFAULT is set that way.

I had to recreate a protection group for another reason, and didn't realize it had auto-set that on a new protection group.

Sorry for the attitude, been a long week and that was the last straw.

Thanks for the assistance
Christine.