Secomea Release 8.2

Software Release: Secomea Remote Device Management 8.2 - Public release
Release Date: 2018-08-22

     (c) Copyright 2018, Secomea A/S.  All rights reserved.

Scope and production information

This is Secomea Remote Device Management release 8.2 build 18335.

For LinkManager 8.x and GateManager, this release note describes changes
since release 8.1 build 18253.

For SiteManager and SiteManager Embedded, this release note describes
changes since release 7.4 build 18052.

Numbers #xxxx are references to Secomea bug tracker issues.

Products covered:

GateManager 4250 (Hardware version)
GateManager 4260 (Hardware version)
GateManager 8250 (Software version [for Linux OS])
GateManager 9250 (Software version [for GateManager OS])

LinkManager Mobile (GateManager Integrated service)

LinkManager 6051 - Client software, for Windows 7, 8, and 10.

SiteManager 3439 - Hardware, DIN mount, 4-port switch, integrated 3G
SiteManager 1439 - Hardware, DIN mount, 4-port switch, integrated 3G

SiteManager 3429 - Hardware, DIN mount, 4-port switch, ext 3G (USB)
SiteManager 1429 - Hardware, DIN mount, 4-port switch, ext 3G (USB)

SiteManager 3349 - Hardware, DIN mount, integrated WiFi Client
SiteManager 1149 - Hardware, DIN mount, integrated WiFi Client

SiteManager 3339 - Hardware, DIN mount, integrated 4G (EU/US/CN/JP models)
SiteManager 1139 - Hardware, DIN mount, integrated 4G (EU/US/CN/JP models)

SiteManager 3339 - Hardware, DIN mount, integrated 3G (old model)
SiteManager 1139 - Hardware, DIN mount, integrated 3G (old model)

SiteManager 3239 - Hardware, DIN mount, integrated 3G
SiteManager 1039 - Hardware, DIN mount, integrated 3G

SiteManager 3229 - Hardware, DIN mount, external 3G (USB)
SiteManager 1129 - Hardware, DIN mount, external 3G (USB)
SiteManager 1029 - Hardware, DIN mount, external 3G (USB)

SiteManager Embedded 6110 - Software, for Windows XP/7/8/10
SiteManager Embedded 6111 - Software, for Linux x86/x64

Deprecation/EOL announcement:

The LinkManager 6041 Client software - LinkManager 7.x release series,
will not receive any future feature updates.

Secomea will continue to provide necessary security updates for the 6041
client software 7.x release series until end of May 2019.

The latest LinkManager 6041 software release is 7.4 build 18025.

1. Highlights of this release

• Add support for well-known "Go To Appliance" services in LinkManager 8.x

• Other than that, this is primarily a bugfix release which addresses some
  issues with the new Unified GateManager / LinkManager user interface and
  LinkManager client software introduced with release 8.0.

• This is also the first 8.x release for the SiteManager and SiteManager
  Embedded products, but for these it is mainly a bugfix release.

2. New features and improvements

GateManager (GM)

• Add support for starting "standard" GTA service programs via LM. #9382

  When an agent is connected remote, clicking on the blue (i) icon in the
  status and counter panel will now show GTA buttons (like LM 7.x) for the
  following GTA services, provided that a suitable program is installed to
  perform the actual GTA operation: rdp, vnc, ssh, telnet, and "folder".

  Note: For VNC services in particular, this means the if LM client is
  connected, and a VNC service is supported, that service is started rather
  than using noVNC in the browser; however, if the "External Viewer" option
  is selected, the usual "Manual Start Service" popup is shown (rather than
  actually starting the viewer).

• Apply "flash" icon to all connected agents. #9329 #9255

  When doing a "Connect Group", all connected agents in the group (as well
  as the SiteManager hosting the agents) now show the "flash" icon.

  Note: Only the agent which was used to do the "Connect Group" will have
  the "Disconnect" button and the status and traffic counter display.

• Localized $Ox links now use https rather than http in the URL. #9448

• Add override for $O6 link: linkmanager8.html #9407

• Updated Japanese online help texts for Basic Administrators and
  LinkManager Users. #9446

• Support separate lm-login-info.png and landing-info.png images. #9280
  See Files > Public online help for more information.

• Syslog improvements:

  • It is now easier to find the agent/relay that logs certain errors (like
    unapproved addresses or invalid targets) in the system log. #9143

  • If someone tries to load a non-existing web page, the syslog error
    now includes the full path as well as the requester's IP address. #8402

  • If a mobile number is remapped by an SMS gateway script, log the
    resulting mobile number in syslog (only if SMS debug is enabled). #9430

  • Add support for systems which does not store syslog in "messages" file.
    #9414

• Notify the LM User (in the GM portal) if a connection fails because
  the LM Service or LM Adapter is not operational. #9327

• Impose idle-timeout on LogTunnel, Device Relay, and FTP DATA connections.
  #9277

  Notice:

  Before this change, there was no idle-timeout on active TCP connections,
  so this change is - in principle - not backwards compatible, as it will
  now by default impose a 120 seconds idle timeout on all LogTunnel and
  relay related TCP connections.

  Consequently, this may break some use-cases which rely on long-lived
  mostly-idle TCP connections. To remedy that, set an explicit timeout
  value (max 65535 seconds) on the LogTunnel agent or static relay.

• Simplify LinkManager startup and detection by removing most of the "Start
  LinkManager" buttons from the GM portal GUI. Use the "Detect" buttons
  or simply make a remote connection to start the LinkManager Client (if it
  is not already started). #9299

• Add mouse-over feedback on "locked" configuration parameters. #9213
  Also explain the lock in "External Public Hostname" online help.

LinkManager Mobile (LMM)

• N/A

LinkManager (LM) Client 6051 (8.x release series)

• Add support for starting "standard" GTA service programs via LM. #9382

  LM will now detect supported GTA services by searching for and starting
  relevant programs to handle the following standard GTA services using a
  small selection of "well-known" programs to handle them:

  rdp: use "mstsc" program (MS' Remote Desktop Connection program)
  vnc: use TightVNC, Ultravnc and RealVnc viewers if installed
  ssh: use PuTTY if installed
  telnet: use PuTTY if installed
  folder: use "explorer" program

  Username and passwords are passed as arguments to the programs - if
  supported, or alternatively (for rdp and folder), LM will call the
  "cmdkey" utility (if available) to temporarily setup the proper
  credentials for performing the GTA command.

• The LM Tray icon will now show mouse-over status "LinkManager Connected"
  whenever LM has an active remote connection. #9268

• Notify the LM User (in the GM portal) if a connection fails because
  the LM Service or LM Adapter is not operational. #9327

• Optimized GateManager connection setup. #9399
  LinkManager will now try the various possible connections (GM address,
  ports, proxies) in a more optimal way aimed at reducing the number of
  connections attempts made and thus finding a working connection faster.

SiteManager (SM)

• Optimized GateManager connection setup. #9399

  SiteManager will now try the various possible connections (GM address,
  ports, proxies) in a more optimal way aimed at reducing the number of
  connections attempts made and thus finding a working connection faster.

SiteManager Embedded (SM-E)

• Optimized GateManager connection setup. #9399

  SM-E will now try the various possible connections (GM address, ports,
  proxies) in a more optimal way aimed at reducing the number of
  connections attempts made and thus finding a working connection faster.

• Support 100 relays on SM-E for Linux (v6111). #9306

  If SM-E v6111 is assigned an "Extended 10 agents" license, it now
  supports upto 100 static relays (rather than 10).

Device Agents

• Add the "ssh" service to device and vendor agent plugin. #9382

3. Bug Fixes

GateManager (GM)

• Fix intermittent crashes if GM server was updated with a TLS SHA-256
  certificate without a corresponding private key file. #9458

• Remove Install/Start options from "detection failed" popup. #9456

• Fix "sticky resize changes" for help popup size. #9154
  If you ever resized the online help popup, it would no longer auto-resize
  to fit the actual contents on subsequent use.

• Fix UPLINK2 > SMS PIN layout issues in USB Configuration Wizard. #9154

• Properly return to the GM portal if an error is reported in the "Make
  CSR" request. #9116

• Fix inability to change own password for accounts using X.509. #9457

• Fix importing an exported domain with identical account names for
  different roles (like Basic Administrator, LM User and LM Mobile User). #9300

• Change EL/US to LT/US in audit log info field. #9146

• Fix occasional HTML format error in "serial number locked" line. #9424

• Fix noVNC support for B&R X20 PLC. #9307

• Fix use of $ON in FR, IT start package templates. #9377

• Fix inability to change the "Detect LM on startup" option. #9366

LinkManager (LM) Client 6051 (8.x release series)

• Improve handling of the "Keep Connection on Close" option which didn't
  work reliably in some browsers. Note that in some browsers, changing the
  option while a connection is active has no effect on the active
  connection. #9268

• If a remote connection failed, LM would not cleanup the connection on the
  GM side; specifically, LM would still be in "logged in" state and the
  floating license allocated for the remote connection was not released.
  #9329

• Cleanup "zombie routes" on LM startup and after restarting the LM
  Service. #9327

  If the LM Service is stopped while there are active routes setup by
  LM client, those routes cannot be removed when LM is disconnected
  or shut down. Now cleanup such "zombie routes" at the first given
  opportunity.

• Use "LinkManager Client" (instead of "LinkManager protocol" or
  "LinkManager Tray") in automatic browser popups when starting the
  LinkManager client. #9391

LinkManager Mobile (LMM)

• N/A

SiteManager (SM)

• Fix sporadic failures to connect through an NTLM proxy. #9330

• Fix auto-subnet agent failure if DEV interface is down on power-on. #8955

• Reset relay rx/tx/ctl counters when connection is opened. #9277

• Fix issue where some agents (like Pro-face Ethernet) would never go online
  once it had gone offline. #8907

• Fix incomplete storage of some relay configuration parameters. #8996

• Remove misleading information about "heartbeat-only" setting providing
  remote access to the SiteManager itself. #3336

• Fix apache crash on certain invalid requests. #9155 #9192 #9243
  Although the crashes themselves were harmless, they would drop an
  unwanted crashdump file on the SiteManager.

• Increase modem detection time.
  Improve modem detection by increasing the time SiteManager burn when
  scanning for build in modem. #8036

SiteManager Embedded (SM-E)

• Fix sporadic failures to connect through an NTLM proxy. #9330

• Fix issue where some agents (like Pro-face Ethernet) would never go online
  once it had gone offline. #8907

• Fix incomplete storage of some relay configuration parameters. #8996

• Remove misleading information about "heartbeat-only" setting providing
  remote access to the SiteManager Embedded itself. #3336

Device Agents

• The Generic Desktop agent now actually uses individual usernames and
  passwords for the RDP and VNC services. #9449

4. Upgrade information

Using the GateManager Portal

Your GateManager and all your SiteManagers can be upgraded directly from
the GateManager Portal.

First use the Server Administrator account to upload the firmware or installer
file to the GateManager's Files > Firmware repository.

Then you can use the "Upgrade Firmware" command or the [Upgrade] button to
upgrade your GateManager and each of your SiteManagers.

You can also use an Action to perform a bulk update of all your SiteManagers.

Note: Upgrading GateManager 3.x and 4.x servers directly to release 8.1 is
not supported; please contact Secomea support for assistance if needed.

Upgrading from LinkManager 6041 (7.x) to LinkManager 6051 (8.x)

When you install LinkManager 6051, you will be asked if you want to keep
the existing LinkManager 6041 installation. You can have both installed
at the same time, but you cannot run both at the same time.

If you need to connect to GateManager servers which are not yet upgraded to
release 8.x or rely on the LMv1 API, you will need to keep the LM 6041
installation.

Notice that none of the saved certificates, passwords or other settings are
migrated from the LinkManager 6041 (7.x) to the new LinkManager 6051 (8.x);
you will have to use the original .LMC certificate file and password to login
with the new LinkManager (on the GM portal).

5. Known issues or limitations

• Domain Messages that used to be shown when logging in on the legacy
  LinkManager Console, are not shown to LinkManager Users logging into the
  GateManager portal.

• The LinkManager 7.x client supported customized "Go To Appliance
  Services" which could launch specific applications for a specific
  service. This is not supported by the new Unified interface.

• COM-port number can not be changed while there is an active connection
  using the COM-port; make sure to disconnect before changing the number.
  Also, after changing the number, you may need to wait a minute or so
  before starting the connection, as it takes some time for the Windows
  Device Manager to effectuate the change.

The following are not particularly new for this release

SiteManager

• SiteManager WiFi supports WPA/WPA2 and TKIP/AES encryption.
  WEP is not supported.

• WiFi access points that require web page login are not supported.

• Note that using the PPI option requires optimal bandwidth for both
  the LinkManager and the SiteManager. This is due to the PPI protocol and
  Step7 software by design do not take into account the delays (latency)
  that may occur when relaying the communication over long distances.

• The Siemens Step5 agent requires optimal bandwidth for both the LinkManager
  and the SiteManager.

END