# How to force client update

**URL:** <https://forum.inductiveautomation.com/t/how-to-force-client-update/9922>\
**Category:** Ignition\
**Created:** [April 16, 2015, 3:19pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922 "2015-04-16T15:19:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [April 16, 2015, 3:19pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/1 "2015-04-16T15:19:00Z")

</div>

I have 2 ignition vision client on the same PC with 2 monitor.  
Some client’s interactions are made with message handler (7.7 feature 🙂 )

When I publish a modification, I have the “Project update available.Click here to update” notification on both clients.

When the operator accept the update on one client, I would like automatically accept update on the other one.

With the tag a client tag change script on [System]Client/System/EditCount, we can catch the event and send a message to the other client, but then how to force the update ???

Any other solution to achieve such a request ? ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [April 16, 2015, 4:10pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/2 "2015-04-16T16:10:04Z")

</div>

Would retargeting to itself do it? ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")

---

<div class="post-metadata">

**Author:** ![nmudge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nmudge/32/3394_2.png) [@nmudge](https://forum.inductiveautomation.com/u/nmudge)\
**Post date:** [April 16, 2015, 5:55pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/3 "2015-04-16T17:55:57Z")

</div>

I know it isn’t the same thing but you could avoid the issue by setting the project Publish Mode to Auto.

Edit:

Yes, Carl is right. That’s what I meant. In Project Properties -\> Client -\> General

Set Update Mode to Push.

Best,

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [April 16, 2015, 6:10pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/4 "2015-04-16T18:10:00Z")

</div>

The setting you’d want isn’t the publish mode, it’s the “Update Mode” - you’d change it to “Push” from “Notify”

---

<div class="post-metadata">

**Author:** ![khashey.ahmed](https://avatars.discourse-cdn.com/v4/letter/k/c5a1d2/32.png) [@khashey.ahmed](https://forum.inductiveautomation.com/u/khashey.ahmed)\
**Post date:** [June 1, 2018, 6:49pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/5 "2018-06-01T18:49:03Z")

</div>

Hi all I have ignition 7.9.5,  
I have set update to auto but my some clients are updating while others are not any ideas???

---

<div class="post-metadata">

**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\
**Post date:** [June 1, 2018, 7:11pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/6 "2018-06-01T19:11:10Z")

</div>

Have you tried restarting/updating all the clients after you first changed the update mode to “Push” and committed?

---

<div class="post-metadata">

**Author:** ![khashey.ahmed](https://avatars.discourse-cdn.com/v4/letter/k/c5a1d2/32.png) [@khashey.ahmed](https://forum.inductiveautomation.com/u/khashey.ahmed)\
**Post date:** [June 1, 2018, 7:33pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/7 "2018-06-01T19:33:06Z")

</div>

yes I tried that some does auto update some don’t

---

<div class="post-metadata">

**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\
**Post date:** [June 1, 2018, 7:58pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/8 "2018-06-01T19:58:25Z")

</div>

For the ones that aren’t auto updating, do they still display the ribbon in the top that prompts users to update when you make commits?

---

<div class="post-metadata">

**Author:** ![khashey.ahmed](https://avatars.discourse-cdn.com/v4/letter/k/c5a1d2/32.png) [@khashey.ahmed](https://forum.inductiveautomation.com/u/khashey.ahmed)\
**Post date:** [June 1, 2018, 8:10pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/9 "2018-06-01T20:10:18Z")

</div>

yes ,  
It will ask me weather I want to publish updates.

---

<div class="post-metadata">

**Author:** ![bfuson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bfuson/32/4597_2.png) [@bfuson](https://forum.inductiveautomation.com/u/bfuson)\
**Post date:** [June 1, 2018, 8:57pm UTC](https://forum.inductiveautomation.com/t/how-to-force-client-update/9922/10 "2018-06-01T20:57:04Z")

</div>

Publish is what you do from the designer. The clients just prompt to download the update, or do it automatically if you have Push mode enabled.

Just to be sure, some clients are auto-updating and others still display this?

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/1/1cea60ee2c40103e128acc6e088a7840b99538d1.png)

Can’t really suggest much besides try killing the Java process, restarting the PC, or reinstalling the JRE.
