Embedded Terminals' configuration
Before you can install a terminal on an MFD, you must create a configuration for it. This is done in the Embedded clients section of SAFEQ Cloud Web UI. You can have any number of configurations, for example, one configuration for MFDs at one site, and another configuration for MFDs of the same brand at another site.
You can use the Filter field to search for the already created terminals.
Creating a new embedded configuration
- Log in to the SAFEQ Cloud Web UI and click Embedded clients.
- Click Add.
- A new dialog window will be displayed.
- The available options depend on the MFD vendor selected. The general options are:
- Device admin username – user name of the device administrator account
- Device admin password – password of the device administrator account
- Automatic logout timeout – timeout for automatic user logout due to inactivity, in seconds
- Print all jobs on card login – release all jobs from the Pull print queue upon user authentication
- Trim zeroes from card ID – remove leading zeroes from cards upon authentication or card self-enrollment
In Mapped devices, select the MFD where you want to use the configuration. Alternatively, you can add devices later on if you haven't added them to SAFEQ Cloud yet. For adding printers, see Printers.
If you don’t see a particular MFD in the list of available devices, make sure you have configured the Terminal Client Service and that you have enabled the Embedded Software option in the settings of the respective MFD in the Printers (Output ports) section of SAFEQ Cloud Web UI.- Click Save.
Deploying the configuration
- After you have created the configuration, click the deploy icon.
- The following options will appear:
- Install and Configure – Deploys (or re-deploys) the embedded application and sets configuration.
- Configure – Sets configuration on previously deployed embedded application.
- Uninstall – Uninstalls the embedded application from the device.
- Manual operations – Describes manual installation steps and links to the documentation.