# Java version client sadness **URL:** \ **Category:** Ignition\ **Created:** [April 12, 2017, 9:13pm UTC](https://forum.inductiveautomation.com/t/java-version-client-sadness/14033 "2017-04-12T21:13:24Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![ryanjmclaughlin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryanjmclaughlin/32/4318_2.png) [@ryanjmclaughlin](https://forum.inductiveautomation.com/u/ryanjmclaughlin)\ **Post date:** [April 14, 2017, 5:10pm UTC](https://forum.inductiveautomation.com/t/java-version-client-sadness/14033/7 "2017-04-14T17:10:55Z")
So I spent some time with the application installer builder **InnoScript**. It’s not bad and fairly straight forward. Basically I build an installer that will put the client launcher in the ProgramData folder along with a custom launch.xml with the gateway name and a JRE folder with 32 or 64bit JRE depending on the client arch. Additionally, the install puts a link in AllUsers Start Menu to **Ignition Applications** which points to the clientlauncher.exe ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/2533ee3c5f8f79fdb98e3843ae72882f26c0cb9a.jpg) The installer can run graphically or completely silent. I’m testing on a few PC’s but looks like I can get IT to approve to deploy to all systems to lighten their headaches with clients and eliminate the need to manage Java installs. Needs some final deployment testing, but so far this is slick. If anyone wants a copy of the installer build script let me know. Only issue is ensuring the client uses the java version in the JRE folder and not the system JRE, but sounds like Inductive will be able to fix that soon. --- _[View the full topic](https://forum.inductiveautomation.com/t/java-version-client-sadness/14033)._