Context
This article describes the process to install the Ricoh SOP Embedded App.
Prerequisites
HCP Prerequisites:
- Ensure the device package firmware is up to date and conflicting print management apps have been removed from the device
- The device has been rebooted and not in use by an end user or administrator
- Secondary Gateway Server installed and accessible from the LAN/WAN where the device is installed
-
- Secondary Server version 3.14 or later
- Terminal Client Service added to the Secondary Gateway Server
- Document Output Service added to the Secondary Gateway Server
- Storage Service added to the Secondary Gateway Server
- Ensure the FQDN of the Gateway is added to the list of domains in 'Portal Name'>Settings> Domains
- Ensure the hostname of the Secondary Server is set in the 'Secondary Server > Settings >Server Domains
-
- A valid and available Embedded device License
- Administrator Privilege's Are assigned to the user performing the installation
Firewall and Network Prerequisites:
Ensure the following Network Ports are open between the Secondary Server and the Ricoh Device and that the Secondary Server is online:
Port |
Protocol |
From |
To |
Description |
161 |
UDP |
HCP Terminal Client Service |
Ricoh MFP’s |
SNMP management |
443 |
TCP HTTPS |
HCP Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to the MFP |
8080 |
TCP HTTP |
HCP Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to Ricoh MFP’s |
51443 |
TCP HTTPS |
HCP Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to Ricoh MFP’s |
8710 |
UDP |
HCP Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to Ricoh and HP MFP’s |
80 |
TCP HTTP |
HCP Terminal Client Service |
Ricoh MFP’s |
Deployment of the embedded client to HP MFP’s |
Ricoh Device Prerequisites:
- Ensure the device firmware is updated
- Local Area connection to the Secondary Server
- An Administrator Account to access the Ricoh Device with the below permissions configured:
NOTE: You must use an admin account with a password which is not blank.
Installation Process
Carry out the following configuration steps from the HCP Web Console
1 Create an Embedded configuration
The embedded configuration option holds settings which will be applied to the device upon installation. One Embedded Configuration profile can be used to configure multiple Ricoh devices.
1.1 From the HCP Web console select Settings > Embedded
1.2 Apply the following settings:
- Name - Give your configuration a name
- Vendor - Select "Ricoh" as the Vendor
- Device admin username - Set the Ricoh Device Admin Username. The username must be a machine administrator used to login at the device to apply configuration settings
- Device admin password - Set the Admin password. Note: A blank password cannot be used.
- All other settings are optional. Set these as desired.
2. Create a Printer
1. Login to the HCP Web Console
2. Select the "Printers" option from the settings menu
3. Click "Add"
4. Apply the following settings:
- Name - Add a descriptive name
- Address (IP or DNS) - Add the target devices IP Address or Hostname
- Description - Add a device description
- Vendor - Select "Ricoh" from the drop down menu
- Model family - Select "Ricoh SOP"
- Output Type - Select a supported print language
- Create Matching Input Port - Enable
- Embedded configuration - Select the configuration made in Step 1
- Client Terminal Services - Select the name of the target secondary server which will manage the device
- Click "Save"
3. Install the embedded app
1. Navigate to Settings > Embedded
2. Select the Embedded Config by clicking the select icon
3. Select the target printer from the list
4. Click on "INSTALL AND CONFIGURE"
5. Successful installation will display the "Installed" status
Troubleshooting
- Installation fails with error "rxspServlet not found" - Restart the device ensuring that the RXOP Java App status is "Starting Up".
- Have found this occurs often - HCP deploys the rxsp servlet but doesn't start it so further deployment of the SOP client fails. Always needs a boot after this.
- Installation fails with error "Cannot retrieve terminal info" - A communication issue exists between the device and Secondary Server. Check network ports, the correct Secondary Server has been selected, DNS is resolved correctly and that the Prerequisites have been satisfied.
- Installation/Configuration fails with "Cannot get terminal information" or "unknown terminal" see article here to troubleshoot.
- Print jobs are received by the device but not printed. The device Print Job Error Log shows "Access denied" for the released job - Set the "Printer Job Authentication" setting on the devices Web Image Monitor > Configuration > Device Settings > User Authentication Management to "Simple (All)"
- When trying to authenticate in the Pull Print App "Unknown Device" error is displayed. Please view the KB Article here.
Comments
0 comments
Please sign in to leave a comment.