----------------------------------------- GO-Global for Windows Release Notes Version 3.1.1 August 4, 2006 ----------------------------------------- (c) GraphOn Corporation 1999-2006. All rights reserved. ___________________________________________________________________ CONTENTS Version 3.1.1.3513 Release Notes 1. Issues fixed since 3.1.0.3504 Version 3.1.1.3504 Release Notes 1. Issues fixed since 3.1.0.3503 Version 3.1.1.3503 Release Notes 1. Issues fixed since 3.1.0.3502 Version 3.1.1.3502 Release Notes 1. Issues fixed since 3.1.0.3501 Version 3.1.1.3501 Release Notes 1. Issues fixed since 3.1.0.3500 Version 3.1.1.3500 Release Notes 1. Issues fixed since 3.1.0.3499 Version 3.1.1.3499 Release Notes 1. Issues fixed since 3.1.0.3498 Version 3.1.1.3498 Release Notes 1. Known Issues 2. Issues fixed since 3.1.0.3494 Version 3.1.1.3494 Release Notes 1. Known Issues 2. New Features 2.1 SSL Security 2.2 Linux Client Enhancements 2.3 Session and Idle Time Limits 2.4 Drive Letter Mapping 2.5 Password Caching 2.6 Client Printer Naming Customization 3. Redundant License Servers 4. Issues Fixed in 3.1.1.3494 3.1.1.3513 (8/4/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3504 ------------------------------------------------------------------- Cases 5485, 5624, 5549, 5858, 5921, 10755, and 10921: Server stability problems (BSOD). Cases 5906, 5926, 5943, 5566, and 10724: Clients disconnecting with GO-Global 3.1.1.3498. A change that was made in 3.1.1 was backed out, which, in some environments, intermittently caused users to be disconnected from their sessions. This change makes version 3.1.1 work the same way it did in version 3.1.0 with the TCP Transport selected. Another problem that may have been causing disconnects was that the connection verifier (pinger) did not calculate the start time of the verification period correctly. As a result, connections that were open for a long time could eventually be closed erroneously. The solution was to set the start time of the verification interval to the current time. Additional diagnostic (level 4) output was added to record when the pinger closes a connection. Case 5560: In Quickbooks, 'Save As PDF' brings up the printer window instead of saving to a PDF. Quickbooks can use different versions of the Amyuni PDF Converter printer driver. We added the new name to the list of supported pdf drivers. Currently, these are: Adobe PDF Converter, Amyuni Document Converter and Amyuni PDF Converter. Case 10890: APS on the GGW server is pinned to 99%. This problem is caused by our 3rd party license manager,flexLM, probably because one of their functions is not thread safe. Cases 10869 and 6011: Network printers on GO-Global for Windows server not visible to clients if Client Printers feature is turned ON. This is regression from version 3.1.0. Case 5867: Display issues with FileMaker Pro versions 7 and 8. Case 4448: If Apply Group Policy is enabled in the Cluster Manager, and the Group Policy is configured to activate a screensaver during the windows logon, the server crashes (bluescreens) after logging in. Case 10891, 5513, and 5068: Applications packaged with the Armadillo software protection system do not run through GO-Global. Applications that are packaged with anti-debugging and anti-monitoring protection will generally not run through GO-Global. The fix that is included in this patch allows applications packaged with this system to run. Bug 4734: SSL: The user is NOT alerted that the certificate was issued by a provider that they have not chosen to trust. This fix requires a client change, but it is optional if SSL transport is not being used. Bug 4724: Can't connect to GO-Global server using SSL after installing Internet Explorer 7 Beta 2. This fix requires a file change in the native Windows and ActiveX clients. Not required if Internet Explorer 7 and/or SSL transport are not being used. 3.1.1.3504 (5/25/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3503 ------------------------------------------------------------------- Case 5813: Added support for keyboard mapping files to the Solaris Client. Case 5924: Client-side network printer configuration problem that causes all printers to be visible in Notepad's print dialog. We changed the naming scheme for client network printers when they are configured on the server. We no longer use the \\server\printer style, they are now named 'printer - server'. This change will help prevent the server from confusing proxy printers from network printers, which is likely the cause of this bug. 3.1.1.3503 (5/22/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3502 ------------------------------------------------------------------- Case 5825: The print dialog window takes over 30 seconds to come up. We added an optimization to the printer enumeration and filtering functions in the print component. Rather than opening each printer to find its port, we use the existing data (if it is available) collected previously. This may improve performance when opening a print dialog, especially when some server-based printers are not configured correctly and are susceptible to time-outs. 3.1.1.3502 (5/18/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3501 ------------------------------------------------------------------- Case 5826: Added some diagnostic output to the APS log to help troubleshoot COM port redirection issues. 3.1.1.3501 (5/12/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3500 ------------------------------------------------------------------- Case 5536: Discrepency in the number of concurrent sessions vs. the number of licenses being checked out. We changed the flexLM TCP timeout from 2 hours to 10 minutes. What this means is that when using a license server, if the GO-Global server crashes, gets powered off, or loses network connectivity, any licenses used by sessions on that server will be released after 10 minutes. If the GO-Global server comes back online and the sessions are still running, the manual heartbeat will re-checkout the licenses within two minutes of being connected. 3.1.1.3500 (5/12/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3498 ------------------------------------------------------------------- Case 5063: GO-Global causing a system crash. Case 5808: Taskbar item not created when application is launched. Case 5691: Client printer names are being created as INVALID. The ClientIdentifiers.ini file was getting out of sync in some scenarios when cache client printers was enabled. 3.1.1.3499 (4/28/2006) ------------------------------------------------------------------- 1. Issues fixed since 3.1.1.3498 ------------------------------------------------------------------- Case 5540: Custom application hangs when using the embedded windows client. Case 5650: Provide support for REMOTE_USER CGI variable. 3.1.1.3498 (4/21/2006) ------------------------------------------------------------------- 1. Known Issues ------------------------------------------------------------------- When a user connects through Remote Desktop Connection using the /console switch to a Windows Server 2003, an error is presented in the Remote Desktop Connection Console session on the client as follows: "Error connecting to existing session for wilson (Id 0). The operation completed successfully." When a user connects through Remote Desktop Connection using the /console switch to a Windows XP Server, no error is presented in the Remote Desktop Connection console session on the client and the session closes. Remote Desktop Connection is not supported in GO-Global for Windows Version 3.1.1.3498 on Windows XP Servers. No error message is presented to the user when a version 3.1.0 GO-Global client connects to a version 3.1.1 GO-Global Server. ------------------------------------------------------------------- 2. Issues fixed since 3.1.1.3494 ------------------------------------------------------------------- Case 3596: HS Win application crashes upon launch on W2k. Case 5001: Error dialogue appears natively but it doesn't appear in GGW. The fix for this bug was to implement hard error message boxes. Case 5318: Objects in "GoGlobalTest2.exe" are not always displayed. Case 5012: Access Image is displayed with the wrong size when the client and server resolution are different. Case 5693: Client session freezes when using Session Reconnect. Case 5588: In Kingdee custom app, printing does not work. The application has a module named prints.dll so our prints.dll was never getting loaded. We renamed our module to ggprints.dll. Case 5633: Idle timeout is not working. Case 5386: Test program works differently in 3.1.1.3434 than it does in 3.1.0.3292. Case 5566: Session times out. Case 5590: Experiencing hangs and disconnects. Case 4918: Logon script using 'description' field does not work. Case 4481: Want GG to support converting a document to a PDF file using Acrobat 7. NOTE: With Adobe Acrobat 7 installed on a Windows Server 2003 or a Windows XP GO-Global server, you can save PDF files to any folder on the client. When the GO-Global server is Windows 2000, you can only save to the root of folder of a client-side drive. 3.1.1.3494 (3/1/2006) ------------------------------------------------------------------- 1. Known Issues ------------------------------------------------------------------- When a GO-Global version 3.1.0 client attempts to connect to a version 3.1.1 server, no error message will appear on the client but the Connection dialog will re-appear. When connecting from the Windows CE Client or the Mac X11 Client to a server that has SSL enabled and the "Use TCP as fallback" option disabled, the proper error message indicating that the client does not support SSL does not appear. Instead, the following message appears on the client: "Failed to connect to . Please verify that the server address is correct." Using the console switch with Remote Desktop or a Terminal Services client to connect to a GO-Global Server is not supported (e.g., %SystemRoot%\System32\mstsc.exe /console). Remote Desktop is not supported on Windows XP when it is being used as a GO-Global Server. The user is prompted to disable it during installation. Using Remote Desktop or a Terminal Services client to connect to a GO-Global Server that is installed in a VMWare virtual machine is not supported. With the Linux client, COM port redirection may not work in applications that open a port for send and receive. If the Macrovision License Manager process LMGRD is started without a valid license file on the server, an error dialog will appear when you log on interactively to the server. Adding a valid license file to the Programs directory will remedy the problem. GO-Global does not support Linux distributions that use the window manager Metacity 2.10 and later, e.g., Ubuntu 5.x. On certain Linux platforms such as CentOS and Debian3, the GO-Global Connection dialog may appear behind the Linux console when the Linux Client is run from the console. Password caching is not supported on Windows XP and Windows Server 2003 servers that are members of Windows NT domains. ------------------------------------------------------------------- 2. New Features ------------------------------------------------------------------- 2.1 SSL Security ---------------- GO-Global provides support for Secure Socket Layer (SSL) as a method for communication between GO-Global clients and servers. When SSL transport mode is selected through the Cluster Manager, the following encryption algorithms are available: 56-bit DES, 128-bit RC4, 168-bit 3DES, and 256-bit AES. A strong encryption license is required to use the last three algorithms. To obtain this license, contact your GO-Global sales representative. SSL certificates are required to secure communication between GO-Global clients and servers. You can obtain a certificate from a trusted Certificate Authority (CA), or you can create your own certificate authority and then sign your server certificates from this authority. 2.2 Linux Client Enhancements ----------------------------- The following enhancements have been added to the Linux Client: - Support for foreign keyboards. (Keyboard translation files for French, French Belgian, Portugese (Brazil ABNT2), German, Polish, and Japanese, are included.) - Support for the mouse wheel. - Support for COM ports. 2.3 Session and Idle Time Limits -------------------------------- Through the Cluster Manager, administrators can specify time limits for the number of minutes of client idle time and the number of minutes that sessions are allowed to run on a server. Administrators can also specify whether the user is either disconnected or logged off when the idle limit is reached, and when to display warning messages to users about to be disconnected or logged off. Administrators can also designate a grace period during the logoff period to allow users to save files and close applications, etc. 2.4 Drive Letter Mapping ------------------------ When applications are run in GO-Global sessions with the client Drives feature enabled, GO-Global must ensure there is a one-to- one mapping between drive letters and the drives of the client and server computers. If a drive on the client and a drive on the server are assigned the same drive letter, GO-Global must assign a new drive letter to one of the drives. Client drives can be remapped by either listing them sequentially starting at a given drive letter or incrementing their drive letters by a specified value. 2.5 Password Caching -------------------- When a user logs on to a GO-Global Server with a username and password (either with the Logon dialog, HTML parameters, or command- line arguments), that user is added to the server's INTERACTIVE group. Alternatively, a user that logs on to a GO-Global Server using standard pass-through authentication is added to the server's NETWORK group. By default, members of the INTERACTIVE group have greater access to the server's resources than members of the NETWORK group. As a result, a user that logs on via standard pass-through authentication may encounter "access denied" errors under a number of conditions. To avoid these errors, administrators can enable the Cache passwords option on the server. When this option is enabled, users are prompted for their passwords the first time they connect to a server and their password is encrypted and saved within their profile on the server. Thereafter, when users connect to the server, they are automatically logged on to the server using their cached password and are granted the same rights to the server's resources as when they log on by typing their user name and password into the Logon dialog. 2.6 Client Printer Naming Customization --------------------------------------- GO-Global installs a printer on the server for each printer that is configured on the client machine. These printers are called proxy printers and are the printers that are seen by users when printing via GO-Global. Since multiple users connect to a GO-Global Server, these printers must be filtered so that users see only their own printers. This requires that each printer be assigned a unique identifier. Through the Registry, administrators can specify the format of these proxy printer names and include information such as the user’s name, the client computer’s IP address, and the client machine name. ------------------------------------------------------------------- 3. Redundant License Servers ------------------------------------------------------------------- GO-Global supports redundancy via a set of three redundant license servers. With three-server redundancy, if any two of the three license servers are up and running, the system is functional and serves its total complement of licenses. If you wish to use redundant servers, select stable systems as server machines. Do not pick systems that are frequently rebooted or shut down. Redundant license server machines are any supported server machines. These servers must have excellent communications on a reliable network and need to be located in the same subnet. Avoid configuring redundant servers with slow communications or dial-up links. Three server redundancy is designed to provide hardware failover protection only and does not provide load-balancing. This is because with three-server redundancy, only one of the three servers is "master" and capable of issuing licenses. Since all clients must contact "master" all clients must have reliable networking to a single machine. For example: SERVER concord 000476BA8EE9 27000 SERVER newman 00115B73383E 27000 SERVER ottawa 000476BA8F74 27000 DAEMON blm INCREMENT session blm 3.1 31-dec-2006 5 99E86D1B9A64 HOSTID=ANY INCREMENT any_app blm 3.1 31-dec-2006 uncounted D1D222D051C4 \ HOSTID=ANY ------------------------------------------------------------------- 4. Issues Fixed in 3.1.1.3494 ------------------------------------------------------------------- Case 5494: Windows CE Client should have compression enabled by default. Cases 5060 and 5435: Client name is missing from the printer name when using the Windows Client on Windows 98. Case 5435: No Client Printers are listed in the File-Print dialog (Windows 95 Japanese). Case 5459: Some keys are not mapped correctly with the Linux Client using a Japanese Keyboard. Case 4441: Request for Environment Variables support for the Global Logon script in the Cluster Manager. Case 4441: User-Specific logon script is not running, even with Pass-Through Authentication disabled. Case 4352: Logon script not executing when Pass-Through Authentication is enabled. Case 2767: A redundant license server configuration doesn't work correctly. Cases 4269 and 4424: Some applications don't launch on Windows Server 2003 with Service Pack 1 when DEP (Data Execution Prevention) is enabled on the server. Case 4717: The wrong drive name is displayed when hiding server drive D: and client drive D:. Case 4927: Blue screen after installing KB896424 on a server already running the latest compatibility updates. Case 5059: Client drives are always remapped starting at Z no matter how it is configured. Case 4677: The Appplication Publishing Service becomes unresponsive on the relay server. Case 4852: Intermittently, users cannot log on because they cannot authenticate. Case 3977: The cursor is not displayed in application dialog boxes. Case 4680: Memory leaks on the Solaris Client cause the client to shut down. Case 4718: Unable to open the Printer Property dialog in Microsoft Word if the printer name contains Kanji characters. Case 4723: Password Caching does not work when using Roaming Profiles on the client. Case 4361: Starting the Application Publishing Sercice removes existing SPNs and delegation does not work. Case 4673: The server deadlocks when a user connects when kernel debugging is enabled on the server. Case 4795: The caret does not behave as expected in scrollable text field. Case 4963: ACT 2000 and Microsoft Office applications crash. Case 4732: Session freezes when trying to maximize the application using the Linux taskbar pull-down menu. Cases 4781 and 4678: Server stability problems. Case 3960: Request for support of the mouse wheel with the Linux Client. Case 3976: Request for German keyboard support for the Linux Client. Case 4387: Dependent application servers hang and only respond when pinged. Case 4669: Performance issue when typing text. Case 3226: Foreign (French or German) keyboard mapping problems on the Linux Client. Case 3982: Request for COM support on Linux Client. Case 4456: Request for support of the Polish keyboard with the Linux Client. Case 4520: When specifying a password on the command-line with the Linux Client, the password may be visible to other users running process reporting tools such as ps. Case 4761: Problems when minimizing/restoring applications using the Linux Taskbar. Case 4912: Alerts crash Outlook 2000 Help|About crashes all Office 2000 applications on Windows Server 2003. Case 5098: Unable to print in custom application. Case 4693: Dependent server stability problem caused by memory leak. Case 4952: Stability problem caused by memory corruption. Most likely to occur when network drives are mapped in logon scripts. Case 4669: CPU performance enhancement when typing text. Case 4327: Deadlock between EXCEL.EXE and KHS41V01.exe. Case 4552: The server blue screens when a user connects when SpySweeper is installed on the server. Case 4553: System crash when after exiting a Java application (intermittent). Case 4433: Universal Print Driver does not print OCR-B font. Bug 4445: The Update Client (UC.EXE) is not updating the VBMs on multi-processor machines. Bug 4467: print.ini is not populated if the interactive user doesn't have modify/write permission. NOTE: The print.ini file is now stored in the user's profile (e.g., C:\Documents and Settings\username\Local Settings\Application Data). If that folder does not exist (which is the case with Windows 95 and Windows 98), print.ini is created in the user's temp folder or whatever %temp% is in the environment variable. Bug 4458: Session and Processes are not enumerated properly in the Cluster Manager on the dependent servers. Bug 4303: When running the Linux Client in loose windows mode, maximized windows do not fit the entire work area when using the mouse pull-down menu from the Linux taskbar. Bug 4305: On the Linux Client, gray background from the menus in Office 2003 applications remain painted after scrolling through the menus of an empty document. Bug 4344: When running the Linux Client with GNOME Desktop-METACITY 2.6, the client freezes when attempting to move the GO-Global window to the bottom of the screen. Bug 4311: Request for support for Japanese keyboards on the Linux Client. Bug 4428: Menu offset issue in the Program Window when running the Linux Client with GNOME Desktop. Bug 4353: With GO-Global Servers running Japanese Windows 2000, the Program Window disappears after being minimized by users with non-administrator accounts when using any client that does not have a taskbar, i.e., embedded clients. Bug 4365: If the account password is blank, the Logon dialog prompts the user for a password every time. Bug 4436: Windows Update 896424 incompatible on Windows 2000 with SP4, Windows Server 2003, and Windows XP SP2. Bug 4486: Windows Update 908523 incompatible on Windows 2000 with SP4. Bug 4341: Windows Update 835732 incompatible on Windows 2000 with SP4. Bug 4517: Windows Update 912919 is incompatible with GO-Global on Windows XP SP2, Windows 2000 SP4, and Windows Server 2003 SP1.