# Ignition Vision Client Version Management

**URL:** <https://forum.inductiveautomation.com/t/ignition-vision-client-version-management/117121>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [September 17, 2026, 5:16pm UTC](https://forum.inductiveautomation.com/t/ignition-vision-client-version-management/117121 "2026-09-17T17:16:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brandon\_Hanson](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@Brandon\_Hanson](https://forum.inductiveautomation.com/u/Brandon_Hanson)\
**Post date:** [September 17, 2026, 5:16pm UTC](https://forum.inductiveautomation.com/t/ignition-vision-client-version-management/117121/1 "2026-09-17T17:16:34Z")

</div>

Just curious what everyone else is doing for version management of ignition vision clients. Over the last several versions, we've noticed that sometimes the client will no longer connect / display available projects on from an updated gateway until the client software is manually updated. How is everyone else doing this? Custom wrappers, RMM, etc?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 17, 2026, 5:53pm UTC](https://forum.inductiveautomation.com/t/ignition-vision-client-version-management/117121/2 "2026-09-17T17:53:32Z")

</div>

The client launcher just needs to be at least as new as the gateway. Launchers are backwards compatible. The new 8.3 launchers can launch clients for v8.1 gateways. You should simply install the latest available launcher everywhere, even if you haven't yet deployed that newest gateway version anywhere.

Launchers can usually target gateways a few versions newer, so you don't have to go wild.

Consider doing this every six months.