Independent Service Manager (ISM)
Last Updated: July 01, 2026
The Service Agent and the ISM are devices, servers, or virtual machines that are always running in your environment, and you promoted them to provide additional service functions in the PrinterLogic app. For example, the Control Panel Application (CPA) An app installed on a compatible multifunction device (MFD) that aids in the release of held print jobs, supports authentication for secure printing, and provides simple scanning functionality., Simple Network Management Protocol (SNMP), and Offline Printing.
The ISM has the same functionality as the Service Agent but with a few differences:
- The ISM does not require installing the Vasion Agent on the device.
- Updates for running services download before the services shut down, which improves the update process.
- You must manually update the VasionPrintServiceManager service. For more details refer to Update the ISM.
- Other services on the ISM Service Agent object can update automatically. For more details refer to Automatic Updates.
Key Points
- The ISM is intended for PrinterLogic Output customers with specific deployment requirements. For all other use cases, use the Service Agent Setup. If you are uncertain whether the ISM applies to your environment, contact your Vasion representative.
Requirements
Minimum Device Requirements
The following are the minimum requirements for the ISM device. You might need to increase these specifications depending on the services you are running. Monitor CPU and RAM usage, and allocate additional resources as needed.
- Device:
- Windows 10 or 11 and Server 2016, 2019, 2022, or 2025.
- Visual C++ Redistributable for Visual Studio 2015-2022 bundle.
- You must install both the x86 and x64 redistributable packages. You can download these packages from the Windows Download Center.
- The Service Agent cannot be a Windows device using an ARM processor.
- Visual C++ Redistributable for Visual Studio 2015-2022 bundle.
- macOS with an Intel processor.
- Ubuntu LTS box 22.04.
- Windows 10 or 11 and Server 2016, 2019, 2022, or 2025.
- 20GB of available hard drive space.
- 8GB of RAM.
- Dual-core processor.
- Vasion Agent installed and authorized.
- The device (server, virtual machine, workstation) must be available on the network for the services to function. Shutting down the device stops the services from running.
Additional CPA Requirements
The number of printers with the CPA An app installed on a compatible multifunction device (MFD) that aids in the release of held print jobs, supports authentication for secure printing, and provides simple scanning functionality. installed that a single Service Agent or Independent Service Manager (ISM) can support depends on the device's resources and operating system (OS). Windows and Linux devices that follow the CPA requirements below support around 1000 printers. If you have a large environment with 1000 or more printers using the CPA, consider adding an additional Service Agent or ISM.
Additional requirements for the printer apps service for the CPA include the following:
- The device running the printer apps service must be on the same network as the printers it is managing.
- For every 100 printers, add an additional 2GB of RAM to the minimum listed above.
- If single sign-on (SSO) is used, monitor RAM usage and increase as needed to handle increased memory usage during check-ins.
- The device that is running the PrinterLogicServicePrinterApp.exe service must have OpenSSL 3.3 or later installed. Windows and macOS should have the correct version of this tool by default. For Ubuntu, you might need to manually update the tool. For more details refer to OpenSSL Documentation.
Authorization Code
Like the Vasion Agent, you must authorize the ISM to communicate with your instance. For more details refer to Device Authorization.
Download the ISM
Follow these steps to download the ISM:
- Select a device that meets the minimum requirements listed above to set up as the ISM.
- In the device's directory, create a folder in a location in which you have admin rights.
- In the Admin Console, go to Tools
Settings
Client, and scroll down to the Independent Service Manager section. -
Select the download button for the OS on the ISM device.
- Place the file in the folder you created.
- Extract the files.
Install the ISM
The scripts folder in the ISM file structure is the location you navigate to when running the commands below. Running the command file with --help offers additional information about the command. For example, install.exe --help.
- Open your preferred terminal window as an admin (Command Prompt, Powershell, Terminal, etc.).
- Change the directory to the scripts folder in the ISM folder.
-
Run the following command:
Copy Codeinstall -u <HOME_URL_HERE> -c <AUTH_CODE_HERE>Replace
<HOME_URL_HERE>with your instance's URL, and replace<AUTH_CODE_HERE>with your authorization code. -
If the service does not start automatically after installation, run the following command:
Copy Codestart - Confirm that the Enable Automatic Updates service is running.
Create a Service Agent Object
Create a New Service Agent
- Log in to the Admin Console.
- Select the folder in which you want to place the Service Agent.
-
Select the New button at the top of the tree structure.
- In the Name field, give the Service Agent object an identifiable name.
- In the IP Address or Hostname field, enter the IP address or fully qualified domain name (FQDN) The complete domain name for a specific device or host on a network, consisting of the hostname, the domain name, and the top-level domain. of the Service Agent object host device.
-
Select Add Service Client.
If you use HTTPS, use the FQDN to reduce potential communication issues. This action is especially important for CPA manufacturers, such as Ricoh, Toshiba, and Kyocera.
In the Admin Console, turn on the services that you want to run on the ISM.
Automatic Updates
The Enable Automatic Updates option applies to the services running on the ISM but not to the ISM service itself. You must manually update the ISM. For more details refer to Update the ISM.
PrinterLogic frequently updates Service Agent features.
While we do not recommend turning off automatic updates, you can do so by going to the Service Agent's General tab and deselecting the Enable Automatic Updates checkbox.
When this setting is deselected, the following services still function but do not update automatically:
- Email Printing.
- Printer Apps (CPA).
- Simple Network Management Protocol (SNMP).
- Offline Printing.
- Simple Badge Release.
- Identity Sync.
- Internal Routing Service (IRS) and External Gateway (Off-Network Print (ONP)).
- PrinterLogic Output.
If you choose to pause automatic updates, set up a regular cadence for turning on the setting.
When you are ready to update the services, do the following:
- Go to the Service Agent's General tab.
- Select the checkbox for Enable Automatic Updates.
- Select Save.
- Wait 10-15 minutes for the services to update.
- Deselect the checkbox for Enable Automatic Updates.
- Select Save.
Update the ISM
Follow these steps to manually update the ISM service (VasionPrintServiceManager).
- On the ISM device, access the PrinterLogic Admin Console.
- In the Admin Console, go to Tools
Settings
Client, and scroll down to the Independent Service Manager section. -
Select the download button for the OS on the ISM device.
- Move the file from its download location to the folder you created for the ISM.
- Extract the files, and select the Replace option when prompted.
- Open your preferred terminal window as an admin (Command Prompt, Powershell, Terminal, etc.).
- Change the directory to the scripts folder in the ISM folder.
-
Run the following command related to your OS:
Copy Codeupdate -u <HOME_URL_HERE> -c <AUTH_CODE_HERE> -
Replace
<HOME_URL_HERE>with your instance's URL, and replace<AUTH_CODE_HERE>with your authorization code. - Confirm that the VasionPrintServiceManager service is running.
Uninstall the ISM
The following steps guide you through uninstalling the ISM from a device:
- Open your preferred terminal window as an admin (Command Prompt, Powershell, Terminal, etc.).
- Change the directory to the scripts folder in the ISM file.
-
Run the following command related to your OS:
Copy Codeuninstall - Delete the folder and contents as needed.
In this topic:




