In reading lots of posts about GPOs I am realizing that my approach is probably really wrong. I create a GPO for installing say Java618. Then I link this GPO to an OU that I might call Java618. Then when I want to install it I move the computers into that OU and reboot them a couple of times. Then I move the computers back to the default computers OU. This works much of the time.

With Java I have taken the position that leaving the older versions is probably ok, so I have a GPO for each version. I considered trying the option to upgrade another GPO version but sometimes that version was skipped for some reason, or one of the techs in our organization installed it manually or something.

So I am baffled. If any one has a particular resource where I could read about this it would be good. I just find so many different ways to do it that I don't know which one would work best.

Thanks.

Jane
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
Check my method for deploying apps via AD as explained in a nutshell:

1. add GPO's to the computer's OU - DO NOT move computers to where the GPO is - this is because policies apply to whatever is in that OU at that time. Setup your OUs in a similiar structure to your business departments is a good starting point. - also have seperate OUs for computers and users! You can't add GPOs to the default container.

2. Create one Java install GPO - add to that your latest java MSI to install - you can apply the same GPO to multiple OUs or set up a heirarchical relationship between departments so common GPOs can flood down the branches of your directory from top down.

3. when oracle releases a newer java version, remove the software installation from the actual GPO - upon doing so you will be prompted to either immediatly remove the software on the computers (which will actually happen next reboot) or leave the software version in place. I only keep the latest version of Java on personally and see no benefits for our organisation keeping older versions around.

4. add the new java msi to the same java GPO you set up. This is the cleanest way I've found to keep apps up to date.
Answered 02/09/2011 by: squeakstar
Orange Senior Belt

Please log in to comment
0
Thanks so much. I will take a look at that. I assume that if a computer already has java, that it will not try to install it each time it reboots.

Jane
Answered 02/09/2011 by: jfrasier
Seventh Degree Black Belt

Please log in to comment
0
Another question. Can I do the uninstall and install in the same reboot? Or do I need to remove the old one and say to uninstall and reboot. And then add the new installation and reboot?
Answered 02/09/2011 by: jfrasier
Seventh Degree Black Belt

Please log in to comment
0
I have created the same exact GPO at each site for my software, the only difference is the location is pointing to each site for the application share to avoid over the wan installs. That being the case, if I did a mass deployment in the home office, setting these machines up and installing the software all in one site to avoid over the WAN traffic, then moved those machines into the OU for each site, will things stay intact for will I face issues? Mainly since the only thing that is different is the app share.

I hope I am not confusing. thanks for the help.
Answered 03/07/2011 by: aahmad
Senior Yellow Belt

Please log in to comment
0
I have developed exactly the same precise GPO at each web site for my application, the sole variation is the location is pointing to just about every web site to the software share in order to avoid above the wan installs.[/align]
Answered 08/02/2011 by: Stephen.herbert
Yellow Belt

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