SlideShare a Scribd company logo
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
1
@Remote - New Remote Service
Field service training
Solution Master
Full training
Created by: Group L&D Version: 9.1.a Classification: Ricoh Family Group internal use only
2
Objectives
 After completing this training you should be able to:
 Explain the features of @Remote-NRS
 Install, configure and maintain @Remote-NRS
 Troubleshoot @Remote-NRS
3
Requirements
 Training material and manuals
 Devices with GW controller
 RC Gate:
 Basil or UZ-A1 (incl. options)
 PC workstation with MS IE 6.0 or higher
 User account for the Center Server GUI
4
Pre-requisites and exam
 There are no pre-requisites for this training.
 After this training, you can do the exam on My-Ricoh.
5
Module overview
 1. @Remote overview
 2. Installation
 You can choose to do Chapter 2.2 Installation Basil and/or
Chapter 2.3 Installation UZ-A1.
 3. Maintenance
 4. Reporting website
 5. Troubleshooting & support
 Appendices
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
6
1. @Remote overview
7
Chapter overview
 1.1 Introduction
 1.2 System overview
 1.3 Center Server GUI overview
 1.4 Product compatibility
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
8
1.1 Introduction
9
What is @Remote-NRS?
 @Remote is a printing device management service.
 With @Remote, the service organisation monitors, manages, and
services the customer’s printing devices over the Internet.
 With @Remote, the service organisation deliverers detailed
device reports to the customer through a website.
10
@Remote features
 Remote monitoring of counter and device information.
 Remote monitoring of alerts and service calls.
 Remote monitoring of supply calls.
 Remote firmware update.
 Remote SP-Mode reading/writing/executing.
 Reporting website.
11
Why should the customer want @Remote?
 Outsourcing to the service organisation
 Automatic meter reading process.
 Automatic toner supply process.
 Automatic service call handling (pro-active service).
 Reduce device downtime
 Fast notification of service calls to the service organisation.
 The service organisation can remotely analyse problems
(e.g. SC-call history).
 The service organisation can remotely do adjustments on
devices (SP-mode / firmware-update).
 Detailed fleet reports
 Device management reports.
 Supports TCO consultancy (reduce running costs).
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
12
1.2 System overview
13
System overview (Center Server)
Service organisation
Center Server GUI
Center
Server
Customer
Monitor/manage
device data
External RC-
Gate
(Basil/UZ-A1)
Internal
RC-Gate
(Cumin)
Device data
14
System overview (Reporting Server)
Reporting
Server
Center
Server
Customer
Device
counter
data
Reporting website
Service organisation
Manage
reporting
website
15
RC-Gate (UZ-A1, Basil and Cumin)
Center
Server
Customer environment
Cumin
Device data
External
RC Gate
SNMP / HTTPS
HTTPS / SMTP (E-mail
only Basil)
HTTPS
16
Other RC-Gate type
 The UZ-S1 is not within scope of this training.
 This RC-Gate is described in a separate training module on
WICE.
 Remote Communication Gate S with @Remote
Connector.
 Server application based on Web Smart Device Monitor.
17
Product positioning 2/2
 Target Customer segment by appliance
 For customer with over 1000 device:
 UZ- S1 Pro (main) and UZ- A1 1000 Op (sub)
 For customer with 100 – 1000 device:
 UZ- A1 1000 Op (main) and UZ- S1 Pro (sub)
 For customer with under 100 devices:
 UZ- A1
L
S
M
GMA, MA
UZ-S1
UZ-A1
UZ-A1 1000 op
1000 Devices
100 Devices
20%
(av.2,000 device)
43%
(av.250 device)
38%
(av.22 device)
@Remote connecting MIF ratio
(Average device per appliance)
18
Differences between the External RC Gates
Category: RC Gate BN RC Gate A1
Device Type: @Remote
Device
GW MIB
Device
Other MIB
Devices
@Remote
Device
GW MIB
Device
Other MIB
Devices
Network
Protocol
to Device
SOAP SNMP V1/V2 SOAP/
REST*1
SNMP V1/V2/V3
Monitored
Devices
(Un-
Manage)
500
(including 100 Managed Devices)
100/1,000*2
Registered
Devices
(Manage)
100
(Including 5 Standalone)
500
1,500 (including 1,000 managed device) *2
PSTN*4
Yes Yes Yes No
E-Mail*5
Yes Yes Yes No
User Code
Counter
capturing
*3
No No No Yes No No
19
Features on UZ-A1, that are not available on Basil
 Support SNMP v3
 SNMP v3 has more security options then previous versions.
 Some companies demand the use of SNMP v3 capable devices
before they allow the device onto their network.
 No e-mail communication between RG gate and Center server.
(e-mail notification still available.)
 New RFU setting
 Ability to block certain times where network activity may be high.
 User code Counter Capturing
 For in-house cost recovery
 NOT in 1st production but after Firmware update (Firmware
expected March 2010)
 Prepared for Cosmos controller support
 UZ-A1 supports REST a protocol supported by future Cosmos
products
 NOT in 1st production but after Firmware update. (TBA)
20
RC-Gate - Center Server communication
 Communication between the RC-Gate and Center Server is
always initiated by the RC-Gate.
 When you enter a request on the Center Server GUI to carry out
an action on an RC-Gate, the Center Server does NOT contact
the RC-Gate, but waits to be polled by the RC-Gate.
 The RC-Gate polls the Center Server once every hour.
 The RC-Gate does not send device data when polling the
Center Server.
Center
Server
Customer environment
Cumin
External
RC Gate
Poll Center Server (1/hour)
21
Security
 The Center Server does not communicate to the RC-
Gate/devices without any indication from customer side.
 Data is only transmitted after mutual authentication (SSL)*
 Device data is encrypted before sending*.
 Center Server security
 Physical security
 Redundant / load balancing
 IP access restrictions
 Backup / restore
 The external RC-Gates are ISO 15408 certified
(see next slide).
22
ISO 15408 certificate
 The ISO 15408 is an international standard for evaluating
security on IT equipment.
23
Used ports & protocols
Occasion Comm. direction Port no. Protocol Type
1 RC Gate is connecting to device by FTP RC Gate => Device 20 FTP TCP
2 RC Gate is sending firmware. RC Gate => Device 21 FTP TCP
3 RC Gate is sending information by E-mail. RC Gate => Center
Server
25 SMTP TCP
4 RC Gate is capturing MIB information of device. RC Gate => Device 161 SNMP UDP
5 RC Gate is authenticating in POP before SMTP. RC Gate => POP Server 110 POP TCP
6 RC Gate is sending notification to Center Server via
HTTPS.
RC Gate => Center
Server
443 HTTPS TCP
Device is sending notification such as Service Call. Device => RC Gate
CE is operating RC Gate via laptop. CE’s laptop => RC Gate
RC Gate is requesting firmware information. RC Gate => Center
Server
7 RC Gate is capturing device information. RC Gate => Device 7443 HTTPS TCP
8 RC Gate is sending rescue information RC Gate => Device 7444 HTTPS TCP
24
Terminology
 Center Server
 (Center) GUI Server
 Remote Gateway Center System
 @Remote Center GUI Server
 Communication Server (GUI)
 Reporting Server
 (Reporting) web portal
 @Remote.net
 Basil
 External Box
 RC Gate (BN)
 UZ-A1
 External Box
 RC Gate A1
 Cumin
 NRS Embedded Device
 RC Gate (CN)
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
25
1.3 Center Server GUI overview
26
Internet browser configuration
 Supported browsers: Internet Explorer 6 or 7.
 The Center Server GUI website uses ActiveX.
 Configure the following in your browser ‘Internet Options’:
 For other initials settings, such as ‘deleting temporary internet files’ and
‘enabling cookies’, see the Center Server GUI Manual.
Add Center Server GUI website (https://rcg.support.ricoh.com) to ‘Trusted Sites’.
Enable Run
ActiveX
controls and
plug-ins’.
27
Center Server GUI login
 https://rcg.support.ricoh.com/atremotecenter/MainServlet
Login
Start screen (information)
Installation of ActiveX
modules (only at first
login or GUI changes).
28
Deleting ActiveX modules (OCX files)
 Files to delete Center Server GUI OCX files from your PC.
29
Change/forgot password
 A link to the ‘Single User ID website’ is available on the
home page of the Center Server GUI.
 Use this website to change your password or if you forgot
your password.
‘Single User ID’ website
https://suid.isd.ricoh.co.jp/index_en.html
30
Sites, Service Depots and Appliances
 Device data and user access is grouped into:
 Sites (service organisations)
 Service Depots (service locations)
 Appliances (RC-Gates).
Ricoh France
Customer 1
Appliance
Appliance
Appliance
Customer 2
Appliance
Appliance
Appliance
Customer 3
Appliance
Appliance
Appliance
Ricoh Italy
Ricoh Italy office
Appliance
Appliance
Appliance
Customer 1
Appliance
Appliance
Appliance
Customer 2
Appliance
Appliance
Appliance
Ricoh Spain
Ricoh Spain West
Appliance
Appliance
Appliance
Ricoh Spain East
Appliance
Appliance
Appliance
Customer 1
Appliance
Appliance
Appliance
Sites
Service
Depots
31
Center Server GUI menu overview
 The available/displayed menus depend on your access
rights.
Registration
Search
Counter CSV
Supply CSV
Service Call
Firmware
Maintenance
Administrator
32
Searching Appliances/Devices basics (1/3)
 Search Appliance example
Select Service Depot
Search Appliance
33
Searching Appliances/Devices basics (2/3)
 Appliance List
Customer Name/ID Appliance S/N Appliance type
34
Searching Appliances/Devices basics (3/3)
 Device List
Device List
Select Appliance
35
Load Site Information
 Select the ‘Load Site Information’ button to update the
available Sites / Service Depots in drop-down menu’s.
 Examples when to click on ‘Load Site Information’:
Service Depot drop-
down menu is empty.
Drop-down menu shows Service
Depots from previous login account.
An error message appears when you
select a Service Depot.
Or
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
36
Exercise 1
 Login to the Center Server GUI.
 Search for an appliance.
 Look at the Device List of an appliance.
 Make yourself familiar with the available options.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
37
1.4 Product compatibility
38
Device types
 There are 3 types of devices:
@Remote/NRS (HTTPS)
device
Cumin
External
RC Gate
HTTPS
GW-MIB (SNMP)
device
MIB (SNMP) device
(competitor/OEM/pre-GW)
HTTPS
SNMP
SNMP SNMP
39
Service level per device type
40
Counter capture level per device type
Device Usage Information @Remote Device
(NRS Device)
GW MIB device MIB device
Total Supported Supported Supported
Copy/Fax/Print Supported Supported N/A
Color/Black Supported Supported N/A
Scanner/LS/Scan to e-mail Supported N/A N/A
A3/DLT Supported N/A N/A
Duplex Supported N/A N/A
ADF Supported N/A N/A
Dot Coverage Supported N/A N/A
# of Replaced toner Supported N/A N/A
By Toner Supported N/A N/A
By Paper size (A3/A4,,etc) Supported N/A N/A
By Paper type Supported N/A N/A
By Mode (S to D, N-up) Supported N/A N/A
By Paper Tray Supported N/A N/A
By Finishing (Staple/Punch) Supported N/A N/A
By P/J (Page/Job) Supported N/A N/A
By PDL (RPCS/PCL/PS) Supported N/A N/A
SC/CC/MC call Supported N/A N/A
Supply call (end / near end ) Supported Supported N/A
41
Product compatibility list
 This list specifies the level of @Remote functionality per
product.
@Remote
Compatibility Jul31 2009
Attachment (double click to open)
42
Device requirements
 @Remote devices (HTTPS):
 Network connected.
 Autumn 2003 and later devices.
 Security (DESS) module.
 Correct Machine Certificate installed.
 Correct ID2 Code.
 GW-MIB / MIB (SNMP) devices:
 Network connected.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
43
2. Installation
44
Chapter overview
 2.1 Installation overview
 2.2 Basil installation
 2.3 UZ-A1 Installation
 2.4 Cumin Installation
 2.5 Removal
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
45
2.1 Installation overview
46
Customer pre-survey
 Center Server preparation
 Customer name
 Site / Service Depots
 Find out information required to install Basil / UZ-A1 /
Cumin / devices and calculate installation time.
 Network infrastructure
 Proxy information
 Gateway information
 Device IP-ranges (how many Basils/ UZ-A1s / Cumins?)
 IP-addresses for Basil(s) / UZ-A1(s)
 SNMP community names.
 Device models & firmware levels
 CSV file with Hostnames (if required)
47
Appliance registration overview
 You have to pre-register an Appliance (RC Gate) to the Center
Server before you can install it at the customer site.
1. Pre-registration on Center Server GUI
2. Installation at customer site
Cumin
Register
RC Gate to
Center
Server
Request Number ? ………
Request Number = xxxxxxxx
RC Gate
registered
to Center
Server
48
Device registration with a Basil/UZ A1 overview
 Basil
 Managed devices
 Auto Discovery
 Monitored devices
 UZ-A1
 Managed devices
 Auto Discovery
 Monitored devices
49
Managed devices
Registered in
External RC-Gate:
• Device details
• Device IP address
Registered in device:
• External RC-Gate IP
address
50
Monitored devices
External RC Gate
scans the network
and reads standard
MIB info (total
counter) from every
found device.
51
Managed or monitored
52
How many devices can be registered?
 Basil / Standard UZ-A1
 Can ‘monitor’ 500 devices in total.
 You can set a maximum of 100 devices (out of the 500) to
‘managed device’.
 The rest of the devices are ‘monitored’.
 UZ-A1 including optional memory.
 Can ‘monitor’ 1000 devices in total.
 You can set a maximum of 1000 devices to ‘managed’.
 The rest of the devices are ‘monitored’.
 Cumin
 Always has 1 device (the device itself) registered as
‘managed’.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
53
2.2 Basil installation
Click here to go direct to the UZ-A1 training.
(if you want to skip the “Basil installation chapter”)
.
54
Chapter overview
 2.2.1 Basil overview
 2.2.2 Pre-registering the Basil
 2.2.3 Configuring/connecting the Basil to the customer’s network
 2.2.4 Registering the Basil to the Center Server (through HTTPS)
 2.2.5 Device Registration Wizard
 2.2.6 Auto Discovery
 2.2.7 Registering the Basil to the Center Server (through SMTP)
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
55
2.2.1 Basil overview
56
Basil hardware overview
Front Rear
LAN1 port
(Maintenance port)
LED’s LAN2 port
(customer network port)
Modem port
(Not used in European
region.)
1
2
3
57
Basil - Turning OFF
 Procedure
 You must remove the Basil from the Center Server, before
removing the Basil. (See chapter “Removal”)
 If you wan to move the Basil to a different location on the
same network, then:
 Unplug the power cord
 Move the Basil
 Plug in power
58
Basil login accounts
https://<ip-address>
 RC Gate Registrant
 Default password: installation
 Registration of Basil and devices
 RC Gate Admin
 Default password: admin
 Used by the customers administrator
https://<ip-address>/CE
 CE Mode
 Default password: rst107C/S
 Used by the Customer Engineer
 Can be disabled by RC Gate Admin
 It is recommended to
change the default
passwords at first
installation.
!
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
59
2.2.2 Pre-registering the Basil
60
Pre-registering a new Appliance (Basil/Cumin)
Mandatory fields
Optional fields
Batch registration
61
Registration number
62
Checking a pre-registered Appliance (Basil/Cumin)
‘Right-click-
copy’, to copy
registration
number to the
clipboard.
Enter search
conditions
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
63
Exercise 2
 Pre-register your Basil to the Center Server.
 Check your pre-registered Basil on the Center Server.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
64
2.2.3 Configuring/connecting the Basil
to the customer’s network
65
Connect your PC to the Basil
 Connect your PC to the Basil’s maintenance-port (LAN1).
network-cable
PC network settings:
IP : 192.168.10.3
Subnet : 255.255.255.0
Basil maintenance-port (LAN1):
IP : 192.168.10.1 (default)
Subnet : 255.255.255.0
66
Login to the Basil
 Access the Basil-UI (https://192.168.10.1)
 Login to the Basil as ‘RC Gate registrant’
67
RC Gate and Device Settings
 Select ‘RC Gate and Device Settings’
68
Basic settings
 Select ‘RC Gate Settings’ / ‘Basic’.
 Select the correct time zone and click on ‘Apply’.
!
It is important to select
the correct time zone.
69
Date and time settings
 Select ‘RC Gate Settings’ / ‘Date/Time’.
 Enter the correct date/time settings and click on ‘Apply’.
70
Network settings
 Select ‘RC Gate Settings’ / ‘Network’.
 Enter the correct network settings and click on ‘Apply’.
LAN1 port
(maintenance port)
LAN2 port
(customer network)
DNS Server
(optional)
71
Connect the Basil to the customer’s network
 Connect the Basil’s LAN2 port to the customers network.
 You can now still access the Basil-UI through the maintenance
port, or you can access the Basil-UI through the customer’s
network.
Customer’s network
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
72
Exercise 3
 Configure your Basil for the customer network.
 Connect your Basil to the customer network.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
73
2.2.4 Registering the Basil to the
Center Server (through HTTPS)
74
Login to the Basil
 Login to the Basil as ‘RC Gate registrant’
75
RC Gate Registration Wizard
 Select ‘RC Gate Registration Wizard’
76
Communication method setting
 Select HTTPS as the communication method between the
Basil and the Center Server.
77
Enter registration number
 Enter the registration number (‘Request No’) and
confirm/select the time zone.
78
Change IP Address Send Permission
 The ‘IP Address Send Permission’ setting is optional.
 This setting can only be changed at this point. It can NOT be changed
after installation.
79
Confirm/enter date and time
80
Confirm/change network settings
81
Email settings
 When you have selected HTTP as communication
method, Email settings are optional. Click ‘Next’ to skip
the Email settings.
Basil administrator
to receive Email
notifications
(optional)
82
Proxy server settings
 Enter proxy server settings if the Basil must use a proxy
server to connect to Internet.
83
Confirm settings
84
Registration number confirmation
 Before the registration starts, the registration number is
confirmed.
85
Registration at Center Server
 The Basil is registering at the Center Server.
86
Registration result
 The Basil is now registered at the Center Server.
87
Top page
 After the Basil is registered, the ‘RC Gate Registration
Wizard’ button is removed.
Notice the two new
buttons.
88
Checking your Basil in the Center Server
 Searching your Appliance in the Center Server GUI.
Check your
Basil in the
Appliance List
(double click
for Appliance
info)
Enter search
conditions
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
89
Exercise 4
 Register your Basil to the Center Server (HTTPS).
 Check your Basil in the Center Server GUI.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
90
2.2.5 Device Registration Wizard
91
Device Registration Wizard overview
1. Register devices to Basil
2. Register devices to Center Server
Center Server / Device list
Center Server / Device list
92
Login
 Login to the Basil as
‘RC Gate registrant’
 Select ‘Device
Registration Wizard’
93
Enter IP-address search range(s)
 Select ‘IP address ranges’ (‘Host name’ will be explained
later).
 Enter the IP address search range(s)
94
Select devices to register
 The Basil searches the network
 The found devices are displayed
 Select the devices you want to register
 The device type (SNMP/HTTPS) is displayed
95
Obtain Request No. (1/2)
 Click on ‘Obtain Request No.’
96
Obtain Request No. (2/2)
 Results of ‘Obtain Request No.’
97
Registering devices
 The devices are registered to the Basil
98
Register devices by CSV file (hostname or IP-address)
 For each hostname entered in the CSV file the Basil will
query the DNS server (must be configured in the Basil
network settings) to find the device IP adress.
CSV file
The CSV file can
contain both hostnames
and IP-addresses
separated by a comma
or a new line.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
99
Exercise 5
 Use the “Device Registration Wizard” to register devices.
 Check the registered devices in the Center Server GUI.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
100
2.2.6 Auto Discovery
101
Auto Discovery overview
1. Configure Auto Discovery
2. Manage monitored devices (optional)
Center Server / Device list
Center Server / Device list
Center Server / Device list
102
Login
 Login to the Basil as
‘RC Gate registrant’
 Select ‘Auto
Discovery Setting
Wizard’
103
Auto Discovery settings
 Enter the Auto Discovery settings
104
Auto Discovery IP-Address ranges
 Set more search ranges via ‘add’ or ‘impor a CSV file’.
105
Configuring Auto Discovery (3/5)
 A summary of search ranges is displayed.
106
Result of Auto Discovery
 Devices which are found with the Auto Discovery option
appear as ‘monitored’ on the Center Server.
107
From ‘monitored’ to ‘managed’
 To make ‘monitored’ devices ‘managed’, select the
devices and select ‘Manage Devices’.
Select to manage as ‘HTTPS’ or ‘SNMP’ device.
Enter M/R Date
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
108
Exercise 6
 Configure Auto Discovery on the Basil.
 Check the result of Auto Discovery on the Center Server
GUI.
 Make some of the ‘Monitored’ devices ‘Managed’ devices.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
109
2.2.7 Registering the Basil to the
Center Server (through SMTP)
110
Login
 Login to the Basil as
‘RC Gate registrant’
 Select ‘RC Gate
Registration Wizard’
111
Settings
 Select the
communication
method (SMTP).
 Enter the Request
Number and the
Time zone.
 RC Gate registrant
E-mail address
(optional). Will
receive an E-mail
with registration
result.
 Enter the
date/time.
optional
112
Confirm network settings
113
Enter the SMTP settings
Optional
Mandatory
Optional
114
Registration result
 Result message
 If an RC Gate registrant E-mail address has been
configured (optional), the results from the registration will
be sent to the this E-mail address.
115
Registering devices whit SMTP registered Basil
 When you register the Basil through SMTP, you can only
configure Auto Discovery (no Device Registration Wizard).
 The result of Auto Discovery will not be visible in the
Center GUI (no device list).
 If you configured an RC-Gate admin E-mail address
(optional), results from the Auto Discovery function will be
sent the RC-Gate admin address.
 E-mail content to RC-Gate admin is NOT encrypted.
One text file for each found device
116
Basil registered with SMTP limitations
 It is not recommended to register the Basil with SMTP
and should only be done when absolutely necessary.
 Registering the Basil with SMTP gives very limited Center
Server functionality:
 Devices can not be managed. (Devices can only be
monitored by Auto Discovery function.)
 Only MIB counter information.
 No device list.
 No device status indication.
 No Service/Supply Call indication.
 No remote firmware update.
 Only available functions:
 Counter CSV file and Reporting website functionality.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
117
2.3 UZ-A1 Installation
Click here to go direct to the Cumin training.
(if you want to skip the “UZ-A1 Installation chapter
”).
118
Chapter overview
 2.3.1 UZ-A1 overview
 2.3.2 Pre-registering the UZ-A1
 2.3.3 Options for the UZ-A1
 2.3.4 Configuring/connecting the UZ-A1 to the customer’s network
 2.3.5 Registering the UZ-A1 to the Center Server (through HTTPS)
 2.3.6 Device Registration Wizard
 2.3.7 Auto Discovery
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
119
2.3.1 UZ-A1 overview
120
UZ-A1 hardware overview
Front
Rear
LAN port (customer network port)
PC port (Maintenance port)
LED’s
Power Button
LCD Display
121
UZ-A1 - Turning ON
 Plug in the power cord of the UZ-A1.
 There is no power switch to turn on.
 Note that if the customer uses DHCP, the IP address of the
RC Gate A may be changed after turning the UZ-A1 OFF
and ON.
122
UZ-A1 - Turning OFF
 Procedure
 You must remove the UZ-A1 from the Center Server, before
removing the UZ-A1.
 Procedure
1. Either; - Select "Shut Down RCGate" in the UI of the UZ-A1.
OR - Hold the "Shutdown" button on the front of the UZ-A1 for 5
seconds or longer.
2. Unplug the power cord of the UZ-A1.
 If you unplug the power cord without doing step 1, the memory
could be damaged and log data lost.
123
UZ-A1 login accounts
 https://<ip-address>:9443
 Administrator
 Default password: administrator
 Registration of UZ-A1 and devices
 Change setting/configurations
 General user
 Default, this account does not exist (An
administrator must create it)
 When you select ‘General user’, then the
configuration option is greyed out!
 User can view information of ‘managed
devices’
 https://<ip-address>:9443/CE
 CE Mode
 Default password: rst107C/S
 Used by the Customer Engineer
 Can be disabled by RC Gate Admin
 It is recommended to
change the default
passwords at first
installation.
!
124
Features on UZ-A1, Device Management
 The user can check/monitor
the status of managed
devices on the UZ-A1 in the
device management menu.
(Through the web interface.)
 The menu includes:
 Device list
 Call history
 Counter list
 Individual device status
125
Features on UZ-A1, @Remote On/Off
 On the UZ-A1, the customer can disable @Remote
communication. (This is supposed to be a temporary measure.)
 For example, when the customer needs to isolate the cause of a
problem during network troubleshooting.
 This is not available on the Basil.
 While @Remote is disabled, the Center GUI can read the
settings in the appliance, but can not make changes.
 The customer administrator or a technician can make changes,
using the UI of the appliance.
126
Features on UZ-A1, Notification Timing
 On the UZ-A1 you can specify what to do when it receives
a call from a device.
 This is not available on the Basil.
 There are three settings.
 No Send: The call is not passed on to the @Remote Center
 Real Time: The call is passed on immediately after it is
received from the device.
 Periodic: Calls are passed on either Daily, Weekly, or
Monthly.
 The setting is made from the Center GUI.
 Center GUI: Administrator menu – Appliance Information for
Admin – Notification tab
127
Features on UZ-A1, Retries
 With this function:
 You can specify on the Center GUI how many retries (and at
what interval) an RC Gate A must pass auto calls from
devices to the @Remote Center.
 Administrator menu – Appliance Information for Admin –
Notification tab
 This is not available on the Basil.
128
Features on UZ-A1, User counter capture
 With this function:
 The user can retrieve individual user counters.
 This is not available on the Basil
 You can test if the user counter information can be
obtained from each device (Via the UZ-A1 UI).
 Enter a device's IP address to check if it is possible to
acquire per-user counter information for that device.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
129
2.3.2 Pre-registering the UZ-A1
130
Pre-registering a new Appliance
Mandatory fields
Optional fields
Batch registration
131
Registration number
132
Checking a pre-registered Appliance
‘Right-click-
copy’, to copy
registration
number to the
clipboard.
Enter search
conditions
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
133
Exercise 7
 Pre-register your UZ-A1 to the Center Server.
 Check your pre-registered Appliance on the Center Server.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
134
2.3.3 Options for the UZ-A1
135
Available options
 There are two options available.
1. DIMM Memory :
 With this DIMM installed, the RC Gate A can store/export user
counters.
2. SSD Memory:
 Increases the maximum number of managed devices from 100
to 1000.
 When you install the SSD, you must also install the DIMM.
 The activation of the options must be done by an
engineer.
 You must first remove the UZ-A1 from the center server!
 When you activate the options, a new (larger) data table is
created. (All the existing data is removed.)
 Then you must register the UZ-A1 again.
136
Installing the options
 Install the DIMM and the SSD.
 You can install only the DIMM.
 When you install the SSD, you must also install the DIMM.
SSD
DIMM
137
Connect your PC to the UZ-A1
 Connect your PC to the UZ-A1s maintenance-port (PC).
network-cable
PC network settings:
IP : 192.168.10.3
Subnet : 255.255.255.0
UZ-A1 maintenance-port (PC):
IP : 192.168.10.1:9443 (default)
Subnet : 255.255.255.0
138
Login to the UZ-A1
 When options are installed then first proceed by checking
the available memory and enabling the extended function
setting.
 Follow the steps in the next few slides
 Access the UZ-A1-UI via CE login
139
Memory Operation Check
 Do the memory operation check to ensure that the options
are recognized by the UZ-A1 .
(1)
(2)
(3)
(4)
140
Extended Function Setting
 Enable the options.
 Switch ‘Extend the number of monitored devices’ to Use.
 Once ‘Use’ has been selected, the setting cannot be
changed to back.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
141
2.3.4 Configuring/connecting the UZ-
A1 to the customer’s network
142
Settings required for using the RC Gate A
 The following settings are required for using the UZ-A1.
 Time Zone and Date/Time Settings
 HTTP Proxy Settings
 Email Settings
 Change IP Address Send Permission
 Entering Request No.
 Starting Registration
143
Login to the UZ-A1
 Access the UZ-A1-UI (https://192.168.10.1:9443)
1. Login as ‘administrator’
2. Select ‘Initial settings’
(1)
(2)
144
Set up the RC Gate A
 Set up the RC Gate A
 Run the ‘Setup Wizard’
 You can also select the ‘RC Gate Configuration’ menu and
browse through the settings manually.
 Follow the steps and input all relevant information.
145
Date/Time settings
 Select ‘RC Gate Settings’ - ‘Date/Time’.
 Select the correct time and time-zone and click on ‘Apply’.
!
It is important to select
the correct time zone.
146
Network settings
 Select ‘RC Gate Settings’ / ‘Network’.
 Enter the correct network settings and click on ‘Apply’.
PC port
(maintenance port)
LAN port (customer
network)
DNS Server
(optional)
147
IP Address Send Permission
 Choose permit (default) if you want all functionalities to be
available:
148
Network settings
 You can setup e-mail notification.
149
Setup complete
 When the initial setup is complete, you will get the
following notification:
150
Connect the UZA1 to the customer’s network
 Now you can connect the UZ-A1 - LAN2 port to the customers
network.
 You can still access the UZ-A1 UI through the maintenance port, or
you can access the UZ-A1-UI through the customer’s network.
Customer’s network
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
151
Exercise 8
 Configure your UZ-A1 for the customer network.
 Connect your UZ-A1 to the customer network.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
152
2.3.5 Registering the UZ-A1 to the
Center Server
153
Overview
154
Login to the Basil
 After the initial setup, you get the following screen.
 Select ‘@remote Service Registration Wizard’.
 If you already logged out, then login to the UZ-A1 as
‘Administrator’.
 Select ‘Initial settings’ - ‘@remote Service Registration
Wizard’.
155
Enter registration number
 When you input the Request Number use copy-paste to
prevent typing errors.
156
Confirm/change network settings 1/2
 Double check all network/proxy settings.
157
Confirm/change network settings 2/2
 Click ‘Confirm with server’
158
Appliance registration 1/2
 If this error message occurs, make sure that the request
number is correct. (copy-paste)
 If confirmation is successful, then click ‘Start Registration’
159
Appliance registration 2/2
 A progress bar will show during the registration process.
 If registration is successful, then click ‘Finish’
160
Checking your UZ-A1 in the Center Server
 Searching your Appliance in the Center Server GUI.
Check your
UZ-A1 in the
Appliance List
(double click
for Appliance
info)
Enter search
conditions
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
161
Exercise 9
 Register your UZ-A1 to the Center Server.
 Check your UZ-A1 in the Center Server GUI.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
162
2.3.6 Device Registration Wizard
163
Overview
164
Device Registration Wizard 1/9
 Log in as ‘Administrator’
 Select ‘Initial Settings’
165
Device Registration Wizard 2/9
 Use the Device Registration Wizard.
 Devices found with the Device Registration Wizard are
‘managed’.
 If you see a device with condition “Managed - Found” on
the Center Server, then you must wait, the condition will
automatically change to “Managed – Registered”.
166
Device Registration Wizard 3/9
(1)
(2)
167
Device Registration Wizard 4/9
(2)
(1)
(3)
168
Device Registration Wizard 5/9
(2)
(1)
169
Device Registration Wizard 6/9
(1)
170
Device Registration Wizard 7/9
(1)
(2)
171
Device Registration Wizard 8/9
(1)
(2)
172
Device Registration Wizard 9/9
(1)
(2)
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
173
Exercise 10
 Use the “Device Registration Wizard” to register devices.
 Check the registered devices in the Center Server GUI.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
174
2.3.7 Auto Discovery
175
Overview
176
Auto Discovery Setting Wizard 1/6
 Use the Auto Discovery Setting Wizard.
 Devices found with the Auto Discovery Setting Wizard are
‘monitored’.
 You can select devices that are found on the device list on
the Center GUI.
 When you click ‘Register Devices’.
 They become ‘managed’ devices.
 If you see a device with condition “Managed - Found” on
the Center Server, then you wait, the condition will
automatically change to “Managed – Registered”.
177
Auto Discovery Setting Wizard 2/6
 Select ‘Auto Discovery’
178
Auto Discovery Setting Wizard 3/6
(1)
(2)
(3)
179
Auto Discovery Setting Wizard 4/6
(1)
(2)
180
Auto Discovery Setting Wizard 5/6
(1)
(2)
181
Auto Discovery Setting Wizard 6/6
182
Extended Device Search
 During Auto Discovery, problems may occur with Ricoh
devices that contain controllers from other manufacturers
(such as EFI or Samsung).
 With this new feature you can enable / disable a different
type of search function.
 Set to Enable to increase the change to find those devices.
183
IP Address Exclusion 1/2
 It is possible to set IP addresses which you (or the customer) do
not wish to be searched by the UZ-A1.
 You can set max. 255 IP addresses.
184
IP Address Exclusion 2/2
 During Auto Discovery, the excluded addresses are
skipped.
 When an excluded machine uses DHCP and its IP address
changes into a discoverable address, it will not be skipped
during the next Auto Discovery.
 When you use IP Address Exclusion, it is best to use
reserved IP addresses for the devices. (Or at least for the
excluded devices.)
185
From ‘monitored’ to ‘managed’
 To make ‘monitored’ devices ‘managed’, select the
devices and select ‘Manage Devices’.
Select to manage as ‘HTTPS’ or ‘SNMP’ device.
Enter M/R Date
186
Remote registration 1/2
 During Auto Discovery, the external RC gate collects the
following for each device: Device S/N, IP address, MAC address
 The data at the @Remote Center is normally 1 day old.
 Only the IP address and MAC address are used for
Registration.
 Registration at the center can only go ahead if the external RC
gate can connect to the specified IP address and the MAC
address is correct.
 The center GUI sends the IP address and MAC address to the
external RC gate.
 The external RC gate checks that the device with that IP address
has the correct MAC address.
 Then the external RC gate registers that device at the @Remote
Center.
 If the device power is off at the time of registration, or if the IP
address has changed due to DHCP (the data at the center is
one day old), the external RC gate sends an error to the center.
187
Remote registration 2/2
 If a different device responds to the IP address (i.e., the MAC
address is different), or if there is no device at that IP address,
the UZ-A1searches again within the same segment for a device
that has the MAC address in question.
 This only works within the same segment. So, if the device was
moved to another room, it may be in another segment, and will
not be found.
 The Basil can only accept one registration request at a time
from the Center GUI (up to 100 devices per request).
 If there are more than 100 devices for the Basil, you must wait
until the first batch has been registered, before you can send a
registration request for the next 100.
 Otherwise, the RC Gate will return an error message (busy –
request not accepted).
 For the UZ-A1, up to 100 requests can be queued.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
188
Exercise 11
 Configure Auto Discovery on the UZ-A1.
 Check the result of Auto Discovery on the Center Server
GUI.
 Make some of the ‘Monitored’ devices ‘Managed’ devices.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
189
2.4 Cumin installation
190
Cumin installation overview
1. Pre-register Cumin to Center Server
2. Proxy settings
3. Register appliance/device to Center Server
191
Pre-register Cumin to Center Server
 Pre-registering a Cumin to the Center Server is the same
as pre-registering an external RC gate to the Center Server.
192
Proxy server settings
193
Register the appliance/device
 Select ‘Setup RC Gate’
 Enter the Request No. Select ‘Confirm’.
 The confirmation result is displayed.
 Select ‘Program’. The registration result is displayed.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
194
Exercise 12
 Register a Cumin device to the Center Server.
 Check the registered appliance/device in the Center Server
GUI.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
195
2.5 Removal
196
Removing a device
 To remove a device from the Center Server select the device
and click on ‘Remove Devices’. The status of the device will
then be ‘removing’.
 The next time the Appliance (external RC gate or Cumin)
contacts the Center Server, the device will be removed from
the Center Server.
 If the Appliance is physically disconnected or it’s power is off,
the device will be removed from the Center Server after 4 hours.
197
Removing an Appliance
 IMPORTANT! : Before removing an Appliance (external RC
gate or Cumin) from the Center Server, first remove all
devices from that Appliance.
 When all devices of the Appliance are removed, select the
Appliance and click on ‘Remove Appliance’. The status of
the Appliance will then be ‘removing’.
 The next time the Appliance (Basil or Cumin) contacts the
Center Server, the Appliance will be removed from the
Center Server.
 If the Appliance is physically disconnected or it’s power is
off, the Appliance will be removed from the Center Server
after 90 minutes.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
198
3. Maintenance
199
Chapter overview
 3.1 Search menu
 3.2 Device information
 3.3 Counter / Supply CSV
 3.4 Service Calls
 3.5 Email notifications
 3.6 Solution list
 3.7 Firmware Update
 3.8 Calendar list
 3.9 Administrator menu
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
200
3.1 Search menu
201
Search Appliance
 The search result is displayed in the Appliance list.
You can use the % character as wildcard in this fields.
Leave this field blank to search
through all Service Depots.
In that case you must use at least one
other search field.
202
Search Device
 The search result is displayed in the Device list.
This field is
mandatory, you
cannot leave this
field blank.
Only in this field
you can use the %
character as
wildcard.
Customer name is
CaSe sensitive
203
Searching devices through Search Appliance
 If you need to search a device by Device S/N, through all
Service Depots, this is the most easiest way:
 The search result is an Appliance displayed in the
Appliance list. This is the Appliance containing the device.
Leave this field blank.
Enter the Device S/N
204
Search for disconnected devices/appliances (1/3)
Select ‘Search Appliance’
or ‘Search Device’
 This function only works for managed devices.
205
Search for disconnected devices/appliances (2/3)
 Disconnected Appliance / Device List
206
Search for disconnected devices/appliances (3/3)
 You can also check if devices might be disconnected by
checking the Device list.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
207
3.2 Device information
208
Device Information screen (1/2)
 Double click on a device to go to the Device Information
screen.
Optional information fields
Mandatory
information
fields
209
Device Information screen (2/2)
 Update
 Sends the updated fields to the Center Server
 Call History
 Exports a .csv file of calls (closed & open) (see chapter
‘Service Calls’).
 Device Status
 Displays device status information.
 Comm
 Read/write device information and read/write/execute SP-
modes.
210
Device Status
 State
 Machine status
 Jam Log
 Count Log
 Over 400 counter items
 Time Log
 Total duration main motor
 SC Log
 Function
 Fusing temp, ID sensor offset, etc.
211
COMM overview (1/2)
 Communication Main menu
Read / Write / Execute requests are
displayed here. If the request has
been processed, double click on the
request to display the result.
212
COMM overview (2/2)
 Read
 Read device information at next polling interval.
 After clicking start use the “refresh” button to see the Next
Polling Time
 Write
 Write (new) values to SP-Modes at next polling interval.
 After clicking start use the “refresh” button to see the Next
Polling Time
 Execute
 Reset SC, PM counters, Jam Counters or force a toner supply call
at next polling interval.
 After clicking start use the “refresh” button to see the Next
Polling Time
213
Read request
Select the items you want to
read from the device.
The result of the read request is displayed
here, after the Appliance has polled the
Center Server. (See ‘Next Polling Time’).
Select the items you want to
read from the device.
214
Write request
Before you can write SP-modes, you
must first do a read request here.
After the read request has been performed, the current
values are displayed under ‘Present’. Then you can enter a
new value under ‘New’ and click ‘Write Start’.
Do not forget to mark the checkboxes for
the SP-modes you want to ‘write’.
215
Execute request
 Only the SP-modes which are available to execute are
displayed.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
216
Exercise 13
 Read the device information and SP modes from a device.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
217
3.3 Counter / Supply CSV
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
218
3.3.1 Counter-CSV
219
Counter/Device info communication to Center Server
 Counter and Device information is collected by the RC-Gate, send to the
Center Server and processed by the Center Server as shown below.
Center Server
external
RC gate
Cumin
Collection
Managed
devices
(HTTPS)
1 / 12 hours
(retry after 6
hours)
Managed
devices
(SNMP)
1 / 12 hours
(retry after 6
hours)
Auto
Discovery
enabled
AD schedule
(daily/weekly/
monthly)
Transfer to CS
Managed
(HTTPS)
1 / Day
Managed
(SNMP)
1 / Month
(MR
Date)
Auto
Discovery
AD
schedule
CS Processing
Managed
(HTTPS)
Max. 1 Day
Managed
(SNMP)
Max. 1 Day (only latest or M/R
counter is saved)
Auto
Discovery
Max. 1 Day (only latest or M/R
counter is saved)
220
New Counter-CSV request
Request settings
(explained later)
221
List with Counter-CSV requests
222
Download Counter-CSV
 If the request status is ‘completed’, double click on the
request to download the CSV file(s).
223
Counter-CSV request main settings overview
Immediate or Scheduled
Meter Reading or Reporting
Download to ‘Your PC’ or ‘Back-End’
CSV Separator
Site Name / data range
Optional filters
224
Meter Reading Counter-CSV request
 The downloaded file for an M/R Counter-CSV request can
contain 2 files.
225
Meter Reading Counter-CSV file content
1 line per device:
The counters from the M/R data.
OR (if M/R counters are not available)
The latest acquired counters within the specified data range.
226
Reporting Counter-CSV request
227
Reporting Counter-CSV file content
Multiple lines per device:
All counters for all devices within the specified data range.
228
Scheduled Counter-CSV request
List with Counter-CSV requests
Schedule settings
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
229
3.3.2 Supply-CSV
230
Supply Call communication to Center Server
 Supply Calls are notified by the RC-Gate, send to the Center
Server and filtered by the Center Server as shown below.
Center Server
external
RC gate
Cumin
Notification
Managed
devices
(HTTPS)
Immediate
Managed
devices
(SNMP)
After SNMP
polling.
(Default =
every 10 min.)
Auto
Discovery
devices
N.A.
(no Supply
Calls)
Transfer to CS
Managed
(HTTPS)
Immediate
Managed
(SNMP)
Immediate
Auto
Discovery
N.A.
CS Filtering
Depending on the device (prefix) multiple calls will
be filtered using 1 of the following 2 methods:
Total Counter
Number of bottles used
 Supply Call settings on the device are not always ‘ON’ by default
 In the embedded Excel document you can find the default settings of Supply
Call related SP modes per controller series.
! Microsoft Excel
Worksheet
231
Supply-CSV overview
 Using the Supply-CSV menu works the same as Counter-
CSV menu.
New Supply-
CSV request
List with
Supply-CSV
request
Double click
to download
Supply-CSV
232
Supply-CSV request settings
Toner or All Supplies
 Most settings work the same as in Counter-CSV request.
233
Supply-CSV file content
Supply Calls received in the specified data range
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
234
Exercise 14
 Create a new request for Counter CSV (report)
 Create a new request for Supply CSV (report)
 Download the reports
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
235
3.3.3 ERP Linkage
236
ERP linkage
 Counter and supply-call data can be send to your ERP
system using the Ricoh Europe Common Server.
 This allows you to automate processes, such as billing
and toner replenishment, through your ERP system.
 The procedure to create the link to your ERP system is
outside the scope of this training.
 Contact Ricoh Europe through your default support route if
you require more information.
Service organisation
ERP system
Common
Server (EU)
Center
Server
Counter/
supply-
call data
Counter/
supply-
call data
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
237
3.4 Service Calls
238
Service Call communication to Center Server
 Service Calls are received by the RC-Gate and send to
the Center Server as shown below.
Center Server
external
RC gate
Cumin
Notification
Managed
devices
(HTTPS)
Immediate
Managed
devices
(SNMP)
After SNMP
polling.
(Default =
every 10 min.)
Auto
Discovery
devices
N.A.
(no Service
Calls)
Transfer to CS
Managed
(HTTPS)
Immediate
Managed
(SNMP)
Immediate
Auto
Discovery
N.A.
CS Processing (to show in Call
List)
Type A SC-
Call
Immediate.
Type B/D
SC-Calls
After 30 minutes.
239
Call List
 The Call List shows all incoming calls from
devices/appliances.
 The Call List does NOT show Supply Calls.
240
Call Detail
 Double click on a call to go to the Call Detail screen.
241
Manual Call on an MFP
 Press <clear><0><0><clear/stop> (keep the last button
pressed until the “Remote Diagnostics” screen appears on
the operation panel.
 Press the “Call” button and wait for a completion
message.
242
Manual Call on an LP
 On LP’s with a 2-line display:
 Press and Hold the "Escape" Key for about 5 seconds.
 A Message will appear in the Operation Panel allowing you
to Place a Call.
 On LP’s with a 4-line display:
 Press the "Menu" key.
 Go to the "Remote Service" menu.
243
Closing Calls
 You can close all calls for the same device by selecting the
close all calls checkbox
 You can close calls one-by-one by selecting the applicable
checkboxes and click the ‘Update’ button
 You can select only pre-defined solutions (also see solutions
slide) for a call you want to close
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
244
Exercise 15
 Search, Select and Close a Call
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
245
3.5 Email notification
246
Call Email List
247
New Email List
You can enter
multiple email
addresses
separated by a
comma.
Use this setting
to receive a daily
Email with all
disconnected
Appliances within
your Site/Service
depot.
248
Email Notification Timing
 Depending on the local infrastructure receiving Call Emails
from the Center Server can take up to 5 minutes
 If no Email is received check spam filters on Email servers
or try an external email address.
 If it looks like email is received more than 30 minutes later,
check all (device/ external RC gate) regional settings
(date/time)
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
249
3.6 Solution list
250
Solution
The default sort is
alphabetic. You cannot
change this.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
251
Exercise 16
 Add a new “Solution” named “Manual Closed Manual Call”
 Add a new “Call Email Entry” type “Manual Call”
 Create a Manual Call on one of the training machines
 Check your mailbox
 Close the call with your newly added solution
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
252
3.7 Firmware Update
253
Remote Firmware Update (RFU)
 You can update firmware for appliances and devices from
the Center Server.
 On the UZ-A1 the are some extra specifications that are
not available for the Basil:
 RFU Enable/Disable
 RFU Prohibition Interval
 RFU Shift Device Firmware Update Time
254
RFU Enable/Disable 1/2
 For the model RC Gate BN:
 You must individually prohibit RFU at each device
connected to the RC Gate BN.
 For the RC Gate A:
 You can prohibit RFU for all devices with a setting in the RC
Gate A.
255
RFU Enable/Disable 2/2
 For the RC Gate A, there are two settings:
1. Enable/disable RFU for the appliance.
2. Enable/disable RFU for the devices (this is a new function
for RC Gate S Pro/RC Gate A).
256
RFU Prohibition Interval
 Normally, when setting up at the Center GUI, RFU is set
for a convenient time for the customer. It must be finished
within a set period (default: 3 days).
 If RFU is done during office hours, it can be inconvenient
for the customer.
 With the UZ-A1 appliance, it is possible to prohibit RFU
during working hours.
 If RFU is in progress when working hours start, it is
suspended, until the end of working hours. Then it
resumes.
257
RFU Shift Device Firmware Update Time 1/2
 An appliance can monitor devices in (very) remote
locations.
 For example, the external RC Gate an be in Moscow, but
some devices can be in London. (a different time zone.)
 If the RFU is set up for 17:00 Moscow time, then the RFU
on the devices in London could start during London office
hours.
 On the UZ-A1 you can prevent this.
 You set up the time shift function for the devices in different
time zones.
 This is not available on the Basil.
258
RFU Shift Device Firmware Update Time 2/2
 To operate this UZ-A1 feature, you specify network segments
that require a time shift and the time shift that is needed
 You can also import a .csv file containing the network segments
that need the time shift.
259
Firmware Main
260
Model Select
Microsoft Excel
Worksheet
The embedded Excel file lists
device prefixes. You can use this
list to select the correct model
before updating firmware.
261
Search Device
Although the list shows SNMP devices,
you can NOT update these devices.
262
Firmware Select
The list of available types
of firmware depend on
the selected model.
263
Firmware Update
Only available
for UZ-S1/A1
appliances.
Update schedule
264
Updating List
Appliance Queue List.
265
Appliance Update Queue List
266
Device firmware update through the Basil GUI
 If you can also update device firmware at the customer
site though the Basil GUI.
 For more details about this procedure, see the Basil
Service Manual.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
267
Exercise 17
Update the firmware of your external RC gate
(through Center Server GUI)
Update the firmware of a device
(through Center Server GUI)
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
268
3.8 Calendar list
269
Add new calendar
 The calendar specifies the office hours of the service
organisation.
 Devices will not display ‘an engineer will be sent’ when an
error occurs outside office hours.
270
Configure calendar month
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
271
3.9 Administrator menu
272
Administrator - Appliance
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
273
4. Reporting website
274
Reporting website introduction
 The reporting website (@Remote.net) provides the
@Remote reporting features to the customer.
Multiple reports
Export to Excel / CSV
Graphical reports
3rd
parties reporting
275
Reporting server overview
 Every day device counter data on the Center Server is
send to the Reporting Server.
Reporting
Server
Center
Server Device
counter
data
Customer Service organisation
Manage
reporting
website
Reporting
website
276
Link between Center Server and Reporting Server
 Communication between the Center Server and Reporting
Server is one-way (from Center Serv. to Reporting Serv.).
Reporting
Server
Center
Server Device
counter
data
277
Reporting website URL’s
 https://www.atremote.net/ricoh-europe
 https://www.atremote.net/infotec
 https://www.atremote.net/gma
 https://www.atremote.net/nrg
Ricoh
Infotec
GMA
NRG
US
EU
Reporting
Server
278
Login
 When you do not have a user account, you can have a
look at the website using the following user:
 User Name: Sample
 Password: password
279
User agreement
 At first log-in each user must accept the user agreement
to continue.
 The User Agreement is always available for your review,
via a link on the home page of the website.
280
Home page overview (1/2)
 Homepage (https://atremote.net/ricoh-europe)
Choose language
Reports
281
Home page overview (2/3)
 Select Appliances
Click to expand
282
Home page overview (3/3)
 Change Customer
283
Reporting website (@Remote.net) User Guide
 The user guide can be downloaded from the website.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
284
5. Troubleshooting & support
285
Basil / UZ-A1 - login & logout
 If you close your browser while you are logged into the
external RC Gate, the session is NOT terminated
 The session will time-out after 30 minutes.
 Therefore, always use the ‘Logout’ button to close the
session.
286
Procedure: Migrating from RC Gate BN to RC Gate A
1. RC Gate BN & device information backup
 Create a list of Appliance information (Screen dump)
 To input later during RC Gate A installation.
 Export: Simple Device Information CSV files from Center GUI
 To import later to new Appliance during device registration procedures
 If you want to keep this information, then export for your own
reference: Reporting CSV, Supply CSV and Call history.
 Un-manage devices
2. Install UZ-A1
 Retrieve: Request number from Center GUI
 Setup: Appliance
 Run: Device Registration Wizard
 Run: Auto Discovery Settings Wizard
 Upload: Device Information CSV files into the correct Appliance via
Center GUI.
3. Remove RC Gate BN
 Unregister Appliance at Center GUI
 Remove RC Gate BN
287
RC Gate migration Step-by-Step
Migrating from RC Gate to RC Gate-A
At the RC Gate.
Create a list with all
Registered Devices.
At the RC Gate.
Access the RC Gate UI in
CE mode.
At the Center GUI.
2. Make screen dumps of
the Appliance Information
for Admin. (Log in as an
Administrator.)
At the Center GUI.
3.1 Export:
Device List
( Simple)
At the Center GUI.
3.2 Export:
Reporting CSV
At the Center GUI.
3.3 Export:
Supply CSV
At the Center GUI.
3.4 Export:
Call History
At the RC Gate A.
Register the RC Gate A
on the @Remote Center.
At the RC Gate A.
4. Install the RC Gate A.
At the RC Gate A.
When asked to input
settings, input the settings
from the old RC Gate (see
step 1).
At the RC Gate A.
Make sure that the Auto
Discovery Settings are set
up.
At the Center GUI.
5. Input the data from
the screen dumps of
the Appliance
Information for Admin
that you made earlier.
(You must log in as an
Administrator.)
At the Center GUI.
6. Un-manage all
Managed Devices.
At the RC Gate.
7. Make the Device
Check Request call from
each of the RC Gates to
be removed.
At the Center GUI.
8. Check on the Device
List, that all devices are
removed.
At the Center GUI.
9. Remove the RC Gates
from the Center.
At the RC Gate-A.
10. Register the devices.
At the Center GUI.
11. Check the Device List
from the RC Gate A.
(Compare it with the
exported device list CSV
files.)
At the RC Gate-A.
12. When devices are
listed as Found, you can
make a Device Check
Request Call from the
RC Gate A. To speed-up
the registration process.
Wait for 1 hour
Wait until 24 hours have
passed since the Auto
Discovery Settings were
made in the RC Gate A
at the customer site.
At the Center GUI.
13/14. You can use
Remote Registration to
try to register devices
that are still not
registered
If some devices are still
not registered and
Managed, make sure
that all the devices are
listed as ‘Monitored’ or
‘Found’.
If any devices are not
listed, check their
condition, and recover
them.
15. Retrieve the Old
Device Information
Import the device
information from the old
RC Gates.
Import it from the
Exported Device List
CSVs that you made in
step 3.
You need the Export
Device List: Simple
16. Make Sure that M/R
is Correct
The M/R dates have all
been reset to 1. They
must be set to the same
values as they were
when registered on the
previous RC Gates
At the RC Gate.
1. Make lists of settings in
the RC Gates at the
customer site. (Make screen
dumps of the settings from
the RC Gate UI.
288
Switching from many RC Gate (BN)s to one RC Gate A
To
From
RC Gate BN RC Gate S Pro RC Gate A
1x RC Gate BN Standard Not Possible Possible
Multiple RC
Gates
Not possible Will become available as “Special
Operation”
RC Gate S Pro Not possible Standard Not Possible
RC Gate A x 1 Not possible Not Possible Standard
289
Important when doing the transition procedure
 Pre-conditions
 Access to the Center Server from customer site.
 The technician needs access to the Administrator menu of
the Center GUI to complete all tasks.
290
Appliance Replacement
 You only have to replace your external RC
gate when is defect.
 The Appliance Replacement procedure is
described in detail in the Center GUI Manual
and the external RC gate Service Manual.
Note
 You cannot replace a Basil, if it is installed
using one-way communication (SMTP).
 You cannot replace an external RC gate, when
permit sending IP address is prohibited
 You cannot replace a Cumin Appliance type.
!
291
@Remote related SP Modes
 5501-xxx PM Alarm
 5504-xxx Jam Alarm
 5505-xxx Error Alarm
 5507-xxx Supply Alarm
 5508-xxx CC Call Alarm
 5515-xxx Report Setting
 5816-xxx Remote Service
 5821-xxx Remote Service
Address
 5870-xxx Common Key Info
Writing
 5985-xxx Feature Support
 5816-200 Manual Polling
 5816-003 Function Flag
 0: Not registered
 1: Registered
 5816-201 Regist Status
 Display of installation condition
 0: Not installed
 1: Installed as Cumin (pre-registered)
 2. Installed as Cumin
 3: Installed to external RC gate
 4: NRS Module is not available
 5816-209 @Remote Setting Clear
 5816-250 CommLog
This list gives you an overview of some important SP Modes.
For a more complete list see notes page.
!
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
292
Exercise 18
 Check a device installation condition using SP mode.
293
Device Firmware Levels
 During site survey
 Check which type of device are in use at the customers site.
This is to help you calculate the time needed for installation.
Older devices and many different models at the same
customer can increase the needed level of troubleshooting
 While troubleshooting
 If a device is not working correctly check for RTB’s on
firmware levels (see example)
Adobe Acrobat
Document
294
Browser issues
 Center Server GUI not accessible
 Browser compatibility
 Although it looks like Center Server operation works fine with other
browsers than MS-IE 6 or 7 some functions might not work
 Browser (security) settings
 If the center server URL is not listed in the trusted sites list in your IE
security settings you might get an error message.
 Browser error(s)
 The first time you connect to the Center Server it takes some for the
browser to download settings. Wait for the “Done” message in the
bottom-left corner of your browser.
 Old OCX’s
 The procedure is on the splash page just after logging in to the Center
Server
295
Service Calls
 Service Test Call
 To perform end-to-end test a “Service Test Call” can be
initiated from the device or external RC gate.
 Manual Call
 To provide information to service, a “Manual Call” can be
initiated from the device.
 Device Check Request call (Only for UZ-A1).
 Sends the status of the UZ-A1 to the Center Server.
 Service Call
 This shows the service call information. Only shown when
the RC Gate A has a problem.
296
Service Calls
 Service Calls
Name of call Operation
Appliance Basil Service Test Call 1.Select “RC Gate and Device Settings” menu
2.Select [Service Test Call] under Maintenance >
Communication Server Calls
UZ-A1 Service Test Call 1. Log in as “Administrator” into RC Gate Configuration
2. Select: Maintenance>Service Test Call
3. Click Start
Device Check Request
call
1. Log in as “Administrator” into RC Gate Configuration
2. Select: Maintenance> Device Check Req. Call
3. Click Start
Service Call 1. Log in as ”General User” into RC Gate or as
“Administrator” into RC Gate Configuration
2. Select: Maintenance> Service Call
Device
MFP Service Test Call System Settings > Administrator Tools > Service Test Call
LP
(4 lines LCD)
Service Test Call Menu > Remote Services > Service Test Call, then “Start”
LP
(2 lines LCD)
Service Test Call “Escape” for 5 seconds > Remote Services, select “Test
Call”, then “Enter”
297
Service Test Call Example (MFP)
298
Common Key (Authkey)
 5870-xxx Common Key Info
 This SP Mode is used to re-write the
“machine certification” (not ID2). The
correct sequence to (re-)write the
“Common Key” is:
 Remove the device in Center GUI Server
(also if monitored)
 Wait for external RC Gate or Device to
communicate this change (normally every
1 hour)
 Execute sp 5870-003 (if available) and
5870-001
 After executing SP5870-001 successfully
immediately POWER OFF and ON the
device !
 Re-register the device using normal device
registration procedure
299
ID2 check
 In order for a device to be registered as an NRS device ID2
Code for that device needs to be correct.
 To check if ID2 Code is correct print out the SMC data list and
check SP 5811 (machine serial) Compare with SP 5811 “ID2
Code Display”. The value of ID2 should be the same as the
serial number but with 6 spaces between the prefix and the
actual serial number
example:
incorrect ID2
example:
correct ID2
300
ID2 re-write overview
 ID2 re-write
 Make sure that the device is not registered and
also not monitored.
 If the device is registered or monitored first
remove the device with the Center Server GUI
 Manually create certification/ID2 call
 Register the call
 Open the call
 Execute the call
 Wait for result
! This is only for devices connected trough an external RC Gate
301
ID2 re-write - Register ID2 Call
 The “Device Model Code” is the serial number prefix (3
characters)
 The “Device Serial Code” is the serial number without the
prefix (8 characters)
 The “IP Address” is the device IP address
302
ID2 re-write - Open the ID2 Call
 Go to the “Call List” menu on the left hand side
 Search and open the ID2 Call (double click)
303
ID2 re-write - Execute the ID2 Call
 Type the correct values for ID2 (prefix and serial)
 Click on the “Execute” button
304
ID2 re-write - Check result
 Wait for the result (Refresh)
305
Prohibit @Remote Service
 This setting prohibits @Remote communication.
 Available on GW2005A or later devices.
 The default setting is ‘Do not Prohibit’ (enable).
User Tools -> System Settings -> Administrator Tools -> Extended Security
306
Device registration error codes displayed on device (Cumin)
 The cumin/device service manuals have a chapter with error
codes. In addition to the codes described in the manual, the
following error codes can occur (displayed in Web Image
Monitor):
 12005; @Remote communication is prohibited. The device has
a problem with a Cumin function.
 12006; After confirmation was completed, the confirmation
request was made again.
 12007; Different request number was used for registration than
the one for confirmation.
 12008; The device function was in use, updating certification
has failed.
307
Device registration error codes displayed on Center Server GUI
 @REMOTE RESULT_NG
 HTTPS device
 The device is a SNMP Device
 The device is disconnected
 The device is powered off
 Wrong IP address used
 DESS not installed
 SNMP device
 The device is disconnected
 The device is powered off
 Wrong IP address used
 @REMOTE RESULT_BUSY
 The Basil is still busy with the previous request.
 @REMOTE RESULT_EXIST_DEVICE_IP
 Retry the registration request again with the latest auto
discovery (AD) data.
308
Basil Communication Log
 Log into the RC Gate
using the Registrant
Mode
 Navigate to the “RC
Gate and Device
Settings” menu
 Go to the
“Maintenance” menu
on the Left side of the
page
 Go to the
“Communication
Log”.
 Select all data in the log window and copy it to a text file.
 Send this text file together with appliance serial number, device
serial number, full customer name and Site name to your
technical support specialist.
309
Center Server responsibilities
 General
 You can not request User ID’s for the Center Server for yourself
unless trained.
 New Site or Service Depot
 Who’s responsible : Ricoh Europe
 How to request : Via your default support route
 Required : Site name, Service Depot name and user-id of requestor
 User ID for Center Server
 Who’s responsible : Ricoh Europe
 How to request : Via your default support route
 Required : Internet e-mail address, name, country, organisation,
@remote administrator’s e-mail address.
310
@Remote Q&A
 A lot of answers to @Remote related questions can be
found in the Tier-2 Knowledgebase through TESSA.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
311
@Remote - New Remote Service
Field service training
END
After this slide there is additional information
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
312
Appendices
Additional Information
313
Appendices - Overview
 Customer pre-survey UZ-A1
 Differences between the External RC Gates
 UZ-A1 - DIP Switches
 Basil – Dipswitch
 Basil - Reset Switch
 Basil - SD Card Slot
 Migrating from RC Gate BN to RC Gate A
314
Customer pre-survey UZ-A1 1/2
 No optional memory
 How many units do I need?
315
Customer pre-survey UZ-A1 2/2
 With optional memory
 How many units do I need?
316
Differences between the External RC Gates
 Periodical reboot
 RC Gate A: Unnecessary
 RC Gate BN: Adjustable; Weekly
or Monthly
 RC Gate S Pro: Unnecessary
 When an Appliance SC occurs
 RC Gate A: Will reboot.
 RC Gate BN: Will reboot.
 RC Gate S Pro: RC Gate S Pro
itself does not reboot, but the
internal @Remote service will
reboot.
 SNMP Version
 RC Gate A: SNMP v1/v2/v3
 RC Gate BN: SNMP v1/v2 only
 RC Gate S Pro: SNMP v1/v2/v3
 Communication Protocol
 RC Gate A: SNMP/SOAP/REST
 RC Gate BN: SNMP/SOAP
 RC Gate S Pro:
SNMP/SOAP/REST*
 REST is available from S1 mk2.
 Communication Method (between
appliance and center)
 RC Gate A: HTTPS only
 RC Gate BN: SMTP (1-way) or
HTTPS (2-way)
 RC Gate S Pro: HTTPS only
 Appliance ID2
 RC Gate A: V7800000001
 RC Gate BN: J77 /
(J76)Ymm00001
 RC Gate S Pro: S5600000001
 System Log
 RC Gate A: 2MB
 RC Gate BN: 4KB
 RC Gate S Pro: 500MB
 Communication Log
 RC Gate A: 2MB
 RC Gate BN: 64kB
 RC Gate S Pro: 10MB
 Security Log
 RC Gate A: 2MB
317
UZ –A1 - DIP Switches
 The DIP switches are used for
two functions.
 Function 1: To delete the
registered IP address in the
RC Gate A.
 Function 2: To clear the
settings of the RC Gate A.
 Switch number 6 is the switch
for the lithium battery.
 If you turn off this switch, the
data in the SD card is erased.
(It erases the flash memory.
This memory is copied to the
SD-card thus erasing the SD
card.)
O
N
1
2
3
4
5
6
7
8
SW1
318
Basil - Dipswitch SW1
Operation
mode
1 2 3 4
normal off off off on
reset IP
address on off off on
clear all
memory off on off on
firmware
update off off on on
DIP Switch SW1
Attention!
Do not use the
‘firmware
update’ DIP
switch setting.
319
Basil - Reset Switch SW1
 With the reset switch you can restart the RC Gate. To access
the switch, insert a pin into the opening on the upper cover of
the RC Gate and push the switch.
320
Basil - SD Card Slot
 In the past, the SD Card slot was used for local firmware
updating.
 This procedure is now only used in case of customised
firmware.
 Regular FW update must be done through the Center Server
GUI.
321
Basil - LED’s
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
322
Migrating from RC Gate BN to RC
Gate A
Detailed Procedure
323
1. Making Lists of Settings at the RC Gate BN UI
 Make lists of settings in the RC Gate BNs at the customer site.
 The RC Gate A must have the same settings.
 The Registered Device List must be taken from all the RC Gate BNs.
 Access the RC Gate BN UI in CE mode.
 Make screen dumps of the settings in the menus above of the RC
Gate BN UI.
324
2. Making lists of settings at the Center GUI
 At the Center GUI, log in as an Administrator.
 Make screen dumps of the Appliance Information for Admin, for
a RC Gate BN that has the full range of settings made.
325
3. Exporting Lists - Device List CSV 1/3
 Export Device List: Detail
 This exported device list can be used for the following:
 To designate devices to be registered under RC Gate A.
 To retrieve the M/R Date of each device
(after devices are registered at the center, the M/R Date is set
to 1 by default, so you need to edit the M/R Date by using the
Export Device List: Detail.)
 Export Device List: Simple
 After registering devices under RC Gate A, this exported
device list can be used to retrieve information for each
device by using “Update Device Info. by CSV Import”.
 Then, the information can be imported later after registering
the RC Gate A.
326
3. Exporting Lists - Device List CSV 2/3
 Export Device List: Detail and Simple
 Center GUI, Maintenance Menu, Export Device List: The lists for all
RC Gate BNs can be exported in one operation.
 You cannot do this if you do not have access to the Maintenance
Menu.
327
(7) (8)
3. Exporting Lists - Device List CSV 3/3
(1)
(2)
(3)
(4)
(5)
(6)
This is an example of Device List: Detail
(9)
328
3. Exporting Lists - Reporting CSV 1/2
 At the center, counter data from all appliances is saved for
up to a maximum of 40 days.
 Perform the download as two separate operations to
obtain all the data.
 You can download max 30 days at once.
329
3. Exporting Lists - Reporting CSV 2/2
 To get the data for all 40 days, do the operation twice. (e.g. First
30 days, followed by last 10 day.)
330
3. Exporting Lists - Supply CSV 1/2
 For customers to which the toner replenishment services
are provided, download Call History from the devices.
 At the center, supply data for all appliances is saved for
up to a maximum of 30 days.
 You can download max 7 days at a time.
331
3. Exporting Lists - Supply CSV 2/2
 To get the data for all 30 days, you must do the operation 5 times.
332
3. Exporting Lists - Call History 1/2
 For customers to which the call handling and/or toner
replenishment services are provided, download Call
History from the devices.
 You must capture the call history for each individual device.
(One at a time.)
333
3. Exporting Lists - Call History 2/2
 You have to download Call History CSV for each device
one by one.
 It will take about 20 minutes to download call history from
100 devices.
Example of Call History
334
4. Install the RC Gate A
 Input the settings from the old RC Gate BN (see step 1).
 Setup the Auto Discovery Settings.
 Register the RC Gate A with the @Remote Center.
335
5. Input the Appliance Information for Admin
 At the Center GUI, log in as an Administrator.
 Input the data from the screen dumps of the Appliance
Information for Admin that you made earlier.
336
6. Un-manage all Managed Devices 1/3
 This procedure is the opposite of the ‘Registering at the
Center GUI’ procedure.
337
(1)
(3)
(2)
6. Un-manage all Managed Devices 2/3
338
6. Un-manage all Managed Devices 3/3
(1)
(2)
(3)
339
(1)
(2)
(3)
7. Make a Call from each RC Gate BN
(4)
340
8. After Receiving the Calls
 After the Device Check Request call, check the Device
List again, to make sure that all devices were removed.
 Sometimes one or more devices are not removed and the
device data remains at the Gateway.
 In this case, it is not possible to remove the device from the
site, and only the solution is to contact Ricoh Europe support
to remove the data.
341
9. Remove the RC Gate BNs from the Center Server
 The operation is similar to removing the devices, except
this time we use Appliance in the Search menu.
(1)
(2)
(3)
342
9. Remove the RC Gate BNs from the Center Server
(1)
(2)
(3)
343
10. Register the Devices on the RC Gate A
 Register the devices on the RC Gate A, using the Device
Registration Wizard.
344
11. Check the Device List for the RC Gate A
 During the Device Registration Wizard, the RC Gate A
contacts the @Remote Center with the new device data.
 The device list at the Center GUI for the new RC Gate A
should contain all the registered devices.
 Check this list.
 Compare it with the exported device list CSV files that you
made earlier.
 Make sure that all devices are registered and Managed
 If any failed, investigate, and try to recover.
 If some devices still cannot be registered and Managed,
wait one day and try from the @Remote Center with
Remote Registration.
345
12. If Needed, make a Call from the RC Gate A
 In the Maintenance menu of
the RC Gate A UI:
 Click Maintenance
 Device Check Req. Call.
 Then click Start.
346
13. Remote Registration
 Wait until 24 hours have passed since the Auto Discovery
Settings were made in the RC Gate A at the customer
site.
 Check the Device List for the RC Gate A.
 If some devices are still not registered and Managed, make
sure that all the devices are listed as ‘Monitored’ or ‘Found’.
 If any devices are not listed, check their condition, and
recover them.
 Register the devices.
347
14. Register the Devices
 After you finished this step make a Device Check Request
call or wait for at least an hour (until automatic hourly polling
is done).
 Then check the list of registered devices.
 Compare it with the exported device list CSV files (from step
1).
 Make sure that all devices are registered and Managed
 If any failed, investigate and try to recover.
348
15. Retrieve the Old Device Information
 Import the device information from the old RC Gate BNs.
 Import it from the Exported Device List CSV’s that you made
in step 3.
 You need the Export Device List: Simple
349
(1)
(2)
(3)
(4)
15. Retrieve the Old Device Information: Export device list
Exported Device List: Simple
350
15. Retrieve the Old Device Information: Import device list
(1)
(2)
(3)
(4)
Retrieve data
351
15. Retrieve the Old Device Information
Exported Device List: Simple
All editable fields in device Information
can be exported and imported.
352
15. Retrieve the Old Device Information
(1)
(2)
(4)
(5)
(3)
353
16. Make Sure that M/R is Correct
 The M/R dates are all reset to 1. They must be set to the same
values as they were when registered on the previous RC
Gate(s).
Data when registered on
the RC Gate BN
Data after registering on
the RC Gate A
M/R Dates are all reset set to
1.
Specific M/R dates are set.
354
16. Make Sure that M/R is Correct
 Exported Device List: Detail (1)
(2)
(4)
(5)
You can edit
M/R Dates for a
max. 500
devices in one
operation.
Ricoh
Academy
Europe
@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a
355
Appendices
End

More Related Content

PDF
SIMATIC manager سيماتك منجر سيمنز
PDF
S7 PLCSim Advanced 2.0 - SIMATIC Siemens
PDF
9Tuts.Com New CCNA 200-120 New CCNA New Questions 2
PDF
[Advantech] ADAM-3600 training kit and Taglink
DOCX
2232016 Sample Implementation Plan1.htmlfileCUsers.docx
PPTX
Yokogawa Centum-VP-Engneering-Course.pptx
PDF
CertsOut Checkpoint-156-587 exam dumps pdf
PPTX
Service Assurance Constructs for Achieving Network Transformation by Sunku Ra...
SIMATIC manager سيماتك منجر سيمنز
S7 PLCSim Advanced 2.0 - SIMATIC Siemens
9Tuts.Com New CCNA 200-120 New CCNA New Questions 2
[Advantech] ADAM-3600 training kit and Taglink
2232016 Sample Implementation Plan1.htmlfileCUsers.docx
Yokogawa Centum-VP-Engneering-Course.pptx
CertsOut Checkpoint-156-587 exam dumps pdf
Service Assurance Constructs for Achieving Network Transformation by Sunku Ra...

Similar to @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a.ppt (20)

PPTX
Service Assurance Constructs for Achieving Network Transformation - Sunku Ran...
PDF
Siemens s7 300 programming
PDF
Signal-Oriented ECUs in a Centralized Service-Oriented Architecture: Scalabil...
PDF
IWAN Lab Guide
PPTX
Siemens PXC Controller Series Part-2
PDF
ATS @Station
PPT
C Cure Users Group Presentation Final 4
PPTX
The Internet of things for integration people - UKCSUG - public version
DOC
Parimal Resume
PPTX
01 introduction to_plc-pac_rev01_fa16
PDF
6 profiling tools
PPTX
cFrame framework slides
PDF
RAD Industrial Automation, Labs, and Instrumentation
PDF
Cucm 9.x licensing
PDF
Free Cisco 200-301 Practice Questions PDF – Download Demo Now
PDF
"Pass Cisco 200-301 CCNA Exam with Certifiedumps – Verified Dumps for Guarant...
PDF
Pass Your Cisco 200-301 CCNA Exam in 2025 with Confidence
PDF
Pass Cisco 200-301 CCNA Exam with Certifiedumps – Latest Dumps Cover Networki...
PDF
Cisco 200-301 Exam Practice Questions – Certifiedumps (Latest 2025 Version)
PPT
Installation et configuration de système
Service Assurance Constructs for Achieving Network Transformation - Sunku Ran...
Siemens s7 300 programming
Signal-Oriented ECUs in a Centralized Service-Oriented Architecture: Scalabil...
IWAN Lab Guide
Siemens PXC Controller Series Part-2
ATS @Station
C Cure Users Group Presentation Final 4
The Internet of things for integration people - UKCSUG - public version
Parimal Resume
01 introduction to_plc-pac_rev01_fa16
6 profiling tools
cFrame framework slides
RAD Industrial Automation, Labs, and Instrumentation
Cucm 9.x licensing
Free Cisco 200-301 Practice Questions PDF – Download Demo Now
"Pass Cisco 200-301 CCNA Exam with Certifiedumps – Verified Dumps for Guarant...
Pass Your Cisco 200-301 CCNA Exam in 2025 with Confidence
Pass Cisco 200-301 CCNA Exam with Certifiedumps – Latest Dumps Cover Networki...
Cisco 200-301 Exam Practice Questions – Certifiedumps (Latest 2025 Version)
Installation et configuration de système
Ad

Recently uploaded (20)

PDF
Sports Quiz easy sports quiz sports quiz
PDF
3rd Neelam Sanjeevareddy Memorial Lecture.pdf
PDF
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
PDF
STATICS OF THE RIGID BODIES Hibbelers.pdf
PDF
Physiotherapy_for_Respiratory_and_Cardiac_Problems WEBBER.pdf
PDF
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
PDF
2.FourierTransform-ShortQuestionswithAnswers.pdf
PDF
Complications of Minimal Access Surgery at WLH
PDF
Anesthesia in Laparoscopic Surgery in India
PPTX
Microbial diseases, their pathogenesis and prophylaxis
PPTX
Renaissance Architecture: A Journey from Faith to Humanism
PPTX
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
PDF
Computing-Curriculum for Schools in Ghana
PDF
Module 4: Burden of Disease Tutorial Slides S2 2025
PPTX
PPH.pptx obstetrics and gynecology in nursing
PDF
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
PDF
Basic Mud Logging Guide for educational purpose
PDF
FourierSeries-QuestionsWithAnswers(Part-A).pdf
PPTX
GDM (1) (1).pptx small presentation for students
PPTX
Introduction_to_Human_Anatomy_and_Physiology_for_B.Pharm.pptx
Sports Quiz easy sports quiz sports quiz
3rd Neelam Sanjeevareddy Memorial Lecture.pdf
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
STATICS OF THE RIGID BODIES Hibbelers.pdf
Physiotherapy_for_Respiratory_and_Cardiac_Problems WEBBER.pdf
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
2.FourierTransform-ShortQuestionswithAnswers.pdf
Complications of Minimal Access Surgery at WLH
Anesthesia in Laparoscopic Surgery in India
Microbial diseases, their pathogenesis and prophylaxis
Renaissance Architecture: A Journey from Faith to Humanism
1st Inaugural Professorial Lecture held on 19th February 2020 (Governance and...
Computing-Curriculum for Schools in Ghana
Module 4: Burden of Disease Tutorial Slides S2 2025
PPH.pptx obstetrics and gynecology in nursing
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
Basic Mud Logging Guide for educational purpose
FourierSeries-QuestionsWithAnswers(Part-A).pdf
GDM (1) (1).pptx small presentation for students
Introduction_to_Human_Anatomy_and_Physiology_for_B.Pharm.pptx
Ad

@Remote-Field service_full-ct_SOL_ppt_EN_9.1.a.ppt

  • 1. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 1 @Remote - New Remote Service Field service training Solution Master Full training Created by: Group L&D Version: 9.1.a Classification: Ricoh Family Group internal use only
  • 2. 2 Objectives  After completing this training you should be able to:  Explain the features of @Remote-NRS  Install, configure and maintain @Remote-NRS  Troubleshoot @Remote-NRS
  • 3. 3 Requirements  Training material and manuals  Devices with GW controller  RC Gate:  Basil or UZ-A1 (incl. options)  PC workstation with MS IE 6.0 or higher  User account for the Center Server GUI
  • 4. 4 Pre-requisites and exam  There are no pre-requisites for this training.  After this training, you can do the exam on My-Ricoh.
  • 5. 5 Module overview  1. @Remote overview  2. Installation  You can choose to do Chapter 2.2 Installation Basil and/or Chapter 2.3 Installation UZ-A1.  3. Maintenance  4. Reporting website  5. Troubleshooting & support  Appendices
  • 7. 7 Chapter overview  1.1 Introduction  1.2 System overview  1.3 Center Server GUI overview  1.4 Product compatibility
  • 9. 9 What is @Remote-NRS?  @Remote is a printing device management service.  With @Remote, the service organisation monitors, manages, and services the customer’s printing devices over the Internet.  With @Remote, the service organisation deliverers detailed device reports to the customer through a website.
  • 10. 10 @Remote features  Remote monitoring of counter and device information.  Remote monitoring of alerts and service calls.  Remote monitoring of supply calls.  Remote firmware update.  Remote SP-Mode reading/writing/executing.  Reporting website.
  • 11. 11 Why should the customer want @Remote?  Outsourcing to the service organisation  Automatic meter reading process.  Automatic toner supply process.  Automatic service call handling (pro-active service).  Reduce device downtime  Fast notification of service calls to the service organisation.  The service organisation can remotely analyse problems (e.g. SC-call history).  The service organisation can remotely do adjustments on devices (SP-mode / firmware-update).  Detailed fleet reports  Device management reports.  Supports TCO consultancy (reduce running costs).
  • 13. 13 System overview (Center Server) Service organisation Center Server GUI Center Server Customer Monitor/manage device data External RC- Gate (Basil/UZ-A1) Internal RC-Gate (Cumin) Device data
  • 14. 14 System overview (Reporting Server) Reporting Server Center Server Customer Device counter data Reporting website Service organisation Manage reporting website
  • 15. 15 RC-Gate (UZ-A1, Basil and Cumin) Center Server Customer environment Cumin Device data External RC Gate SNMP / HTTPS HTTPS / SMTP (E-mail only Basil) HTTPS
  • 16. 16 Other RC-Gate type  The UZ-S1 is not within scope of this training.  This RC-Gate is described in a separate training module on WICE.  Remote Communication Gate S with @Remote Connector.  Server application based on Web Smart Device Monitor.
  • 17. 17 Product positioning 2/2  Target Customer segment by appliance  For customer with over 1000 device:  UZ- S1 Pro (main) and UZ- A1 1000 Op (sub)  For customer with 100 – 1000 device:  UZ- A1 1000 Op (main) and UZ- S1 Pro (sub)  For customer with under 100 devices:  UZ- A1 L S M GMA, MA UZ-S1 UZ-A1 UZ-A1 1000 op 1000 Devices 100 Devices 20% (av.2,000 device) 43% (av.250 device) 38% (av.22 device) @Remote connecting MIF ratio (Average device per appliance)
  • 18. 18 Differences between the External RC Gates Category: RC Gate BN RC Gate A1 Device Type: @Remote Device GW MIB Device Other MIB Devices @Remote Device GW MIB Device Other MIB Devices Network Protocol to Device SOAP SNMP V1/V2 SOAP/ REST*1 SNMP V1/V2/V3 Monitored Devices (Un- Manage) 500 (including 100 Managed Devices) 100/1,000*2 Registered Devices (Manage) 100 (Including 5 Standalone) 500 1,500 (including 1,000 managed device) *2 PSTN*4 Yes Yes Yes No E-Mail*5 Yes Yes Yes No User Code Counter capturing *3 No No No Yes No No
  • 19. 19 Features on UZ-A1, that are not available on Basil  Support SNMP v3  SNMP v3 has more security options then previous versions.  Some companies demand the use of SNMP v3 capable devices before they allow the device onto their network.  No e-mail communication between RG gate and Center server. (e-mail notification still available.)  New RFU setting  Ability to block certain times where network activity may be high.  User code Counter Capturing  For in-house cost recovery  NOT in 1st production but after Firmware update (Firmware expected March 2010)  Prepared for Cosmos controller support  UZ-A1 supports REST a protocol supported by future Cosmos products  NOT in 1st production but after Firmware update. (TBA)
  • 20. 20 RC-Gate - Center Server communication  Communication between the RC-Gate and Center Server is always initiated by the RC-Gate.  When you enter a request on the Center Server GUI to carry out an action on an RC-Gate, the Center Server does NOT contact the RC-Gate, but waits to be polled by the RC-Gate.  The RC-Gate polls the Center Server once every hour.  The RC-Gate does not send device data when polling the Center Server. Center Server Customer environment Cumin External RC Gate Poll Center Server (1/hour)
  • 21. 21 Security  The Center Server does not communicate to the RC- Gate/devices without any indication from customer side.  Data is only transmitted after mutual authentication (SSL)*  Device data is encrypted before sending*.  Center Server security  Physical security  Redundant / load balancing  IP access restrictions  Backup / restore  The external RC-Gates are ISO 15408 certified (see next slide).
  • 22. 22 ISO 15408 certificate  The ISO 15408 is an international standard for evaluating security on IT equipment.
  • 23. 23 Used ports & protocols Occasion Comm. direction Port no. Protocol Type 1 RC Gate is connecting to device by FTP RC Gate => Device 20 FTP TCP 2 RC Gate is sending firmware. RC Gate => Device 21 FTP TCP 3 RC Gate is sending information by E-mail. RC Gate => Center Server 25 SMTP TCP 4 RC Gate is capturing MIB information of device. RC Gate => Device 161 SNMP UDP 5 RC Gate is authenticating in POP before SMTP. RC Gate => POP Server 110 POP TCP 6 RC Gate is sending notification to Center Server via HTTPS. RC Gate => Center Server 443 HTTPS TCP Device is sending notification such as Service Call. Device => RC Gate CE is operating RC Gate via laptop. CE’s laptop => RC Gate RC Gate is requesting firmware information. RC Gate => Center Server 7 RC Gate is capturing device information. RC Gate => Device 7443 HTTPS TCP 8 RC Gate is sending rescue information RC Gate => Device 7444 HTTPS TCP
  • 24. 24 Terminology  Center Server  (Center) GUI Server  Remote Gateway Center System  @Remote Center GUI Server  Communication Server (GUI)  Reporting Server  (Reporting) web portal  @Remote.net  Basil  External Box  RC Gate (BN)  UZ-A1  External Box  RC Gate A1  Cumin  NRS Embedded Device  RC Gate (CN)
  • 26. 26 Internet browser configuration  Supported browsers: Internet Explorer 6 or 7.  The Center Server GUI website uses ActiveX.  Configure the following in your browser ‘Internet Options’:  For other initials settings, such as ‘deleting temporary internet files’ and ‘enabling cookies’, see the Center Server GUI Manual. Add Center Server GUI website (https://rcg.support.ricoh.com) to ‘Trusted Sites’. Enable Run ActiveX controls and plug-ins’.
  • 27. 27 Center Server GUI login  https://rcg.support.ricoh.com/atremotecenter/MainServlet Login Start screen (information) Installation of ActiveX modules (only at first login or GUI changes).
  • 28. 28 Deleting ActiveX modules (OCX files)  Files to delete Center Server GUI OCX files from your PC.
  • 29. 29 Change/forgot password  A link to the ‘Single User ID website’ is available on the home page of the Center Server GUI.  Use this website to change your password or if you forgot your password. ‘Single User ID’ website https://suid.isd.ricoh.co.jp/index_en.html
  • 30. 30 Sites, Service Depots and Appliances  Device data and user access is grouped into:  Sites (service organisations)  Service Depots (service locations)  Appliances (RC-Gates). Ricoh France Customer 1 Appliance Appliance Appliance Customer 2 Appliance Appliance Appliance Customer 3 Appliance Appliance Appliance Ricoh Italy Ricoh Italy office Appliance Appliance Appliance Customer 1 Appliance Appliance Appliance Customer 2 Appliance Appliance Appliance Ricoh Spain Ricoh Spain West Appliance Appliance Appliance Ricoh Spain East Appliance Appliance Appliance Customer 1 Appliance Appliance Appliance Sites Service Depots
  • 31. 31 Center Server GUI menu overview  The available/displayed menus depend on your access rights. Registration Search Counter CSV Supply CSV Service Call Firmware Maintenance Administrator
  • 32. 32 Searching Appliances/Devices basics (1/3)  Search Appliance example Select Service Depot Search Appliance
  • 33. 33 Searching Appliances/Devices basics (2/3)  Appliance List Customer Name/ID Appliance S/N Appliance type
  • 34. 34 Searching Appliances/Devices basics (3/3)  Device List Device List Select Appliance
  • 35. 35 Load Site Information  Select the ‘Load Site Information’ button to update the available Sites / Service Depots in drop-down menu’s.  Examples when to click on ‘Load Site Information’: Service Depot drop- down menu is empty. Drop-down menu shows Service Depots from previous login account. An error message appears when you select a Service Depot. Or
  • 36. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 36 Exercise 1  Login to the Center Server GUI.  Search for an appliance.  Look at the Device List of an appliance.  Make yourself familiar with the available options.
  • 38. 38 Device types  There are 3 types of devices: @Remote/NRS (HTTPS) device Cumin External RC Gate HTTPS GW-MIB (SNMP) device MIB (SNMP) device (competitor/OEM/pre-GW) HTTPS SNMP SNMP SNMP
  • 39. 39 Service level per device type
  • 40. 40 Counter capture level per device type Device Usage Information @Remote Device (NRS Device) GW MIB device MIB device Total Supported Supported Supported Copy/Fax/Print Supported Supported N/A Color/Black Supported Supported N/A Scanner/LS/Scan to e-mail Supported N/A N/A A3/DLT Supported N/A N/A Duplex Supported N/A N/A ADF Supported N/A N/A Dot Coverage Supported N/A N/A # of Replaced toner Supported N/A N/A By Toner Supported N/A N/A By Paper size (A3/A4,,etc) Supported N/A N/A By Paper type Supported N/A N/A By Mode (S to D, N-up) Supported N/A N/A By Paper Tray Supported N/A N/A By Finishing (Staple/Punch) Supported N/A N/A By P/J (Page/Job) Supported N/A N/A By PDL (RPCS/PCL/PS) Supported N/A N/A SC/CC/MC call Supported N/A N/A Supply call (end / near end ) Supported Supported N/A
  • 41. 41 Product compatibility list  This list specifies the level of @Remote functionality per product. @Remote Compatibility Jul31 2009 Attachment (double click to open)
  • 42. 42 Device requirements  @Remote devices (HTTPS):  Network connected.  Autumn 2003 and later devices.  Security (DESS) module.  Correct Machine Certificate installed.  Correct ID2 Code.  GW-MIB / MIB (SNMP) devices:  Network connected.
  • 44. 44 Chapter overview  2.1 Installation overview  2.2 Basil installation  2.3 UZ-A1 Installation  2.4 Cumin Installation  2.5 Removal
  • 46. 46 Customer pre-survey  Center Server preparation  Customer name  Site / Service Depots  Find out information required to install Basil / UZ-A1 / Cumin / devices and calculate installation time.  Network infrastructure  Proxy information  Gateway information  Device IP-ranges (how many Basils/ UZ-A1s / Cumins?)  IP-addresses for Basil(s) / UZ-A1(s)  SNMP community names.  Device models & firmware levels  CSV file with Hostnames (if required)
  • 47. 47 Appliance registration overview  You have to pre-register an Appliance (RC Gate) to the Center Server before you can install it at the customer site. 1. Pre-registration on Center Server GUI 2. Installation at customer site Cumin Register RC Gate to Center Server Request Number ? ……… Request Number = xxxxxxxx RC Gate registered to Center Server
  • 48. 48 Device registration with a Basil/UZ A1 overview  Basil  Managed devices  Auto Discovery  Monitored devices  UZ-A1  Managed devices  Auto Discovery  Monitored devices
  • 49. 49 Managed devices Registered in External RC-Gate: • Device details • Device IP address Registered in device: • External RC-Gate IP address
  • 50. 50 Monitored devices External RC Gate scans the network and reads standard MIB info (total counter) from every found device.
  • 52. 52 How many devices can be registered?  Basil / Standard UZ-A1  Can ‘monitor’ 500 devices in total.  You can set a maximum of 100 devices (out of the 500) to ‘managed device’.  The rest of the devices are ‘monitored’.  UZ-A1 including optional memory.  Can ‘monitor’ 1000 devices in total.  You can set a maximum of 1000 devices to ‘managed’.  The rest of the devices are ‘monitored’.  Cumin  Always has 1 device (the device itself) registered as ‘managed’.
  • 53. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 53 2.2 Basil installation Click here to go direct to the UZ-A1 training. (if you want to skip the “Basil installation chapter”) .
  • 54. 54 Chapter overview  2.2.1 Basil overview  2.2.2 Pre-registering the Basil  2.2.3 Configuring/connecting the Basil to the customer’s network  2.2.4 Registering the Basil to the Center Server (through HTTPS)  2.2.5 Device Registration Wizard  2.2.6 Auto Discovery  2.2.7 Registering the Basil to the Center Server (through SMTP)
  • 56. 56 Basil hardware overview Front Rear LAN1 port (Maintenance port) LED’s LAN2 port (customer network port) Modem port (Not used in European region.) 1 2 3
  • 57. 57 Basil - Turning OFF  Procedure  You must remove the Basil from the Center Server, before removing the Basil. (See chapter “Removal”)  If you wan to move the Basil to a different location on the same network, then:  Unplug the power cord  Move the Basil  Plug in power
  • 58. 58 Basil login accounts https://<ip-address>  RC Gate Registrant  Default password: installation  Registration of Basil and devices  RC Gate Admin  Default password: admin  Used by the customers administrator https://<ip-address>/CE  CE Mode  Default password: rst107C/S  Used by the Customer Engineer  Can be disabled by RC Gate Admin  It is recommended to change the default passwords at first installation. !
  • 60. 60 Pre-registering a new Appliance (Basil/Cumin) Mandatory fields Optional fields Batch registration
  • 62. 62 Checking a pre-registered Appliance (Basil/Cumin) ‘Right-click- copy’, to copy registration number to the clipboard. Enter search conditions
  • 63. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 63 Exercise 2  Pre-register your Basil to the Center Server.  Check your pre-registered Basil on the Center Server.
  • 65. 65 Connect your PC to the Basil  Connect your PC to the Basil’s maintenance-port (LAN1). network-cable PC network settings: IP : 192.168.10.3 Subnet : 255.255.255.0 Basil maintenance-port (LAN1): IP : 192.168.10.1 (default) Subnet : 255.255.255.0
  • 66. 66 Login to the Basil  Access the Basil-UI (https://192.168.10.1)  Login to the Basil as ‘RC Gate registrant’
  • 67. 67 RC Gate and Device Settings  Select ‘RC Gate and Device Settings’
  • 68. 68 Basic settings  Select ‘RC Gate Settings’ / ‘Basic’.  Select the correct time zone and click on ‘Apply’. ! It is important to select the correct time zone.
  • 69. 69 Date and time settings  Select ‘RC Gate Settings’ / ‘Date/Time’.  Enter the correct date/time settings and click on ‘Apply’.
  • 70. 70 Network settings  Select ‘RC Gate Settings’ / ‘Network’.  Enter the correct network settings and click on ‘Apply’. LAN1 port (maintenance port) LAN2 port (customer network) DNS Server (optional)
  • 71. 71 Connect the Basil to the customer’s network  Connect the Basil’s LAN2 port to the customers network.  You can now still access the Basil-UI through the maintenance port, or you can access the Basil-UI through the customer’s network. Customer’s network
  • 72. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 72 Exercise 3  Configure your Basil for the customer network.  Connect your Basil to the customer network.
  • 74. 74 Login to the Basil  Login to the Basil as ‘RC Gate registrant’
  • 75. 75 RC Gate Registration Wizard  Select ‘RC Gate Registration Wizard’
  • 76. 76 Communication method setting  Select HTTPS as the communication method between the Basil and the Center Server.
  • 77. 77 Enter registration number  Enter the registration number (‘Request No’) and confirm/select the time zone.
  • 78. 78 Change IP Address Send Permission  The ‘IP Address Send Permission’ setting is optional.  This setting can only be changed at this point. It can NOT be changed after installation.
  • 81. 81 Email settings  When you have selected HTTP as communication method, Email settings are optional. Click ‘Next’ to skip the Email settings. Basil administrator to receive Email notifications (optional)
  • 82. 82 Proxy server settings  Enter proxy server settings if the Basil must use a proxy server to connect to Internet.
  • 84. 84 Registration number confirmation  Before the registration starts, the registration number is confirmed.
  • 85. 85 Registration at Center Server  The Basil is registering at the Center Server.
  • 86. 86 Registration result  The Basil is now registered at the Center Server.
  • 87. 87 Top page  After the Basil is registered, the ‘RC Gate Registration Wizard’ button is removed. Notice the two new buttons.
  • 88. 88 Checking your Basil in the Center Server  Searching your Appliance in the Center Server GUI. Check your Basil in the Appliance List (double click for Appliance info) Enter search conditions
  • 89. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 89 Exercise 4  Register your Basil to the Center Server (HTTPS).  Check your Basil in the Center Server GUI.
  • 91. 91 Device Registration Wizard overview 1. Register devices to Basil 2. Register devices to Center Server Center Server / Device list Center Server / Device list
  • 92. 92 Login  Login to the Basil as ‘RC Gate registrant’  Select ‘Device Registration Wizard’
  • 93. 93 Enter IP-address search range(s)  Select ‘IP address ranges’ (‘Host name’ will be explained later).  Enter the IP address search range(s)
  • 94. 94 Select devices to register  The Basil searches the network  The found devices are displayed  Select the devices you want to register  The device type (SNMP/HTTPS) is displayed
  • 95. 95 Obtain Request No. (1/2)  Click on ‘Obtain Request No.’
  • 96. 96 Obtain Request No. (2/2)  Results of ‘Obtain Request No.’
  • 97. 97 Registering devices  The devices are registered to the Basil
  • 98. 98 Register devices by CSV file (hostname or IP-address)  For each hostname entered in the CSV file the Basil will query the DNS server (must be configured in the Basil network settings) to find the device IP adress. CSV file The CSV file can contain both hostnames and IP-addresses separated by a comma or a new line.
  • 99. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 99 Exercise 5  Use the “Device Registration Wizard” to register devices.  Check the registered devices in the Center Server GUI.
  • 101. 101 Auto Discovery overview 1. Configure Auto Discovery 2. Manage monitored devices (optional) Center Server / Device list Center Server / Device list Center Server / Device list
  • 102. 102 Login  Login to the Basil as ‘RC Gate registrant’  Select ‘Auto Discovery Setting Wizard’
  • 103. 103 Auto Discovery settings  Enter the Auto Discovery settings
  • 104. 104 Auto Discovery IP-Address ranges  Set more search ranges via ‘add’ or ‘impor a CSV file’.
  • 105. 105 Configuring Auto Discovery (3/5)  A summary of search ranges is displayed.
  • 106. 106 Result of Auto Discovery  Devices which are found with the Auto Discovery option appear as ‘monitored’ on the Center Server.
  • 107. 107 From ‘monitored’ to ‘managed’  To make ‘monitored’ devices ‘managed’, select the devices and select ‘Manage Devices’. Select to manage as ‘HTTPS’ or ‘SNMP’ device. Enter M/R Date
  • 108. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 108 Exercise 6  Configure Auto Discovery on the Basil.  Check the result of Auto Discovery on the Center Server GUI.  Make some of the ‘Monitored’ devices ‘Managed’ devices.
  • 110. 110 Login  Login to the Basil as ‘RC Gate registrant’  Select ‘RC Gate Registration Wizard’
  • 111. 111 Settings  Select the communication method (SMTP).  Enter the Request Number and the Time zone.  RC Gate registrant E-mail address (optional). Will receive an E-mail with registration result.  Enter the date/time. optional
  • 113. 113 Enter the SMTP settings Optional Mandatory Optional
  • 114. 114 Registration result  Result message  If an RC Gate registrant E-mail address has been configured (optional), the results from the registration will be sent to the this E-mail address.
  • 115. 115 Registering devices whit SMTP registered Basil  When you register the Basil through SMTP, you can only configure Auto Discovery (no Device Registration Wizard).  The result of Auto Discovery will not be visible in the Center GUI (no device list).  If you configured an RC-Gate admin E-mail address (optional), results from the Auto Discovery function will be sent the RC-Gate admin address.  E-mail content to RC-Gate admin is NOT encrypted. One text file for each found device
  • 116. 116 Basil registered with SMTP limitations  It is not recommended to register the Basil with SMTP and should only be done when absolutely necessary.  Registering the Basil with SMTP gives very limited Center Server functionality:  Devices can not be managed. (Devices can only be monitored by Auto Discovery function.)  Only MIB counter information.  No device list.  No device status indication.  No Service/Supply Call indication.  No remote firmware update.  Only available functions:  Counter CSV file and Reporting website functionality.
  • 117. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 117 2.3 UZ-A1 Installation Click here to go direct to the Cumin training. (if you want to skip the “UZ-A1 Installation chapter ”).
  • 118. 118 Chapter overview  2.3.1 UZ-A1 overview  2.3.2 Pre-registering the UZ-A1  2.3.3 Options for the UZ-A1  2.3.4 Configuring/connecting the UZ-A1 to the customer’s network  2.3.5 Registering the UZ-A1 to the Center Server (through HTTPS)  2.3.6 Device Registration Wizard  2.3.7 Auto Discovery
  • 120. 120 UZ-A1 hardware overview Front Rear LAN port (customer network port) PC port (Maintenance port) LED’s Power Button LCD Display
  • 121. 121 UZ-A1 - Turning ON  Plug in the power cord of the UZ-A1.  There is no power switch to turn on.  Note that if the customer uses DHCP, the IP address of the RC Gate A may be changed after turning the UZ-A1 OFF and ON.
  • 122. 122 UZ-A1 - Turning OFF  Procedure  You must remove the UZ-A1 from the Center Server, before removing the UZ-A1.  Procedure 1. Either; - Select "Shut Down RCGate" in the UI of the UZ-A1. OR - Hold the "Shutdown" button on the front of the UZ-A1 for 5 seconds or longer. 2. Unplug the power cord of the UZ-A1.  If you unplug the power cord without doing step 1, the memory could be damaged and log data lost.
  • 123. 123 UZ-A1 login accounts  https://<ip-address>:9443  Administrator  Default password: administrator  Registration of UZ-A1 and devices  Change setting/configurations  General user  Default, this account does not exist (An administrator must create it)  When you select ‘General user’, then the configuration option is greyed out!  User can view information of ‘managed devices’  https://<ip-address>:9443/CE  CE Mode  Default password: rst107C/S  Used by the Customer Engineer  Can be disabled by RC Gate Admin  It is recommended to change the default passwords at first installation. !
  • 124. 124 Features on UZ-A1, Device Management  The user can check/monitor the status of managed devices on the UZ-A1 in the device management menu. (Through the web interface.)  The menu includes:  Device list  Call history  Counter list  Individual device status
  • 125. 125 Features on UZ-A1, @Remote On/Off  On the UZ-A1, the customer can disable @Remote communication. (This is supposed to be a temporary measure.)  For example, when the customer needs to isolate the cause of a problem during network troubleshooting.  This is not available on the Basil.  While @Remote is disabled, the Center GUI can read the settings in the appliance, but can not make changes.  The customer administrator or a technician can make changes, using the UI of the appliance.
  • 126. 126 Features on UZ-A1, Notification Timing  On the UZ-A1 you can specify what to do when it receives a call from a device.  This is not available on the Basil.  There are three settings.  No Send: The call is not passed on to the @Remote Center  Real Time: The call is passed on immediately after it is received from the device.  Periodic: Calls are passed on either Daily, Weekly, or Monthly.  The setting is made from the Center GUI.  Center GUI: Administrator menu – Appliance Information for Admin – Notification tab
  • 127. 127 Features on UZ-A1, Retries  With this function:  You can specify on the Center GUI how many retries (and at what interval) an RC Gate A must pass auto calls from devices to the @Remote Center.  Administrator menu – Appliance Information for Admin – Notification tab  This is not available on the Basil.
  • 128. 128 Features on UZ-A1, User counter capture  With this function:  The user can retrieve individual user counters.  This is not available on the Basil  You can test if the user counter information can be obtained from each device (Via the UZ-A1 UI).  Enter a device's IP address to check if it is possible to acquire per-user counter information for that device.
  • 130. 130 Pre-registering a new Appliance Mandatory fields Optional fields Batch registration
  • 132. 132 Checking a pre-registered Appliance ‘Right-click- copy’, to copy registration number to the clipboard. Enter search conditions
  • 133. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 133 Exercise 7  Pre-register your UZ-A1 to the Center Server.  Check your pre-registered Appliance on the Center Server.
  • 135. 135 Available options  There are two options available. 1. DIMM Memory :  With this DIMM installed, the RC Gate A can store/export user counters. 2. SSD Memory:  Increases the maximum number of managed devices from 100 to 1000.  When you install the SSD, you must also install the DIMM.  The activation of the options must be done by an engineer.  You must first remove the UZ-A1 from the center server!  When you activate the options, a new (larger) data table is created. (All the existing data is removed.)  Then you must register the UZ-A1 again.
  • 136. 136 Installing the options  Install the DIMM and the SSD.  You can install only the DIMM.  When you install the SSD, you must also install the DIMM. SSD DIMM
  • 137. 137 Connect your PC to the UZ-A1  Connect your PC to the UZ-A1s maintenance-port (PC). network-cable PC network settings: IP : 192.168.10.3 Subnet : 255.255.255.0 UZ-A1 maintenance-port (PC): IP : 192.168.10.1:9443 (default) Subnet : 255.255.255.0
  • 138. 138 Login to the UZ-A1  When options are installed then first proceed by checking the available memory and enabling the extended function setting.  Follow the steps in the next few slides  Access the UZ-A1-UI via CE login
  • 139. 139 Memory Operation Check  Do the memory operation check to ensure that the options are recognized by the UZ-A1 . (1) (2) (3) (4)
  • 140. 140 Extended Function Setting  Enable the options.  Switch ‘Extend the number of monitored devices’ to Use.  Once ‘Use’ has been selected, the setting cannot be changed to back.
  • 142. 142 Settings required for using the RC Gate A  The following settings are required for using the UZ-A1.  Time Zone and Date/Time Settings  HTTP Proxy Settings  Email Settings  Change IP Address Send Permission  Entering Request No.  Starting Registration
  • 143. 143 Login to the UZ-A1  Access the UZ-A1-UI (https://192.168.10.1:9443) 1. Login as ‘administrator’ 2. Select ‘Initial settings’ (1) (2)
  • 144. 144 Set up the RC Gate A  Set up the RC Gate A  Run the ‘Setup Wizard’  You can also select the ‘RC Gate Configuration’ menu and browse through the settings manually.  Follow the steps and input all relevant information.
  • 145. 145 Date/Time settings  Select ‘RC Gate Settings’ - ‘Date/Time’.  Select the correct time and time-zone and click on ‘Apply’. ! It is important to select the correct time zone.
  • 146. 146 Network settings  Select ‘RC Gate Settings’ / ‘Network’.  Enter the correct network settings and click on ‘Apply’. PC port (maintenance port) LAN port (customer network) DNS Server (optional)
  • 147. 147 IP Address Send Permission  Choose permit (default) if you want all functionalities to be available:
  • 148. 148 Network settings  You can setup e-mail notification.
  • 149. 149 Setup complete  When the initial setup is complete, you will get the following notification:
  • 150. 150 Connect the UZA1 to the customer’s network  Now you can connect the UZ-A1 - LAN2 port to the customers network.  You can still access the UZ-A1 UI through the maintenance port, or you can access the UZ-A1-UI through the customer’s network. Customer’s network
  • 151. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 151 Exercise 8  Configure your UZ-A1 for the customer network.  Connect your UZ-A1 to the customer network.
  • 154. 154 Login to the Basil  After the initial setup, you get the following screen.  Select ‘@remote Service Registration Wizard’.  If you already logged out, then login to the UZ-A1 as ‘Administrator’.  Select ‘Initial settings’ - ‘@remote Service Registration Wizard’.
  • 155. 155 Enter registration number  When you input the Request Number use copy-paste to prevent typing errors.
  • 156. 156 Confirm/change network settings 1/2  Double check all network/proxy settings.
  • 157. 157 Confirm/change network settings 2/2  Click ‘Confirm with server’
  • 158. 158 Appliance registration 1/2  If this error message occurs, make sure that the request number is correct. (copy-paste)  If confirmation is successful, then click ‘Start Registration’
  • 159. 159 Appliance registration 2/2  A progress bar will show during the registration process.  If registration is successful, then click ‘Finish’
  • 160. 160 Checking your UZ-A1 in the Center Server  Searching your Appliance in the Center Server GUI. Check your UZ-A1 in the Appliance List (double click for Appliance info) Enter search conditions
  • 161. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 161 Exercise 9  Register your UZ-A1 to the Center Server.  Check your UZ-A1 in the Center Server GUI.
  • 164. 164 Device Registration Wizard 1/9  Log in as ‘Administrator’  Select ‘Initial Settings’
  • 165. 165 Device Registration Wizard 2/9  Use the Device Registration Wizard.  Devices found with the Device Registration Wizard are ‘managed’.  If you see a device with condition “Managed - Found” on the Center Server, then you must wait, the condition will automatically change to “Managed – Registered”.
  • 167. 167 Device Registration Wizard 4/9 (2) (1) (3)
  • 173. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 173 Exercise 10  Use the “Device Registration Wizard” to register devices.  Check the registered devices in the Center Server GUI.
  • 176. 176 Auto Discovery Setting Wizard 1/6  Use the Auto Discovery Setting Wizard.  Devices found with the Auto Discovery Setting Wizard are ‘monitored’.  You can select devices that are found on the device list on the Center GUI.  When you click ‘Register Devices’.  They become ‘managed’ devices.  If you see a device with condition “Managed - Found” on the Center Server, then you wait, the condition will automatically change to “Managed – Registered”.
  • 177. 177 Auto Discovery Setting Wizard 2/6  Select ‘Auto Discovery’
  • 178. 178 Auto Discovery Setting Wizard 3/6 (1) (2) (3)
  • 179. 179 Auto Discovery Setting Wizard 4/6 (1) (2)
  • 180. 180 Auto Discovery Setting Wizard 5/6 (1) (2)
  • 182. 182 Extended Device Search  During Auto Discovery, problems may occur with Ricoh devices that contain controllers from other manufacturers (such as EFI or Samsung).  With this new feature you can enable / disable a different type of search function.  Set to Enable to increase the change to find those devices.
  • 183. 183 IP Address Exclusion 1/2  It is possible to set IP addresses which you (or the customer) do not wish to be searched by the UZ-A1.  You can set max. 255 IP addresses.
  • 184. 184 IP Address Exclusion 2/2  During Auto Discovery, the excluded addresses are skipped.  When an excluded machine uses DHCP and its IP address changes into a discoverable address, it will not be skipped during the next Auto Discovery.  When you use IP Address Exclusion, it is best to use reserved IP addresses for the devices. (Or at least for the excluded devices.)
  • 185. 185 From ‘monitored’ to ‘managed’  To make ‘monitored’ devices ‘managed’, select the devices and select ‘Manage Devices’. Select to manage as ‘HTTPS’ or ‘SNMP’ device. Enter M/R Date
  • 186. 186 Remote registration 1/2  During Auto Discovery, the external RC gate collects the following for each device: Device S/N, IP address, MAC address  The data at the @Remote Center is normally 1 day old.  Only the IP address and MAC address are used for Registration.  Registration at the center can only go ahead if the external RC gate can connect to the specified IP address and the MAC address is correct.  The center GUI sends the IP address and MAC address to the external RC gate.  The external RC gate checks that the device with that IP address has the correct MAC address.  Then the external RC gate registers that device at the @Remote Center.  If the device power is off at the time of registration, or if the IP address has changed due to DHCP (the data at the center is one day old), the external RC gate sends an error to the center.
  • 187. 187 Remote registration 2/2  If a different device responds to the IP address (i.e., the MAC address is different), or if there is no device at that IP address, the UZ-A1searches again within the same segment for a device that has the MAC address in question.  This only works within the same segment. So, if the device was moved to another room, it may be in another segment, and will not be found.  The Basil can only accept one registration request at a time from the Center GUI (up to 100 devices per request).  If there are more than 100 devices for the Basil, you must wait until the first batch has been registered, before you can send a registration request for the next 100.  Otherwise, the RC Gate will return an error message (busy – request not accepted).  For the UZ-A1, up to 100 requests can be queued.
  • 188. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 188 Exercise 11  Configure Auto Discovery on the UZ-A1.  Check the result of Auto Discovery on the Center Server GUI.  Make some of the ‘Monitored’ devices ‘Managed’ devices.
  • 190. 190 Cumin installation overview 1. Pre-register Cumin to Center Server 2. Proxy settings 3. Register appliance/device to Center Server
  • 191. 191 Pre-register Cumin to Center Server  Pre-registering a Cumin to the Center Server is the same as pre-registering an external RC gate to the Center Server.
  • 193. 193 Register the appliance/device  Select ‘Setup RC Gate’  Enter the Request No. Select ‘Confirm’.  The confirmation result is displayed.  Select ‘Program’. The registration result is displayed.
  • 194. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 194 Exercise 12  Register a Cumin device to the Center Server.  Check the registered appliance/device in the Center Server GUI.
  • 196. 196 Removing a device  To remove a device from the Center Server select the device and click on ‘Remove Devices’. The status of the device will then be ‘removing’.  The next time the Appliance (external RC gate or Cumin) contacts the Center Server, the device will be removed from the Center Server.  If the Appliance is physically disconnected or it’s power is off, the device will be removed from the Center Server after 4 hours.
  • 197. 197 Removing an Appliance  IMPORTANT! : Before removing an Appliance (external RC gate or Cumin) from the Center Server, first remove all devices from that Appliance.  When all devices of the Appliance are removed, select the Appliance and click on ‘Remove Appliance’. The status of the Appliance will then be ‘removing’.  The next time the Appliance (Basil or Cumin) contacts the Center Server, the Appliance will be removed from the Center Server.  If the Appliance is physically disconnected or it’s power is off, the Appliance will be removed from the Center Server after 90 minutes.
  • 199. 199 Chapter overview  3.1 Search menu  3.2 Device information  3.3 Counter / Supply CSV  3.4 Service Calls  3.5 Email notifications  3.6 Solution list  3.7 Firmware Update  3.8 Calendar list  3.9 Administrator menu
  • 201. 201 Search Appliance  The search result is displayed in the Appliance list. You can use the % character as wildcard in this fields. Leave this field blank to search through all Service Depots. In that case you must use at least one other search field.
  • 202. 202 Search Device  The search result is displayed in the Device list. This field is mandatory, you cannot leave this field blank. Only in this field you can use the % character as wildcard. Customer name is CaSe sensitive
  • 203. 203 Searching devices through Search Appliance  If you need to search a device by Device S/N, through all Service Depots, this is the most easiest way:  The search result is an Appliance displayed in the Appliance list. This is the Appliance containing the device. Leave this field blank. Enter the Device S/N
  • 204. 204 Search for disconnected devices/appliances (1/3) Select ‘Search Appliance’ or ‘Search Device’  This function only works for managed devices.
  • 205. 205 Search for disconnected devices/appliances (2/3)  Disconnected Appliance / Device List
  • 206. 206 Search for disconnected devices/appliances (3/3)  You can also check if devices might be disconnected by checking the Device list.
  • 208. 208 Device Information screen (1/2)  Double click on a device to go to the Device Information screen. Optional information fields Mandatory information fields
  • 209. 209 Device Information screen (2/2)  Update  Sends the updated fields to the Center Server  Call History  Exports a .csv file of calls (closed & open) (see chapter ‘Service Calls’).  Device Status  Displays device status information.  Comm  Read/write device information and read/write/execute SP- modes.
  • 210. 210 Device Status  State  Machine status  Jam Log  Count Log  Over 400 counter items  Time Log  Total duration main motor  SC Log  Function  Fusing temp, ID sensor offset, etc.
  • 211. 211 COMM overview (1/2)  Communication Main menu Read / Write / Execute requests are displayed here. If the request has been processed, double click on the request to display the result.
  • 212. 212 COMM overview (2/2)  Read  Read device information at next polling interval.  After clicking start use the “refresh” button to see the Next Polling Time  Write  Write (new) values to SP-Modes at next polling interval.  After clicking start use the “refresh” button to see the Next Polling Time  Execute  Reset SC, PM counters, Jam Counters or force a toner supply call at next polling interval.  After clicking start use the “refresh” button to see the Next Polling Time
  • 213. 213 Read request Select the items you want to read from the device. The result of the read request is displayed here, after the Appliance has polled the Center Server. (See ‘Next Polling Time’). Select the items you want to read from the device.
  • 214. 214 Write request Before you can write SP-modes, you must first do a read request here. After the read request has been performed, the current values are displayed under ‘Present’. Then you can enter a new value under ‘New’ and click ‘Write Start’. Do not forget to mark the checkboxes for the SP-modes you want to ‘write’.
  • 215. 215 Execute request  Only the SP-modes which are available to execute are displayed.
  • 216. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 216 Exercise 13  Read the device information and SP modes from a device.
  • 219. 219 Counter/Device info communication to Center Server  Counter and Device information is collected by the RC-Gate, send to the Center Server and processed by the Center Server as shown below. Center Server external RC gate Cumin Collection Managed devices (HTTPS) 1 / 12 hours (retry after 6 hours) Managed devices (SNMP) 1 / 12 hours (retry after 6 hours) Auto Discovery enabled AD schedule (daily/weekly/ monthly) Transfer to CS Managed (HTTPS) 1 / Day Managed (SNMP) 1 / Month (MR Date) Auto Discovery AD schedule CS Processing Managed (HTTPS) Max. 1 Day Managed (SNMP) Max. 1 Day (only latest or M/R counter is saved) Auto Discovery Max. 1 Day (only latest or M/R counter is saved)
  • 220. 220 New Counter-CSV request Request settings (explained later)
  • 222. 222 Download Counter-CSV  If the request status is ‘completed’, double click on the request to download the CSV file(s).
  • 223. 223 Counter-CSV request main settings overview Immediate or Scheduled Meter Reading or Reporting Download to ‘Your PC’ or ‘Back-End’ CSV Separator Site Name / data range Optional filters
  • 224. 224 Meter Reading Counter-CSV request  The downloaded file for an M/R Counter-CSV request can contain 2 files.
  • 225. 225 Meter Reading Counter-CSV file content 1 line per device: The counters from the M/R data. OR (if M/R counters are not available) The latest acquired counters within the specified data range.
  • 227. 227 Reporting Counter-CSV file content Multiple lines per device: All counters for all devices within the specified data range.
  • 228. 228 Scheduled Counter-CSV request List with Counter-CSV requests Schedule settings
  • 230. 230 Supply Call communication to Center Server  Supply Calls are notified by the RC-Gate, send to the Center Server and filtered by the Center Server as shown below. Center Server external RC gate Cumin Notification Managed devices (HTTPS) Immediate Managed devices (SNMP) After SNMP polling. (Default = every 10 min.) Auto Discovery devices N.A. (no Supply Calls) Transfer to CS Managed (HTTPS) Immediate Managed (SNMP) Immediate Auto Discovery N.A. CS Filtering Depending on the device (prefix) multiple calls will be filtered using 1 of the following 2 methods: Total Counter Number of bottles used  Supply Call settings on the device are not always ‘ON’ by default  In the embedded Excel document you can find the default settings of Supply Call related SP modes per controller series. ! Microsoft Excel Worksheet
  • 231. 231 Supply-CSV overview  Using the Supply-CSV menu works the same as Counter- CSV menu. New Supply- CSV request List with Supply-CSV request Double click to download Supply-CSV
  • 232. 232 Supply-CSV request settings Toner or All Supplies  Most settings work the same as in Counter-CSV request.
  • 233. 233 Supply-CSV file content Supply Calls received in the specified data range
  • 234. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 234 Exercise 14  Create a new request for Counter CSV (report)  Create a new request for Supply CSV (report)  Download the reports
  • 236. 236 ERP linkage  Counter and supply-call data can be send to your ERP system using the Ricoh Europe Common Server.  This allows you to automate processes, such as billing and toner replenishment, through your ERP system.  The procedure to create the link to your ERP system is outside the scope of this training.  Contact Ricoh Europe through your default support route if you require more information. Service organisation ERP system Common Server (EU) Center Server Counter/ supply- call data Counter/ supply- call data
  • 238. 238 Service Call communication to Center Server  Service Calls are received by the RC-Gate and send to the Center Server as shown below. Center Server external RC gate Cumin Notification Managed devices (HTTPS) Immediate Managed devices (SNMP) After SNMP polling. (Default = every 10 min.) Auto Discovery devices N.A. (no Service Calls) Transfer to CS Managed (HTTPS) Immediate Managed (SNMP) Immediate Auto Discovery N.A. CS Processing (to show in Call List) Type A SC- Call Immediate. Type B/D SC-Calls After 30 minutes.
  • 239. 239 Call List  The Call List shows all incoming calls from devices/appliances.  The Call List does NOT show Supply Calls.
  • 240. 240 Call Detail  Double click on a call to go to the Call Detail screen.
  • 241. 241 Manual Call on an MFP  Press <clear><0><0><clear/stop> (keep the last button pressed until the “Remote Diagnostics” screen appears on the operation panel.  Press the “Call” button and wait for a completion message.
  • 242. 242 Manual Call on an LP  On LP’s with a 2-line display:  Press and Hold the "Escape" Key for about 5 seconds.  A Message will appear in the Operation Panel allowing you to Place a Call.  On LP’s with a 4-line display:  Press the "Menu" key.  Go to the "Remote Service" menu.
  • 243. 243 Closing Calls  You can close all calls for the same device by selecting the close all calls checkbox  You can close calls one-by-one by selecting the applicable checkboxes and click the ‘Update’ button  You can select only pre-defined solutions (also see solutions slide) for a call you want to close
  • 247. 247 New Email List You can enter multiple email addresses separated by a comma. Use this setting to receive a daily Email with all disconnected Appliances within your Site/Service depot.
  • 248. 248 Email Notification Timing  Depending on the local infrastructure receiving Call Emails from the Center Server can take up to 5 minutes  If no Email is received check spam filters on Email servers or try an external email address.  If it looks like email is received more than 30 minutes later, check all (device/ external RC gate) regional settings (date/time)
  • 250. 250 Solution The default sort is alphabetic. You cannot change this.
  • 251. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 251 Exercise 16  Add a new “Solution” named “Manual Closed Manual Call”  Add a new “Call Email Entry” type “Manual Call”  Create a Manual Call on one of the training machines  Check your mailbox  Close the call with your newly added solution
  • 253. 253 Remote Firmware Update (RFU)  You can update firmware for appliances and devices from the Center Server.  On the UZ-A1 the are some extra specifications that are not available for the Basil:  RFU Enable/Disable  RFU Prohibition Interval  RFU Shift Device Firmware Update Time
  • 254. 254 RFU Enable/Disable 1/2  For the model RC Gate BN:  You must individually prohibit RFU at each device connected to the RC Gate BN.  For the RC Gate A:  You can prohibit RFU for all devices with a setting in the RC Gate A.
  • 255. 255 RFU Enable/Disable 2/2  For the RC Gate A, there are two settings: 1. Enable/disable RFU for the appliance. 2. Enable/disable RFU for the devices (this is a new function for RC Gate S Pro/RC Gate A).
  • 256. 256 RFU Prohibition Interval  Normally, when setting up at the Center GUI, RFU is set for a convenient time for the customer. It must be finished within a set period (default: 3 days).  If RFU is done during office hours, it can be inconvenient for the customer.  With the UZ-A1 appliance, it is possible to prohibit RFU during working hours.  If RFU is in progress when working hours start, it is suspended, until the end of working hours. Then it resumes.
  • 257. 257 RFU Shift Device Firmware Update Time 1/2  An appliance can monitor devices in (very) remote locations.  For example, the external RC Gate an be in Moscow, but some devices can be in London. (a different time zone.)  If the RFU is set up for 17:00 Moscow time, then the RFU on the devices in London could start during London office hours.  On the UZ-A1 you can prevent this.  You set up the time shift function for the devices in different time zones.  This is not available on the Basil.
  • 258. 258 RFU Shift Device Firmware Update Time 2/2  To operate this UZ-A1 feature, you specify network segments that require a time shift and the time shift that is needed  You can also import a .csv file containing the network segments that need the time shift.
  • 260. 260 Model Select Microsoft Excel Worksheet The embedded Excel file lists device prefixes. You can use this list to select the correct model before updating firmware.
  • 261. 261 Search Device Although the list shows SNMP devices, you can NOT update these devices.
  • 262. 262 Firmware Select The list of available types of firmware depend on the selected model.
  • 263. 263 Firmware Update Only available for UZ-S1/A1 appliances. Update schedule
  • 266. 266 Device firmware update through the Basil GUI  If you can also update device firmware at the customer site though the Basil GUI.  For more details about this procedure, see the Basil Service Manual.
  • 267. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 267 Exercise 17 Update the firmware of your external RC gate (through Center Server GUI) Update the firmware of a device (through Center Server GUI)
  • 269. 269 Add new calendar  The calendar specifies the office hours of the service organisation.  Devices will not display ‘an engineer will be sent’ when an error occurs outside office hours.
  • 274. 274 Reporting website introduction  The reporting website (@Remote.net) provides the @Remote reporting features to the customer. Multiple reports Export to Excel / CSV Graphical reports 3rd parties reporting
  • 275. 275 Reporting server overview  Every day device counter data on the Center Server is send to the Reporting Server. Reporting Server Center Server Device counter data Customer Service organisation Manage reporting website Reporting website
  • 276. 276 Link between Center Server and Reporting Server  Communication between the Center Server and Reporting Server is one-way (from Center Serv. to Reporting Serv.). Reporting Server Center Server Device counter data
  • 277. 277 Reporting website URL’s  https://www.atremote.net/ricoh-europe  https://www.atremote.net/infotec  https://www.atremote.net/gma  https://www.atremote.net/nrg Ricoh Infotec GMA NRG US EU Reporting Server
  • 278. 278 Login  When you do not have a user account, you can have a look at the website using the following user:  User Name: Sample  Password: password
  • 279. 279 User agreement  At first log-in each user must accept the user agreement to continue.  The User Agreement is always available for your review, via a link on the home page of the website.
  • 280. 280 Home page overview (1/2)  Homepage (https://atremote.net/ricoh-europe) Choose language Reports
  • 281. 281 Home page overview (2/3)  Select Appliances Click to expand
  • 282. 282 Home page overview (3/3)  Change Customer
  • 283. 283 Reporting website (@Remote.net) User Guide  The user guide can be downloaded from the website.
  • 285. 285 Basil / UZ-A1 - login & logout  If you close your browser while you are logged into the external RC Gate, the session is NOT terminated  The session will time-out after 30 minutes.  Therefore, always use the ‘Logout’ button to close the session.
  • 286. 286 Procedure: Migrating from RC Gate BN to RC Gate A 1. RC Gate BN & device information backup  Create a list of Appliance information (Screen dump)  To input later during RC Gate A installation.  Export: Simple Device Information CSV files from Center GUI  To import later to new Appliance during device registration procedures  If you want to keep this information, then export for your own reference: Reporting CSV, Supply CSV and Call history.  Un-manage devices 2. Install UZ-A1  Retrieve: Request number from Center GUI  Setup: Appliance  Run: Device Registration Wizard  Run: Auto Discovery Settings Wizard  Upload: Device Information CSV files into the correct Appliance via Center GUI. 3. Remove RC Gate BN  Unregister Appliance at Center GUI  Remove RC Gate BN
  • 287. 287 RC Gate migration Step-by-Step Migrating from RC Gate to RC Gate-A At the RC Gate. Create a list with all Registered Devices. At the RC Gate. Access the RC Gate UI in CE mode. At the Center GUI. 2. Make screen dumps of the Appliance Information for Admin. (Log in as an Administrator.) At the Center GUI. 3.1 Export: Device List ( Simple) At the Center GUI. 3.2 Export: Reporting CSV At the Center GUI. 3.3 Export: Supply CSV At the Center GUI. 3.4 Export: Call History At the RC Gate A. Register the RC Gate A on the @Remote Center. At the RC Gate A. 4. Install the RC Gate A. At the RC Gate A. When asked to input settings, input the settings from the old RC Gate (see step 1). At the RC Gate A. Make sure that the Auto Discovery Settings are set up. At the Center GUI. 5. Input the data from the screen dumps of the Appliance Information for Admin that you made earlier. (You must log in as an Administrator.) At the Center GUI. 6. Un-manage all Managed Devices. At the RC Gate. 7. Make the Device Check Request call from each of the RC Gates to be removed. At the Center GUI. 8. Check on the Device List, that all devices are removed. At the Center GUI. 9. Remove the RC Gates from the Center. At the RC Gate-A. 10. Register the devices. At the Center GUI. 11. Check the Device List from the RC Gate A. (Compare it with the exported device list CSV files.) At the RC Gate-A. 12. When devices are listed as Found, you can make a Device Check Request Call from the RC Gate A. To speed-up the registration process. Wait for 1 hour Wait until 24 hours have passed since the Auto Discovery Settings were made in the RC Gate A at the customer site. At the Center GUI. 13/14. You can use Remote Registration to try to register devices that are still not registered If some devices are still not registered and Managed, make sure that all the devices are listed as ‘Monitored’ or ‘Found’. If any devices are not listed, check their condition, and recover them. 15. Retrieve the Old Device Information Import the device information from the old RC Gates. Import it from the Exported Device List CSVs that you made in step 3. You need the Export Device List: Simple 16. Make Sure that M/R is Correct The M/R dates have all been reset to 1. They must be set to the same values as they were when registered on the previous RC Gates At the RC Gate. 1. Make lists of settings in the RC Gates at the customer site. (Make screen dumps of the settings from the RC Gate UI.
  • 288. 288 Switching from many RC Gate (BN)s to one RC Gate A To From RC Gate BN RC Gate S Pro RC Gate A 1x RC Gate BN Standard Not Possible Possible Multiple RC Gates Not possible Will become available as “Special Operation” RC Gate S Pro Not possible Standard Not Possible RC Gate A x 1 Not possible Not Possible Standard
  • 289. 289 Important when doing the transition procedure  Pre-conditions  Access to the Center Server from customer site.  The technician needs access to the Administrator menu of the Center GUI to complete all tasks.
  • 290. 290 Appliance Replacement  You only have to replace your external RC gate when is defect.  The Appliance Replacement procedure is described in detail in the Center GUI Manual and the external RC gate Service Manual. Note  You cannot replace a Basil, if it is installed using one-way communication (SMTP).  You cannot replace an external RC gate, when permit sending IP address is prohibited  You cannot replace a Cumin Appliance type. !
  • 291. 291 @Remote related SP Modes  5501-xxx PM Alarm  5504-xxx Jam Alarm  5505-xxx Error Alarm  5507-xxx Supply Alarm  5508-xxx CC Call Alarm  5515-xxx Report Setting  5816-xxx Remote Service  5821-xxx Remote Service Address  5870-xxx Common Key Info Writing  5985-xxx Feature Support  5816-200 Manual Polling  5816-003 Function Flag  0: Not registered  1: Registered  5816-201 Regist Status  Display of installation condition  0: Not installed  1: Installed as Cumin (pre-registered)  2. Installed as Cumin  3: Installed to external RC gate  4: NRS Module is not available  5816-209 @Remote Setting Clear  5816-250 CommLog This list gives you an overview of some important SP Modes. For a more complete list see notes page. !
  • 293. 293 Device Firmware Levels  During site survey  Check which type of device are in use at the customers site. This is to help you calculate the time needed for installation. Older devices and many different models at the same customer can increase the needed level of troubleshooting  While troubleshooting  If a device is not working correctly check for RTB’s on firmware levels (see example) Adobe Acrobat Document
  • 294. 294 Browser issues  Center Server GUI not accessible  Browser compatibility  Although it looks like Center Server operation works fine with other browsers than MS-IE 6 or 7 some functions might not work  Browser (security) settings  If the center server URL is not listed in the trusted sites list in your IE security settings you might get an error message.  Browser error(s)  The first time you connect to the Center Server it takes some for the browser to download settings. Wait for the “Done” message in the bottom-left corner of your browser.  Old OCX’s  The procedure is on the splash page just after logging in to the Center Server
  • 295. 295 Service Calls  Service Test Call  To perform end-to-end test a “Service Test Call” can be initiated from the device or external RC gate.  Manual Call  To provide information to service, a “Manual Call” can be initiated from the device.  Device Check Request call (Only for UZ-A1).  Sends the status of the UZ-A1 to the Center Server.  Service Call  This shows the service call information. Only shown when the RC Gate A has a problem.
  • 296. 296 Service Calls  Service Calls Name of call Operation Appliance Basil Service Test Call 1.Select “RC Gate and Device Settings” menu 2.Select [Service Test Call] under Maintenance > Communication Server Calls UZ-A1 Service Test Call 1. Log in as “Administrator” into RC Gate Configuration 2. Select: Maintenance>Service Test Call 3. Click Start Device Check Request call 1. Log in as “Administrator” into RC Gate Configuration 2. Select: Maintenance> Device Check Req. Call 3. Click Start Service Call 1. Log in as ”General User” into RC Gate or as “Administrator” into RC Gate Configuration 2. Select: Maintenance> Service Call Device MFP Service Test Call System Settings > Administrator Tools > Service Test Call LP (4 lines LCD) Service Test Call Menu > Remote Services > Service Test Call, then “Start” LP (2 lines LCD) Service Test Call “Escape” for 5 seconds > Remote Services, select “Test Call”, then “Enter”
  • 297. 297 Service Test Call Example (MFP)
  • 298. 298 Common Key (Authkey)  5870-xxx Common Key Info  This SP Mode is used to re-write the “machine certification” (not ID2). The correct sequence to (re-)write the “Common Key” is:  Remove the device in Center GUI Server (also if monitored)  Wait for external RC Gate or Device to communicate this change (normally every 1 hour)  Execute sp 5870-003 (if available) and 5870-001  After executing SP5870-001 successfully immediately POWER OFF and ON the device !  Re-register the device using normal device registration procedure
  • 299. 299 ID2 check  In order for a device to be registered as an NRS device ID2 Code for that device needs to be correct.  To check if ID2 Code is correct print out the SMC data list and check SP 5811 (machine serial) Compare with SP 5811 “ID2 Code Display”. The value of ID2 should be the same as the serial number but with 6 spaces between the prefix and the actual serial number example: incorrect ID2 example: correct ID2
  • 300. 300 ID2 re-write overview  ID2 re-write  Make sure that the device is not registered and also not monitored.  If the device is registered or monitored first remove the device with the Center Server GUI  Manually create certification/ID2 call  Register the call  Open the call  Execute the call  Wait for result ! This is only for devices connected trough an external RC Gate
  • 301. 301 ID2 re-write - Register ID2 Call  The “Device Model Code” is the serial number prefix (3 characters)  The “Device Serial Code” is the serial number without the prefix (8 characters)  The “IP Address” is the device IP address
  • 302. 302 ID2 re-write - Open the ID2 Call  Go to the “Call List” menu on the left hand side  Search and open the ID2 Call (double click)
  • 303. 303 ID2 re-write - Execute the ID2 Call  Type the correct values for ID2 (prefix and serial)  Click on the “Execute” button
  • 304. 304 ID2 re-write - Check result  Wait for the result (Refresh)
  • 305. 305 Prohibit @Remote Service  This setting prohibits @Remote communication.  Available on GW2005A or later devices.  The default setting is ‘Do not Prohibit’ (enable). User Tools -> System Settings -> Administrator Tools -> Extended Security
  • 306. 306 Device registration error codes displayed on device (Cumin)  The cumin/device service manuals have a chapter with error codes. In addition to the codes described in the manual, the following error codes can occur (displayed in Web Image Monitor):  12005; @Remote communication is prohibited. The device has a problem with a Cumin function.  12006; After confirmation was completed, the confirmation request was made again.  12007; Different request number was used for registration than the one for confirmation.  12008; The device function was in use, updating certification has failed.
  • 307. 307 Device registration error codes displayed on Center Server GUI  @REMOTE RESULT_NG  HTTPS device  The device is a SNMP Device  The device is disconnected  The device is powered off  Wrong IP address used  DESS not installed  SNMP device  The device is disconnected  The device is powered off  Wrong IP address used  @REMOTE RESULT_BUSY  The Basil is still busy with the previous request.  @REMOTE RESULT_EXIST_DEVICE_IP  Retry the registration request again with the latest auto discovery (AD) data.
  • 308. 308 Basil Communication Log  Log into the RC Gate using the Registrant Mode  Navigate to the “RC Gate and Device Settings” menu  Go to the “Maintenance” menu on the Left side of the page  Go to the “Communication Log”.  Select all data in the log window and copy it to a text file.  Send this text file together with appliance serial number, device serial number, full customer name and Site name to your technical support specialist.
  • 309. 309 Center Server responsibilities  General  You can not request User ID’s for the Center Server for yourself unless trained.  New Site or Service Depot  Who’s responsible : Ricoh Europe  How to request : Via your default support route  Required : Site name, Service Depot name and user-id of requestor  User ID for Center Server  Who’s responsible : Ricoh Europe  How to request : Via your default support route  Required : Internet e-mail address, name, country, organisation, @remote administrator’s e-mail address.
  • 310. 310 @Remote Q&A  A lot of answers to @Remote related questions can be found in the Tier-2 Knowledgebase through TESSA.
  • 311. Ricoh Academy Europe @Remote-Field service_full-ct_SOL_ppt_EN_9.1.a 311 @Remote - New Remote Service Field service training END After this slide there is additional information
  • 313. 313 Appendices - Overview  Customer pre-survey UZ-A1  Differences between the External RC Gates  UZ-A1 - DIP Switches  Basil – Dipswitch  Basil - Reset Switch  Basil - SD Card Slot  Migrating from RC Gate BN to RC Gate A
  • 314. 314 Customer pre-survey UZ-A1 1/2  No optional memory  How many units do I need?
  • 315. 315 Customer pre-survey UZ-A1 2/2  With optional memory  How many units do I need?
  • 316. 316 Differences between the External RC Gates  Periodical reboot  RC Gate A: Unnecessary  RC Gate BN: Adjustable; Weekly or Monthly  RC Gate S Pro: Unnecessary  When an Appliance SC occurs  RC Gate A: Will reboot.  RC Gate BN: Will reboot.  RC Gate S Pro: RC Gate S Pro itself does not reboot, but the internal @Remote service will reboot.  SNMP Version  RC Gate A: SNMP v1/v2/v3  RC Gate BN: SNMP v1/v2 only  RC Gate S Pro: SNMP v1/v2/v3  Communication Protocol  RC Gate A: SNMP/SOAP/REST  RC Gate BN: SNMP/SOAP  RC Gate S Pro: SNMP/SOAP/REST*  REST is available from S1 mk2.  Communication Method (between appliance and center)  RC Gate A: HTTPS only  RC Gate BN: SMTP (1-way) or HTTPS (2-way)  RC Gate S Pro: HTTPS only  Appliance ID2  RC Gate A: V7800000001  RC Gate BN: J77 / (J76)Ymm00001  RC Gate S Pro: S5600000001  System Log  RC Gate A: 2MB  RC Gate BN: 4KB  RC Gate S Pro: 500MB  Communication Log  RC Gate A: 2MB  RC Gate BN: 64kB  RC Gate S Pro: 10MB  Security Log  RC Gate A: 2MB
  • 317. 317 UZ –A1 - DIP Switches  The DIP switches are used for two functions.  Function 1: To delete the registered IP address in the RC Gate A.  Function 2: To clear the settings of the RC Gate A.  Switch number 6 is the switch for the lithium battery.  If you turn off this switch, the data in the SD card is erased. (It erases the flash memory. This memory is copied to the SD-card thus erasing the SD card.) O N 1 2 3 4 5 6 7 8 SW1
  • 318. 318 Basil - Dipswitch SW1 Operation mode 1 2 3 4 normal off off off on reset IP address on off off on clear all memory off on off on firmware update off off on on DIP Switch SW1 Attention! Do not use the ‘firmware update’ DIP switch setting.
  • 319. 319 Basil - Reset Switch SW1  With the reset switch you can restart the RC Gate. To access the switch, insert a pin into the opening on the upper cover of the RC Gate and push the switch.
  • 320. 320 Basil - SD Card Slot  In the past, the SD Card slot was used for local firmware updating.  This procedure is now only used in case of customised firmware.  Regular FW update must be done through the Center Server GUI.
  • 323. 323 1. Making Lists of Settings at the RC Gate BN UI  Make lists of settings in the RC Gate BNs at the customer site.  The RC Gate A must have the same settings.  The Registered Device List must be taken from all the RC Gate BNs.  Access the RC Gate BN UI in CE mode.  Make screen dumps of the settings in the menus above of the RC Gate BN UI.
  • 324. 324 2. Making lists of settings at the Center GUI  At the Center GUI, log in as an Administrator.  Make screen dumps of the Appliance Information for Admin, for a RC Gate BN that has the full range of settings made.
  • 325. 325 3. Exporting Lists - Device List CSV 1/3  Export Device List: Detail  This exported device list can be used for the following:  To designate devices to be registered under RC Gate A.  To retrieve the M/R Date of each device (after devices are registered at the center, the M/R Date is set to 1 by default, so you need to edit the M/R Date by using the Export Device List: Detail.)  Export Device List: Simple  After registering devices under RC Gate A, this exported device list can be used to retrieve information for each device by using “Update Device Info. by CSV Import”.  Then, the information can be imported later after registering the RC Gate A.
  • 326. 326 3. Exporting Lists - Device List CSV 2/3  Export Device List: Detail and Simple  Center GUI, Maintenance Menu, Export Device List: The lists for all RC Gate BNs can be exported in one operation.  You cannot do this if you do not have access to the Maintenance Menu.
  • 327. 327 (7) (8) 3. Exporting Lists - Device List CSV 3/3 (1) (2) (3) (4) (5) (6) This is an example of Device List: Detail (9)
  • 328. 328 3. Exporting Lists - Reporting CSV 1/2  At the center, counter data from all appliances is saved for up to a maximum of 40 days.  Perform the download as two separate operations to obtain all the data.  You can download max 30 days at once.
  • 329. 329 3. Exporting Lists - Reporting CSV 2/2  To get the data for all 40 days, do the operation twice. (e.g. First 30 days, followed by last 10 day.)
  • 330. 330 3. Exporting Lists - Supply CSV 1/2  For customers to which the toner replenishment services are provided, download Call History from the devices.  At the center, supply data for all appliances is saved for up to a maximum of 30 days.  You can download max 7 days at a time.
  • 331. 331 3. Exporting Lists - Supply CSV 2/2  To get the data for all 30 days, you must do the operation 5 times.
  • 332. 332 3. Exporting Lists - Call History 1/2  For customers to which the call handling and/or toner replenishment services are provided, download Call History from the devices.  You must capture the call history for each individual device. (One at a time.)
  • 333. 333 3. Exporting Lists - Call History 2/2  You have to download Call History CSV for each device one by one.  It will take about 20 minutes to download call history from 100 devices. Example of Call History
  • 334. 334 4. Install the RC Gate A  Input the settings from the old RC Gate BN (see step 1).  Setup the Auto Discovery Settings.  Register the RC Gate A with the @Remote Center.
  • 335. 335 5. Input the Appliance Information for Admin  At the Center GUI, log in as an Administrator.  Input the data from the screen dumps of the Appliance Information for Admin that you made earlier.
  • 336. 336 6. Un-manage all Managed Devices 1/3  This procedure is the opposite of the ‘Registering at the Center GUI’ procedure.
  • 337. 337 (1) (3) (2) 6. Un-manage all Managed Devices 2/3
  • 338. 338 6. Un-manage all Managed Devices 3/3 (1) (2) (3)
  • 339. 339 (1) (2) (3) 7. Make a Call from each RC Gate BN (4)
  • 340. 340 8. After Receiving the Calls  After the Device Check Request call, check the Device List again, to make sure that all devices were removed.  Sometimes one or more devices are not removed and the device data remains at the Gateway.  In this case, it is not possible to remove the device from the site, and only the solution is to contact Ricoh Europe support to remove the data.
  • 341. 341 9. Remove the RC Gate BNs from the Center Server  The operation is similar to removing the devices, except this time we use Appliance in the Search menu. (1) (2) (3)
  • 342. 342 9. Remove the RC Gate BNs from the Center Server (1) (2) (3)
  • 343. 343 10. Register the Devices on the RC Gate A  Register the devices on the RC Gate A, using the Device Registration Wizard.
  • 344. 344 11. Check the Device List for the RC Gate A  During the Device Registration Wizard, the RC Gate A contacts the @Remote Center with the new device data.  The device list at the Center GUI for the new RC Gate A should contain all the registered devices.  Check this list.  Compare it with the exported device list CSV files that you made earlier.  Make sure that all devices are registered and Managed  If any failed, investigate, and try to recover.  If some devices still cannot be registered and Managed, wait one day and try from the @Remote Center with Remote Registration.
  • 345. 345 12. If Needed, make a Call from the RC Gate A  In the Maintenance menu of the RC Gate A UI:  Click Maintenance  Device Check Req. Call.  Then click Start.
  • 346. 346 13. Remote Registration  Wait until 24 hours have passed since the Auto Discovery Settings were made in the RC Gate A at the customer site.  Check the Device List for the RC Gate A.  If some devices are still not registered and Managed, make sure that all the devices are listed as ‘Monitored’ or ‘Found’.  If any devices are not listed, check their condition, and recover them.  Register the devices.
  • 347. 347 14. Register the Devices  After you finished this step make a Device Check Request call or wait for at least an hour (until automatic hourly polling is done).  Then check the list of registered devices.  Compare it with the exported device list CSV files (from step 1).  Make sure that all devices are registered and Managed  If any failed, investigate and try to recover.
  • 348. 348 15. Retrieve the Old Device Information  Import the device information from the old RC Gate BNs.  Import it from the Exported Device List CSV’s that you made in step 3.  You need the Export Device List: Simple
  • 349. 349 (1) (2) (3) (4) 15. Retrieve the Old Device Information: Export device list Exported Device List: Simple
  • 350. 350 15. Retrieve the Old Device Information: Import device list (1) (2) (3) (4) Retrieve data
  • 351. 351 15. Retrieve the Old Device Information Exported Device List: Simple All editable fields in device Information can be exported and imported.
  • 352. 352 15. Retrieve the Old Device Information (1) (2) (4) (5) (3)
  • 353. 353 16. Make Sure that M/R is Correct  The M/R dates are all reset to 1. They must be set to the same values as they were when registered on the previous RC Gate(s). Data when registered on the RC Gate BN Data after registering on the RC Gate A M/R Dates are all reset set to 1. Specific M/R dates are set.
  • 354. 354 16. Make Sure that M/R is Correct  Exported Device List: Detail (1) (2) (4) (5) You can edit M/R Dates for a max. 500 devices in one operation.

Editor's Notes

  • #1: List of Changes: (See: View > Notes Page)
  • #2: No additional notes.
  • #3: GW controller At least one of the machines needs a GW 2005 Spring controller or later model, which supports the Cumin function (embedded Remote Communication gate). This is to do the exercises regarding the Cumin function. Options for UZ-A 256 MB DIMM Memory 16 GB SSD Memory Versions This training is based on the following versions Basil firmware version: 3.57 - 1.15 UZ-A1 firmware: CV1.09, AV1.10, KV1.03, PV1.09 Center Server GUI version: 2.2.17 Reporting website version: 4.2.1.0
  • #4: IMPORTANT: To do this training, you need basic knowledge about TCP/IP networking, SNMP and the SP-modes. These topics are covered by the following related modules: Network Management (Basic). GW 2007 or later (Basic).
  • #5: No additional notes.
  • #6: No additional notes.
  • #7: No additional notes.
  • #8: No additional notes.
  • #9: @Remote-NRS naming ‘@Remote’ is the name of the service which is provided to the customer. ‘NRS’ (New Remote System) is the name used by Ricoh internally to describe the system that is used to provide the @Remote service to the customer. In this presentation ‘@Remote’ and ‘NRS’ mean the same. How does @Remote work? A short description: Customer device data is sent by a Remote Communication Gate (external box or embedded in the device) through the Internet to the Center Server (a data centre located in Japan). Service organisations can monitor, manage and service printing devices from their customers through the Center Server. Device counter information is send from the Center Server to the Reporting Server. Customers can get detailed reports of their devices through the website of the Reporting server.
  • #10: Remote monitoring of counter and device information With @Remote, Ricoh Family Group devices and competitors devices can be monitored/managed. With @Remote, new devices on the customer’s network can be detected automatically (Auto Discovery function). E-mail notification @Remote can be configured to send e-mail notifications based on incoming Service Calls and Supply Calls.
  • #11: No additional notes.
  • #12: No additional notes.
  • #13: Remote Communication Gate (RC-Gate) The RC-Gate is located in the customer network. The RC-Gate sends device data (device counters / device information / service calls / supply calls) through the Internet to the Center Server. The RC-Gate can be an external box (Basil/UZ-A1) or embedded in the device (Cumin). The names ‘Basil’, ‘UZ-A1’ and ‘Cumin’ are design names. Center Server The Center Server is a data centre located at Ricoh Japan. The Center Server collects the device data send by the RC-Gate. Center Server GUI The Center Server GUI is a website on the Center Server. Service organisations can monitor/manage device data and service devices from their customer through the Center Server GUI. Service organisations can only monitor/manage device data and service devices to which they have access (only their own customers).
  • #14: Reporting Server Every day the device counter data on the Center Server is send to the Reporting Server. The Reporting Server is located in the USA. Customer reporting website Customers can get detailed reports of their devices through the reporting website on the Reporting server. Customers can only see reports from devices to which they have access (only their own devices). Service organisations manage the reporting website for their customers. Customers can do administrative tasks themselves, such as creating user accounts for their employees.
  • #15: External RC-Gate RC-Gate = Remote Communication Gate The RC-Gate sends device data (such as device counters, service calls, supply calls) to the Center Server. External RC-Gate (Basil/UZ-A1) is an external hardware box installed in the customer network. collects device data (device counters / device information / service calls / supply calls) from multiple printing devices through SNMP and/or HTTPS. can collect device data from Ricoh Family Group devices (HTTPS / SNMP standard MIB / SNMP private MIB data) and competitor devices (SNMP standard MIB data). sends collected device data to the Center Server through HTTPS or SMTP (SMTP-E-mail only Basil). Cumin (embedded RC-Gate) The Cumin is embedded in the controller software of the device. The Cumin is NOT a hardware option. The Cumin can only collects device data from one device (the device itself). The Cumin sends device data to the Center Server through HTTPS.
  • #16: No additional notes.
  • #17: UZ S1 – Server based fleet-management @Remote Enterprise WSDM + Enhanced features + @Remote A combination of On-site fleet management AND Remote fleet management UZ A1 – Appliance based fleet management @Remote Office The successor of the Basil box Remote fleet management UZ D1 – Desktop based fleet-management Smart Device Monitor for Admin + AR On-site fleet management
  • #18: For more detailed info see the Appendix RC Gate BN is also know as Basil RC Gate A1 is also known as UZ-A1 *1 : This is a new protocol, supported from COSMOS products. *2 : The Storage Option (16GB SSD) and Memory Option (512MB DIMM) are required. *3 : This is a new feature added from the Uz-A1. The Memory Option (DIMM) is required. The first release of the Uz-A1 firmware will not support this function. Support will begin from the Uz-A1 firmware update scheduled for release at the end of March 2010. *4 : PSTN on RC Gate BN is only used for Japan domestic market. *5 : You can set up an SMTP connection via e-mail to communicate with the center server (for RC Gate BN).
  • #19: REST = Representational State Transfer Cosmos is the new platform for Ricoh devices, the successor of GW-architecture RFU = Remote Firmware Update
  • #20: RC-Gate - Center Server polling By default the RC-Gate polls the Center Server once every hour. You can manually force the RC-Gate to poll the Center Server. This is explained in the chapter ‘Troubleshooting and support’.
  • #21: *: SSL is not supported when using SMTP as connection method to the Center Server When using SMTP as communication method, the RC-Gate sends device information to the Center Server as an encrypted (S/MIME) E-mail attachment. Center Server datacenter security Building entrance 24/7 security and video surveillance Security guards Environment Environmental monitoring systems maintain constant temperature and humidity. Fire protection Early warning system. N-2 gas-based fire suppression system. Remote access Only limited network can access remotely via SSH. Periodic password changes are required. Power Continuous, uninterruptible power supply. Multiple standby generators. Monitoring Operation is monitored 24/7.
  • #22: No additional notes.
  • #23: No additional notes.
  • #24: No additional notes.
  • #25: No additional notes.
  • #26: Internet browser support Although the Center Server GUI may work fine with other Internet browsers, only MS Internet Explorer 6 and 7 are supported.
  • #27: URL The URL to access the Center Server GUI is CaSe sensitive Installation of ActiveX modules ActiveX modules are installed/updated in the following situations: The first time you log into the Center Server GUI. It takes some time for the browser to download the ActiveX modules. Wait for the “Done” message in the bottom-left corner of your browser. When there are changes to the Center Server GUI. After login, your browser downloads/updates ActiveX modules.
  • #28: Deleting old ActiveX modules (OCX files) On the start screen of the Center Server GUI you can download a .bat file which deletes Center Server GUI OCX-files from your PC. When problems occur related to the OCX-files occur, execute this .bat file to ‘refresh’ the Center Server GUI OCX-files on your PC. The ‘old’ OCX-files are deleted and ‘new’ OCS-files are downloaded again after login. Also use this procedure when the Center Server GUI has been updated. Updates are announced on the home page of the Center Server GUI.
  • #29: Recommendation: Because the link on the Center Server GUI homepage is only displayed after you log-in, it is recommended to add the ‘Single User ID website’ to your web browser favorites, so you can access the website when you forgot your password.
  • #30: Appliances Appliances are RC-Gates (Basil, UZ-A1 or Cumin). An Appliance manages/monitors a number of devices (the device list). The device list of a External RC Gate can contain multiple devices. The device list of a Cumin contains one device (the device itself). An Appliance is part of a Service Depot. Service Depots A Service Depot represents a service location. You can use a Service Depots to group your Appliances. For example: a Service Depot can represent a customer location, or a location of the service organisation, such as a department or a regional office. Center GUI user access can be restricted based on Service Depots. A Service Depot is part of a Site. Sites A Site is a section in the Center GUI to which a service organisation has access. A service organisation can have access to one or more Sites. A service organistation only has access to device data, Service Depots and user accounts within its own Sites. Center GUI user access can be restricted based on Sites. Management of Sites, Service Depots Each service organisation manages its own Sites and Service Depots. Sometimes when a large customer consists of many different customer locations, the service organisation can decide to create a separate Site for this customer. The Service Depots then represent the different locations of that customer.
  • #31: Center Server GUI menu overview Registration Registering new Appliances / replacing Appliances. Search Searching (disconnected) Appliances / devices. Counter CSV Downloading CSV files containing collected device counters. Supply CSV Downloading CSV files containing collected supply calls. Service Call Monitoring incoming service calls. Firmware Updating device / Appliance firmware. Maintenance System maintenance, such as Site / Service Depot access management and configuring Email notifications. Administrator Advanced Appliance settings.
  • #32: Searching Appliances/Devices basics In the Center Server GUI you can search for Appliances and Devices in the ‘Search’ menu. Select ‘Appliance’ in the ‘Search’ menu to search for Appliances throughout all your Service Depots or within a specific Service Depot. Select ‘Device’ in the ‘Search’ menu to search for devices within a specific Service Depot. Search Appliance example To search an appliance in the Center Server GUI, select ‘Appliance’ in the ‘Search’ menu. Select a Service Depot. Only the Service Depots to which you have access are displayed. Click on ‘Search’.
  • #33: Appliance S/N An appliance S/N starting with J77 is a Basil An appliance starting with V78 is a UZ-A1 An appliance S/N starting with S56 is a UZ-S1 server (Remote Communication Gate S with @Remote connector). The appliance S/N for a Cumin is the same as the device S/N. Appliance types Embedded Cumin External: RC-Gate BN : Basil RC Gate A1 : UZ-A1 RC-Gate S : UZ-S1 server (Remote Communication Gate S with @Remote connector).
  • #34: No additional notes.
  • #35: Load Site Information The ‘Load Site Information’ button updates the available Sites/Service Depots according to your access rights. Normally you have to use this button only in the following situations: After you log-in for the first time: Site / Service Depot drop-down menus are empty. When access rights for your account are changed, for example if your account has been added to a new Site or Service Depot. After you login with another login account: Site / Service Depot drop-down menus show Sites / Service Depots available for the previous login account. When you select one of these Sites / Service Depots, an error message ‘No relevant data exists’ appears.
  • #36: No additional notes.
  • #37: No additional notes.
  • #38: Device types MIB (SNMP) device (competitor / Ricoh OEM / Ricoh pre-GW) Can only be connected through an external RC Gate (does not support not Cumin). The external RC Gate communicates with the device through SNMP and can only read Standard MIB information. This can be competitor devices or pre-GW Ricoh devices. For this type of device, sometimes the MAC address is displayed instead of the serial number. This depends on the controller of the device. GW MIB (SNMP) device Can only be connected through an external RC Gate (does not support Cumin). The external RC Gate communicates with the device through SNMP and can read both Standard and Public MIB information. This can only be Ricoh devices (not competitor devices). NRS (HTTPS) device Can be connected through an external RC Gate or a Cumin. The external RC Gate or Cumin connects to the device using HTTPS (SOAP) communication. Detailed device information can be acquired (more detailed then through SNMP). This can only be Ricoh devices (not competitor devices). Simple Object Access Protocol (SOAP) Messages from HTTPS devices are communicated using the SOAP protocol. SOAP is a standard for exchanging XML-based messages over a computer network, normally using HTTP. SOAP forms the foundation layer of the web services stack, providing a basic messaging framework that more abstract layers can build on.
  • #39: No additional notes.
  • #40: No additional notes.
  • #41: No additional notes.
  • #42: @Remote devices (HTTPS) DESS The “Security Module” (DESS) must be installed. This module is pre-installed from November 2004 onwards. On models with a production date before nov.2004 the DESS module has to be installed. To check if DESS is installed: Print the diagnostics page (SP 5990-005) sometimes DESS is integrated in the NCS firmware (see example) Use Web Image Monitor > ROM Update (see example) ID2 Code A device is registered to @Remote through the ID2 code. The ID2 Code of a device must be correct to be used as an @Remote (HTTPS) device. In some cases the ID2 certification is not correct or is lost (for example after NV-RAM clear). To check if ID2 Code is correct print out the SMC data list and check SP 5811 (machine serial) Compare with SP 5811 “ID2 Code Display”. The value of ID2 should be the same as the serial number but with 6 spaces between the prefix and the actual serial number. You can re-write the machine ID2 code. (See the ‘Troubleshooting & support’ chapter). Machine Certification In some cases machine certification is not correct or is lost (for example after NV-RAM clear). You can not check if it is correct but you can re-write the Machine Certification by using SP 5870. (See the ‘Troubleshooting & support’ chapter).
  • #43: No additional notes.
  • #44: No additional notes.
  • #45: No additional notes.
  • #46: Device models & firmware Levels Check which type of devices are used at the customers site. This is to help you calculate the time needed for installation. Older devices and many different models can increase the needed level of troubleshooting. For more detailed information refer to the Appendix
  • #47: Pre-registration During the pre-registration you enter the Site, Service Depot, and Customer Name to which the RC Gate will be registered. At he end of the pre-registration the Center Server will issue a Request Number. This Request Number has to be used when installing the RC Gate at the customer site.
  • #48: Device Registration Wizard To register devices during installation at customer location. You can specify IP-ranges or import a CSV file to find devices on the network. You can then select which found devices you want to register. On UZ-A1 you can also select ip addresses that must be skipped during auto discovery. (This is discussed in detail later in the training.) Devices are registered as ‘managed’ devices (see next slide). Auto Discovery You can specify IP-ranges and schedule when the Basil must scan these IP-ranges (daily / weekly / monthly). The Basil scans the network using SNMP to find devices. Found devices are registered as ‘monitored’ devices (see next slide).
  • #49: Managed devices On the slide the purple line indicates the relation between the external RC-Gate and the device (the device is ‘managed’ by the external RC-Gate).
  • #50: No additional notes.
  • #51: Monitored Devices found by Auto Discovery option. Device reporting: simple (only standard MIB information is acquired.) Managed (‘Managed/Register’) Managed SNMP devices Device reporting: simple (only standard MIB information is acquired.) Supports MIB service/supply call detection (SNMP polling interval: 10 min.) Managed HTTPS devices Device reporting: detailed (HTTPS communication) Supports real-time SC call / Supply call detection Supports remote settings / firmware update MIB Counter The counter value obtained from a MIB device does not always correspond with the counter value displayed on the Operation Panel of that device. Especially in case of color MFP's, the output made using an SDK cannot distinguish color and B/W in the MIB. Therefore all output using an SDK is counted as B/W in the Counter-CSV you export with the Center Server GUI. In addition, the output made from the Local Storage of a J-C1 and J-C1 have the same issue. As a result, colour counter is low and the black counter is high compared with the counter from the Operation Panel. Therefore it is better to register these devices as ‘managed’ instead of monitored.
  • #52: UZ-A1 When you install the SSD, you must also install the DIMM. The maximum number of managed devices goes from 100 to 1000. With this DIMM installed, the RC Gate A can also store/export user counters.
  • #53: No additional notes.
  • #54: No additional notes.
  • #55: No additional notes.
  • #56: Rear connectors LAN1 Basil configuration (local) LAN2 Basil configuration (through customer network) Modem Not used in European region. LED’s Power LED (Green) ON when the equipment is operating. System error LED (Red) ON when the equipment is NOT operating correctly. Communication Error LED (Orange) ON when communication with the Center Server is NOT operating correctly. This is also the case when the Basil is operating, but is not yet registered to the Center Server. Remains ON when the Basil is installed using SMTP communication. In this case this LED does not indicate any error. During booting, al LED’s are flashing in a specified sequence.
  • #57: No additional notes.
  • #58: CE Mode Before you can login using CE Mode the RC Gate Admin must give permission (security menu) Basil logout If you close your browser while you are logged into the Basil, the session is NOT terminated The session will time-out after 30 minutes. Therefore, always use the ‘Logout’ button to close the session. Access to the Basil’s User Interface (UI) Use Internet Explorer 5.0 or newer to connect.
  • #59: No additional notes.
  • #60: Pre-registering a new Appliance (Basil/Cumin) You must do the pre-registration procedure before you install a new Appliance (Basil/Cumin). The pre-registration procedure results in a ‘registration number’. The ‘registration number’ has to be entered when you register the Basil/Cumin to the Center Server during the installation at the customer site. Mandatory fields You must enter ‘Customer Name’, ‘Site Name’ and ‘Service Depot Name’. The Basil/Cumin will be registered under this ‘Customer Name’, ‘Site Name’ and ‘Service Depot’ when you register the Basil/Cumin to the Center Server during the installation at the customer site. The ‘Operation Calendar’ selection can be left on ‘DEF’ (default calendar). The ‘Operation Calendar’ function will be explained later. Batch registration You can use this function when you are going to install multiple Basils/Cumins at the same Customer / Site / Service Depot. Fill in a number to generate multiple registration numbers. Leave this field blank if you only need 1 registration number. Optional fields Here you can enter useful information for administrative or reporting purposes.
  • #61: Registration number The registration number can be copied to the clipboard. The registration number is unique and can be used only once. After you installed the Basil/Cumin using the registration number, this registration number cannot be used again. Registration number / Request number In some screens the registration number is referred to as ‘Request number’. ‘Request number’ means the same as ‘Registration number’.
  • #62: Checking a pre-registered Appliance The registration number will be available in the ‘Pre-Installed Appliance’ menu for a maximum of 3 months. If the registration number is not used within 3 months, it will be automatically deleted. When you use the registration number to install a Basil/Cumin, it will be deleted and cannot be used again.
  • #63: No additional notes.
  • #64: No additional notes.
  • #65: Network-cable to connect your PC to the Basil The network-cable must be a cross-over-cable, unless the PC network-card has ‘auto-cross-over’ functionality. Nowadays most PC network-cards have ‘auto-cross-over’ functionality.
  • #66: No additional notes.
  • #67: No additional notes.
  • #68: Attention! It is important to select the correct time zone. The time zone setting effects many timing settings, such as the timing for notification emails, sending of counter information etc.
  • #69: No additional notes.
  • #70: LAN1 port (maintenance port) setting You can select one of the following IP addresses for this port: 192.168.10.1 (default) 192.168.1.1 192.168.250.1 DNS Server Enter a DNS server when you want to register devices through hostname (explained later).
  • #71: No additional notes.
  • #72: No additional notes.
  • #73: No additional notes.
  • #74: No additional notes.
  • #75: No additional notes.
  • #76: No additional notes.
  • #77: No additional notes.
  • #78: No additional notes.
  • #79: No additional notes.
  • #80: No additional notes.
  • #81: Optional Email notifications When the Basil is registered to the Center Server using HTTPS and you specify the Email settings, the following E-mails notifications will be sent to the Basil administrator: Suspended Device: When the communication between the Basil and registered devices has been suspended. Connection to the Communication Server Suspended Reconnected to the Communication Server Update Device Firmware: when the firmware of the registered devices is updated.
  • #82: No additional notes.
  • #83: No additional notes.
  • #84: No additional notes.
  • #85: No additional notes.
  • #86: No additional notes.
  • #87: No additional notes.
  • #88: No additional notes.
  • #89: No additional notes.
  • #90: No additional notes.
  • #91: No additional notes. Blue is the old situation, but installations done before last GUI release will show up with this status. Status can still be managed/found if the ID2-code and/or security certificate is not correct. Orange is current situation, when device registration has been performed the status will be managed/registered.
  • #92: No additional notes.
  • #93: No additional notes.
  • #94: No additional notes.
  • #95: No additional notes.
  • #96: No additional notes.
  • #97: Registration Result If the result is ‘Failed’ click on the regarding ‘Machine ID’ to see more details.
  • #98: No additional notes.
  • #99: No additional notes.
  • #100: No additional notes.
  • #101: No additional notes.
  • #102: No additional notes.
  • #103: Configuration Advise In older firmware version of the basil it is possible to configure the Auto Discovery to run every hour. This will generate an enormous amount of network traffic. The advise is to configure Auto Discovery to run every week during normal operation hours because then most of the (new) devices will be switched on.
  • #104: No additional notes.
  • #105: No additional notes.
  • #106: No additional notes.
  • #107: Manage as ‘HTTPS’ You can always select ‘HTTPS’ when you select ‘Manage Devices’, even if the target device is an ‘SNMP’ device. If you try to manage an ‘SNMP’ device as ‘HTTPS’ device, the registration will fail and will result in an error message. M/R Date The M/R date is the day of the month which is used for billing purposes. This is the counter which is used on the M/R Counter-CSV report (explained later).
  • #108: No additional notes.
  • #109: No additional notes.
  • #110: No additional notes.
  • #111: No additional notes.
  • #112: No additional notes.
  • #113: RC Gate E-mail address (for sender) (MANDATORY) Basil E-mail address (default = rc_gate) RC Gate E-mail address (for receiver) (OPTIONAL) ‘Reply address’ for E-mails to RC Gate administrator address. RC Gate admin’s E-mail address (OPTIONAL) Receives results of Auto Discovery function. Receives E-mail send by ‘Send Test E-mail’ function. SMTP server address Enter the IP-address of the customers SMTP server. This is the SMTP server that will sent Email messages from the basil to the Center Server.
  • #114: No additional notes.
  • #115: No additional notes.
  • #116: Registering with SMTP is NOT possible with a UZ-A1.
  • #117: No additional notes.
  • #118: No additional notes.
  • #119: No additional notes.
  • #120: Rear connectors PC UZ-A1 configuration (local) LAN UZ-A1 configuration (through customer network) LED’s Power LED (Green) ON when the equipment is operating. System error LED (Red) ON when the equipment is NOT operating correctly. Problem description on LCD display LCD display shows: IP address System Status Messages (Normal Operation, Comm. error etc.)
  • #121: No additional notes.
  • #122: If you remove the RC Gate A from the customer site, you must first un manage all the devices and remove the Appliance from the Center Server. For the previous model ‘RC Gate BN’, there is no Shutdown button to press on the machine. There is only a selection to make from the user interface.
  • #123: Login names are CaSe sensitive. UZ-A1 logout If you close your browser while you are logged into the Basil, the session is NOT terminated The session will time-out after 30 minutes. Therefore, always use the ‘Logout’ button to close the session. Access to the UZ-A1 User Interface (UI) Recommended web browser: Internet Explorer 6.0 or newer to connect. Adobe flash player 9.0 or later must be installed.
  • #124: No additional notes.
  • #125: When @Remote is off: The appliance does not poll the @Remote Center The appliance does not check device connections The appliance ignores requests received from the @Remote Center The appliance ignores calls from devices The appliance keeps communication/system logs but doesn’t make/send responses.
  • #126: Calls from a device: Supply call, SC call, alarm call, etc Each type of call can have its own timing setting. Technicians and user administrators can make these settings.
  • #127: No additional notes.
  • #128: To display this screen, click [Security]- [Authentication for Counter per User Retrieval] - [Confirmation].
  • #129: No additional notes.
  • #130: Pre-registering a new Appliance You must do the pre-registration procedure before you install a new Appliance. The pre-registration procedure results in a ‘registration number’. The ‘registration number’ has to be entered when you register the Appliance to the Center Server during the installation at the customer site. Mandatory fields You must enter ‘Customer Name’, ‘Site Name’ and ‘Service Depot Name’. The Appliance will be registered under this ‘Customer Name’, ‘Site Name’ and ‘Service Depot’ when you register the Appliance to the Center Server during the installation at the customer site. The ‘Operation Calendar’ selection can be left on ‘DEF’ (default calendar). The ‘Operation Calendar’ function will be explained later. Batch registration You can use this function when you are going to install multiple Appliances at the same Customer / Site / Service Depot. Fill in a number to generate multiple registration numbers. Leave this field blank if you only need 1 registration number. Optional fields Here you can enter useful information for administrative or reporting purposes.
  • #131: Registration number The registration number can be copied to the clipboard. The registration number is unique and can be used only once. After you installed the Appliance using the registration number, this registration number cannot be used again. Registration number / Request number In some screens the registration number is referred to as ‘Request number’. ‘Request number’ means the same as ‘Registration number’.
  • #132: Checking a pre-registered Appliance The registration number will be available in the ‘Pre-Installed Appliance’ menu for a maximum of 3 months. If the registration number is not used within 3 months, it will be automatically deleted. When you use the registration number to install an Appliance, it will be deleted and cannot be used again.
  • #133: No additional notes.
  • #134: No additional notes.
  • #135: The activation of the options must be done by an engineer. When you activate the options, a new (larger) data table is created. (All the existing data is removed.) DIMM 512MB DIMM DDR1 SSD = Solid State Disk 16GB SSD (2.5 inch) SATA
  • #136: RC Gate A/ RC Gate S-pro FSM , RC Gate A Installation, Installation Procedure
  • #137: Network-cable to connect your PC to the Basil The network-cable must be a cross-over-cable, unless the PC network-card has ‘auto-cross-over’ functionality. Nowadays most PC network-cards have ‘auto-cross-over’ functionality.
  • #138: No additional notes.
  • #139: RC Gate A/ RC Gate S-pro FSM , RC Gate A Installation, Installation Procedure Click ‘RC Gate Settings’ Click ‘Basic’ Check ‘Storage Capacity (extended)’ is 16 GB Check ‘Memory Capacity (extended)’ is 512 MB
  • #140: RC Gate A/ RC Gate S-pro FSM , RC Gate A Installation, Installation Procedure Click ‘Maintenance’ Click ‘Extended Function Setting’ Click ‘Use’
  • #141: This section describes the initial setting procedure for the RC Gate A.
  • #142: No additional notes.
  • #143: No additional notes.
  • #144: No additional notes.
  • #145: Attention! It is important to select the correct time zone. The time zone setting effects many timing settings, such as the timing for notification emails, sending of counter information etc.
  • #146: DNS Server Enter a DNS server when you want to register devices through hostname (explained later).
  • #147: No additional notes.
  • #148: No additional notes.
  • #149: No additional notes.
  • #150: No additional notes.
  • #151: No additional notes.
  • #152: No additional notes.
  • #153: No additional notes.
  • #154: If you follow the initial setting wizard, the request number will automatically be asked. If the RC Gate is registered, this step is skipped.
  • #155: No additional notes.
  • #156: No additional notes.
  • #157: No additional notes.
  • #158: No additional notes.
  • #159: No additional notes.
  • #160: No additional notes.
  • #161: No additional notes.
  • #162: No additional notes.
  • #163: No additional notes.
  • #164: The RC Gate A can discover devices in 3 different ways: By searching through a specified range of IP addresses. By searching through specified network segments. By searching through specified host names.
  • #165: The RC Gate A can discover devices in 3 different ways: By searching through a specified range of IP addresses. By searching through specified network segments. By searching through specified host names.
  • #166: Select a protocol for the search. The correct setting depends on the customer’s network SNMP version If in doubt, select SNMP V3 priority. SNMP V3 will be used first, then the other protocols. Click Next.
  • #167: You can also import a list of IP addresses as a .csv file. Select a search method Input the IP Address Ranges. (Or import CSV) If you want to prevent some IP addresses from being searched, click ‘Go to Access Prohibited IP Address Settings’
  • #168: Input the IP addresses you wish to exclude. (Or import CSV file) Click OK.
  • #169: Click ‘Start Search’ when you have specified the IP addresses.
  • #170: Click the boxes next to the devices that you wish to register. Then click ‘Prepare Registration’.
  • #171: Input a request number for each device. If you click ‘Obtain Request No’, the request number fields will be filled in automatically. Then click ‘Confirm with Server’.
  • #172: The RC Gate A searches for machines that can be registered. When a list appears as shown above: Select the devices to register Click ‘Register’. A results screen will be shown. Click ‘Complete’ to finish. If the request is accepted, the system registers the device at the Center Server.
  • #173: No additional notes.
  • #174: No additional notes.
  • #175: No additional notes.
  • #176: The RC Gate A can discover devices in 2 different ways: By searching through a specified range of IP addresses. By searching through specified network segments
  • #177: The RC Gate A can discover devices in 2 different ways: By searching through a specified range of IP addresses. By searching through specified network segments It takes 13 min. of processing time to register 500 devices at one time. For RC Gate A (maximum of 1000 devices), it takes up to 26 minutes. Each registration operation can handle up to 500 devices, so you have to do up to 2 operations for the RC Gate A.
  • #178: To enable auto discovery, select ‘Use’ Input the schedule Click ‘Next’. When the Setting Result screen appears, click ‘Finish’.
  • #179: Select a protocol for the search. The correct setting depends on the customer’s networks SNMP version If in doubt, select SNMP V3 priority. SNMP V3 will be used first, then the other protocols. Click Next.
  • #180: Set the search ranges If you want to prevent some IP addresses from being searched, click ‘Go to Access Prohibited IP Address Settings’
  • #181: When finished, click ‘Complete’.
  • #182: Normal Ricoh MFPs have a GW controller that contains Printer MIB, Fax MIB, Copier MIB, and so on. The appliance looks for the MIB and recognizes the type of device in accordance with the type of MIB found. In models with EFI controllers, the printer MIB is held in the EFI controller, not the GW controller. With the normal AD search (ping, followed by SNMP inquiry), the appliance finds the EFI or other controller, because it contains the printer MIB, but cannot find the GW controller. So, this device cannot be managed as a HTTPS device by remote registration. It can only be managed as an SNMP (MIB) device. With the new AD search function, the RC Gate A searches first using the normal search method (prtGeneralConfigChanges). Then, using another type of MIB command (ricohNetContType), it investigates the devices that it found but did not have printer MIB in the GW controller. This can find printer MIB stored in other controllers, such as EFI or Samsung controllers. This search takes twice as long. Devices with the Cosmos controller can be found with the first search.
  • #183: You must select one at a time. With the RC Gate A, it is also possible to import a set of addresses as a .csv file. You can set up this function during setting up Auto Discovery.
  • #184: RC Gate A/ RC Gate S-pro FSM , IP Address Exclusion These IP addresses are only excluded during discovery-type sweeping operations, which ping each address within a specified range, looking for a response. Functions that use direct communication between the RC Gate A and a managed device, by pinpointing a known IP address, will still work for an address that has been excluded. Also, during Remote Registration, if the excluded IP addresses are changed before registration is complete, and a device happens to be one of the excluded addresses, Remote Registration will still work, because this is not a sweeping-type operation.
  • #185: Manage as ‘HTTPS’ You can always select ‘HTTPS’ when you select ‘Manage Devices’, even if the target device is an ‘SNMP’ device. If you try to manage an ‘SNMP’ device as ‘HTTPS’ device, the registration will fail and will result in an error message. M/R Date The M/R date is the day of the month which is used for billing purposes. This is the counter which is used on the M/R Counter-CSV report (explained later).
  • #186: No additional notes.
  • #187: No additional notes.
  • #188: No additional notes.
  • #189: No additional notes.
  • #190: No additional notes.
  • #191: No additional notes.
  • #192: No additional notes.
  • #193: No additional notes.
  • #194: No additional notes.
  • #195: No additional notes.
  • #196: No additional notes.
  • #197: No additional notes.
  • #198: No additional notes.
  • #199: No additional notes.
  • #200: No additional notes.
  • #201: Search options You can search with only a portion of the Customer Name/ID, Appliance S/N, Tag ID or Device S/N. Add “%” at the beginning or end of the partial character string. For example, “ABC%” can be input as the Customer Name/ID instead of the full “ABC Company”.
  • #202: No additional notes.
  • #203: No additional notes.
  • #204: No additional notes.
  • #205: Disconnected Appliance / Device List The screenshot on the slide shows the Disconnected Device List. The Disconnected Appliance List looks the same. The list shows appliances / devices which were/are detected as disconnected within the specified data range. The list shows for each day within the specified data range the status of the appliance/device. The status is indicated with colours: Yellow : Disconnection start (AM) Light orange: Disconnection start (PM) Dark orange: Disconnecting Light green: Recovered (AM) Dark green: Recovered (PM) White: Operating Grey: Disconnected-Recovered within the same day
  • #206: ‘First AD Time’ and ‘Last Report Date/Time’ column In the Device List scroll to the right to see the ‘First AD Time’ and ‘Last Report Date/Time’ column. First AD (Auto Discovery) Time Shows the date on which AD information was acquired for the fist time. This is available only for monitored devices Last Report Date/Time For monitored devices: Shows the date on which AD information was acquired for the last time. For managed devices: Shows the date on which the latest HTTPS counter was acquired or Shows the date on which AD information was acquired for the last time. This can happen when a Basil was not able to collect the HTTPS counter, but was able to collect AD information from the device. A possible cause is that the device main power was switched ‘off’ when the Basil tried to capture the HTTPS counter, but was switched ‘on’ when the external RC gate did Auto Discovery.
  • #207: No additional notes.
  • #208: Device Information Device Information is only available for managed devices. You can edit the white coloured fields. Use the optional fields to register additional information to the device. This information is also displayed in reports such as the Counter-CSV and Supply-CSV. M/R (Meter Reading) Date The M/R date is the day of the month which is used for billing purposes. This is the counter which is used on the M/R Counter-CSV report (explained later).
  • #209: No additional notes.
  • #210: No additional notes.
  • #211: No additional notes.
  • #212: No additional notes.
  • #213: No additional notes.
  • #214: No additional notes.
  • #215: No additional notes.
  • #216: No additional notes.
  • #217: No additional notes.
  • #218: No additional notes.
  • #219: When Auto Discovery is disabled, there is only 1 counter per month available for Managed SNMP devices.
  • #220: No additional notes.
  • #221: No additional notes.
  • #222: No additional notes.
  • #223: Immediate or Scheduled Immediate: Immediately start processing the Counter-CSV request. Scheduled: Schedule the Counter-CSV request. The request will be processed automatically every month/week/day. Meter Reading or Reporting Meter Reading: Provides one meter reading (M/R date reading or latest reading) per device within the selected date range. This can be used for billing purposes. Reporting: Provides all counter data from all devices within the selected date range. This can be used for reporting purposes. Download to ‘Your PC’ or ‘Back-End’ Your PC: Download the Counter-CSV directly to your PC. Back-End: This option is not for general Center Server GUI use. This option is used for the following: Sending data to the Reporting website. This is automatically configured for each Site and does not need any action from the Service Organisation. Sending data to your ERP system. This is outside the scope of this training (see ‘ERP linkage’ chapter).
  • #224: M/R Counter-CSV file The downloaded file for an M/R Counter-CSV request can contain 2 files. One file contains the devices for which counters are available in the specified date range (the M/R or latest counter). The other file (‘Not obtained’), contains the devices for which no counters are available in the specified data range. Only ‘managed’ devices are listed in this file.
  • #225: HTTPS - Auto Discovery It is possible that the Counter CSV file shows devices as ‘Device Type: HTTPS’ and the ‘Counter Type: Auto Discovery’. This can happen when an external RC gate was not able to collect the HTTPS counter, but was able to collect AD information from the device. A possible cause is that the device main power was switched ‘off’ when the Basil tried to capture the HTTPS counter, but was switched ‘on’ when the Basil did Auto Discovery.
  • #226: No additional notes.
  • #227: No additional notes.
  • #228: No additional notes.
  • #229: No additional notes.
  • #230: Multiple supply calls filtering in the external RC gate. Multiple supply calls from SNMP devices can take place when the device generates 2 calls between 2 polling's (customer shakes the bottle and puts it back in again). When polling takes place, both calls are send to the basil. From version 3.57 these calls are filtered at the basil and only one is send to the center server.
  • #231: No additional notes.
  • #232: Toner or All Supplies Toner: Provides toner calls received within the selected date range. All Supplies: Provides toner calls and calls for other supplies (such as Waste Toner bottle and Fuser Oil) received within the selected date range.
  • #233: No additional notes.
  • #234: No additional notes
  • #235: No additional notes.
  • #236: No additional notes.
  • #237: No additional notes.
  • #238: Additional communication between external RC gate and center server. When an SC call has been notified, the basil will communicate with the center server every minute for the next 30 minutes, so additional information can be collected very easy. Filtering in center server When receiving a type B/D SC call, the Center Server waits 30 minutes before adding it to the Call List (and sending the email). If the center receives a recovery call during this 30 minute period, the Center Server cancels the SC call and does not send out a notification email.
  • #239: Definitions Alarm Call Notifying tendency of SC, paper jam and PM CC Call (Center Call) Service Call when continuous paper jam, long remaining jams, long remaining door open, waste toner bottle (near) full, etc. CC101: Continuous Jam CC201: Remaining Jam CC202: Cover Open CC301: Fusing Cleaning Web Near End CC302: Fusing Cleaning Web End CC401: Dev Aspiration Bottle Near Full CC501: Dev Aspiration Motor Near Lifetime CC601: Waste Toner Bottle Full CC611: Waste Toner Bottle Near Full: OPC CC612: Waste Toner Bottle Near Full: Transfer Belt CC621: Waste Ink Tank Full CC622: Waste Ink Tank Near Full CC631: Ink Gate Unit Full CC632: Ink Gate Unit Near Full CC701: Fusing Oil End CC801: Waste Oil Bottle Full CC811: Waste Oil Bottle Near Full CC1111: Indicates User CC Call for Continues Jams. CC1222: Indicates User CC Call for Cover Open.MC (Manual Call) Calls manually made by an operator SC (Service Call) Service Call (SC error occurrence on the device)
  • #240: No additional notes.
  • #241: Manual Call To provide information to service, a “Manual Call” can be initiated from the device. This is only available for managed devices.
  • #242: No additional notes.
  • #243: No additional notes.
  • #244: No additional notes.
  • #245: No additional notes.
  • #246: No additional notes.
  • #247: No additional notes.
  • #248: No additional notes.
  • #249: No additional notes.
  • #250: No additional notes.
  • #251: No additional notes.
  • #252: No additional notes.
  • #253: No additional notes.
  • #254: RC Gate A/ RC Gate S-pro FSM , Managed Functions Previous model (RC Gate BN): Has enable/disable RFU for its own firmware but not for devices.
  • #255: No additional notes.
  • #256: No additional notes.
  • #257: No additional notes.
  • #258: No additional notes.
  • #259: Firmware Main Firmware Update jobs are user specific. If you select “Firmware Main” from the menu you will only see jobs that you (using your user id) have submitted.
  • #260: If you update firmware from an Appliance, then you must select the Appliance pre-fix in the drop down box.
  • #261: No additional notes.
  • #262: No additional notes.
  • #263: No additional notes.
  • #264: No additional notes.
  • #265: Restart Que The “Restart Que” button will start the next job in the job que after a job has failed. It will not restart a failed job. For example if a System/Copy firmware update has failed, you do not want to update the other firmware's of the same (group of) devices.
  • #266: No additional notes.
  • #267: No additional notes.
  • #268: No additional notes.
  • #269: No additional notes.
  • #270: No additional notes.
  • #271: No additional notes.
  • #272: No additional notes.
  • #273: No additional notes.
  • #274: No additional notes.
  • #275: Reporting Server The Reporting Server is located in the USA. Reporting website Customers can get detailed fleet reports through the reporting website. Customers can only see reports from devices to which they have access (only their own devices). Service organisations manage the reporting website for their customers. Customers can do administrative tasks themselves, such as creating user accounts for their employees. The reporting website can also be used by sales departments to deliver TCO consultancy to the customer. The reporting website is also known as ‘@Remote.net’ or ‘web fleet reporting portal’.
  • #276: Link between Center Server and Reporting Server The Center Server sends device counter data to the Reporting Server through a scheduled Counter-CSV request to Back-End. This is automatically configured for each Site. The link between the Center Server and Reporting Server is one-way (only from Center Server to Reporting Server). The Reporting Server does not contact the Center Server. Databases on the Reporting Server do not interact with databases on the Center Server. For example: If an appliance is removed from the Center Server, the appliance is not automatically removed from the Reporting Server. User accounts on the Center Server are completely separate from user accounts on the Reporting Server.
  • #277: Reporting website URL’s Different URL’s are available for different brandings. Each URL uses a separate database for user accounts and device data. Most european organisations use the ‘Ricoh-Europe’ URL. The ‘GMA’ URL is for Global/Major Accounts.
  • #278: Sample user This user is only valid through the Ricoh Europe URL.
  • #279: No additional notes.
  • #280: Reports Reports can be selected on the home page or in the ‘Reports’ drop-down menu. Website language Currently the website is available in the following languages: English German Spanish French Italian Dutch Polish Portuguese Suomi
  • #281: Select Appliances If the selected customer has multiple appliances, you can select which appliances to show on the reports. In the example on the slide the optional ‘Appliance Description’ field has been populated to indicate the location. See chapter ‘Location Maintenance’ for more details.
  • #282: Change Customer When you are log-in with a ‘Service Provider’ user account you can select which customer to use for the reports. As a Service Provider you can use this function to look at the reports from your customer’s perspective.
  • #283: User Guide The User Guide is designed for customers. The User Guide contains detailed instructions for the customer and explains the reporting and maintenance features.
  • #284: No additional notes.
  • #285: No additional notes.
  • #286: No additional notes.
  • #287: You can find a more detailed description of this procedure in the Appendix.
  • #288: This table shows which conversions are possible. We will concentrate on the ‘Special Operation’ needed to switch a customer from multiple RC Gate BNs to one RC Gate A.
  • #289: Instead of a Device Check Request Call, a Service Test Call can also be made, but this takes longer. Execute a Device Check Request Call from the appliance UI each time a center command is created (e.g. Device remove request, Device Registration request, Parameter change request, etc.). This prevents the need to wait for the next polling. Please note that the following functions and services may not work properly during the transition: Auto Calls (SC/CC/Supply Calls/MIB Calls) may not be notified to the center. Counter information and regular device information may not be captured and notified to the @Remote center. RFU (Normally, no one would conduct an RFU during a transition). Any setting change notification from devices (IP address change, power on, etc.)
  • #290: Replace with same Appliance As from March 2008 it is possible to replace an appliance with the same appliance (after memory all clear). In this case you do not need a new appliance. For example if your basil has software errors (SC900) this is very useful.
  • #291: @Remote related SP modes details In this embedded Excel files you will find examples and detailed SP modes related to @Remote.
  • #292: No additional notes.
  • #293: No additional notes.
  • #294: No additional notes.
  • #295: Service Test Call from Basil This does not work on a basil that is configured for email communication (SMTP) Test Email Communication When you are setting up a Basil to communicate using email you can test the Email communication settings with the “send test email” button in the external RC Gate’s installation GUI. Device Check Request call (Only for UZ-A1). There is no indication when a Device Check Request Call has been completed successfully, or if it failed. It takes a very short time, a service test call takes much longer, but then you get a clear indication of whether the call succeeds or fails.
  • #296: No additional notes.
  • #297: No additional notes.
  • #298: Machine Certification When new devices leave the factory the “machine certification” should last for at least 30 years. Known occasions when devices can lose this “machine certification” are: On pre-production machines When replacing NV-Ram MIB2HTTP When a device is detected as a MIB device during the registration process while you are sure that the device is a true NRS device (HTTP compatible) you can try to re-write the “machine certification” (see slide) to correct this problem. In addition to (re-)writing the “machine certification” it might be necessary to also re-write the ID2 Code (see next slides)
  • #299: No additional notes.
  • #300: No additional notes.
  • #301: No additional notes.
  • #302: No additional notes.
  • #303: No additional notes.
  • #304: No additional notes.
  • #305: No additional notes.
  • #306: No additional notes.
  • #307: No additional notes.
  • #308: No additional notes.
  • #309: No additional notes.
  • #310: No additional notes.
  • #311: No additional notes.
  • #312: No additional notes.
  • #313: No additional notes.
  • #314: Keep in mind that in the future the customer may remove some of these machines or install some new ones. So you may need to adjust the amount of RC Gate A’s accordingly.
  • #315: Keep in mind that in the future the customer may remove some of these machines or install some new ones. So you may need to adjust the amount of RC Gate A’s accordingly.
  • #316: REST: Representational State Transfer REST is used for devices that have a Cosmos controller. SOAP: Simple Object Access Protocol
  • #317: RC Gate A Service Manual, Troubleshooting Guide, Additional Information for RC Gate A The service manual has details on how to use the dip switches for these two functions.
  • #318: DIP Switch SW1 This DIP Switch is used for several purposes reset Ip address clear all memory update firmware, DO NOT USE ! This DIP switch setting does not work anymore. See Appendix W for the correct procedure for local firmware update. Reset IP address Unplug the RC Gate Remove the bottom cover Set the dipswitch as listed in the table Make sure that the network cable is firmly connected (if any) Plug in the RC Gate Check that the LED turns on and off as follows: 1) All: On 2) Red/yellow: Blink 3) Yellow/red: Blink This may continue for several minutes Unplug the RC Gate. Set the dipswitch to "normal use" as listed in the table Reassemble the RC Gate Plug in the RC Gate Check the operation
  • #319: No additional notes.
  • #320: No additional notes.
  • #321: No additional notes.
  • #322: No additional notes.
  • #323: If SMTP AUTH or POP before SMTP or Proxy is enabled, you will have to obtain the detailed information from the Customer to properly program it into the RC Gate A. Settings: RC Gate BN Settings menu Network: DHCP on/off setting, IP address E-mail: See the example screen dump on the left. Net Connection Settings menu HTTP Proxy: See the example screen dump on the right. Auto Discovery menu: All settings Device Management menu: Registered Device List – Needed for each RC Gate BN, not only an example RC Gate BN Security menu: Network security setup (ping on/off) Serial number setting menu: These settings are related to acquiring the serial numbers of non-Ricoh MIB devices.
  • #324: Make screen dumps of the settings in each tab.
  • #325: No additional notes.
  • #326: To do this operation with the Maintenance Menu, you need to have the following ACL Access Rights. These are set up with Site ACL and Service Depot ACL in the Maintenance menu of the Center GUI. Site ACL The ACL setting must be ‘Full’ The Dev setting must be ‘Site Administrator’ or higher. In the row of check boxes, Mt must be checked. The status of the other boxes can be either checked or unchecked. Service Depot ACL The ACL setting must be ‘Full’
  • #327: Use of % as a wild card: For example, if the customer names are registered as ABC Germany, ABC France, and ABC Italy, you can select all these names by inputting ‘ABC%’ as the target customer in step 4. Go to Export Device List menu. Select List Type; Detail or Simple. Select Service Depot Name. Type the target Customer. You can designate multiple RC Gate BNs by using % as a wild card. Click [Export]. Click [OK] 2X. Requested list is shown. Double-click the data to save the CSV file. You can create and Export CSV file.
  • #328: No additional notes.
  • #329: No additional notes.
  • #330: No additional notes.
  • #331: No additional notes.
  • #332: No additional notes.
  • #333: No additional notes.
  • #334: These steps are covered in the chapter: Installation.
  • #335: No additional notes.
  • #336: Click ‘Device’ in the Search Menu.
  • #337: Select “Managed” for Installed Condition and “Not Specified” for Device Condition. Input the Service Depot, Appliance S/N, and other search conditions Click ‘Search’ Device Condition: Some devices may be listed as ‘Found’. These also need to be unmanaged. So, we must select ‘Not specified’. Installed condition: Monitored devices do not have to be unmanaged and re-registered. However, the customer may want to compare the lists of monitored devices made before and after switching over. To do this, you can use the device list that was exported in step 3, and compare it with a device list made after completing the switchover to RC Gate A.
  • #338: Make sure that “EDIT OFF” is selected. Select all devices. Click “Remove Devices”. While the remove request for a managed device is being carried out, “Removing” is displayed in the “Requested Status” area. At the next polling (or after a Device Check Request Call is made), the center requests the RC Gate BN to remove the device.
  • #339: In the Maintenance menu of the RC Gate BN UI, click: Click ‘Maintenance’ Click ‘Communication Server Calls’ Click ‘Device Check Req. Call’ Click ‘Start’ Make the Device Check Request call from each of the RC Gate BNs to be removed. The Device Check Request call takes a very short time. A service test call takes much longer, but you get a clear indication of whether the call succeeds or fails. This prevents the need to wait one hour for the next polling. There is no indication when a Device Check Request Call has been completed successfully, or if it failed. If the procedure continues without a successful Device Check Request Call, the RC Gate BNs will still have registered device data in the memory when they are disconnected and taken back to the service depot. So they cannot be installed again at a new customer. If the Call succeeded, the device data is deleted from the RC Gate BNs, and they are returned to the same condition as when they were new. However, the @Remote Center has deleted the device data, so the same devices can be registered again on the new RC Gate A.
  • #340: Normally, the device is online during removal. The RC Gate BN resets the flag in the device to be removed, receives a response from the device, and reports to the @Remote Center. Then the device is removed. If the device is disconnected, the flag will not be reset, but the RC Gate BN lists the device as deleted, and this is picked up by the gateway and the center. Flag: 5816-209. But, if the RC Gate BN is disconnected, it cannot receive a remove device request from the center. After 4 hours, the center times out, and removes the devices from the center database, but not from the Gateway. The only solution is to ask for assistance from IT/S in Japan to delete the records from the database.
  • #341: Click ‘Appliance’ in the Search menu Input search parameters Click “Search”
  • #342: Make sure that ‘EDIT OFF’ is selected. Select the appliances Click ‘Remove Appliance’. After a RC Gate BN has been removed at the Center GUI disconnect it. Timing for disconnecting the RC Gate BNs at the customer site After removing a RC Gate BN at the Center GUI, the RC Gate BN becomes initialized (like a brand new RC Gate). All 3 LEDs become lit (this is the ‘shut down’ status). Then the RC Gate BN can be disconnected and taken back to the service depot. If a RC Gate BN could not be initialized after removal at the Center GUI (e.g., because it is disconnected), the RC Gate BN is still active and may send data to the gateway if still connected. This will cause a problem at the Gateway when an unknown RC Gate BN (already removed at the Center GUI) sends data to it. So, after a RC Gate BN is removed at the Center GUI, the field technician should disconnect it immediately. Note that for Global Major Accounts and other large customers, RC Gate BNs may be installed in different locations, or even in different countries. It is necessary to organize technician visits at the time of removal from the Center GUJI, in order to disconnect the RC Gate BNs at the correct time.
  • #343: It takes 13 min. of processing time to register 500 devices at one time. So, for RC Gate A (maximum of 1000 devices), it takes up to 26 minutes. And for RC Gate S Pro (maximum of 5000 devices), it takes up to 2 and a half hours. Each registration operation can handle up to 500 devices, so you have to do up to 2 operations for the RC Gate A, or up to 10 operations for the RC Gate S Pro.
  • #344: Each registration operation can handle up to 500 devices, so you have to do up to 2 operations for the RC Gate A.
  • #345: If devices are listed as Found, ask the field technician to make a Device Check Request Call from the RC Gate A. This prevents the need to wait one hour for the next polling. After registering devices with the Device Registration Wizard, they are also automatically registered at the Center GUI. However, some may still be in the Found status. If so, a Device Check Request Call from the RC Gate A will change them from Found to Registered. If that fails, then the Center GUI operator will have to register them manually, and then another Device Check Request Call will be needed.
  • #346: We use Remote Registration to try to register devices that are still not registered.
  • #347: No additional notes.
  • #348: No additional notes.
  • #349: You don’t have to re-type device information. To Export Device List Export device list Select ‘List Type – Simple” Do the relevant settings Export the CSV file
  • #350: You don’t have to re-type device information. To Import Device List Update device info by CSV import Input site name Select CSV file Click ‘Update Devices’
  • #351: No additional notes.
  • #352: In the exported Device List: Simple CSV, change the Appliance S/N from the old RC Gate BN’s S/N to the S/N for the new RC Gate A and other information if necessary. Click “Update Device Info by CSV Import” in the Maintenance menu of the center GUI. Select the Site Name. Select the CSV file to import. Click [Update Device]. Open the Device List in the Center GUI, and check that all updates are correct.
  • #353: No additional notes.
  • #354: Select and Copy the “M/R Date” column (Column G) from CSV data. Set [EDIT ON] Paste the “M/R Date” Column in the GUI display. Set [EDIT OFF] Click [Update Devices]. Click [Update].
  • #355: No additional notes.