martinkasabov

Thanks for the input, goran13! That is true (would not work for WinXP), as the variable %PROGRAMDATA% in XP points to "C:\Documents and Settings\All Users\Application Data", where there is indeed a "Microsoft" Folder, but there is no "Windows" folder where normally the Start Menu > Programs > Java will be placed. Instead, a "%ALLUSERSPROFILE%\Start Menu\Programs\Java" can be used for XP. However, your alternative is better, as it is applicable for both OS, which is pretty cool.

No, I actually use the same vbscript that I embed in the MST - along with its main purpose to remove the JAVA start menu folder, I did add few lines that call a batch file from a network share (on our deployment server), using the xcopy command to dump the whole Directory Sun (with subdirs Java, Deployment, and the files there) in Windows Folder. The batch file has a IF statement, so if the Sun directory already exists, it will just exit without any actions; otherwise it will deliver that content. I figured the MST can be handy for pushing future JAVA updates, as BOTH actions in the embedded vbscript (Remove Start Menu Dir and Deploy system-wide config) are conditional, and if there is no need to apply them, they will be skipped...

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.

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?

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="" at the command options for msiexec... Arthur, thank you for pointing that out!

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 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 ; - Type > ENTER "6" without the Quotations! (Type 6 = VBScript file stored in a Binary Table stream) - Source > Type the value from the Binary Table! - Target > NULL (Leave Blank)! 3. Go to "InstallExecuteSequence" Table > Add a row: - Action > Type the 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.

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.