- GateManager Own - Datalogging Scenarios
- LogTunnel Scenarios
- SiteManager Embedded Scenarios
- SiteManger Scenarios
Following the release of LinkManager 8.x (LM8) in May 2018, please observe the following schedules regarding the EOL of its predecessor LinkManager 7.x (LM7):
- EOL (End of Life) date: December 31st 2019
- EOS (End of Support) date: July 1st 2020 (Configuration, product support. help and assistance.)
- EOS (End of Service) date: July 1st 2020 (GateManager 9.1 with expected release by end of 2019 will be the last GM version with LM7 support)
LM8 represents a major upgrade in terms of usability and security compared to LM7(refer to this announcement https://www.secomea.com/news/secomea-release-8-0-out-now/ , and related technical articles here: https://kb.secomea.com/helpdesk/KB/Category/402893-getting-started )
Based on customer feedback, we have found that the main arguments for not migrating from LM7 to LM8 are related to the below reasons and assumptions, which we here give our comments to:
- LM8 does not have the ability to shown only the online appliances and corresponding domains.
With release of GateManager 9.1 (expected late 2019 / early 2020) this will be included, together with other tree-view improvements.
- LM8 does not support the Messages function in GateManager
As LM8 connect is now an integral part of the GateManager web GUI, and can be performed by both Admins and dedicated LinkManager users, the Messages function is not architectural compatible. Instead we recommend using the bulk-email function in GateManager to send information to selected user groups based on roles
A more generic GateManager login-message function is implemented in GateManager release 9.1 (expected late 2019 / early 2020)
- LM8 does not support configuration of Custom services.
We found the Custom services to be too complicated for most people, and difficult to maintain for larger user groups. Instead focus was put on automatically starting RDP and automatically detect the most commonly VNC clients, in addition to the Inbrowser VNC service. For users missing the automatic start of SSH or Telnet, it is actually still possible via an undocumented feature: If "putty.exe" is installed on the PC (in "%programfiles%\PuTTY\putty.exe"), both SSH and Telnet buttons will be shown automatically in the GateManager for agents stating this support.