****************************************************************************
Software Release:      Secomea GateManager 4.4 - public release

Release Date:          2011-05-26 - v2

****************************************************************************

	(c) Copyright 2011, Secomea A/S.  All rights reserved.


****************************************************************************
Scope and production information
****************************************************************************

  This is Secomea GateManager release 4.4.11212.208

  This release note describes changes since Release 4.3.10352.208

  Please refer to the older release notes for further information.

  Products covered:
  ---------------------------------------------------
    GateManager 8250 (Software version)

  Version and Build numbers:
  -------------------------------------------------------
    GateManager Server software version 4.4.11212.208
    GateManager Console installer version 4.4.11212.208
    GateManager Proxy software version 4.4.11212


****************************************************************************
1. Highlights of this release
****************************************************************************

 - Important Bugfix release

****************************************************************************
2. New features and improvements.
****************************************************************************

GateManager
----------------------------------

 - New Plugin for SiteManager Appliances including alerts for 8xI/O (#4448)


****************************************************************************
3. Bug Fixes.
****************************************************************************

GateManager
----------------------------------

 - Appliance cannot be deleted (#4400, #3977)
   Due to an error in the cleaning process, the appliance log would over
   time become very large and could create a situation that prevented an
   appliance to be deleted. Additionally a large log would also slow
   down the server. The appliance log is now limited to 100.000 records 
   similar to the Audit log. 
   Should you still encounter problems deleting specific appliances you have
   two options - 1) wait a few more days, the appliance log table will 
   overtime clean the erroneous records - 2) increase the GateManager memory.
   If the server has more than 2G ram, you can savely configure the 
   GateManager to 2000 MByte.

 - Double allocation issue (#4533, #4067):
   This issue can occur if the server host is abruptly stopped as result of
   a power failure, or by issuing the linux commands "halt" or "reboot".
   Now when the Linux system is halted the GateManager service is 
   automatically stopped.
   If you already experience the issue you can fix the problem using the 
   GateManager repair option:
     service gatemanager repair
   The symptom for the issue is that you cannot establish a GateManager
   Console connection within the first minutes after the server has been 
   started. Alternatively you can search the following file for 
   the phrase "double allocation":
   tail -f /usr/local/gatemanager/jboss/server/default/log/gmserver.log

 - Scheduled backup is not executed (#3641)
   If a database is restored from a backup it could happen that the schedule
   definitions were not recovered properly. Now a full recovery process is 
   performed every time the GateManager server is started and ensures that
   the scheduler is updated correctly.

 - Max GateManager Consoles limit exceeded (#4230)
   Reuse oldest, non-active GateManager Console connection if max_gm_consoles
   limit is reached.   

 - LinkManager old license support (#4230)
   Allow LinkManager using old-style certificates to connect to GateManager
   if auto_applove_lm is set. (don't require auto_approve_relays to be set).
   

GateManager Console
----------------------------------

NOTE: These fixes were introduced in GateManager Console Version 4.3b build
      10507. If you already have this version, it is not necessary to upgrade
      to version 11212.

 - Fixes a DNS issue (#4343):
   In some cases GM console login will be very slow or fail due to broken DNS
   resolution in the java runtime engine (JRE). This could occur when switching
   between different network cards for GateManager access (typically on a laptop
   where both wired and Wireless connections were used). The JRE could in
   some cases, where the inactive network adapter was located first in the
   adapter list, still attempt to use that adapter for DNS resolution. In best
   case the login would be very slow (up to 1-2 minutes).

 - Fixes issue with handling appliances with no mac-address (#4232):
   If the function "New Appliance" was interrupted by a Cancel, it was possible
   to create an appliance with no serial number/mac-address.


****************************************************************************
4. Upgrade information.
****************************************************************************

All Software Products
-----------------------------------

 - Refer to the Upgrade documentation found on the Secomea web site (requires
   your partner login)

 - Please notice that GateManager Console must be upgraded by running the
   corresponding Installer program using an administrator account.

   
****************************************************************************
5. Known issues or limitations
****************************************************************************

 - GateManager Console (Java application) may shutdown unexpectedly.
   
   This problem happens to several Java-based applications due to a
   conflict with a Samsung LCD monitor utility called Multiscreen.
   This utility supposedly hooks into the Windows display drivers in a
   non-complient way which can cause Java applications to fail when
   trying to update the display.  If you encounter this type of error
   and you use the Samsung Multiscreen utility, disabling or exiting the
   Multiscreen utility (via its Tray icon) will resolve the issue.

 - Due to new restrictions on secure web-site certificate authentication,
   Internet Explorer 7, Firefox 3, or newer may prevent you from accessing
   https based services via the LinkManager's Go To Appliance functionality
   in the non-activated state (Domain view).

   This is because the Go To Appliance function uses a different IP address
   than the actual IP address of the remote device, so the browser suspects
   that the target device's certificate (typically self-signed) may be a
   forgery.

   There is no easy way to get around this problem, so you will have to
   follow the somewhat tedious procedure of your browser to bypass the
   warnings and connect to the device anyway.

   Note: You should not store the certificate permanently in Firefox 3.


****************************************************************************
END
****************************************************************************