Re: JRE Mistake - Help
- From: Dennis Procopio <DennisProcopio@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Jul 2007 06:40:00 -0700
Jules,
Yes I did notice I wasn't the only one experiencing problems with this
package. I removed the "install at logon" checkbox from the new policy and
it doesn't seem to be harming the systems or going crazy anymore, but your
description of the problem appears to be dead-on. Thanks for the reply, it
may help if I have to do further troubleshooting or some explaining to
management ;-).
Dennis.
"JulesKremer" wrote:
The Java Runtime version 1.5 release 9 (as you described) has a update.
problem. It can't be removed correctly in one step, but it can't be
updated directly to a new version either, as it fails with an error. But
you can correct this. After this update error there is a update file
left behind in the application data section (the name depends on the
update number you are running, has almost the same name as your
downloaded executable). You can start it there by hand, or retrieve the
file and deploy it on all systems running 1.5 release 9. After that
procedure, you can do what you want. Upgrade further, or complete removal.
Jules
Dennis Procopio wrote:
I needed to deploy Java Runtime 1.5.0_09 to a select group of managers for
use with ADP timeclock software. I created a group called ADP Managers, and
applied a GPO to assign the package via user software installation to only
that group via security filtering. What I failed to realize was that these
users were not local administrators, so the package did not take. I decided
to "start from scratch." Although the policy had "uninstall when falls out
of the scope of management" enabled, I did not have the patience (regrets!)
to see to it that group policy was refreshed for all of the users and that
the machines were rebooted. Instead I simply deleted the GPO, left all of
the users in that group, eventually elevated them all to local admins, then
redeployed the package. Now what happens is everytime the users log in,
"Removing Application Java Runtime 1.5.0_09" runs, throws an error in the
event log, then runs "Installing Java Runtime 1.5.0_09".
Now...
The event log shows that the uninstallation succeeded, however the policy
that dicatated uninstallation when falling out of the scope of management was
deleted weeks ago.
The new policy's installation routine succeeds, it does not have "uninstall
when..." checked.
2 questions:
Why is the uninstallation still running when that GPO no longer exists? The
group membership never changed..could it still be processing it because I am
using the same originally filtered group?
If the event log says the uninstall succeeded, then why is it doing it every
logon?
I'd really like to stop this removal routine...please let me know if you
know how.
Thanks!
- Follow-Ups:
- Re: JRE Mistake - Help
- From: JulesKremer
- Re: JRE Mistake - Help
- References:
- Re: JRE Mistake - Help
- From: JulesKremer
- Re: JRE Mistake - Help
- Prev by Date: Re: Locking Computer Name
- Next by Date: Re: JRE Mistake - Help
- Previous by thread: Re: JRE Mistake - Help
- Next by thread: Re: JRE Mistake - Help
- Index(es):
Relevant Pages
|
