# Gateway Commissioning EAM Upgrade

**URL:** <https://forum.inductiveautomation.com/t/gateway-commissioning-eam-upgrade/75328>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 21, 2023, 10:24am UTC](https://forum.inductiveautomation.com/t/gateway-commissioning-eam-upgrade/75328 "2023-06-21T10:24:50Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [June 22, 2023, 2:04pm UTC](https://forum.inductiveautomation.com/t/gateway-commissioning-eam-upgrade/75328/5 "2023-06-22T14:04:13Z")

</div>

It looks like it might be off to _Registry Editor_ to set environment variables for Windows services (I'm unsure if there is a UI for this hidden somewhere 🤷):

 ![2023-06-22 at 8.57 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/f/eff6a1f162bfaafaf5dec8076b7af554ef66a846.png)

Looks like you can go to `HKLM\SYSTEM\CurrentControlSet\Services\<service name>` and define a _Multi-String_ registry key called `Environment` and put individual `<name>=<value>` definitions on each line. The key wasn't there for me after a fresh installation. Upon submitting, it produced a warning about stripping empty strings (even though I tried to not have a blank newline in the value data) but seemed to work just fine.

With Windows you could probably even distribute this via Group Policy if your machines are domain-joined.

---

_[View the full topic](https://forum.inductiveautomation.com/t/gateway-commissioning-eam-upgrade/75328)._