Java package 6.18 reinstalling itself...
Hi,
With the help of this site and a couple of day's I was able to get a Java package built using Orca and also include all of the usual transforms in the package needed for deployment.
I deployed the package via AD GPO into a test environment of about 40 which went super smooth...
The problem I'm currently experiencing is this:
On random workstations after being restarted the package would start installing itself again and completely breaking Java, Basically to the point where all the files under the Program Files\Java\jre6\bin\client and Program Files\Java\jre6\bin\new_plugin have been completely deleted out.
I've searched the subject up and down on the boards but I'm coming up empty handed, I'm now wondering if I need to include some sort of a Launch Condition in Orca to look Java V6 U18 before it initiates an installation.
At this point any input would be great, I know the package works good but I can't let GPO handle it.
Thank you,
Adi
With the help of this site and a couple of day's I was able to get a Java package built using Orca and also include all of the usual transforms in the package needed for deployment.
I deployed the package via AD GPO into a test environment of about 40 which went super smooth...
The problem I'm currently experiencing is this:
On random workstations after being restarted the package would start installing itself again and completely breaking Java, Basically to the point where all the files under the Program Files\Java\jre6\bin\client and Program Files\Java\jre6\bin\new_plugin have been completely deleted out.
I've searched the subject up and down on the boards but I'm coming up empty handed, I'm now wondering if I need to include some sort of a Launch Condition in Orca to look Java V6 U18 before it initiates an installation.
At this point any input would be great, I know the package works good but I can't let GPO handle it.
Thank you,
Adi
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
This sounds very much to me like you haven't disabled auto-update, which has kicked in and half-worked.
I think your best option is to build a new package, ensuring that auto-update is disabled (how to do that is documented here on AD), set the GPO's scope such that the package is uninstalled, then deploy the new package under a different GPO.
I think your best option is to build a new package, ensuring that auto-update is disabled (how to do that is documented here on AD), set the GPO's scope such that the package is uninstalled, then deploy the new package under a different GPO.
Posted by:
AdiR
14 years ago
Here is what I've got for transforms go:
I have read that adding the following to Orca would disable the update for sure:
CustomAction Table-
Action: DisableAutoUpdate
Type: 98
Source: SystemFolder
Target: reg add "HKLM\Software\JavaSoft\Java Update\Policy" /v EnableJavaUpdate /t REG_DWORD /d 0 /f
InstallExecuteSequence-
Action: DisableAutoUpdate
Condition: NOT Installed
Sequence: 3187
Other switches are:
AUTOUPDATECHECK = 0
IEXPLORER = 1
JAVAUPDATE = 0
JU = 0
MOZILLA = 1
SYSTRAY = 0
I have varified that all of these settings are the same in the registry after the package has been installed.
Update services are not running and the Update Tab is gone, only thing that is there is the Java Quick Starter..
I have read that adding the following to Orca would disable the update for sure:
CustomAction Table-
Action: DisableAutoUpdate
Type: 98
Source: SystemFolder
Target: reg add "HKLM\Software\JavaSoft\Java Update\Policy" /v EnableJavaUpdate /t REG_DWORD /d 0 /f
InstallExecuteSequence-
Action: DisableAutoUpdate
Condition: NOT Installed
Sequence: 3187
Other switches are:
AUTOUPDATECHECK = 0
IEXPLORER = 1
JAVAUPDATE = 0
JU = 0
MOZILLA = 1
SYSTRAY = 0
I have varified that all of these settings are the same in the registry after the package has been installed.
Update services are not running and the Update Tab is gone, only thing that is there is the Java Quick Starter..
Posted by:
anonymous_9363
14 years ago
Are you sure, though, that AutoUpdate isn't running? As per a previous post, you need to trace the component which is being repaired by referring to the ID identified in the Event log.
And why are you using a script to add a registry value? Use the Registry table. Much cleaner and more reliable. That is, after all, why it's there! :)
And why are you using a script to add a registry value? Use the Registry table. Much cleaner and more reliable. That is, after all, why it's there! :)
Posted by:
AdiR
14 years ago
The reason I'm using a script is only because, I've been reading on the board here that by modifying the "Properties" table in Orca doesn't turn off the AutoUpdate feature...
Are you saying that I should be modifying the Registry table itself? If so I don't see where I can change the values under the Registry table to modify the necessary switches, unless you're deleting keys completely.
Is there a process besides jusched.exe that I'm missing??
Here are some pictures of my registry key's and transforms.
http://img684.imageshack.us/img684/2032/orcatrans.jpg
http://img27.imageshack.us/img27/9717/reg2w.jpg
http://img697.imageshack.us/img697/5908/reg1pe.jpg
http://img20.imageshack.us/img20/3791/msiinstall.jpg
Are you saying that I should be modifying the Registry table itself? If so I don't see where I can change the values under the Registry table to modify the necessary switches, unless you're deleting keys completely.
Is there a process besides jusched.exe that I'm missing??
Here are some pictures of my registry key's and transforms.
http://img684.imageshack.us/img684/2032/orcatrans.jpg
http://img27.imageshack.us/img27/9717/reg2w.jpg
http://img697.imageshack.us/img697/5908/reg1pe.jpg
http://img20.imageshack.us/img20/3791/msiinstall.jpg
Posted by:
thugz888
14 years ago
Hi Adir
try checking on the custom action because some of the custom acton is only triggered in installation. whene it is trying to install itself again it is triggering a repair sequence.. some custom action have condition "Not Installed" meaning they only trigger during installation try changing it to "NOT REMOVE". hope this helps.[:)]
try checking on the custom action because some of the custom acton is only triggered in installation. whene it is trying to install itself again it is triggering a repair sequence.. some custom action have condition "Not Installed" meaning they only trigger during installation try changing it to "NOT REMOVE". hope this helps.[:)]
Posted by:
anonymous_9363
14 years ago
I don't see where I can change the values under the Registry table...The registry setting details are all in the 'Package KB' and in various AD posts. Translating those into Registry table entries (don't forget you'll need companion entries in the 'Component' table, too) should be simple enough. See MSDN for details on the Registry table.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.