Deploying Java 7u45

[Gongalong]

Hi folks,

 

I'm trying to deploy Java 7u45 with GP. Previously I've used Orca to edit the MSI file as per this helpful guide How to package and deploy Java JRE 1.6.0_26 via Group Policy | ivan's blog

 

Now when I edit the 7u45 MSI file I get an error that it has "Failed to open MSI database".

 

Anyone know if there's a workaround, or an alternative to editing the MSI?

 

TIA

[Arthur]

Do you get the same error with InstEd?

[Gongalong]

Yes, a "failed to open" error.

[AngryTechnician]

Are you making changes directly to the MSI or creating a transform? Transforms are almost always the recommended approach, and it worked for me when I deployed 7u45 this morning.

[Gongalong]

I've never tried transforms, and used the guide above with the Orca editor.

[Gongalong]

It looks like Orca is one tool used to create transforms. Are there any others?

[AngryTechnician]

InstEd It! - InstEd - Make packaging more productive

[Gongalong]

As mentioned above though, InstEd won't open the MSI.

 

I'm not sure if something has changed, but following Ivan's blog the MSI for u45 is much larger than for u17 (863kB vs. 25 MB) - this is the MSI retrieved from the temp directory How to package and deploy Java JRE 1.6.0_26 via Group Policy | ivan's blog

[Arthur]

Do you have the following two files?

 

http://i.imgur.com/WVVouSg.png

 

32-bit: %UserProfile%\AppData\LocalLow\Sun\Java\jre1.7.0_45
64-bit: %UserProfile%\AppData\LocalLow\Sun\Java\jre1.7.0_45_x64

[Gongalong]

Nope, so let me double check the extract.

 

I get jre1.7.0_45-c.msi and java_sp.dll

[Arthur]

I get jre1.7.0_45-c.msi and java_sp.dll

Re-download Java using the download link(s) in the thread below and then try again.

 

www.edugeek.net/forums/downloads/125430-java-runtime-environment-7-update-45-released-one-critical.html

[Gongalong]

Wunderbar! That seems to have worked. Thanks.

 

We've just started adding some 64 bit workstations. Is it just a case of adding both 32 and 64 into the GPO, and the install will just fail for the incorrect machine?

[Gongalong]

Also, when removing old versions is it best to tell GP to uninstall immediately, or just leave them in place on the basis that the new version should overwrite? We have had some workstations with multiple versions of Java, so I'm guessing that the former might be the better option.

[Arthur]

Is it just a case of adding both 32 and 64 into the GPO, and the install will just fail for the incorrect machine?

The 64-bit version is only required if you use a 64-bit browser e.g. IE10 when you have Enhanced Protected Mode enabled. In most cases you could get away with just installing the 32-bit version of Java (even on 64-bit editions of Windows).

 

Also, when removing old versions is it best to tell GP to uninstall immediately, or just leave them in place on the basis that the new version should overwrite? We have had some workstations with multiple versions of Java, so I'm guessing that the former might be the better option.

I use SCCM to deploy software. With that we normally uninstall the old version before installing the latest version. There seems to be far less problems that way.

Edited October 17, 2013 by Arthur

[Gongalong]

GP gives the option to uninstall when you remove, or just leave installed on the PC. I think I'll go with uninstall moving forwards.

 

One day I'll get around to setting up SCCM...

[Gongalong]

Curiously a fair few machines with problems this morning, all getting stuck at the "Please Wait" before the logon screen appears. All related to either the Java or latest flash deployment over GP.

 

I removed the deployments and that resolved it. Oddly it seems to be our fastest PCs, often those with SSDs, that get stuck by this. Other machines are unaffected.

 

I had this before with a handful of machines and the Java/Flash update but turning them off and on resolved it. Not this time.

 

I'll do some testing later on... (note the update had been tested on a small group of IT department machines, but I wonder if this relates to sending out an uninstall command followed by the update itself over the weekend. Normally I do this during the school day)

[Zyxn]

Curiously a fair few machines with problems this morning, all getting stuck at the "Please Wait" before the logon screen appears. All related to either the Java or latest flash deployment over GP.

 

I removed the deployments and that resolved it. Oddly it seems to be our fastest PCs, often those with SSDs, that get stuck by this. Other machines are unaffected.

 

I had this before with a handful of machines and the Java/Flash update but turning them off and on resolved it. Not this time.

 

I'll do some testing later on... (note the update had been tested on a small group of IT department machines, but I wonder if this relates to sending out an uninstall command followed by the update itself over the weekend. Normally I do this during the school day)

 

 

I'm actually encountering this currently as well. In testing on a few machines before a full pushout.

I did the following:

1) extracted offline installers of Java x86 & x64

2) Created transformations using ORCA and applied them in the GPO.

2.1) The transformations include:

Property:

-AUTOUPDATECHECK 0

-IEXPLORER 1

-JAVAUPDATE 0

-JU 0

-MOZILLA 1

3) Disabled x86 Java from installing on 64bit machines.

4) Deployed on test xp and Win 7 machines and gets held up at the "Please wait" or if you enable verbose status messaging, "Installing Java Update v45"

*After leaving the computer for over an hour, it cancels and yields an error with Java not being able to be installed.

*I don't run an uninstall command beforehand, I just let the Java update push and hopefully do it.

 

-I'm thinking there has to be some kind of new setting to configure when deploying.

[AngryTechnician]

For what it's worth, I also have REMOVEEXISTING=1 set in my transform. I don't set the JU property as setting JAVAUPDATE=0 seems to take care of it.

 

However, I install via WSUS/Local Update Publisher, not GPO, so it may be something (such as a race condition) specific to GPO deployment.

[Gongalong]

I had the same "please wait" with the previous update as well (7u25 from memory) but to a lesser extent. It was so bad this time I had to back out the update so people could logon (it didn't show in testing).

[Gongalong]

For what it's worth, I also have REMOVEEXISTING=1 set in my transform.

I don't see this as an option listed under PROPERTY (using Orca).

[Arthur]

I don't see this as an option listed under PROPERTY.

You have to add the property yourself as a new row.

[Gongalong]

Oddly it doesn't seem to be affecting our older slower HDD based machines. It's only our faster SSD based machines that seemed affected, albeit it could be some software difference. I'm waiting to see if/when the latter boot past the "please wait" stage and will check Event Viewer, along with the install state for Java.

[Arthur]

It's only our faster SSD based machines that seemed affected, albeit it could be some software difference.

Do the PCs with SSDs have the Java QuickStarter Service installed? If so, does it make any difference if you disable this service prior to installing the new version of Java?

[Gongalong]

Nope, no Java Quickstarter Service. Having turned on a room of 28 of the slower PCs a couple are affected, but the bulk not.

 

The quicker PCs are all starting to get to the logon screen now, after an hour or so of "please wait". Java 7u45 has not installed, and there's no clues I can spot in Event Viewer. There is mention of the logon service taking around an hour to arrive (no surprise). I also got an odd client service message about Java not being installed properly, although Java 7u25 is purportedly on these machines.

 

Retesting now with REMOVEEXISTING=1 added...

[Gongalong]

The error I'm getting is from a dialog labelled "Interactive Services Detection". It's telling me that "a program running on this computer is trying to display a message. The program might need information form [sic] you or your permission to complete a task." The program requesting attention is RunDLL. The message is, "There was a problem starting C:\Program Files\Java\jre7\bin\\installer.dll. The specified module could not be found." Once I acknowledge that the message goes.