# Export all Designer Launcher hosts?

**URL:** <https://forum.inductiveautomation.com/t/export-all-designer-launcher-hosts/96831>\
**Category:** General Discussion\
**Tags:** ignition81\
**Created:** [October 4, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/export-all-designer-launcher-hosts/96831 "2024-10-04T15:02:02Z")\
**Posts on this page:** 3\
**Page:** 1

<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:** [October 4, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/export-all-designer-launcher-hosts/96831/1 "2024-10-04T15:02:02Z")

</div>

This seems so basic I'm worried I'm asking a dumb question:

- Is there a way I can export ALL of my designer hosts from Designer Launcher?

For example, if I have a new employee and want to get their Designer Launcher set up for all of our endpoints in one action?

---

<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:** [October 4, 2024, 3:03pm UTC](https://forum.inductiveautomation.com/t/export-all-designer-launcher-hosts/96831/2 "2024-10-04T15:03:41Z")

</div>

Grab the config file and drop it into their system. `~/.ignition/clientlauncher-data/designer-launcher.json`

---

<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:** [October 4, 2024, 3:12pm UTC](https://forum.inductiveautomation.com/t/export-all-designer-launcher-hosts/96831/3 "2024-10-04T15:12:40Z")

</div>

> **[Deploying Pre-Configured Launchers | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/launchers-and-workstation/deploying-pre-configured-launchers#deploying-the-launcher)**
>
> In some cases, it may be desirable to deploy a pre-configured Launcher to remote clients. Doing so bypasses the installation process on the remote machine. The procedure to do so is outlined below, but in short it simply involves installing a...