There are no licensing considerations with Java.
Layering Naming and Versioning
Unidesk recommends including the OS Type and OS bit level in the name, for Example Java Win7x32. For versions remember that when choosing a layer you can see the version name but not the version description. Use naming that will allow you to differentiate versions appropriately. Java is updated frequently so it is recommended to use a format of Date and Time for versions. For example while still in development/testing “2/6/2013 9:57AM QA ONLY”, but when ready for production “2/6/2013 9:57AM”.
Java can easily be downloaded from http://www.java.com. You can also download the installer and install from a network share if desired.
Java, by default, will want to automatically update itself. If Java is allowed to do this, the updates will go into the personalization layer and thereby bloat the personalization with unnecessary updates. It is best to turn off automatic updates completely.
Unidesk recommends using Group Policy to disable automatic updates or you can manually set the flag in the registry when building the application layer. If you are using 32-bit Java on a 32-bit system or 64-bit Java on a 64-bit system the key is HKEY_LOCAL_MACHINESoftwareJavaSoftJava UpdatePolicy. The entry is called EnableJavaUpdate and is a DWORD value. Setting the value to 0 will disable automatic updates. If you are using 32-bit Java on a 64-bit system the key is a little different. It can be found at HKEY_LOCAL_MACHINESoftwareWoW6432NodeJavaSoftJava UpdatePolicy. The value is still the same as above.
There is also a java scheduled updater that gets added to the registry that needs to be removed or the updater will still run. It’s in HKLMSoftwareMicrosoftWindowsCurrentVersionRun it runs the jusched.exe file at startup and should be pulled for VDI images or any image that shouldn’t be auto updating.
So the scheduled tasks that sometimes get added would need to be disabled.
Considerations for Non-Persistent Desktops