+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 25
Downloads Thread, Java Runtime Environment 7 Update 40 released. Update warning can now be disabled! in Links, Downloads and Scripts; Click here for details or see the quoted text below. Java SE 7 Update 40 (expires 10th December 2013) Download ...
  1. #1


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    8,917
    Thank Post
    226
    Thanked 2,676 Times in 1,973 Posts
    Rep Power
    787

    Java Runtime Environment 7 Update 40 released. Update warning can now be disabled!

    Click here for details or see the quoted text below.

    Java SE 7 Update 40 (expires 10th December 2013)
    Download (Windows: 32-bit, 64-bit / OS X: 64-bit) / Release Notes

    Option to disable the "JRE out of date" warning
    Starting from 7u40, a new deployment property deployment.expiration.check.enabled is available. This property can be used to disable the "JRE out of date" warning.

    When the installed JRE (7u10 or later), falls below the security baseline or passes it's built-in expiration date, an additional warning is shown to users to update their installed JRE to the latest version. For businesses that manage the update process centrally, users attempting to update their JRE individually, may cause problems.

    To suppress this specific warning message, add the following entry in the deployment properties file:

    Code:
    deployment.expiration.check.enabled=false
    Last edited by Arthur; 10th September 2013 at 11:51 PM.

  2. #2

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,212 Times in 761 Posts
    Rep Power
    394
    It seems that the newest irritation for Java is that as of update 40 it dumps a load of shortcuts on the Start Menu:

    java shortcuts.png

    Because the .msi is a wrapper and not a true .msi, there's no Shortcuts table to remove lines from. I also can't see anything in the Property table to set that might suppress them. Does anyone know a way to install 7u40 without these or do I have to resort to deleting them using GPP after the install?

  3. #3

    Join Date
    Jun 2009
    Location
    East Renfrewshire
    Posts
    145
    Thank Post
    20
    Thanked 22 Times in 16 Posts
    Rep Power
    14
    A complete and utter fudge might be to do it the way I do our software deploys - have a compiled AU3 script run the MSI/whatever, and then do tidying up of shortcuts.
    Yep, it's a pockle, but if it works...

  4. #4


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    8,917
    Thank Post
    226
    Thanked 2,676 Times in 1,973 Posts
    Rep Power
    787
    Quote Originally Posted by AngryTechnician View Post
    Because the .msi is a wrapper and not a true .msi, there's no Shortcuts table to remove lines from.
    This is one of the most infuriating things about the installer. I am almost tempted to create my own MSI.

    Quote Originally Posted by AngryTechnician View Post
    Does anyone know a way to install 7u40 without these
    I have created a .vbs custom action to delete the shortcut folder during installation. MST attached. You can use this in combination with your existing transform file if you want, since it only contains the bits required to delete the folder. e.g.

    Code:
    msiexec /i jre1.7.0_40.msi TRANSFORMS="jre1.7.0_40.mst;DeleteStartMenuFolder.mst" /qb!
    Attached Files Attached Files

  5. 2 Thanks to Arthur:

    AngryTechnician (4th October 2013), martinkasabov (4th October 2013)

  6. #5

    Join Date
    Oct 2013
    Posts
    7
    Thank Post
    3
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Hi there!
    Where is that "deployment properties" file?
    I have looked all inside the cab file that is extracted along with the MSI when the offline EXE installer is run...
    I could not find the file name mentioned in your posting.

  7. #6

    Join Date
    Oct 2013
    Posts
    7
    Thank Post
    3
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Hi there!
    Here is what I have done and it works like a charm:

    You first need to create a vbscript file with the following content:
    -------------------------------------------------------------------
    dim strProgramData, strJavaPath


    set wshShell = CreateObject("WScript.shell")
    set scrFilesystem = CreateObject("Scripting.FileSystemObject")


    strProgramData = wshShell.ExpandEnvironmentStrings("%ProgramData%")
    strJavaPath = strProgramData & "\Microsoft\Windows\Start Menu\Programs\Java"


    if scrFileSystem.FolderExists(strJavaPath) then
    scrFileSystem.DeleteFolder(strJavaPath)
    end if
    ---------------------------------------------------
    I have named it "DelStartMenuDir.vbs" - ir can be any name, just need to know it and its location.

    [Edit the MSI w/ InstEd It! or Orca:]


    1. Go to "Binary" table, add row: give <NAME> and for Data [Binary Data]:
    ... Browse to the "DelStartMenuDir.vbs" File > OK
    (The script will now be embedded into the MSI)
    (No need to provide it w/ the installer when deployed)


    2. Go to "CustomAction" Table > Add a row:
    - Action > Give it a <TITLE>;
    - Type > ENTER "6" without the Quotations!
    (Type 6 = VBScript file stored in a Binary Table stream)
    - Source > Type the <NAME> value from the Binary Table!
    - Target > NULL (Leave Blank)!


    3. Go to "InstallExecuteSequence" Table > Add a row:
    - Action > Type the <TITLE> value from the CustomAction Table!
    - Condition > ENTER "Not Installed" without the quotations!
    - Sequence > ENTER "-1" without the quotations!
    (msiDoActionStatusSuccess = -1)
    (Successful completion)
    (Used with Exit dialog boxes)
    *It means it will be applied just before the MSI Exits
    upon successful installation...

    Save your MSI and run it. No need to provide .MST, post-install script/command, GPO or anything extra.
    I do this for BOTH 32-bit & 64-bit JAVA Installers, as we maintain both in our environment...

    Hope this helps.

  8. Thanks to martinkasabov from:

    AngryTechnician (4th October 2013)

  9. #7

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,212 Times in 761 Posts
    Rep Power
    394
    The similar solutions from @Arthur and @martinkasabov are both very interesting. I've never dabbled in creating my own custom actions before and wasn't aware they could be as simple as calling a VBS. Will definitely think about using that trick again in future.
    Last edited by AngryTechnician; 4th October 2013 at 03:55 PM.

  10. #8


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    8,917
    Thank Post
    226
    Thanked 2,676 Times in 1,973 Posts
    Rep Power
    787
    Quote Originally Posted by martinkasabov View Post
    Save your MSI and run it. No need to provide .MST
    It's probably worth mentioning that modifying a vendor supplied MSI directly (without creating a transform) is considered bad practice and should only be done as a last resort.

  11. Thanks to Arthur from:

    martinkasabov (4th October 2013)

  12. #9

    Join Date
    Oct 2013
    Posts
    7
    Thank Post
    3
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Good and valid point, Arthur.
    Then I believe your approach would be best fit regarding best practices.
    I am not trying to steal ideas or any of that. I realize your solution (using MST and custom action with vbscript) is basically what I did apply in my case, and it was thanks to your posting. In my posting I just wanted to share the detailed steps to take to make this happened.

    So at the end - to correct the process I described, instead of saving these changes directly to the MSI:

    [Edit the MSI w/ InstEd It! or Orca:]

    *Create New Transform
    (From the Menu > This will create an MST File - provide name and THE location where the original MSI is)

    *Start making the changes listed as before;

    -----------------------------

    *At the end save THIS file (mst) and exit.

    Then when deploying just add the TRANSFORMS="<FILENAME.MST>" at the command options for msiexec...


    Arthur, thank you for pointing that out!

  13. #10


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    8,917
    Thank Post
    226
    Thanked 2,676 Times in 1,973 Posts
    Rep Power
    787
    Quote Originally Posted by martinkasabov View Post
    In my posting I just wanted to share the detailed steps to take to make this happened.
    No worries. It's good to have the steps documented - thanks for posting them. I even learnt something new too (the bit about using -1).

  14. #11

    Join Date
    Oct 2013
    Posts
    7
    Thank Post
    3
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Yes, that was challenge indeed. I tried several different values (as recommended straight from Microsoft, regarding InstallExecuteSequence Table in MSI Files)
    Suggested InstallExecuteSequence (Windows)
    ... but this specific JAVA Installer did not like any of them.

    So at the end I used another reference that explains pretty good the usage of negative values:
    InstallExecuteSequence Table (Windows)

    On another note - I did ask you about the:

    "Option to disable the "JRE out of date" warning
    Starting from 7u40, a new deployment property deployment.expiration.check.enabled is available. This property can be used to disable the "JRE out of date" warning."


    from your original posting here...
    Where exactly is this file where we can add this property?

  15. #12

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,660
    Thank Post
    859
    Thanked 646 Times in 429 Posts
    Rep Power
    498
    Update 40! Bleedin heck!
    What happened to 26 thru 39?!

  16. #13


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    8,917
    Thank Post
    226
    Thanked 2,676 Times in 1,973 Posts
    Rep Power
    787
    Quote Originally Posted by martinkasabov View Post
    Where exactly is this file where we can add this property?
    The deployment.properties file needs to be placed in the folder listed below along with another file named deployment.config. I have attached a copy of the files I use so you can see what they should contain. Feel free to customize the 'deployment.properties' file to suit your environment though.

    Code:
    %SystemRoot%\Sun\Java\Deployment
    Attached Files Attached Files

  17. Thanks to Arthur from:

    martinkasabov (7th October 2013)

  18. #14


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    8,917
    Thank Post
    226
    Thanked 2,676 Times in 1,973 Posts
    Rep Power
    787
    Quote Originally Posted by Gatt View Post
    What happened to 26 thru 39?!
    Oracle have switched to a new naming convention.

    • Limited Update releases will be numbered in multiples of 20.
    • We intend for Critical Patch Updates to continue to use odd numbers. The numbers will be calculated by adding multiples of five to the prior Limited Update and when needed adding one to keep the resulting number odd.

    This is best illustrated with an example:

    The next Limited Update for JDK 7 will be numbered 7u40, and the next 3 CPUs after that will be numbered 7u45, 7u51, and 7u55. The next release will be a Limited Update 7u60, followed by CPUs 7u65, 7u71, and 7u75.

    This numbering scheme will leave several numbers between releases which will allow us to insert releases – for example security alerts or support releases, should that become necessary - without having to renumber later releases.

  19. #15

    Join Date
    Oct 2013
    Posts
    7
    Thank Post
    3
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Thank you, Arthur!
    I was able to successfully deploy these files and everything works great. I utilized most of the settings you have in the properties file provided.
    The only confusing thing was the "deployment.properties" generated in the user profile when java installation is verified (via web browser, visiting java.com), or when java.cpl is opened. That file contains different config that the one in %SystemRoot%\Sun\Java\Deployment, which I am not sure why and what affect it has. But I confirmed that the system-wide settings deployed take over and enforce that configuration. All good.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 0
    Last Post: 19th June 2013, 05:41 AM
  2. Sun Java Runtime Environment 6 Update 21
    By Arthur in forum Downloads
    Replies: 3
    Last Post: 9th July 2010, 04:00 PM
  3. Replies: 2
    Last Post: 9th April 2010, 08:37 PM
  4. Replies: 0
    Last Post: 16th June 2006, 09:00 PM
  5. Updating Java Runtime
    By ITWombat in forum Windows
    Replies: 3
    Last Post: 18th May 2006, 12:44 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •