I recently followed Sun's guide to extract the . msi package and .cab file for Java 6u18 and deploy it via GPO software settings. In the same GPO is a startup script that uninstalls old JREs via msiexec.exe as such:

msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D01600##}

I tested this GPO on a couple dozen machines and it worked properly on all of them. However after deploying this GPO to a more populated ou, I've had a number of machines hang on the JRE installation (at the "installing managed software" text).

Am I going about this in a fundamentally incorrect way? Is there an issue with the order the software install and startup script are executing? Do I need to change something with a transform?

I appreciate any advice or links that may help me as I'm a bit lost at the moment.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Not sure if you're doing something wrong per se, but i always just use standard GPO settings with little tweaking. I get the GPO to uninstall the previous version when i remove the old software from the policy as opposed to getting java to do anything clever or using any switches. This has worked fine for me so far, apart from a few versions back (6r10 was it ?) whereby there was a bug with the msi and it would just not uninstall and i had to extarct it with a pair of pliers [;)]

I do tend to keep GPO categories for installing software, instead of having one big GPO and tend not to pile too many changes at once around the network, sometime distributing software ar a sub OU level gradually rolling across the company for big installs.
Answered 02/12/2010 by: squeakstar
Orange Senior Belt

Please log in to comment
0
Enabling MSI logging on one of the recalcitrant workstations will show you exactly what's going on. Make sure you use verbose logging and that you turn it off when you're done.

JREs are happy to live side-by-side. Since they're so small (relatively) and local storage so cheap, I leave them in-situ. If you want to uninstall older versions, leave that to the GPO's group members falling out of scope when you remove them from that group.
Answered 02/12/2010 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

Enabling MSI logging on one of the recalcitrant workstations will show you exactly what's going on. Make sure you use verbose logging and that you turn it off when you're done.



hey, can you quickly explain how to turn on verbose MSI logging on for us newbs???
Answered 02/19/2010 by: squeakstar
Orange Senior Belt

Please log in to comment
0
Honestly, if you lead with your chin... http://www.lmgtfy.com/?q=group+policy+enable+logging
Answered 02/19/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity