# GPO and Java Updates

**URL:** <https://forum.inductiveautomation.com/t/gpo-and-java-updates/15960>\
**Category:** General Discussion\
**Created:** [November 10, 2017, 2:58pm UTC](https://forum.inductiveautomation.com/t/gpo-and-java-updates/15960 "2017-11-10T14:58:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmisztur2](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmisztur2/32/4243_2.png) [@cmisztur2](https://forum.inductiveautomation.com/u/cmisztur2)\
**Post date:** [November 10, 2017, 2:58pm UTC](https://forum.inductiveautomation.com/t/gpo-and-java-updates/15960/1 "2017-11-10T14:58:15Z")

</div>

I think I have asked this before, but I forgot. My problem is that Java updates are pushed out via GPO and when they do, the installed Ignitions apps are removed.

Is there a workaround to this… maybe with the Client Launcher?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 10, 2017, 4:25pm UTC](https://forum.inductiveautomation.com/t/gpo-and-java-updates/15960/2 "2017-11-10T16:25:26Z")

</div>

Client launcher is definitely the easier way to handle distributing Ignition clients. You can put it on a shared network drive (or just on every machine via GPO) and also push out a prebuilt shortcuts to auto-launch whatever clients/designers:  
[https://docs.inductiveautomation.com/display/DOC79/Native+Client+Launchers#NativeClientLaunchers-CustomLaunchSettings](https://docs.inductiveautomation.com/display/DOC79/Native+Client+Launchers#NativeClientLaunchers-CustomLaunchSettings)
