# Setting Gateway Name via Script

**URL:** <https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833>\
**Category:** Ignition\
**Created:** [June 13, 2024, 7:27pm UTC](https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833 "2024-06-13T19:27:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacob.ramirez](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jacob.ramirez](https://forum.inductiveautomation.com/u/jacob.ramirez)\
**Post date:** [June 13, 2024, 7:27pm UTC](https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833/1 "2024-06-13T19:27:37Z")

</div>

Is there a way to set a gateway system name via a script?

I want to be able to change the name on an Ignition Edge system without logging into the gateway config page.

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [June 14, 2024, 11:53pm UTC](https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833/2 "2024-06-14T23:53:08Z")

</div>

Forgive my lack of vision, but I'm having trouble imagining a use case for this. Just out of curiosity, how often would this be done, and if it's a regularly needed thing, why? What problem is solved by changing the gateway system name via scripting? Perhaps somebody in the forum will know an alternate, more conventional approach that could fix the underlying issue.

---

<div class="post-metadata">

**Author:** ![jacob.ramirez](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jacob.ramirez](https://forum.inductiveautomation.com/u/jacob.ramirez)\
**Post date:** [June 15, 2024, 1:02am UTC](https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833/3 "2024-06-15T01:02:13Z")

</div>

It'll be done on remote edge systems. I want the gateway name to be the same have as the equipment. And when you load in a backup. It'll be nice to change that quickly via a tag remotely.

---

<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:** [June 15, 2024, 12:06pm UTC](https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833/4 "2024-06-15T12:06:52Z")

</div>

When you restore a gateway backup via the [gwcmd](https://www.docs.inductiveautomation.com/docs/8.1/platform/gateway/gateway-command-line-utility-gwcmd#command-line-utility-options) command-line tool, you have the option to rename the gateway.

Since it is documented, you can expect it to be supported long-term. Any monkeying around with the gateway's internals via script will not be.

---

<div class="post-metadata">

**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\
**Post date:** [June 15, 2024, 2:20pm UTC](https://forum.inductiveautomation.com/t/setting-gateway-name-via-script/91833/5 "2024-06-15T14:20:07Z")

</div>

Great to know, @pturmel. There are multiple use cases for this sort of thing. OP wants to name deployments at the edge. I want to streamline and minimize risk for deployments of our Ignition-based product at sites where only gateway and tag provider names need to change from a standard gwbk, and then the rest of the plant is deployed via scripting to populate the tag provider.