iTivity 5.3.00 Build 2

The iTivity solution delivers secure remote access to host servers, workstations and desktop computers. Your remote access connections are protected by a TLS-SSL encrypted tunnel from your desktop to the destination system. Since both your desktop and the destination computer may be located across the Internet from the central iServer, remote access is truly global.

iTivity uses standard enterprise authentication and authentication like active directory domains and PAM to verify access permission. iTivity provides PCI-DSS, HIPAA and SOX compliant remote desktop support. Each connection is automatically logged to the central iServer. All access is authenticated at the central iServer. To better meet your needs, iTivity remote access comes in two flavors: on demand and always on.

The live support iAgent provides on demand access for remote user technical support and training. The admin iAgent gives you always on remote access to critical applications, databases and servers. iTivity enables secure application access, remote desktop access, remote control, remote monitoring and secure file transfer. These features are implemented via port forwarding for standard remote administration and support tools such as RDP, FTP, VNC and telnet.

The iTivity manager automatically configures, launches and monitors remote access sessions to systems on your iServer. With iTivity, there is no need to manually configure SSH nor open dangerous pinhole ports on the firewall. Few technologies improve productivity and customer satisfaction like remote support solutions. None go as far as iTivity to help you support and manage complex environments.

With iTivity you host the server so you control the data. Out-of-the-box integration with NTLM, LDAP and PAM authentication servers makes access hassle-free and worry-free.

Give iTivity a try to see what it's really capable of!

Limitations:

· 30 days trial

What's New in This Release: [ read full changelog ]

· 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.