Java 1.5.0_09 in a locked down environment
Hey Guys
I'm trying to deploy Java Runtime Environment 1.5.0_09 in a locked down environment (users are Power Users on WinXP).
I thought I've found the best solution for us in repackaging that strange vendor .msi. It's clean and small and installs fine. However, when I check the installation through Java's WebSite an error shows up (Applet jrCheck not inited) and I get a timeout. At the end, the website says, "could not find java...".
When installed with an admin user, everything works fine (a java proxy dialog box appears and when entering correct credentials the website finds the correct version).
Why doesn't this java proxy dialog box appear when logged in with PowerUsers?
Where do I need to assign more rights?
Thanks for your help guys
I'm trying to deploy Java Runtime Environment 1.5.0_09 in a locked down environment (users are Power Users on WinXP).
I thought I've found the best solution for us in repackaging that strange vendor .msi. It's clean and small and installs fine. However, when I check the installation through Java's WebSite an error shows up (Applet jrCheck not inited) and I get a timeout. At the end, the website says, "could not find java...".
When installed with an admin user, everything works fine (a java proxy dialog box appears and when entering correct credentials the website finds the correct version).
Why doesn't this java proxy dialog box appear when logged in with PowerUsers?
Where do I need to assign more rights?
Thanks for your help guys
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
AngelD
17 years ago
As power users can only install MSI that do not install/modify any system components (resources) maybe that's the problem, I'm doing a wild guess here. Could you log the installation for both admin and poweruser and compare any differences?
Posted by:
rpfenninger
17 years ago
That's a good idea.
I'll log the installation and compare the log files...
I'll log the installation and compare the log files...
Posted by:
rpfenninger
17 years ago
Ok, I've found the following workaround which does the trick in our environment:
When using the original exe-based Setup instead of the .MSI ZENworks is able to install the software with system rights (using "unsecure system user" option) and that way even with a user logged in with only PowerUser rights, the install runs fine and the application works like a charm.
Thanks
Roland
When using the original exe-based Setup instead of the .MSI ZENworks is able to install the software with system rights (using "unsecure system user" option) and that way even with a user logged in with only PowerUser rights, the install runs fine and the application works like a charm.
Thanks
Roland
Posted by:
AngelD
17 years ago
Great that it finally worked.
Just of interest did you find out if the exe-based setup passed public properties to the MSI and maybe therefore managed to handle this? Also if the "wrapper" added some pre-configuration to the system that the MSI during installation used to get this working?
Just of interest did you find out if the exe-based setup passed public properties to the MSI and maybe therefore managed to handle this? Also if the "wrapper" added some pre-configuration to the system that the MSI during installation used to get this working?
Posted by:
turbokitty
17 years ago
FYI, the disabling of the autoupdate doesn't seem to work in this latest _09 version. You can disable it for the logged on user but it won't stick for new users that login to the box. We had to deploy _05 to get this to work properly.. but I didn't try version _08, _07, or _06.
If you repackaged it, this wouldn't be an issue I'm assuming.
If you repackaged it, this wouldn't be an issue I'm assuming.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.