![Print via Launcher 1 person-setup-machine](https://www.agilicus.com/www/75dcd850-person-setup-machine.avif)
Print Via Service Launcher
Print from a local application to a remote printer via the Agilicus Launcher.
Print Via Launcher
(For site-to-site printing, see also Print Via Service Forwarder).
In this model, which is more suited if we have multiple users sharing the printer, we use a launcher with a local application. When the local application is running, the printer will be available. It will not be otherwise available.
Step 1. Create Network (same as Step 3 in Print Via Service Forwarder, no change)
Step 2. Create Launcher
Step 3. Test via profile
Step 4. Optional, consider enabling desktop integration
Step 2. Create Launcher
![Print via Launcher 2 6d9e6d52 image](https://www.agilicus.com/www/6d9e6d52-image-1024x444.png)
![Print via Launcher 3 ad92f8b2 image](https://www.agilicus.com/www/ad92f8b2-image-1024x753.png)
At this stage we can test. The user will need to install the Launcher on their desktop, via https://profile.YOURDOMAIN. If installed, they can either use the desktop integration, or, run refresh and observe the new icon, launch it.
![Print via Launcher 4 1b1cd532 image](https://www.agilicus.com/www/1b1cd532-image-1024x344.png)
Once the app is up, you can install the printer as in Print Via Service Forwarder (localhost:631, IPP). It will work while the app is running.
We can check with netstat to see it is listening.
![Print via Launcher 5 cb70ee77 image](https://www.agilicus.com/www/cb70ee77-image-1024x606.png)
NOTE: Multiple Printers
The method we are using above to tunnel the printer works best with a single printer. In order to use multiple printers at the same time, when creating the network, use a source-port override such that each printer is unique.
For example:
printer1 -> port 631
printer2 -> port 632
printer3 -> port 633
![Print via Launcher 6 4888907b image](https://www.agilicus.com/www/4888907b-image-1024x468.png)