Host Release Notes Version - PDF Free Download

1. Enhancements Windows Desktop Support The Windows desktop (start menu, task bar, etc.) can now be accessed via GO-Global. To access the Windows desktop from a GO-Global client, append -desktop to the client's command line. When this option is specified, the client displays the remote session and its desktop inside a window on the client computer. To access the Windows desktop from a GO-Global Add-on, append &desktop=true to the URL. To display the desktop within the browser window, also include the embed option in the URL. If the embed option is not specified, the Add-on creates a window outside of the browser and displays the remote session and the desktop in the window (just as the native clients do when the -desktop command line option is used). To disconnect from a session running the Windows desktop, simply close the session's window on the client or, if the session is running embedded within the browser, close the browser tab or browse to another page. To log off from a session running the Windows desktop, simply click the Windows desktop's Log off or Sign out option. Windows Desktop support is disabled by default. To enable the feature, set the value of the AllowDesktop property in the HostProperties.xml file on the host to true. High Resolution Device Support GO-Global 5 lets users change the size of text and other items on their screens by scaling the DPI (Dot Per Inch) of the display. When the GO-Global client is run on Windows, Android or IOS, GO-Global uses the client computer s DPI setting. When the GO-Global client is run on other operating systems, GO-Global uses the DPI setting that is specified for the user under the Control Panel s Display applet on the host. In this configuration, administrators can allow users to modify the DPI setting by publishing the Display applet to users. To publish the Display applet to users: 1. Sign in to the console on the host as an administrator 2. Create a shortcut to the Display applet: a. Click Start Control Panel b. Right-click Display. A shortcut will be added to the Desktop. c. Drag the shortcut to a directory that all users can access (e.g., C:\Users\Public\Desktop). 3. Publish the shortcut to users: a. Run the Cluster Manager and click Applications Add b. Type Display Settings (or some other descriptive name) in the Display Name field c. Enter the path to explorer.exe (e.g., C:\Windows\explorer.exe) in the Executable Path field d. In the Command-Line Options field, type the path to shortcut created in step 2 (e.g., C:\Users\Public\Desktop\Display.lnk). e. Click OK

Themes On Windows 7 and later, GO-Global 5 displays applications using the Theme that is specified on the host. On Windows Server 2008 R2, Themes are not enabled by default in Windows. To enable Themes on Windows Server 2008 R2: 1. Install Desktop Experience (http://technet.microsoft.com/en-us/library/cc742809.aspx) 2. After the host has been rebooted, start the Themes service. 3. Enable Group Policy in the Cluster Manager. 4. Enable Themes for all users via Group Policy: a. Run mmc b. Click File Add/Remove Snap-in c. Select Group Policy Object d. Click Add e. Click Finish f. Click OK g. Navigate to User Configuration\policies\Administrative Templates\Control Panel\Personalization h. Double-click Force a specific visual style file or force Windows Classic i. Click Enabled j. Under Path to Visual Style, type the path: %windir%\resources\themes\aero\aero.msstyles Improved Audio Support On Windows 7 and later, GO-Global 5 supports a virtual audio device that creates a private mixer for every GO-Global session. These components mix the audio played by applications running in the GO-Global session and encode it in Ogg Vorbis format. The host streams the Ogg Vorbis data to the client, and the client plays the audio. On older operating systems, GO-Global 5 plays basic sounds on the client via the feature that was supported in older versions of GO-Global. To enable Improved Audio Support, simply check the Sound option in the Cluster Manager. Client Log Files Earlier versions of the GO-Global client record messages in the host s log file when they are connected to a host, but they output their messages as debug output when they are not connected to a host. This debug output can be captured by a debugger or by an application such as DebugView, but in most cases the information is lost. This makes it difficult to troubleshoot connection problems when the GO-Global client is version 4 or earlier. In order to make it easier to troubleshoot connection issues, the GO-Global 5 client records messages in a log file on the client device when the client is not connected to a host. In addition, after a user signs in to a host, the client synchronizes its log files with the host. Specifically, GO-Global determines if there are any log files on the client from previous sessions with the host that have not already been copied to the host. If there are, GO-Global copies the missing client log files to the host. These changes make it easier for system administrators to determine the cause of connection problems. For example, if a user reports that his or her connection to the host is frequently getting dropped, the system administrator can check the host and client log files to determine the cause. In this scenario, the client log files from the user s previous sessions will generally be available on the host, and the administrator will not need to manually retrieve the client log files from the client device. Generally, administrators will only need to retrieve log files from a user s computer in cases where the user is unable to connect to a host at all.

The names of client log files include the name of the user, the address of the host, and the date and time that the client was started. Client log files are stored in the user s %APPDATA%\GraphOn\Logs directory (on Windows clients) and in the \Program Files\GraphOn\GO-Global\Log\Clients directory on the host. When a log file is copied from the client to the host, the client s copy of the log file is moved to the %APPDATA%\GraphOn\Logs\Old directory on the client computer. Log files are stored on the client for the number of days specified in the HKEY_CURRENT_USER\Software\GraphOn\GO- Global\Client\LogFileAgeLimit registry value. The default is 10 days. As in earlier versions of GO-Global, messages that the client outputs while it is connected to a host are recorded in the host s (APS_...) log file. The GO-Global client only records messages in the client log file when the client is not connected to a host. Automatic Reconnect When a GO-Global client is disconnected from a host, it automatically tries to reconnect to the host 5 times. If the client is unable to reconnect, it then notifies the user that the connection has been broken and asks the user if he or she wants to reconnect. To specify the number of times the client tries to reconnect to the host, add the following command line argument or URL parameter: Command line option: -autoreconnect [x] URL parameter: &autoreconnect=x where x is the number of times to reconnect. To disable this feature, set x to zero. Connection Monitoring GO-Global 5 monitors the latency and the input and output rates of connections to the host. When a new client connects to a host, the host tests the client s connection and records initial values for each of the metrics in the host s log file. Thereafter, the host monitors the connection for quality changes. If the quality of any of the metrics changes while the session is running, the host records the change in its log file. The frequency of quality checks and the quality threshold values are specified in the HostProperties.xml file. Non-admin Installers for Windows Client and Browser Add-ons GO-Global 5 includes new installers for the Windows Client and the Windows GO-Global Add-ons that can be run by users who do not have administrator rights. The new installers are located in the Web\Clients directory on the host. They are: gg-client.desktop.exe: Installs the single-user client and adds shortcuts to the client to the user s Start Menu gg-client.chrome.exe: Installs the single-user client and opens Google Chrome to the extension s installation page gg-client.firefox.exe:: Installs the single-user client and the Firefox Add-on gg-client.ie.exe: Installs the single-user client and the Internet Explorer Add-on These installers install one copy of the single-user client s binary files in the %LOCALAPPDATA%\GraphOn\GO-Global\Client directory, and the single-user client appears once under Programs and Features as GO-Global Client Single User. Mulitple users can install the single-user client on a computer, but GraphOn recommends using the standard GO-Global Client installer (gg-client.windows.exe) when the client will be run from more than one user account.

The GO-Global Add-on installation and upgrade processes have changed in GO-Global 5. If a user browses to a page containing a GO-Global Add-on and the Add-on is not installed, the user is directed to: 1. Download the Add-on s installer (downloads the single-user installer for the user s browser) 2. Run the installer 3. Restart the browser When a user browses to a page containing the GO-Global Add-on and a newer version of the Add-on is available on the host, an Upgrade link is displayed that allows the user to upgrade the Add-on. The procedure for upgrading an Add-on is the same as the procedure for installing an Add-on. When users select the link to install the Windows Client, they are given two options: 1. Install for all users (administrators only) 2. Install only for current user The first option installs the Windows Client and all of the GO-Global Add-ons for all users. The second option installs the Windows Client and all of the GO-Global Add-ons for the current user only. Note: The logon.html page has been modified in GO-Global 5. Administrators can still modify default options by modifying the logon.html page, but the method for doing this has changed. To change a default value: 1. Open the logon.html file in a text editor 2. Uncomment the controlargs.set line corresponding to the parameter you want to change 3. Change the default value of the parameter 4. Save the file Notes: 1. GO-Global 4 clients can connect to GO-Global 5 hosts, but the above enhancements are only supported with GO- Global 5 clients. 2. Windows Vista and Windows Server 2008 are not supported host platforms in Version 5. Windows Server 2008 R2 is a supported host platform in Version 5.

2. Known Issues Description Display issues may occur if a user specifies the desktop option when reconnecting to a session that was started without the desktop option, and vice versa. To work around this issue, always reconnect to sessions using the value of the desktop option that was specified when the session was started. The GO-Global Update Client service and the \GraphOn\GO-Global\Client directory are not removed when the Windows client is uninstalled. The first time a user signs in to a host, GO-Global runs explorer.exe in the background to initialize the user s user profile. As a result, the session takes longer to start. This feature can be disabled by setting the value of the InitializeProfileWithExplorer property in the HostProperties.xml file to 0. Client audio does not work in the first session that is started after the version 5.0 host is installed. On Windows 8.1 and Windows Server 2012 R2 the desktop is painted black if the client does not support 32-bit color. When the desktop URL parameter is set to true in Apple Safari, the embed parameter must also be set to true. Artifacts from an application s title bar may appear in the lower-left corner of the client s desktop when an application is minimized and restored. An SSL security warning dialog may be displayed when users connect from a Mac to a host that is configured to use SSL. When the GO-Global host is Windows 8.1 or Windows Server 2012 R2 and is run on VMWare, the mouse does not work in the console session while the Windows desktop is running in a GO-Global session. The GO-Global installer intermittently hangs on Windows 8 and Windows Server 2012 because of an issue with the Microsoft tiworker.exe process. To work around this issue, terminate the tiworker.exe process and restart the GO-Global installer. Menus in the IME bar may be difficult to close. If you encounter this issue, move the mouse back and forth over the menu, and it will close. The GO-Global Client cannot be run in Apple Safari on Windows. Encrypted PDF documents cannot be printed via the Universal Printer Driver. Applications such as Office 2013 that use DirectX will not run in GO-Global sessions on Windows Server 2008 R2 or Windows 7 when Windows Update KB 2670838 is installed. To work around this issue, uninstall KB 2670838. Background: Windows Update KB 2670838 replaces the user-mode DirectX runtime with a version that requires display drivers to support DirectX. The GO-Global display driver does not support DirectX in versions 4.8.1 and earlier. Beginning in version 4.8.2, the GO-Global display driver supports DirectX, but only on Windows 8, Windows 8.1, Windows Server 2012 and Windows Server 2012 R2. The GO-Global driver only supports DirectX on these versions of Windows because it relies on a Windows component that is not available in earlier versions of Windows. The IME window may not display in the usual location. When explorer.exe is run in the background of the session, the session will take longer to start. Windows Server 2012 Essentials is not supported. Sessions will not start on this operating system.

Avast Free Home Antivirus is not supported on 64-bit hosts. Bitdefender Antivirus is not supported on 32-bit hosts. Radmin is not supported. On Mac OS X 10.8 Mountain Lion, users need to disable Gatekeeper in order to install the native Mac OS X Client. The automatic client update feature is not supported if the client modifies the client installer to install the client in a location other than the default location. To work around this issue, install the client in the default client location. When Integrated Windows Authentication is enabled, client printers may be listed twice in Notepad and WordPad. The 64-bit version of Mozilla Firefox is not supported on the Linux Client. Install the 32-bit version of Firefox before installing the Linux Client. Users must disable the firewall from Total Defense Anti-Virus before a client is able to connect to a GO-Global host. Users must add the GO-Global Application Publishing service (aps.exe) to the exclusion list for Vipre Antivirus before a client is able to connect to a GO-Global host. When using multi-monitors and connecting to hosts running Windows 8, 8.1 or Windows Server 2012 and 2012 R2, display issues might occur when moving windows across the monitors and off-screen. The client is unable to connect to a GO-Global host running Windows 8 on port 491 when McAfee Anti-Virus is installed. To resolve this, open a GO-Global port in the McAfee Firewall. For more information, see http://service.mcafee.com/faqdocument.aspx?id=ts100887. Help files may fail to open when Integrated Windows Authentication is used without server-side password caching. Object Linking and Embedding (OLE) operations may fail when Integrated Windows Authentication is used without serverside password caching. The gateway s Open Desktop feature does not work on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2. Cannot add printers in the Printers applet when the Universal Printer Driver option is not enabled and there is no printer driver installed on the host that has the exact same name as the client printer driver. To work around this issue either a) add an entry to the MappedPrinterDrivers.xml file that maps the name of the driver on the client to the name of a driver on the server (as described in Chapter 6 of the Host Administrator Guide) or b) enable the Universal Printer Driver option in the Cluster Manager. Type 4 printer drivers are not supported, and the Add option in the Printers applet will fail when a Type 4 printer driver is specified. To work around this issue, specify a compatible Type 3 printer driver. Some keys may generate incorrect characters when using Brazilian keyboards with the Linux client when the client IME option is enabled. When the web server on the host is IIS, and IIS is configured to only serve documents with file extensions that are registered MIME types, files with the following extensions may not download:.deb,.crx,.dmg,.xpi. For example, Firefox may display the following error message when a user attempts to install the plug-in: Not a valid install package. To resolve this issue, define a MIME type for the needed extensions as described in Microsoft Knowledge Base article 326965 (http://support.microsoft.com/kb/326965). For the Chrome Extension, specify the MIME type as application/gg-chrome. 2015 GraphOn Corporation. All rights reserved. GraphOn and GO-Global are trademarks or registered trademarks of GraphOn Corp. Other trademarks belong to their respective owners.