Hello, everyone and welcome to another one of my IT tutorials. In my previous Java video, I showed you how to deploy java using domain group policy and a lot of people ask me how would we install updates later and how to disable the automatic updater that comes with installation? Well, now that the newer version of Java has been released, I can answer both of those questions. So, let's start like last time by getting the Java installation, the link to the site will be included in the description of the video. In case you don't know where to get it, I strongly recommend you to watch my first video, as I may skip a few steps in this one, since I already talked about them before.
Okay, now remember one to start the installation, but we don't actually want to run it so leave this window open and go to your Start. Menu hit, run and type in % app data % then go one directory up to the application data, local now Sun Java and the latest version, which is seven point zero four and want to copy both of these to a shared location on your network. If you have file servers, you would probably want to put it there. If you don't well, you might want to create a shared location on your active directory. If you recall from our previous example, we put these files in the shared location on active directory, since we don't have a file server in the system. So let's just go there. Perform silent installation of Java using script here.
Let'S copy these and the shared location was in C software and we have JRE 7.3. So you just make a new one: zero for good I'll, just copy the folder but night. So we paste it here and now we open our group policy management just here or through Administrative Tools, group policy and remember this group policy object Java deployment. Yes, now we don't want to create new one, since this is going to be an update. We just right-click on the previous deployment hit edit once again go to software software installations, new package navigate to the new Java MSI file, which is in the share location. My Explorer already defaulted to the shared location, which is sb/xa DDC with this computer's name, and then software, but we don't want Acura read. That was my adobe deployment.
We want Java, 7 or 4 and this MSI now in this case we want instead of a sign. We want to pick advanced then go to the upgrades tab. As you can see, the installer already knows that we're going to be upgrading the previous package that we have deployed Java 7 update 3. But if this screen was blank like so you would have to go to add and then the packages that you can possibly upgrade will be listed here. So you pick that package and you can do uninstall existing package, then installed upgrade package or the package can upgrade over the existing package. Unless you know the package absolutely can upgrade over existing package, you should just pick. Uninstall might take a bit longer time, but it will work for sure, and then you hit
OK, since this server is also a member of the domain at this, software installation should apply to it as soon as we restart. So, let's do just that restart the server and see who installs standby add the service starting and right after applying computer settings. We should see Java being installed and there you go as we picked uninstall previous version install new one, its first removing Java update 3. Oh, and in terms of this, you have to keep the old MSI file in the shared location until all your systems remove the old version of Java. If you delete that MSI file, the uninstall will fail and probably install the new software will fail as well. So keep it there until you're sure that all your systems have uninstalled the old version, and if we check the control panel, we should see no more update 3 and only update 4 is there and there we go Java. Update 4. Is there update? 3 is gone.
All right, removing automatic update for Java is not going to work 100 % of the time since Sun and now Oracle keep changing the way their updater works, but there are two ways to do it. First, we can add a registry entry which will attempt to disable the update and second, is to remove the updated file itself. I'Ll show you how to do both of them through group policy management. So start group policy management go to edit of Java deployment. Group policy. Go to computer configuration preferences windows settings and let's do the removal of the file first. This will guarantee toward for sure. So we create a new file operation instead of update. We big delete and the file is actually this: its % Program Files open parenthesis, x86. Close parenthesis %, if you have 32-bit systems, obviously you don't have to include the x86. The rest of the path is common files. Java Java space update Ju check. Now, a very peculiar thing happened here. When I deployed this Java installation, it did not install an updated with it. I don't know if it's part of the MSI package or because it's a server, but I can't navigate to this file using browse, because this file just doesn't exist if it does exist. In your systems, this will work just fine and we can pick this so it users don't get Ballard by random errors, hit, ok and that's it.
If you have both 32-bit systems and 64-bit systems, you can just add two file operations and the second one would be also delete, but instead Program Files x86, you just leave program files and suppress errors, hit. Ok now the second one is creating the registry. So it's going to be new registry item, create we want to create it in local machine. The key path will be Java. Soft Java update policy and the name is going to be enable Java update. The value type will be a D word and the value itself will be 0, and then you hit OK, alright. Now that we have added this key, you can exit out the group policy and you can be sure that the updater will not work. Now. I didn't test this, I'm pretty sure there are not going to be errors that the file is missing once you delete the Ju check as many users online suggest that solution, but feel free to comment, and let me know if it worked for you. Thank you for watching. I hope you enjoyed and found this helpful, like is always appreciated.