**************************************************************************** Software Release: RDM 4.0 - RELEASE (build 9201) Release Date: 2009-05-15 **************************************************************************** Scope and production information **************************************************************************** This is the official Remote Device Management release 4.0. This release note describes changes since Release 3.7 build 8481. Please refer to the older release notes for further information. Products covered: --------------------------------------------------- SiteManager 2029 (Hardware with UMTS interface) SiteManager 2034 (Hardware with dual DEV interfaces) SiteManager 2129 (Hardware with UMTS interface) SiteManager 2134 (Hardware with dual DEV interfaces) SiteManager 6040 (Software version, external agent support) SiteManager 6240 (Software version, hosting PC access only) LinkManager 6041 (Software version) GateManager 8250 (Software version) Version and Build numbers: ------------------------------------------------------- GateManager Server software version 4.0.0.202 GateManager Proxy software version 4.0.3 LinkManager Installer version 9201 LinkManager firmware version 4.0, build number 9201 SiteManager Soft Installer version 9201 SiteManager PC Installer version 9201 SiteManager firmware version 4.0, build number 9201 Tray Icon version 2.37.0.9201 **************************************************************************** 1. Highlights of this release **************************************************************************** - GateManager now supports cross-domain account access - GateManager proxy now has a Web-based administrator interface - LinkManager 6041 no longer uses VMware virtual machine - LinkManager user interface reworked with much faster operation - SiteManager device group for simultaneous access to multiple devices - New products supported: SiteManager 2129 SiteManager 2134 SiteManager PC 6240 **************************************************************************** 2. New features and improvements. **************************************************************************** All Products ---------------------------------- - Add support for "Corporate Floating Licenses" for software products. GateManager ---------------------------------- - Add support for cross-domain user access by joining an account to a domain (which is equivalent to joining the domain to the account). This allows the GateManager administrator to grant a user access to devices in domains outside the user's home domain by joining the account to the domains of the relevant devices. More specifically, in the Accounts View, each account now has a "Joined Domains" tab, and in the Domains View, each domain has a "Joined Accounts" tab. To provice cross-domain access, simply add the domain to the joined domains of the account - or if you prefer - add the account to the joined accounts of the domain. - The GateManager proxy now has a built-in administration web GUI. By default, it is only available via the "Go To Appliance" http service from the GateManager console (on the Server appliance itself). The default administrator account is "admin" (password "admin"). To enable external access, set the ADM_PUBLIC variable in the administrator configuration of the web server. Via the administrator web gui, it is possible modify the "proxy.conf" and "relay.conf" configuration files. - Via the proxy.conf file, it is possible to enable "auto attach" mode for device agents. This implies that new device agents created on a SiteManager which is already attached to a domain in GateManager will automatically be attached to the same domain as the SiteManager. (#3298) This is done on a per-domain basis by specifying, e.g. to enable auto attach for all subdomains of ROOT.TEST domain, specify: [ROOT.TEST.*] auto_attach=1 Please see the commentary in "relay.conf" for more details. - Also via proxy.conf, it is now possible to allocate different device address pools, server access restrictions, and web proxy target for disjoint domains. (#3307) This is mostly relevant when hosting independent customer domains on the same GateManager. Please see the commentary in "relay.conf" for more details. - Implement "fast access" API for LinkManager Console. (#3323) LinkManager ---------------------------------- - LinkManager no longer requires VMware to be installed on the PC. (#3322) - The LinkManager console is now split into two side-by-side panels: - a domain selection panel on the left, and - a device selection panel on the right. - The domain selection panel presents the complete domain structure as a dynamically expandable tree structure, similar to the GateManager Console, the Windows Explorer, etc. - Only domains with active devices accessible to the current user are shown, thus reducing the amount of information shown to the user. - The domain tree includes "joined domains" for the current user, allowing one user account to access multiple disjoint domains. - Fetching the full domain tree from GateManager is now much faster. - The device selection panel presents an view of all the active devices in the domain selected in the domain tree panel. - Fetching the device list of a domain is now much faster, so an up-to-date list is retrieved whenever a domain is selected. - Device list now includes SiteManagers without any device agents. - Consequently, the "Up", "Top", and "Back" buttons are no longer present in the console tool bar. - The above improvements are only available when LinkManager is connected to GateManager 4.0 or later; when used with older GateManager 3.x releases, the LinkManager console looks and behaves as before. - The LinkManager login page now offers to save the password for each certificate, so you don't have to retype it on every login. (#3058) - The LinkManager login page also offers to automatically reopen the last visited domain, or even to automatically reconnect to the last activated remote device. (#3058) - The RDP access method is now supported on the LinkManager, allowing a GateManager administrator to remotely connect to the LinkManager PC if Windows' Remote Desktop is enabled. SiteManager ---------------------------------- - Add support for new hardware products: SiteManager 2129 and 2134. - Add support for new software product: SiteManager PC 6240 - One-step installation; does not require VMware. - Provides remote access to the hosting PC only. - Automatically detects VNC and RDP remote desktop access methods. - Additional agents can be installed as required. - Add support for "Device Groups" for simultaneous access to a group of devices from the same LinkManager. Previously, a LinkManager only had the choice of connecting to a single device, or all devices (by activating the SiteManager hosting the agents). (#3282) Now, when connection to any device in a device group, a LinkManager will automatically connect to all the devices in the group. To associate a device with a device group, write the "Group Name" before the device name in the Agent configuration panel like this: $group name: device name That is, a dollar sign, the group name (chosen freely), a colon, an optional whitespace, followed by the device name. - SiteManager 6040 (with external agent support) still requires VMware; it now runs on VMware Player 2.0.5 and 2.5, as well as VMware Server 1.x. It does *not* run with VMware Server 2.0. - SiteManager 2029/2129 have better support for Option HSO UMTS adapters, including a new "Init String" configuration parameter to handle future adapters. - Do not allow multiple LinkManagers to use the serial port or other agents marked as "exclusive use". Device Agents ---------------------------------- - All standard agents are now included with the main firmware, so it is no longer necessary to upgrade the agents after upgrading the firmware. (#3428) - The "Address on GateManager" parameter on Vendor Agents now supports specifying the tcp and udp ports of the static device relays. (#3115) - Agents generally accept the word "SM" as symbolic target address for the SiteManager itself. - Agents running on a SiteManager Soft 6040 or 6240 accepts the word "PC" as symbolic target address for the HOST PC address (if available). - On SiteManager PC 6240, omitting the target defaults to "PC" (the most logical target). - Improved FTP support for connections from LinkManager to devices: Active FTP can be enabled with agent parameters "tcp=21 -S" Passive FTP can be enabled with agent parameters "tcp=*" - Server relays (-S option) are no longer limited to devices on DEV1. - New Vendor Agents: Bosch Rexroth / IndraDrive ELAU / Ethernet ESA / Ethernet Hilscher / NetLink Gateway VIPA / HMI - Enhanced Vendor Agents: Siemens / Ethernet - add support for HMI, PROFINET, MODBUS, and OPC. **************************************************************************** 3. Bug Fixes. **************************************************************************** All products ---------------------------------- - Failed firmware upgrades are now logged in the GateManager Appliance Log. (#3280) - Reset Configuration is now logged in the GateManager Appliance Log. (#3254) - Use Cache-Control HTTP headers to avoid caching status pages instead of using randomized request parameters. (#3210) - The "gmadmin" account is now only available for login via Go To Appliance from GateManager. (#3285) - Fix lockup in GateManager Console if requesting an empty object. (#3337) - Fix problems related to not being able to reconnect to GateManager if server is specified using DNS name, and the DNS server addresses changes. (#3318) GateManager ---------------------------------- - Fix slow connection from GateManager Console to GateManager when a DNS name is used. (#3226) - If GateManager Console connects to GateManager via proxy, and GateManager address is a DNS name, DNS name is now passed on to the proxy. (#3454) - Do not allow to delete an alert if it is set to trigger any scheduled commands. (#3306) - Strip trailing blanks in Go To Appliance commands. (#3121) - Login with username/password is now disabled by default for new user accounts. (#3227) - Automatically send new certificate when changing password with X.509 authentication. (#3262) - Do not send certificate renewal mails for disabled accounts. (#3186) - Always hide empty data-fields in Appliance specific section. - LinkManagers now enter "Disconnected" rather than "Failed" state when it is not connected to the GateManager. (#3408) Specifically, this means that a domain is no longer in failed state (RED) just because it contains a disconnected LinkManager appliance. - Reduce number of .temp.db files in the GM database. (#3453) - Fix harmless but annoying warnings during GM server startup. (#3459) LinkManager ---------------------------------- - Various improvements and fixes for using multiple GateManager Setups. (#3211) - The "Tray Icon" would sometimes enter a "yellow status" / "green status" loop after the PC had returned from standby or hibernate mode, or some other events that caused the Windows network layer to be reset. (#3125) - Do not include registration license in exported backup file, and ignore registration license found in imported backup file. (#3294) - The first UDP response datagram in a sequence of frames would sometimes get the wrong source port. (#3206) - Fix occasional dropping of a series of UDP frames. (#3206) - Use http protocol when accessing a SiteManager administration GUI via Go To Appliance from LinkManager Console. (#3146) - Improve reporting on LinkManager Console of errors related to invalid registration license or GateManager certificates. (#3224) - Stopping and restarting the Web Proxy Relay service did not work. (#3389) SiteManager ----------------------------------- - Firmware upgrade from GateManager would fail if a previous firmware upgrade failed because of loading an invalid firmware image. (#3062) - Incorrect interface names were shown for dynamic DHCP leases. (#3208) - UDP relays are now marked as such in the GateManager > Status view. - A device agent would remain in "STARTING" state on the GateManager > Status if no attachment status was received from GateManager Server. Now the state changes to "DOWN" if device is down, and "WAIT" if device is up, but still waiting for GateManager to respond. (#3100) - Do not show Maintenance > License menu on hardware-based SiteManagers. - Do not include registration license or factory certificate in exported backup file, and ignore registration licenses found in imported backup file. (#3294) Device Agents ----------------------------------- - PC Agent added duplicate 5800 and 5900 ports in some cases. (#3220) - PC Agent now always uses ping to poll device's online status. (#3220) - Serial Agent detailed parameters would be associated with the wrong serial port settting if only the Data/Parity/Stop field is filled in. (#3216) - Agents sometimes failed to restart after a configuration change. (#3207) - Fix support for Ethernet attached Beijer E1061 panel. (#3150) **************************************************************************** 4. Upgrade information. **************************************************************************** LinkManager 6041 ----------------------------------- - LinkManager release 4.0 no longer relies on VMware to operate. Instead it comes with its own virtual "LinkManager Adapter" driver, which is installed and setup by the LinkManager Installer. On Windows XP, this is installed silently, but on Windows Vista, you will have to confirm the installation of the adapter. When upgrading a LinkManager 3.7 or older, the LinkManager Installer automatically migrates all configuration and certificates from the VMware based installation. Once upgraded to 4.0, you cannot downgrade the LinkManager to an older version. - First time you start LinkManager after the upgrade (or after a new installation), you may be prompted to accept the installation of Secomea's CA certificate as a trusted root certificate. You should allow this to prevent Windows from looking for new COM port drivers (it won't find any) each time you establish a serial connection. - Both the LinkManager Tray Icon, LinkManager firmware, and SiteManager firmware must be running least release 3.7 in order to use the virtual COM port. See README.TXT in the LinkManager_xxx.zip file for instructions about how to upgrade the LinkManager components. - The firmware file id for LinkManager has changed from v41 to v6041 to reflect the change from VMware (v41) to non-VMware (v6041). SiteManager 2029 ----------------------------------- - This firmware uses a radically different mechanism for WAN fail-over and load balancing than previous firmware versions did. The user- configurable settings have changed radically too. Hence, after having upgraded, you may need to adjust some settings manually. See the on-line help for details about the new settings for WAN probing, WAN fail-over and WAN load balancing. - Due to changes to the flash memory handling on SiteManager 2029, it is only possible to downgrade from this firmware release to a firmware release 3.7 build 8481 or newer. Device Agents ----------------------------------- - Previously installed standard agents are automatically removed when you upgrade to this firmware which includes all of the standard agents. - This means that you will need to reinstall the agents if you downgrade to a firmware release older than 4.0. **************************************************************************** 5. Known issues or limitations **************************************************************************** - Due to new restrictions on secure web-site certificate authentication, both Internet Explorer 7 or Mozilla Firefox 3 may prevent you from accessing https based services via the LinkManager's Go To Appliance functionality in the non-activated state (Domain view). This is because the Go To Appliance function uses a different IP address than the actual IP address of the remote device, so the browser suspects that the target device's (typically self-signed) certificate may be a forgery. There is no easy way to get around this problem, so you will have to follow the somewhat tedious procedure of your browser to bypass the warnings and connect to the device anyway. Note 1: You should not store the certificate permanently in Firefox 3. Note 2: If you use release 4.0 or newer of both LinkManager, SiteManager, and the GateManager, connecting with Go To Appliance from LinkManager to a SiteManager now uses "http" rather than "https" to circumvent this problem. This is safe, since the http traffic is sent through the encrypted GateManager connection. **************************************************************************** 6. Agent firmware versions **************************************************************************** SiteManager firmware files now includes upgrades for all relevant agents. Older agent firmware versions are automatically removed when upgrading. This also means that if you later want to downgrade to a version before release 4.0, you must reinstall the corresponding agent files manually. **************************************************************************** 7. Special notes for GateManager Owners **************************************************************************** In the following table, the "Revision" field column is the text you must enter when you add a firmware file to the Appliance Products repository: Product Firmware file "Revision" field ---------------- ---------------------- ---------------------- LinkManager 6041 v6041_9201.ffs oper:v6041_9201 SiteManager 2029 v29_9201.ffs oper:v29_9201 SiteManager 2034 v34_9201.ffs oper:v34_9201 SiteManager 2129 v2129_9201.ffs oper:v2129_9201 SiteManager 2134 v2134_9201.ffs oper:v2134_9201 SiteManager 6040 v40_9201.ffs oper:v40_9201 SiteManager 6240 v6240_9201.ffs oper:v6240_9201 Agents n/a (see below) agent:v09_xxxx_9201 Agents are now included in the base firmware, so there is no separate agent firmware file. Agent firmware versions are still shown in the "Revision" field as indicated above. **************************************************************************** END ****************************************************************************