Java Update Suppress Reboot

[doppers]

Hello,

 

We have been able to deploy java update 37 but you need to unistall java 35 update if the client has this installed. Is there anyway to suppress the reboot as this is being forced by the unintstall of 35.

 

So this can affect users that are working on a laptop as it does not give any warning, just starts the reboot action.

[Jorgen Nilsson]

Hi,What command line are you using to uninstall Java Update 35, you should be able to use

REBOOT=Suppress

even for the uninstall command.

[doppers]

Hi, we are using the command MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216035FF} REBOOT=REALLYSUPPRESS /l*v C:\java35.txt /qn .

 

As you can see we are dumping to a log file but this was added to try and see why it is rebooting.

[Peter33]

Are you doing this in a task sequence?

[doppers]

Yes we are doing this in a task sequence

[Peter33]

Well, that explains the reboot. The Windows Installer receives the exit code 3010 (soft reboot) from the installation and initiates the reboot. With a normal package/application Installation this would be a pending reboot. Unfortunately the beviour in task sequnces is different. In your SCCM logs you will just see an "unexpected reboot".

The good new is that you can avoid this by using a script wrapper which replace the exit dodes 3010 and 1641 (hard reboot) simply with a 0. The bad news is that your following installation of JRE will fail until the computer got restarted due to blocked files in the program files folder.

I am using a powershell script as normal application for the whole process. At first it checks if any java application is running and skips the installation if java is used. otherwise it uninstalls all outdated Java Runtimes with a WMI query. As next step it checks again if any java version is installed and only installs the new version if no other installation is present. Otherwise it will force an error as exit code.

Finally it will install our company certificates.

The application is applied to a dynamic collection which checks the installed java version of the clients (all clients without the latest version).

[doppers]

Thanks for the feedback Peter33, as you mentioned we dumped a log file from the install and could see that the reboot was being forced as the file was locked. This file was being used by the anti virus so we created a package to stop the AV service and then ran the uninstall and the clients no longer did a reboot.

[Peter33]

Hi doppers,

 

thanks for sharing the solution. I did'nt even think about that the antivirus could be the blocker.

I will modify our script to disable the service before the uninstall routine when the next patch is released. Hopefully this will improve the initial success rate. Our helpdesk will be grateful for less calls where they have to tell people to reboot their machine.