KYOCERA Device Manager Server Based Application User Guide
- June 11, 2024
- Kyocera
Table of Contents
kyoceradocumentsolutions.com
Device Manager
Installation and Upgrade Guide
Device Manager Server Based Application
Legal notes
Unauthorized reproduction of all or part of this guide is prohibited. The
information in this guide is subject to change without notice. We cannot be
held liable for any problems arising from the use of this product, regardless
of the information herein. © 2023 KYOCERA Document Solutions Inc.
Regarding trademarks
Microsoft®, Windows®, and Active Directory® are registered trademarks of
Microsoft Corporation in the U.S. and/or other countries. All other brand and
product names herein are registered trademarks or trademarks of their
respective companies.
Product overview
Device Manager is a server-based application that lets you monitor and manage printing devices. With this application, you can:
- Configure device settings
- Install applications on one or more devices
- Receive automated alert messages
- Check toner levels
- Upgrade firmware
- Generate device reports
- Arrange devices in groups
Features and options may vary depending on your device.
Documentation
Installation and Upgrade Guide
Provides instructions on how to install Device Manager, and configure this
application to an internal or external database.
This guide is for IT professionals, and non-IT personnel with knowledge of
database installation and configuration.
- This guide includes instructions on installing and configuring Microsoft SQL Server Enterprise and Express editions. Follow these instructions if you prefer to use Device Manager with an external database.
- This guide is not intended to replace the official documentation for Microsoft SQL. For more information, refer to the documentation in the Microsoft website.
User Guide
Provides instructions on how to use the features and settings of the
application. This guide is for IT administrators and service technicians.
Conventions
The following conventions may be used in this guide:
-
Bold text is used for menu items and buttons
-
Screen, text box, and drop-down menu titles are spelled and punctuated exactly as they are displayed on the screen
-
Italics are used for document titles
-
Text or commands that a user enters are displayed as text in a different font or in a text box as shown in these examples:
1. On the command line, enter net stop program
2. Create a batch file that includes these commands:
net stop program gbak -rep -user PROGRAMLOG.FBK -
Icons are used to draw your attention to certain pieces of information. Examples:
This indicates information that is useful to know.
This indicates important information that you should know, including o such things as data loss if the procedure is not done properly.
System requirements
Prerequisites
-
Microsoft .NET Core 6.0.9
-
Microsoft ASP.NET Core 6.0.9
• NET Core and ASP.NET Core installation prerequisite: Microsoft Visual C++ Redistributable for Visual Studio 2015.
• NET Core and ASP.NET Core are included in the installer package. For .NET Core and ASP.NET Core to work properly, your system must have all the latest Windows updates. -
Depending on your system setup and preference, you can configure Device Manager with an internal or external database.
You can only configure Device Manager with one database.
Internal database: Embedded Firebird
This database is embedded with the application, and will be installed in the same computer as the application.
External database: Microsoft SQL Server
This database is installed and set up before installing the application. There is only one database administrator that will access the database locally. The following versions are supported:
• SQL Server 2019
• SQL Server 2017
• SQL Server 2016
• SQL Server 2014
Determine the SQL Server edition to install, based on your needs:
• Enterprise
• Standard
• Express -
This free edition has lower memory capacity compared to the Enterprise or Standard editions, with a maximum database size of 10 GB.
-
For more information on the different Microsoft SQL Server editions, go to the Microsoft website.
Supported operating systems
- Windows 11
- Windows 10
- Windows Server 2022
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
- Windows Server 2012
Supported browsers
- Google Chrome 52 or later
- Microsoft Edge for Windows
- Firefox 53 or later
- Safari
Standard configuration hardware requirements
Recommended hardware | Number of supported devices | Database |
---|
•4 GB RAM
•2 cores (physical)
•1.5 GHz CPU| Up to 100 devices| Internal
•6 GB RAM
•4 cores (physical)
•3.6 GHz CPU| Up to 300 devices| Internal or external
•32 GB RAM
•8 cores
•2.2 GHz CPU
•1,000 Mbps gigabit
Ethernet adapter| Up to 10,000 devices| External
Installation checklist
Depending on your database preference, refer to the following chapters in the
Installation and Upgrade Guide:
Database type | Chapters |
---|---|
Embedded Firebird (internal database) | Device Manager installation and setup |
Since the embedded Firebird database will be used, you do not need to install
and set up Microsoft SQL Server and SQL Server Management Studio.
Microsoft SQL (external database)| 1.SQL database installation and setup
2.Device Manager installation and setup
SQL database installation and setup
Installing SQL Server Express edition
This section describes how to install Microsoft SQL Server Express edition.
For more information, refer to official Microsoft documentation. If you are
installing Microsoft SQL Server Enterprise edition, then go to the next
section.
Steps and details may vary depending on the SQL Server version.
- Run the installer.
- Select the Basic option.
- Read the license terms, and then select Accept.
- Review or specify the installation location, and then select Install.
- When the installation completes, select Install SSMS.
Installing SQL Server Enterprise edition
This section describes how to install Microsoft SQL Server Enterprise edition.
For more information, refer to official Microsoft documentation. If you are
installing Microsoft SQL Server Express edition, then go to the previous
section.
Make sure that your product key is available
Steps and details may vary depending on the SQL Server version.
-
Run the installer.
-
Select Installation > New SQL Server stand-alone installation or add features to an existing installation, and then follow the instructions.
-
When Install Rules completes, select Next. Ignore any warnings that may appear.
-
Select Enter the product key, provide the information, and then select Next.
-
Review the instance configuration details, and then select Next.
• Accept the default instance.
• Select Named instance, and then provide the information. -
In Database Engine Configuration, do the following:
a) Select an Authentication Mode:
• Windows authentication mode
• Mixed Mode (SQL Server authentication and Windows authentication)
Specify a password for the SQL Server system administrator.
b) Manage the SQL Server administrator accounts:
• To add the active user currently logged onto the computer, select Add Current User.
• To add a different user, select Add.
• To remove, select an entry from the list, and then select Remove.
c) Select Next. -
In Ready to Install, review your settings, and then select Install.
-
When the installation completes, select Next > Close.
In SQL Server Installation Center, select Install SQL Server Management Tools,
and then go to the next section.
Installing SQL Server Management Studio
Manage your SQL database permissions with SQL Server Management Studio (SSMS).
For more information, refer to official Microsoft documentation.
- Run the installer.
- Select Install.
- When the installation completes, select Restart.
If there is no Restart option, then manually restart your computer.
Configure SQL Server with SSMS
Before installing Device Manager, you need to create a user and set up server
authentication in SSMS to manage the SQL Server database instance. You will
need this information later to connect Device Manager to the SQL database.
Selecting a database instance
-
Run SSMS.
-
In Server name, select Browse for more.
-
In Database Engine, select a database instance.
If you have more than one database instance, then make sure to select the correct instance for Device Manager. -
Select OK.
Setting up authentication
Make sure that SSMS is running.
-
In SSMS Object Explorer, expand the database object, and then go to Security > Logins.
-
Right-click NT AUTHORITY1SYSTEM, and then select Properties.
-
Select Server Roles > dbcreator.
The dbcreator role should be associated with a user account, which Device Manager will use to connect to the database. Public should be selected by default. If that account is a domain user account, refer to Adding a domain user. -
Select OK.
-
Right-click on the database instance, and then select Properties.
-
Select Security.
-
In Server authentication, select either Windows Authentication mode or SOL Server and Windows Authentication mode, and then select OK.
-
Restart the SQL Server database service.
a) In Windows, select Start, and then search for the Services app.
b) In Services, search for SQL Server.
c) Right-click on the service, and then select Restart.
Adding a domain user
Make sure that SSMS is running.
-
In SSMS Object Explorer, expand the database object, and then select Security.
-
Right-click Logins, and then select New Login.
-
In Login – New, go to General, and then select Windows authentication > Search.
a) In Select User or Group, select Advanced.
b) In Select User, Service Account, or Group, select Locations.
c) In Locations, select Entire Directory > OK.
d) Select Find Now.
e) In Search results, select a user account, and then select OK.
f) In Select User, Service Account, or Group, verify that the correct user account is added, and then select OK. The selected domain user is specified in Login – New. -
In Login – New, go to Server Roles, and then select dbcreator.
Public is selected by default. Keep this selection. -
Select OK.
Device Manager installation and setup
Installing Device Manager
If you plan to use the Device Manager application with an external database,
make sure that SQL Server and SSMS are installed and configured before you
install the application.
-
Run the installer.
-
Review the license agreement, and then select Accept.
-
Review or specify the installation location, and then select Next.
-
Review your settings, and then select Install. If previously stored files are detected, then select an option:
• Select Yes to use configuration files from the previous installation, such as AuditLogs, DeviceUser, and Certificate.
• Select No to replace the previous configuration files with new ones. -
When the installation completes, select Next.
Take note of the default login information. -
Select Finish to restart your computer immediately, or you can restart later.
If you prefer, you can specify to create a desktop shortcut. This shortcut opens Device Manager in your default browser.
Firewall configuration
After installing Device Manager, make sure that the following ports are
accessible:
Device
Destination Port Number | Protocol | Description |
---|---|---|
80 | TCP (HTTP) | Device home page |
161 | UDP (SNMP) | To request data from a device |
162 | SNMP | To request SNMP Trap data from a device |
443 | TCP (HTTPS) | Device secure home page |
9000 | TCP | Computer with local USB agent |
9090 | TCP (HTTP) | To request data from a device |
9091 | TCP (HTTPS) | To request data from a device |
9100 | TCP | To send a firmware upgrade PRESCRIBE command to a device, enable |
the Raw Port option on the Device Operation panel
Device Manager
Destination Port Protocol | Number | Description |
---|---|---|
800-899 | TCP (HTTP) | To request the firmware files from the Device Manager |
server by a device
9191| TCP (HTTP)| Device Manager web page
9292| TCP (HTTPS)| Device Manager secure web page
9595| TCP (HTTP)| To manage internal Device Manager operations
- After installing Device Manager, make sure that ports 9191 and 9292 have been added.
- If you intend to use Device Manager in a private network environment, then change your Firewall settings to private.
External Server
Check the following ports only if the database and Device Manager are
installed on separate computers.
Destination Port Number | Protocol | Description |
---|---|---|
25 | TCP (SMTP) | Simple Mail Transfer Protocol (SMTP) port |
1433 | TCP | Microsoft SQL database server default port |
Upgrading Device Manager
Some recommendations before upgrading:
- Apart from your current system, set up a parallel environment for the upgrade, to have a fail-safe and to test the upgrade integrity.
- Back up all current data and user information in the Device Manager database
- Consult a project manager to have a plan, considering the risks, resources, and impact to your organization
- Run the installer.
- Review the license agreement, and then select Accept.
- Select Upgrade.
- When the upgrade completes, select Next.
- To restart, select Yes > Finish.
• After restarting the computer, make sure that the Device Manager service is running and firewall Inbound Rules are in place.
• Before starting Device manager, make sure to clear the browser cache.
• To retain current data, make sure to select the same database as the previous version.
Connecting Device Manager to the database
-
Open Device Manager.
• Double-click the desktop shortcut.
• Open a supported browser, and then go to https://localhost:9292/. -
Review the license agreement, and then select Accept & continue.
-
Depending on your system setup and preference, select a database type:
Internal database
The embedded Firebird database is used with Device Manager.
External database
The Microsoft SQL database is used with Device Manager.
a. Specify the database server details.
b. Select Test Connection.
Review the results and if necessary, modify the server details. If a Test Connection error appears, then refer to Troubleshooting SQL connection error. -
Select OK.
-
Verify the connection settings:
a) Go to System > System Settings > Database Connection.
b) Depending on your database type, confirm the following:
Database type | Settings |
---|---|
Internal database | Server: (local) Port number: 0 |
External database | Depending on your database server information, make sure |
that Server, Port number, User ID, and Password are correct.
Troubleshooting SQL connection error
A connection error between your SQL Server and Device Manager application may
be due to certain permission or environment settings.
-
In SSMS, make sure that the Remote connections setting is enabled.
a) In SSMS Object Explorer, right-click your database server instance, and then select Properties.
b) In Server Properties, select Connections.
c) In Remote server connections, make sure that Allow remote connections to this server is selected.
In Device Manager, repeat Test Connection. If the problem persists, then go to the next step. -
Check the port and SQL browser service.
a) In TCP/IP Properties, go to IP Addresses > IP1, and then take note of the TCP Port.
b) Open that port in Firewall, and confirm that it is not blocked.
c) In Windows, open Computer Management, and then go to Services and Applications > Services.
d) Search for the SQL Server Browser service, and make sure that Status is Running and Startup Type is Automatic.
• Double-click SQL Server Browser, and then in Startup Type, select Automatic.
• If Service status is not Running, then select Start > OK.
e) Right-click SQL Server Browser, and then select Restart. In Device Manager, repeat Test Connection. If the problem persists, then contact support.
Making a domain user a local administrator
Use Windows Computer Management to provide local administrator rights to a
user in your domain.
-
In Computer Management, go to System Tools > Local Users and Groups > Groups, and then double-click Administrators.
-
Select Add.
a) In Select Users, Computers, Service Accounts, or Groups, select Advanced.
b) In From this location, verify that your domain location is correct. If necessary, select Locations, and then browse for the correct domain.
c) Select Find Now.
d) In Search results, select a target domain user and then select OK.
e) In Enter the object names to select, verify that the correct domain user is added, and then select OK. -
In Members, verify that the correct domain user is added, and then select OK.
-
Restart Device Manager.
Use Windows Local Group Policy Editor to manage administrator approval mode.
- In Local Group Policy Editor, go to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
- Double-click User Account Control: Run all administrators in Admin Approval Mode, and then review the setting. Disabling this setting reduces the security of your computer.
Additional configuration items
In Device Manager:
- Review your security settings in System > Security.
- Configure SMTP settings for sending messages and notifications in System > SMTP.
- Manage notifications and reports in Notifications.
- Change the password by selecting the option from the user icon. If you are logging into a remote server or have configured security settings to require login for a local device installation, then change the administrator password.
Local Device Agent
Install the Local Device Agent (LDA) application on each host computer with a USB-connected device. This allows Device Manager to discover these devices Before installing LDA, make sure that:
-
NET Framework v4.0 or later is installed.
For more information, go to the Microsoft website. -
In Device Manager, the device is removed from the list.
-
The device is connected to the host computer with a USB cable.
-
The host computer is restarted
Disabling Status Monitor
If you plan to access a device that is connected to a host computer through
USB cable, then you must disable Status Monitor.
- Depending on your printer driver status, do the following:
Status| Actions
---|---
Printer driver is installed
Make sure that the latest version is
installed.| a. In Control Panel, select Devices and Printers.
b. Right-click your device, and then select Printing preferences.
c. Go to Advanced > Status Monitor, and then make sure that Enables event notifications is
disabled.
If the Status Monitor option is disabled, then go to the next step.
Printer driver needs to be installed
Make sure that the latest version is
installed.| a. Run the installer.
• In Express Install, make sure that Status Make Monitor is not selected.
• In Custom Install, make sure that Status you have Monitor is not included in Products to the latest
Install.
b. Follow the instructions.
For more information, refer to the Printer Driver User Guide. - Verify that Status Monitor is disabled.
a) In Windows, run Task Manager.
b) From any application, send a print job. You can send a print job with a blank page.
c) After sending a print job, go to Task Manager, and make sure that Status Monitor does not appear in Processes > Apps.
If disabled, then the Status Monitor window does not appear. 1—., If the window appears, then go to Settings > Notifications, and then disable event notification.
Installing LDA
In each host computer with a USB-connected device, do the following:
-
In Device Manager, go to Devices > List > More > Download the local agent.
-
Save and extract the package.
-
Run the installer.
You may need to allow the installer to make changes to your computer. -
Review or modify the Destination folder, and then select Next.
-
Confirm the settings, and then select Install.
-
Review the results, and then select Close.
-
Make sure that LDA is running.
In Task Manager, go to Processes > Background processes, and then search for LDAService.
Discovering USB-connected devices
After installing LDA in host computers with USB-connected devices, you can add
these devices in Device Manager.
Before adding a USB-connected device, make sure that:
- Status Monitor is disabled in the host computer.
- You have the IP address or host name of the host computer.
- The device is not in sleep mode.
- In Device Manager, go to Devices > List > Add devices > Add devices now.
- In Discovery mode, select By IP address or host name.
- In Target, specify the IP address or host name of the computer with the USB-connected device.
- Review or modify other settings, and then select Run.
- Review the results. If necessary, resolve any issues before repeating the process.
In Device list, confirm that the device has been added.
For USB-connected devices listed in Device Manager:
• You cannot edit the location and communication settings.
• You cannot open the device home page.
• In the host computer, make sure that LDAService is running and Status Monitor is disabled.
For the KYOCERA contact in your region, see Sales Sites sections here
https://www.kyoceradocumentsolutions.com/company/directory.html
is a trademark of KYOCERA Corporation
DMIGKDEN300.2023.01
References
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>