These modification notes contain information relating to a maintenance release of Netop Remote Control 9.51 (Windows only) including the ActiveX Guest (nguestx.ocx). Where applicable, the affected support case reference numbers are displayed in brackets below. This is a maintenance release and is free for customers who already have a valid 9.5 license. To read about what’s new in version 9.5, please refer to the release notes at www.netop.com

Connection order - improvements have been made to the way that Netop WebConnect handles communication with the Netop Remote Control modules resulting in much better performance.

WebConnect can now be configured to work with the TCP protocol and HTTP as a fallback. Typically, connections via TCP are faster but not always available through firewalls whereas HTTP with its encapsulation is slower but much more firewall friendly. This means that faster performance can be achieved where outbound TCP connections are possible but connections will automatically revert to HTTP should TCP be blocked for any reason. Furthermore, our standard HTTP communication has also been greatly improved to offer much quicker performance. To take advantage of these performance improvements, you should update your Netop Remote Control modules to this release. The Netop WebConnect solution dictates which connection method to use so no further configuration changes are required on the Netop Remote Control modules providing you already have a valid WebConnect account. For more information about the Netop WebConnect 1.7 release, please refer to the Netop OnDemand/Netop WebConnect release notes on www.netop.com.

Introduction

WebConnect

RELEASE NOTES

MODIFICATION NOTES

Shipping date:

Product/version/build: Remote Control 9.51 (2010215)

ActiveX Guest 9.51 (2010215)

18th August 2010

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 2 of 18

ISA support – a number of changes have been implemented to improve support for Netop Remote Control when running within a Microsoft ISA Server environment.

These enhancements involve changes to the core communication layer within Netop and resolve many connectivity issues related to ISA setups including automatic proxy configuration and NTLM authentication.

Blank screen - an issue has been identified with the Blank Screen function which is available to the Guest during a remote control session. On the majority of Windows operating systems, this feature does not function correctly however there is no indication to the Guest that the Host display has not been ‘blanked’ successfully.

Until this issue is fully resolved and to improve usability, the Blank Screen function will be disabled on the Guest when connected to an incompatible Host operating system. This includes all Windows 64-bit editions, Server 2008, Windows 7 and Vista.

When a Guest remote controlled a Host running Windows Server 2003 (32-bit), the screen transfer mode would default to Bitmap Mode. The screen transfer mode will now default to the faster Command Mode method when selected in the Guest connection properties (49788, 50689)

Running scripts using the Netop scripting ActiveX control (Nfmscrpt.ocx) would fail with a ’OCX Init A’ error message followed by a ’Load dtlnt’ error (47283, 49537, 49603)

When a Guest was configured to use Smartcard authentication via the Security Server, the Confirm Access dialog would not appear on the Host even though the applicable Role Assignment was defined on the Security Server. This fix requires an update to the Host only (51322)

Web update did not function correctly when the Guest or Host was running on Windows 7. Superfluous dialogs have also been removed to help automate the update process (50003)

After sending the Ctrl+Alt+Del command to a Host running a 64-bit Windows operating system, the command would be executed on the Host but the Guest would be presented with a black screen (50684)

Known issues fixed

Communication

Miscellaneous

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 3 of 18

In some situations, the Host display would appear corrupted on the Guest when connected to a Windows Host machine. This would occur when using bitmap mode and limiting the number of display colors to 256 colors

When using the Security Server with Smart Card authentication, the Guest was unable to connect to the Host and received a ’Smart Card logon failed’ error message (49693)

When using the PDF Annotator application during a remote control session, the pencil tool would not function correctly resulting in no line being drawn correctly on the Host machine (50387)

In some cases, the Guest would receive a 0x230000 error when retrieving an inventory scan from the Host. The error was due to insufficient privileges on the Host machine (48257)

Error message in German was truncated when the Guest did not have permission to use the Demonstrate feature (40864)

If the function to ’Prevent further connections to Host’ (GuardHostOnConnect) was enabled on the ActiveX Guest, a subsequent remote control session would not be possible however it would cause the first ActiveX Guest session to be disconnected from the Host (50493)

In certain situations, the ActiveX Guest was unable to view the Host machine when initiating a remote control session. This was due to a timing issue on the Host but would appear as a blank or empty screen within the ActiveX Guest application (50406)

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 4 of 18

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 5 of 18

These modification notes contain information relating to a maintenance release of Netop Remote Control 9.5 (Windows only) including the ActiveX Guest (nguestx.ocx). The affected support case reference numbers are displayed in brackets below. To read about what’s new in version 9.5, please refer to the release notes at www.netop.com

Public/Private Key - in order to help improve a trusted connection between the Host and Security Server, a new PKI (Public Key Infrastructure) implementation has been introduced. This Public/Private key exchange uses RSA 2048-bit keys and replaces the Group ID/Name functionality from previous releases.

Security Server configuration

In the Security Manager, define a Public Key that should be used by your Hosts. The default Public Key is shown and can be used, however, for production environments, it is recommended to generate a new Public Key before deploying your Hosts. Whenever the Public Key is changed, your Hosts will also need to be reconfigured and restarted:

Product/version/build:

MODIFICATION NOTES

Shipping date:

Remote Control 9.5 (2010134)

25th May 2010

ActiveX Guest 9.5 (2010134)

Introduction

Security

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 6 of 18

In order to accommodate the new Public/Private Key functionality, a new database table called DWPKI has been introduced. Whenever you install a new Security Server, you should always run the Security Manager first before running the Security Server as the Security Manager will update the necessary table structure for the Security Server database.

Host configuration When the Host is configured to use the Netop Security Server, the corresponding Public Key from the Security Manager should be defined. The Public Key should be copied to the Host exactly as it is shown in the Security Manager:

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 7 of 18

How it works The new Public/Private key exchange is designed to improve the security between the Host and Security Server and the new implementation works as follows:

1. When the Guest attempts to connect to a Host, the Host generates a random key 2. Host encrypts the random key using it’s known Public Key from the Security Server 3. Host sends the encrypted string to the Security Server 4. Security Server decrypts the string using it’s Private Key and obtains the initial random key

generated by the Host 5. Security Server encrypts the obtained random key using it’s Private Key 6. Security Server sends the encrypted string to the Host 7. Host decrypts the string using it’s Public Key and verifies that the resulting key is identical with

the initial generated random key 8. If verified successfully, the Guest will be authenticated and permitted to control the Host

depending on the access rights defined in the Security Server database

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 8 of 18

Backwards compatibility Although the Public Key replaces the Group ID/Name functionality, it is still possible to authenticate older Hosts that use Security Server authentication. The Group ID/Name can still be defined within the Security Manager; however the following entry must be present in the NETOP.INI file on your Security Servers in order to authenticate your existing Hosts that use the Group ID string: [NSS] AllowOlderHost=TRUE

NOTE: Earlier releases of the Security Server will not be backwards compatible when using Hosts from this release. It is therefore recommended to update all your Security Servers first and then update your Hosts. Using the above INI file entry provides backwards compatibility for your existing Hosts and therefore easing the rollout process.

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 9 of 18

Keep alive – similar to the Windows Guest, it is possible to send a data packet to the Host at pre-defined intervals based on the following entry in the NETOP.INI file: [NGuestX] SendKeepAlive=x (where x = number of seconds, 0=disable keep alive)

When using Remote Management to make changes to the Registry, the entered values appeared as invalid characters. This has now been resolved and only requires a change to the Guest in order to function correctly (8279)

Running a Netop Script from a Guest using Windows 7, Vista or 2008 would fail immediately and cause the Guest to stop responding regardless of the actions included in the script (47786, 45499)

The Command Progress Status window did not close automatically after successful completion. Enabling this option now takes effect when used with the relevant Guest functions including Execute Commands, Inventory, Run Programs, etc (46951)

When remote controlling a Host with a screen resolution of 1366 x 768, part of the right-hand section of the screen was not transferred to the Guest (49417)

The ’Lock machine after disconnect’ feature would not always work when enabled on a Host machine running Windows XP (49395)

Sending a Restart command to a Host machine running Windows XP would take a long time (2-3 mins) to execute when the machine was in a locked state (49414)

The %sessionname% variable did not work when trying to identify the Host module within a Citrix or Terminal Services environment (49641)

Selecting the Schedule option within the Web Update settings would cause the Guest or Host to stop responding

Known issues fixed

ActiveX Guest

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 10 of 18

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 11 of 18

These modification notes contain information relating to a maintenance release of Netop Remote Control 9.5 (Windows only) including the ActiveX Guest (nguestx.ocx). The affected support case reference numbers are displayed in brackets below. To read about what’s new in version 9.5, please refer to the release notes at www.netop.com

The communication channel used at handshake between the Host and Security Server is now protected using 256-AES encryption. This new capability will be available automatically when you update your Hosts and Security Servers to this build. If you are not ready to update all of your Hosts or still want to support older legacy Hosts at the same time, you should update your Security Servers and add the following to the NETOP.INI file:

[NSS] AllowOlderHost=TRUE

This setting will allow your older Hosts to authenticate with the new Security Server but will not use the encrypted handshake.

Using Hosts from this build onwards will not be backwards compatible with previous versions or builds of the Security Server

The ’Request Video’ privilege is now available when defining Security Roles for the Guest via the Security Manager

Product/version/build:

Security

MODIFICATION NOTES

Shipping date:

Remote Control 9.5 (2010084)

7th April 2010

ActiveX Guest 9.5 (2010084)

Introduction

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 12 of 18

RDP support – the ActiveX Guest was unable to function correctly when launched from an RDP session due to restrictions within the licensing system

Closed User Group – the ActiveX Guest now supports connections to Netop modules where special closed user group serial numbers are in use. The ActiveX Guest will require a new license key in order to support this function

Connection attempts – if the initial connection fails, the ActiveX Guest can be configured to retry the connection based on the following entry in the NETOP.INI file: [NGuestX] ConnectAttempts=x (where x = number of retries)

Kiosk mode – this feature allows the Guest to automatically reconnect to a Host when certain events occur including ConnectionLost, EndedByHost and in some cases, OnLoginFailure. The following entry should be added to the NETOP.INI file:

[NGuestX] KioskMode=1

When using the Security Server with Smartcard and Directory Services authentication, the Guest credentials were not authenticated correctly. This problem was due to two nested database queries when used with Microsoft SQL drivers (6579)

The Security Server would sometimes stop responding when trying to authenticate a Guest if the identification string (username, directory services name, etc) was too long

Known issues fixed

ActiveX Guest

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 13 of 18

Within a Windows Domain environment, where the FQDN (Fully Qualified Domain Name) and NetBIOS names were different, the Security Server was unable to correctly query a workstation and the authentication process would fail. The Security Manager will now use the NetBIOS name for the Windows Domain by default. Any existing entries in the Security Manager using an FQDN that differs from the NetBIOS name should be deleted and replaced with new entries Note: Guests, Hosts and Security Servers/Security Managers should be updated for this change to take effect (47932, 8600)

The Hebrew version of the Guest did not display any items when accessing the menu options from the user interface (46945)

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 14 of 18

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 15 of 18

These modification notes contain information relating to a maintenance release of Netop Remote Control 9.5 (Windows only). The affected support case reference numbers are displayed in brackets below. To read about what’s new in version 9.5, please refer to the release notes at www.netop.com

The Send/Receive Clipboard feature did not function correctly and would sometimes display a message saying ‘No supported formats on the clipboard’ (5021, 7991, 8156, 40852, 46950, 47917)

When the Guest or Host was running on a machine within an ISA Proxy environment, the Netop modules would fail with a ’ObjectWindows Exception’ error when using the WebConnect communication profile (47245)

During a remote control session, the Host module would stop responding when a command prompt window was closed. This problem occurred on x64 machines running Windows Server 2003 and 2008 (47151, 42527)

Introduction

RELEASE NOTES

MODIFICATION NOTES

Shipping date:

Product/version/build: Remote Control 9.5 (2010028)

16th February 2010

Known issues fixed

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 16 of 18

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 17 of 18

These modification notes contain information relating to a maintenance release of Netop Remote Control 9.5 (Windows only). The affected support case reference numbers are displayed in brackets below. To read about what’s new in version 9.5, please refer to the release notes at www.netop.com

Remote Desktop compatibility – when remote controlling a Host machine that had previously been connected to using Remote Desktop (RDP), the Netop Guest would display a black screen. This was caused when using the /admin (connect-to-console) switch, which moved the console session to a new session that Netop was unable to access.

The Netop Guest will now be able to remote control the machine following an RDP console session. However, upon logging onto the Host machine, the Guest will be disconnected as the Host reloads itself into the correct console session and the Guest will be notified that it needs to reconnect.

Introduction

RELEASE NOTES

MODIFICATION NOTES

Shipping date:

Product/version/build: Remote Control 9.5 (2009348)

14th December 2009

Connectivity

Netop™ is a trademark of Netop Business Solutions A/S. All other products mentioned in this document are trademarks of their respective manufacturers. Netop Business Solutions A/S denies any and all responsibility for damages caused directly or indirectly as a result of using this document. The content of this document is subject to change without notice. August 2010 Page 18 of 18

When the Guest logged off the Host machine during a remote control session, the connection would be lost and the Host application would fail. The problem occurred when the Host was running on Windows 2000, XP or Server 2003 (46896, 46873, 47049, 47016, 47001, 46967, 46932)

If the Host or Guest was configured to log to a Netop Security Server, the application failed to connect because the Security Server name had been truncated with the first two characters missing. The same behaviour occurred with the log file name when logging locally from the Host or the Guest (46902)

Some translation errors in the German edition of Netop Remote Control Guest have been resolved. Incorrect references to the Netop Student were displayed in the Clipboard function and Phonebook context menu (46988)

Some translation errors in the French edition have been resolved. Incorrect references to the Name Server were displayed in the Directory Services tab in Program Options on the Guest and all Host related modules (46745, 46753, 46774)

Known issues fixed