Take notice of the following information regarding the UMS Web App.

Login

  • The login data of the database user are not accepted for the UMS Web App. For how to log in to the UMS Web App, see Logging in to the UMS Web App.

Permissions

  • The UMS Web App and the UMS Console share the same permissions. For detailed information on access rights in the IGEL UMS, see Create Administrator Accounts.
  • Read permissions to a directory enable access to devices in this directory; permissions only to devices are not sufficient.

Synchronization between the UMS Console and the UMS Web App

  • Changes made in the UMS Console are immediately available in the UMS Web App, and vice versa.
  • Changes made in the UMS Console are searchable not immediately, but after the next reindexing, which is executed every hour.

Logging

  • User actions in the UMS Web App are currently not logged. 
  • Log files for the UMS Web App can be found in /rmguiserver/logs/wums*

Shadowing (VNC)

  • Shadowing over ICG is only possible with IGEL Cloud Gateway version 2.02 or higher.
  • For secure shadowing, newly registered devices need to boot several times until the certificate for the SSL tunnel is transferred to the UMS.
  • Shadowing is currently not working with Internet Explorer.

Certificate

  • Currently, browsers do not accept the certificate of Apache Tomcat used by the UMS Server. 

Resolution and Use on Mobile Devices

  • The minimal supported resolution is 768 px.
  • Currently, IGEL does not recommend using the UMS Web App on tablets and mobile devices.

Installation

  • In case of using the UMS Web App in a HA environment, the UMS Web App does not necessarily have to be installed on every UMS Server. The UMS Console and the UMS Web App can be installed on different servers.

RAM and Disk Space Requirements

  • The increase of the RAM and disk space is required due to the implemented Elasticsearch engine. For the minimum requirements, see Installation Requirements.