PC boots after Update VScan 4.5.0 -> 4.5.1

[AnAngel]

Hello again,

sorry for stupid questions, but im new to this whole thing.

I delivered to serveral test Workstations the VScan 4.5.1. If it is a new install there are no Problems, the VScan installs and everything fine, but if i send VScan 4.5.1 to a machine which has 4.5.0 insalled the workstation reeboots after install without a warning.

We want to make a rollout but without warning of reebooting it will be a mess. And i found no option for a warning.

Can u help me?

Thx

 

[AVChap]

It depends on the OS. If it's 9x, you can't do anything about it. NT Wkstn and higher most of the time doesn't require a reboot EXCEPT if the machine has an older version of the MSI (Microsoft Installer). I believe 1.2 (?) is the version being used by 4.51. If the machine doesn't have this, it will install this version and restart, then continue with the installation.

HTH, AVChap
... take my advice, I don't use it anyway!

 

[VictorySabre]

Hi AnAngel,

Yes, I was surprised by that too when I saw some machines reboot instantly without a prompt or warning that a reboot would occur even though I set the ePO Agent policy to prompt for a reboot and automatically reboot after 3600 seconds.

And I think AVChap's explanation is good as those NT 4 machines that did reboot did not have the latest Windows Installer.

Too bad I can't control the reboot behavior when rolling out the upgrade from NetShield 4.0.3 to NetShield 4.5 and then apply the NetShield 4.5 SP1 update. (If after installing NetShield 4.5 is performed without rebooting and the SP1 is installed, NetShield becomes corrupted)

 

[AnAngel]

And there is nothing i can do against it??? Or, when i can do nothing against it, i would like to give the User a message.

When i think of my own PC.....god.....i would kill the Person who shutdown my PC with unsaved work.

Greetz

 

[VictorySabre]

I don't know if there is a way to deal with it... The only thing I can do is e-mail all the users warning them that an upgrade will take place at 8:00 PM and that a reboot will occur. The e-mail also warns them that they must be logged out before that time.

I never do the upgrades during the work day. I too would like to know what is the solution to this reboot problem.