Softpedia >Windows >Internet >Remote Utils >iTivity >  Changelog

iTivity Changelog

What's new in iTivity 6.0.10

Oct 7, 2014
  • iTivity iManager 6.0.10:
  • iTivity iManager 6.0.10 expands the ability to access most iAgent services from a command line invocation. If you specify both the iServer and iAgent for a command line invocation, then you can also specify which service to access on that iAgent. The following command line flags are now supported. You should only specify one service flag on any given command line launch.
  • When connecting to Windows Vista, Windows 7, Windows 8, 2008 Server, 2012 Server and later systems consoles' via VNC, the iManager 6.0.10 can support automatic reconnection after the screen connection drops due to login or logout. The behavior is controlled by setting the upper limit on the number of reconnections that are allowed for any specific iAgent access. If the set the limit to zero, then no VNC reconnections will take place. You can control the VNC reconnection using this new setting.
  • When running on a Windows desktop, the iTivity iManager 6.0.10 supports automatic forwarding of the iAgent credentials to the RDP client (or Remote Desktop Connection) for immediate login over the RDP connection. While this behavior is enabled by default, you can disable it by setting the following flag to zero. This would be useful if you need to provide iTivity authentication to the iAgent with a different username from the desired RDP login username.
  • iTivity iManager 6.0.10 supports automatic loading of stored iServer
  • credentials, if any, from the default NCN file when none are specified on
  • the command line.
  • iTivity iManager 6.0.10 corrects the occasional problem with vncviewer on Windows systems where it sometimes exits with the error "vncviewer has stopped working" during the initial connection setup.
  • iTivity iManager 6.0.10 corrects intermittent corruption of the iAgent list in the left hand or right hand panel when connected to iServers with very high activity. Symptoms of this problem include blank areas and/or blank lines in the left hand pane.
  • iTivity iManager 6.0.10 corrects the issue with hung processes when launching in command line mode and selecting the RDP service to a Windows based iAgent.
  • iTivity iManager 6.0.10 corrects the issue with hung processes when launching in command line mode and selecting an iAgent that is no longer connected.
  • iTivity iManager 6.0.10 corrects the issue with hung processes when launching in command line mode and the authentication dialog times out with no input.
  • The iTivity iManager 6.0.10 now uses the OpenSSL release 1.0.1i from 06 Aug 2014. This update contains several bug fixes and enhancements. 11- iTivity iManager 6.0.10 corrects the occasional problem with vncviewer on Windows systems where it sometimes exits with the error "vncviewer has stopped working" after logout of a Windows Vista iAgent.

New in iTivity 6.0.06 Build 1 (Oct 7, 2014)

  • The iTivity iServer 6.0.06 now uses the OpenSSL release 1.0.1h from 05 June 2014. This update contains several bug fixes and enhancements, including: fix for the MITM vulnerability (CVE-2014-0224),

New in iTivity 6.0.05 Build 2 (Oct 7, 2014)

  • This release of the iManager supports user configurable grouping of iAgents. When grouping is not enabled iAgents appear under their corresponding iServer in a linear fashion

New in iTivity 6.0.05 Build 1 (Oct 7, 2014)

  • Added the ability for users to connect directly from the command
  • line to one of the following services running on any host :
  • CHAT
  • FTP
  • SFTP
  • SMB
  • SSH
  • TELNET

New in iTivity 6.0.04 Build 1 (Oct 7, 2014)

  • iTivity iServer 6.0.04:
  • The iTivity iServer 6.0.04 now uses the OpenSSL release 1.0.1g from
  • 07 Apr 2014. This update contains several bug fixes and enhancements,
  • including:
  • fix for the TLS heartbeat bug (CVE-2014-0160),
  • fix for side-channel attacks (CVE-2014-0076),
  • fix for TLS record tampering bud (CVE-2013-4353) and
  • fix for TLS version checking bug (CVE-2013-6449).

New in iTivity 6.0.00 Build 1 (Oct 7, 2014)

  • iTivity iServer 6.0.00:
  • The iTivity 6.0.00 iServer installer will automatically configure Windows firewall rules to insure network connectivity on the ports selected for iServer communication.
  • Starting with iTivity 6.0.00, the iServer for Windows has all binaries and libraries signed with the Tridia code signing certificate. This should improve compatibility with some anti-virus software.
  • The iTivity iAgents, iManager and iServer now use the OpenSSL release 1.0.1e from 11 Feb 2013. This update contains several bug fixes and enhancements, including: support for TLS v1.2 and DTLS/TLS heartbeat, protocol protection against BEAST attacks and better performance on Intel hardware via AES-NI instructions.
  • The iTivity 6.0.00 iServer includes improved license usage tracking in the iServer activity log. License usage is reported in the new event types, 701, 702, 703 and 704.
  • iTivity iAgents 6.0.00:
  • The iTivity 6.0.00 iAgent installer will automatically configure Windows firewall rules to insure network connectivity on the ports selected for iAgent communication.
  • Starting with iTivity 6.0.00, the Unattended and Attended iAgents for Windows have all binaries and libraries signed with the Tridia code signing certificate. This should improve compatibility with some anti-virus software.
  • The Unattended and Attended iAgents for Windows include the ability to properly capture and display temporary windows on Windows 7, Vista and 2008 Server that use alpha blending. This includes the ability to show the popup menu above system tray icons with multiple windows open. It also includes the ability to show popup windows in Windows Office.
  • The iTivity iAgents, iManager and iServer now use the OpenSSL release 1.0.1e from 11 Feb 2013. This update contains several bug fixes and enhancements, including: support for TLS v1.2 and DTLS/TLS heartbeat, protocol protection against BEAST attacks and better performance on Intel hardware via AES-NI instructions.
  • iTivity iManager 6.0.00:
  • Added the ability for users to configure what viewer to launch when one double clicks on a host computer. By default the VNC viewer is launched, but now one can configure for the VNC or the RDP viewer to be launched instead and if the RDP viewer is chosen then one can configure the default behavior of opening a new RDP session or connect to the system console. Also the iManager has additional intelligence were if the user double clicks on a host that does NOT support RDP it will fall back and invoke the VNC viewer.
  • Added the ability for users to connect directly from the command line to a new RDP session or to a host's system console. There are two new command line options:
  • rdp - If present then a new RDP session is started.
  • rdpconsole - If present then the user connects directly to the host's system console.
  • The flags are NOT mutually exclusive. The present of the flag -rdpconsole will supercede the presence of the -rdp flag.
  • NOTE : When users run the iManager in debug mode ( use -X flag ) and one performs a direct command line connection to a host ( as in the above item #2 ), after the connection to the host closes the debug windows will remain open in order to display diagnostic information.

New in iTivity 5.4.05 Build 1 (Oct 7, 2014)

  • The 5.4.05 iManager adds support for the Find button on the toolbar.
  • Linux iManager Configuration File
  • etc/iTivity/iManager.conf
  • Menus/ToolBarFind=1,0
  • Windows iManager Registry Settings
  • HKLM\Software\Tridia\iTivity\Mgr\Menus
  • "ToolBarFind"="1,0"
  • iTivity release 5.4.05 of the iManager removes accelerator key conflicts and adds accelerator keys for some menus, including ctrl-P for properties.
  • This release uses a darker authentication green for better contrast with the light blue high-light color.
  • iManager 5.4.05 supports automatic text highlighting when opening the Find

New in iTivity 5.4.04 Build 1 (Oct 7, 2014)

  • The iTivity Attended iAgent has been updated to allow the [View] remote control connection to continue operating during the UAC confirmation dialog on Windows 7, 2008 Server and Vista.
  • The iTivity iAgents, iManager and iServer now use the OpenSSL release 1.0.0c from 02 Dec 2010. This update contains several bug fixes, including one to insure the stability of the TLS server (iServer).

New in iTivity 5.4.03 Build 1 (Oct 7, 2014)

  • iTivity release 5.4.03 of the iManager automatically expands the iAgent listing after authenticating with the iServer.
  • The 5.4.03 iManager automatically trims whitespace from the username, password and support domain credentials during authentication. This improves success ratios when copy/paste gestures unintentionally prefix or append whitespace characters to the username or password.
  • The 5.4.03 iManager no longer recommends the iServer authentication credentials when authenticating to an iAgent. Also, the most recently used Linux and Windows iAgent credentials are kept separate.
  • iTivity release 5.4.03 of the iManager no longer incorrectly displays the prompt for a reason during authentication to the iServer.
  • iTivity release 5.4.03 of the iManager corrects a problem accessing the services of some iAgents containing a comma in the iAgent name. These iAgents can now be accessed normally.

New in iTivity 5.4.02 Build 2 (Oct 7, 2014)

  • The iTivity iAgents, iManager and iServer have been modified to support trusted encryption certificates with either the previous MD5 file naming convention or the newer SHA1 file naming convention. This provides seamless support for both existing and new iServer public key certificates as well as continued support for trusted commercial CA certificates.

New in iTivity 5.4.02 Build 1 (Oct 7, 2014)

  • The iTivity iAgents, iManager and iServer now use the OpenSSL release 1.0.0a from 01 Jun 2010. This update corrects a problem where the encryption certificate was invalid after new installations of the iAgents.

New in iTivity 5.4.01 (Oct 7, 2014)

  • iTivity iManager 5.4.01:
  • iTivity release 5.4.01 of the iManager corrects a problem with the FTP toolbar button when accessing iAgents released before 5.1.00. The FTP toolbar button now works with iAgents of all versions.
  • The 5.4.01 iManager for Windows now shows the iAgent name in the VNC viewer window titlebar. This improves ease of use when viewing multiple iAgents simultaneously.
  • The 5.4.01 iManager now displays the iAgent support domain, if any, in the left-hand panel list. In addition, the iManager now has the ability to Sort and Filter by support domain. The support domain is displayed in angle brackets, for example, "". In contrast, the iAgent username, if any, is displayed in square brackets, for example, "[root]" or "[SYSTEM]".
  • The iManager release 5.4.01 includes the ability to configure the items displayed on the iAgent line in the left-hand pane. You can enable or disable the display of 4 components: iAgent computer name, iAgent username, iAgent support domain, iAgent IP address.=
  • iTivity release 5.4.01 includes support for outbound connections across HTTP proxy servers. This version supports both HTTP and SOCKS based proxy servers. The new settings begin with "hProxy" and are very similar to the settings for SOCKS proxy server, which begin with "socks". On Windows systems, the [Advanced] connection settings dialog now allows the user to configure both HTTP and SOCKS proxy settings.
  • iTivity release 5.4.01 corrects a problem when trying to save the NCN file on a Windows computer. The iManager no longer incorrectly reports that it is unable to write to the target directory.
  • iTivity release 5.4.01 corrects a problem when attempting to exit the iManager with the [X] button or through [File]--[Exit]. The iManager now exits reliably using either method.
  • iTivity release 5.4.01 corrects the issue where the iManager would forget the last username for authenticating with the iServer. The iManager now uses the correct last iServer username rather than the last iAgent username.
  • A rare problem affecting the color handling when connecting from a Windows based iManager to a RISC based Unix server, including AIX and Solaris, was corrected. Colors are now handled properly in these cross-platform situations.
  • iTivity iAgent 5.4.01:
  • iTivity iAgent 5.4.01 includes an update to improve detection and reporting of local services on Solaris and Windows platforms. Remote or forwarded services were already reported consistently.
  • iTivity release 5.4.01 includes support for outbound connections across HTTP proxy servers. This version supports both HTTP and SOCKS based proxy servers. The new settings begin with "hProxy" and are very similar to the settings for SOCKS proxy server, which begin with "socks". On Windows systems, the [Advanced] connection settings dialog now allows the user to configure both HTTP and SOCKS proxy settings.
  • iTivity 5.4.01 Full, iServer, iAgent Installers:
  • iTivity upgrade installs overwrite the previous version LicenseData.txt file. The result is the License Keys are overwritten and lost. The LicenseData.txt files property in the installer has been set to never overwrite a pre-existing LicenseData.txt during an upgrade.

New in iTivity 5.4.00 (Oct 7, 2014)

  • iTivity iManager 5.4.00:
  • Starting in the 5.4.00 release the iTivity iManager includes support for secure shell or SSH login access to Linux, AIX, HP-UX and Solaris systems. SSH login access requires iTivity version 5.4.00 on the iManager and on the iAgent.
  • The 5.4.00 iManager also includes the ability to specify an external secure shell (SSH) client. This feature allows the iManager user to specify a specific third party SSH client for specialized environments, rather than using the implementation included with the iManager.
  • Third party SSH client configuration:
  • Below is an example of how to configure the iManager to use an external SSH client when accessing iAgent systems with a secure shell service via iTivity's secure connection :
  • Windows Registry Editor Version 5.00
  • HKEY_LOCAL_MACHINE\SOFTWARE\Tridia\iTivity\Mgr]
  • "SSHCanUseExternalTermEmulator"=dword:00000001
  • "SSHExternalEmulatorPath"="\"C:\\Program
  • Files\\teraterm\\ttermpro.exe\" %H:%P"
  • "SSHExternalEmulatorPort"=dword:000068d0
  • "SSHExternalEmulatorStartDelayMilliSecs"=dword:000007d0
  • "SSHExternalEmulatorOneSession"=dword:00000000
  • "SSHExternalEmulatorPersonality"="xterm"
  • "SSHExternalEmulatorStopServerOnConnect"=dword:00000000
  • Variables settings explained:
  • SSHExternalEmulatorPath = Holds the path of the program to call when connecting to an SSH server/service via the iTivity secure tunnel. See program path encoding below for details as to how to encode parameters to the SSH client from the iManager. SSHCanUseExternalTermEmulator = Enables/disables the usage of an external SSH client program.
  • SSHExternalEmulatorPort = Port where the external SSH client program should connect to the iManager so that the SH connection can be forwarded via the iTivity secure tunnel to the iAgent SSH server. By default we use port # 26832. But this can be changed to some other value based on other applications conflicting with this port.
  • SSHExternalEmulatorOneSession = This variable, if set to 1 indicates that the external SSH program can only be run ONCE, as opposed to being able to support multiple instances of itself running on the same machine. SSHExternalEmulatorStopServerOnConnect = When set to 1, this variable indicates that the external SSH client can only be run one time. This setting should be used in conjunction with SSHExternalEmulatorOneSession.
  • SSHExternalEmulatorStartDelayMilliSecs = Defines the number of milli-seconds that one must wait from the start of the secure tunnel being established and when the external program can be run. Typically a value of 2000 works fine an 800Mhz Intel system. If there is a problem where the SSH client cannot connect, the by increasing this value on slow machines, or decreasing it on faster ones, could be the solution.
  • SSHExternalEmulatorPersonality defines the value of TERM to be used when invoking the external SSH client. Refer to the %E parameter below.
  • Program Path Encoding:
  • In order to pass parameters from the iManager to a third party SSH client, the variable "SSHExternalEmulatorPath" is used to call an arbitrary program with multiple parameters passed to the the external program. To call an arbitrary program, just specify the full path to the program in this variable. To specify which parameters are passed, a argument> scheme is used, as discussed below. The command line to invoke the external SSH client has the following format: path> [%arg [%arg [%arg...]]] WHERE %arg can be any one of the following :
  • H substitute with the parameter 'host' ( DNS name ).
  • I substitute with the parameter 'ip', address of host.
  • P substitute with the parameter 'port', of the service to connect to.
  • R substitute with the parameter 'rows', the emulator should display.
  • C substitute with the parameter 'cols', the emulator should display.
  • T substitute with the parameter 'termtype', which stands for
  • TERM variable on the host system.
  • E substitute with the parameter 'emulation', which stands for the personality the emulator should be in.
  • 3- The Java Runtime (JRE) has been upgraded to version 1.6.
  • iTivity iServer 5.4.00:
  • The iTivity iServer 5.4.00 includes better feedback to the iManager user when a connection attempt to the iAgent fails. An error message is sent immediately if the connection forwarding fails at the iServer.
  • iTivity iAgent 5.4.00:
  • The iTivity custom application feature has been enhanced to allow for tunneled connections to other computers on the local network. You can specify the hostname or IP address of the other computer in the "interface" (or Network Interface) setting of the custom application. You can define custom applications on Windows iAgents in the registry.
  • You can use the ability to detect and access services on other hosts to support devices without the iAgent installed, including routers, firewalls, out-of-band management (lights-out management) services.
  • The Unattended iAgent includes improved Windows session tracking that only reports active and available Windows sessions, ie. Terminal Server desktops. This update will prevent many of the various causes of the black screen or blank screen on connection problem. It is still possible to experience a black screen on connection, but only if the RDP session client is minimized but still connected.
  • The iAgent installation includes a small fix to make the Windows service installation more reliable.
  • The Attended iAgent now uses HKLM to find the vnchostname and/or vnchostdesc if the HKCU setting is not present.
  • The iAgents provide better feedback to the iManager user when a service connection attempt at the iAgent fails.
  • iTivity 5.4.00 One-Click HTML Unattended iAgent Installer:
  • Fixed an issue in the Unattended iAgent One-Click HTML Installers. The installer no longer installs the "iTivity Unattended Connector to IAS" service twice. The double service installation may result in the overall failure of the service installation. Timing is also a factor as this
  • issues has been reported by a small number of users.

New in iTivity 5.3.00 Build 2 (Feb 10, 2010)

  • Solved the problem where if the user did not have enough privilege to update the hosts file it would not default to 127.0.0.1 and thus the user might see a blank telnet, rdp session.
  • Solved the problem where if you could not update the hosts file, the iManager would issue the error message only once as opposed to every time one tried to connect to a service.
  • Solved the problem were if one selected 'End Session' on an iServer which had a Unix host that had an active connection, then the iManager would consume 100% of the cpu.
  • Solved the problem where an error message would appear stating a connection to the host was lost after selecitng the end session option.

New in iTivity 5.2.02 (Aug 8, 2009)

  • X11 Remote Desktop Access,
  • Web Application Tunnelling