Version 3.4.2

Client Build 13337

Virtual Appliance Build 13337

Enterprise Manager Build 13337

November 2009

---

The information in this Release Note is current as of 17th November 2009 for the Replify Reptor Accelerator, version 3.4.2. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

1. Cases Resolved

   • Case 2506 Addressed an issue whereby editing an Application Server’s IP address incorrectly results in the application server being deleted.

   • Case 2512 Fixed rendering issues with Internet Explorer 7 and Internet Explorer 8 in ‘Compatibility’ mode.

   • Case 2514 Corrected the incorrect behaviour of the secondary Delete button on the CA certificate management page.

   • Case 2530 Certain values were not being exported through SNMP, this issue has been resolved.

   • Case 2534 The default initial cache size slider behaviour has been rectified - previously the slider values were inconsistent.

   • Case 2538 The EM can now scale to several thousand filters being processed per client connect event.

   • Case 2542 Fixed bug where cache clear from the GUI would fail in some cases.

2. Known Issues

   • Case 1083 When connecting via an MS ISA VPN, the Reptor Client can take up to two minutes to notice, and to try and establish connections to the REM and known VAs. (It’s basically instantaneous with other VPN clients.)

   • Case 1119 REM can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios.

   • Case 1395 The Reptor Client will not work “out-of-the-box” on machines that have Check Point SecureClient installed. Please contact us for further information on getting the Reptor Client to work in conjunction with SecureClient.

   • Case 1572 When changing the operational mode of the VA from DC to BOB the message License Expired may appear. On page reload it should disappear.

   • Case 2154 Clearing an X^DR cache via the Virtual Appliance GUI requires a page refresh before the GUI updates and removes the cache from the table.

   • Case 2437 Any changes to a VA’s hostname are not reflected in any peered VA’s GUI until the VA is restarted/rebooted

---

Version 3.4.1

Client Build 13244

Virtual Appliance Build 13238

Enterprise Manager Build 13238

October 2009

---

The information in this Release Note is current as of 14th October 2009 for the Replify Reptor Accelerator, version 3.4.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

Upgrade Notices

Please read before upgrading

• After upgrading a VA from 3.3.x to 3.4.1 it is very important to reboot the VA before attempting to use it. A reboot can be issued from the web GUI via the ‘System’ menu

• Do not attempt to upgrade a 3.3.x Reptor Client install using the 3.4.1 MSI installer. Uninstall the current 3.3.x Reptor Client before using the 3.4.1 MSI installer

1. New Features

   • 
     HTTP header manipulation - The HTTP optimization will now strip out ‘Accept-Encoding: gzip, deflate’ value in order to provide superior performance from X^DR. This feature is enabled by default but can be disabled if required.

   • 
     Reptor Client statistics update - The Reptor Client Tray Utility can now display bytes sent and received using Terabyte units.

   • 
     MSI Installer - In order to ease Enterprise deployment the Reptor Client software is now available as an MSI installer. An Administrative Template file (.adm) is also available to provide configurability.

   • 
     Improved certificate import functionality - When importing a PKCS#12/PFX certificate file the user can now indicate that they also want any contained CA certificates imported.

   • 
     VA to VA Peering - VA’s now support bidirectional peering. Two peered VAs will exchange Application Server details and make these remote Application Servers available to each local network. They also support traffic connections initiated from either side of the network.

   • 
     VA Client Location Awareness - VAs now support basic Reptor Client location awareness. Each VA has an associated location; a defined set of IP addresses. Connecting Reptor Clients determined to be within this IP range are deemed to be on the “local” network and optimization is adjusted accordingly. Please refer to the Client Location Awareness briefing for more detail.

   • 
     Connection Logging - The VA will now keep a log of all completed connections.

   • 
     New Transparency setting for Application Servers - Added Application Servers now support enabling network transparency. Application data being sent to a transparent Application Server has it’s originating address details changed to be that of the originating client machine. Some software solutions rely on this.

   • 
     Browser Tabs now use VA Hostname - VA host names are now displayed in the web browser title bar to simplify handling multiple browser windows across multiple VAs.

   • 
     Adjustable units in the Live Traffic Charts - Provided an option on the Live Traffic Chart to adjust the units to display a variety of traffic rates (kbps, Mbps, etc)

   • 
     Application Server Aliases - Application Server aliases are used within the ‘Optimized Sessions’ page now when possible in place of IP addresses

2. Cases Resolved

   • Case 619 The ‘Network Setup’ page now supports specifying your DNS servers.

   • Case 1461 It is no longer possible to rename or define a new tag in the REM with titles of “all” or “not tagged”.

   • Case 1863 A Diagnostics Report can now be generated from the generic Internal Error (500) page. Previously the user needed to access the Diagnostics page.

   • Case 2130 The ‘Generate New Certificate’ page allowed the same certificate alias to be used again. This has been corrected.

   • Case 2133 Corrected an issue whereby an excluded Application Server address could not be deleted if there were no included Application Servers.

   • Case 2161 Resolved rendering issues with Internet Explorer 8

   • Case 2164 Clarification on the GUI label for ‘Configuration->Settings’, whereby the setting is applied to those VAs which have not had a policy explicitly set. That will include both new and existing VA’s that don’t have an explicit policy set. If you explicitly set a policy (on the ‘Configuration -> Reptor Virtual Appliances’ page) then that will win.

   • Case 2171 VAs can now be completely deleted from the REM, even if the Management Connection is set to ‘Off’.

   • Case 2172 Within the REM viewing the Client Session information for a deleted Client caused a crash. This has been corrected.

   • Case 2189 The REM now trims whitespace from GUI input boxes before submitting user configuration as this caused a few validation issues previously.

   • Case 2219 The User Guide’s Appendix A now describes all the TCP ports we use!

   • Case 2230 Corrected an issue with the upgrade notification on the VA & REM when a major version was available

   • Case 2235 VA ‘Configuration’ menu has been amended to include a ‘Peered Virtual Appliances’ option, which replaces the separate ‘Data Center’ and ‘Branch Office’ configuration options. An ‘Optimizations’ menu entry replaces the previously separate ‘Branch Office Optimizations’ and ‘Optimization Modules’ entries.

   • Case 2241 Several VA SNMP configuration improvements when adding SNMP Traps in the GUI have been made.

   • Case 2250 Within the REM all ‘Virtual Appliance Reports’, in the Appliance System Information panel, contained incorrect Connected Since and Duration values. These have been corrected.

   • Case 2252 Addressed an issue whereby illegal characters in the process name would cause Connection Spy to crash.

   • Case 2267 Under some circumstances Reptor Client licenses were being withheld when a Reptor Client connection was torn down. These cases are now being handled correctly.

   • Case 2278 SSL Certificates with expiry dates after 2050 are now supported.

   • Case 2282 VA header statistics now show the number of Peered VAs in realtime.

   • Case 2312 VA Info tab displays system resource statistics with graphs akin to the REM.

   • Case 2323 Naming conventions for X^DR cache names have been improved to avail of hostnames

   • Case 2332 Various improvements to the REM GUI including… allowing multiple item selections.

   • Case 2336 ‘Data Center’ and ‘Branch Office’ terminology on the VA has been replaced with ‘Peered Virtual Appliances’ configuration. This change is reflected in the REM GUI.

   • Case 2344 Provided the ability to persist user defined iptables rules.

   • Case 2347 Addressed an issue whereby Application Server rules are not being sent to the Client.

   • Case 2353 Improved the Enable SNMP form behaviour in the VA. Previously changing the radio button selection would have cleared the form details. The form details are now retained.

   • Case 2356 Addressed an issue when SNMP is enabled without any configuration.

   • Case 2419 When there are Clients waiting for a connection, the ‘Client Report’ page on the REM now legibly displays them.

   • Case 2426 Addressed some Internet Explorer 6 rendering issues for the VA. While IE6 is still not a recommended browser for the Reptor VA GUI, users who have no other option can use IE6 with the VA.

   • Case 2448 SSL Certificates can be imported without generating javascript warnings.

   • Case 2450 Improvements to SNMP configuration - Multiple SNMP Notification Targets can now be selected for deletion.

   • Case 2493 Corrected an issue whereby when a licensed VA expired the generated dossier contained stale data.

   • Case 2495 Fixed an issue whereby the user is allowed to create a Client Matching Rule without an alias

   • Case 2496 Addressed an issue whereby deleting a filter in the REM could potentially cause a GUI crash.

3. Known Issues

   • Case 1083
     When connecting via an MS ISA VPN, the Reptor Client can take up to two minutes to notice, and to try and establish connections to the REM and known VAs. (It’s basically instantaneous with other VPN clients.)

   • Case 1119
     REM can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios

   • Case 1395
     The Reptor Client will not work “out-of-the-box” on machines that have Check Point SecureClient installed. Please contact us for further information on getting the Reptor Client to work in conjunction with SecureClient.

   • Case 1572
     When changing the operational mode of the VA from DC to BOB the message License Expired may appear. On page reload it should disappear.

   • Case 2154
     Clearing an X^DR cache via the Virtual Appliance GUI requires a page refresh before the GUI updates and removes the cache from the table.

   • Case 2437
     Any changes to a VA’s hostname are not reflected in any peered VA’s GUI until the VA is restarted/rebooted

---

Version 3.3.1

Client Build 11606

Virtual Appliance Build 11606

Enterprise Manager Build 11606

June 2009

---

The information in this Release Note is current as of 8th June 2009 for the Replify Reptor Accelerator, version 3.3.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

Upgrade Notices

Please read before upgrading

• Upgrading to 3.3.1 will cause all existing X^DR caches to be
  deleted.

• A 3.3.1 VA can only provide the benefits of X^DR when used
  in conjunction with a 3.3.1 Reptor Client or another 3.3.1 VA. If a 3.2.2 Reptor
  Client connects to a 3.3.1 VA X^DR will be disabled until the client
  is upgraded to 3.3.1. The same will apply to a 3.3.2 VA.

• Please be aware that the number of license seats associated with the
  VA and REM has changed. Please see below for further details.

1. New Features

   • 
     Highlight expired SSL certificates - The SSL certificate management screen has been enhanced so that expired SSL Certificates are now highlighted and certificates can now be ordered correctly based upon expiry date.

   • 
     Restrict REM Overview Report for VA’s and Application Servers to Top 10 - If you have lots of VAs, then the REM landing page used to get a little crowded. Now it only summarises information. It’s just a summary page, after all. It has links to detailed information.

   • 
     IP ranges permitted within REM client matching rules - The client matching rules on the REM can now contain IP ranges (e.g. 192.168.1.100-192.168.1.200) in addition to individual IP addresses and subnets.

   • 
     Client Download Configuration - An administrator can now configure some aspects of the client downloads available from the REM and VA. The options are:
     (1) the Reptor Client Tray Utility can be configured to start at login
     (2) the Reptor Client Tray Utility can be configured to enable the automatic web updates

   • 
     REM displays Reptor Client statistics grouped by tag - The REM gathers and will display statistics and graphs for each tag you specify. (Reptor Clients can have multiple tags.) Coupled with the ability to automatically tag Clients, this lets you build arbitrary, powerful reports.

   • 
     Autotag Reptor Clients via the REM - The REM now lets you specify rules to automatically apply tags to Reptor Clients based on their machine name or IP address.

   • 
     X^DR throughput enhancement - Minor X^DR disk-layer performance enhancements.

   • 
     Provide Reptor Client limitation on a single VA - A VA now has a limit on the number of Reptor Clients it will allow to connect simultaneously. The default is 100, but this can be changed in the configuration file /replify/proxy/rprx.app through the “max_connected_clients” configuration variable.

   • 
     New ‘Optimized Sessions’ page - This page allows you to view and kill all currently optimized connections through the VA. It also provides a historical tab covering previous connections.

   • 
     Control the default VA provisioning behaviour within the REM - Added a new settings page within the REM to specify the default provisioning behaviour of new BOB & DC VA’s

   • 
     DC/BOB to use 10 licence seats - All VA’s now consume ten licence seats. (Previously a DC VA consumed one, and a BOB consumed seven.) A consequence of this is that you SHOULD NOT UPGRADE to 3.3 without contacting support@replify.com, if you are at the limit of your licensing.

   • 
     Reptor Client installer silent with /silent=yes flag - If you run the Reptor Client installer executable with the /silent flag, it installs totally silently. It doesn’t even warn you that it’s going to interrupt networking.

   • 
     REM to use 20 license seats - A REM now consumes twenty client licences. (If you are at the limit of your licensing, DO NOT UPGRADE without contacting support@replify.com.)

   • 
     New WAN Offload statistic added to the REM & VA - The WAN Offload statistic lets you see the amount and percentage of traffic removed from the WAN by using Replify’s optimizations.

   • 
     New ‘Timezone’ page within the REM & VA - Added a page in the GUI on REM and VAs to set the timezone. (The default timezone on all shipped virtual appliances is Europe, London.)

2. Cases Resolved

   • Case 1315 The REM error report now includes all the necessary log files.

   • Case 1528 Harmonised the two “X factor” numbers on the REM landing page. Previously they measured different things, so they were usually different. This irritated us. We fixed it.

   • Case 1645 CIFS compressed folders would very occasionally exhibit delayed write failures. Not any more.

   • Case 1778 The Client Downloads page on the website now contains more information on configuring personal firewalls to interoperate with the Reptor Client.

   • Case 1784 Corrected an issue whereby a brute-force stop (power off!!) of the REM would display Client connection states incorrectly upon restart.

   • Case 1823 A BOB Backup & Restore file now also includes the paired DC VA’s.

   • Case 1876 The REM now includes an option to delete old VAs from its database. You can optionally delete the accumulated stats for this VA.

   • Case 1886 Occasional disparities could arise between the stats recorded on a BOB and the stats recorded on its corresponding DC VA. They now display the same information.

   • Case 1892 Although the Reptor Tray Utility doesn’t need to be in the list of applications for the Windows firewall (it doesn’t receive connections from outside), other firewalls (McAfee Total Security, in this instance) won’t let applications not in the windows list make outgoing connections. The Reptor Tray Utility needs to be able to make tcp connections, so we’ve added it in to the firewall list.

   • Case 1893 Provide the ability to delete X^DR cache for a given user via a VA’s GUI.

   • Case 1947 Addressed an internal issue regarding writer service restarts after an unexpected event occurs

   • Case 1954 Updated the ‘add-new-disks’ command to function correctly within more recent VMWare Workstation versions

   • Case 1964 Provided a new console command on the VA ‘replify-ctl clear_logs’ which will clear the local log files.

   • Case 1965 Provided a new console command on the REM ‘replify-ctl clear_logs’ which will clear the local log files.

   • Case 1966 Addressed an X^DR cache clear GUI issue when clearing an individual cache

   • Case 1968 Removed the initial default BOB X^DR cache size

   • Case 1971 Addressed an X^DR timeout issue

   • Case 1972 When changing the operational mode from DC to BOB any Reptor Client X^DR caches will be deleted

   • Case 1976 Added a ‘Time Slice’ dropdown option to the Virtual Appliance Reports page on the REM

   • Case 1977 ICMP Redirects have been disabled by default on the VA

   • Case 1981 Fixed minor mark-up issue in BOB GUI when BOB not connected to any DC Reptor Appliances. (”X^DR Disk Size is 0 bytes” overwrote next line.)

   • Case 1989 Adjusted the position of the some of the VA GUI error messages

   • Case 1997 Adjusted the position of the ‘Upgrade Available’ popup message within the VA & REM GUI

   • Case 2007 Fixed an issue whereby the write_service queue did not clean up properly upon reaching capacity

   • Case 2013 Fixed an edge case within the CIFS optimization which could have resulted in premature file closure

   • Case 2028 Fixed an edge case which could have caused an X^DR cache queue to blow after a substantial amount of traffic has passed

   • Case 2046 The VA now comes with tcpdump and ftp installed by default

   • Case 2073 Addressed a statistical totalling error within the Application Server Report on the REM

   • Case 2074 Fixed a GUI redirection issue within the VA & REM

   • Case 2077 If you connect a BOB to a WCCP router via only one physical or virtual ethernet interface, then the BOB has to disconnect from WCCP when it can no longer optimize traffic. It does this now. (The alternative was that some traffic can end up caught in an infinite loop between the BOB and the router in certain configurations.)

   • Case 2105 Changed the name of a BOB as it would appear on the DC VA from ‘replify-reptor\\appliance’ to a unique, more easily identifiable name.

   • Case 2119 When an Application Server was deleted the associated certificate mapping, if any, was not being deleted. This has been corrected.

   • Case 2121 Optimized sessions originating from PBR (Policy Based Routing) or WCCP are now displayed properly on a BOB

   • Case 2142 Improved the responsiveness of VA Provisioning when using tags on the REM

   • Case 2147 Restoring a BOB backup on a DC VA did not restore the operational mode to BOB following the reboot. It does now!

3. Known Issues

   • Case 1083
     When connecting via an MS ISA VPN, the Reptor Client can take up to two minutes to notice, and to try and establish connections to the REM and known VAs. (It’s basically instantaneous with other VPN clients.)

   • Case 1119
     REM can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios

   • Case 1395
     The Reptor Client will not work “out-of-the-box” on machines that have Check Point SecureClient installed. Please contact us for further information on getting the Reptor Client to work in conjunction with SecureClient.

   • Case 1572
     When changing the operational mode of the VA from DC to BOB the message License Expired may appear. On page reload it should disappear.

   • Case 2154
     Clearing an X^DR cache via the Virtual Appliance GUI requires a page refresh before the GUI updates and removes the cache from the table.

---

Version 3.2.2

Client Build 10297

Virtual Appliance Build 10297

March 2009

---

The information in this Release Note is current as of 11th March 2009 for the Replify REPTOR Accelerator, version 3.2.2. There is no Reptor Enterprise Manager release with this hotfix. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify REPTOR Accelerator product.

1. New Features

   • 
     Application Server/Subnet Exclusions - The Application Servers page on the Reptor Virtual Appliance now provides the ability to exclude application servers/subnets from optimization. This can be useful if you wish to accelerate a subnet with the exception of a few IP addresses.

   • 
     32bit Image Upgrade - The 32bit Reptor Virtual Appliance images now avail of 2GB of disk space by default

2. Cases Resolved

   • Case 1832 Addressed an issue whereby a Reptor Virtual Appliance could open multiple management connections to the Reptor Enterprise Manager

   • Case 1843 Adjusted the logging levels on the Reptor Virtual Appliance to be less verbose by default

   • Case 1845 Applied further performance tweaks to the Reptor Virtual Appliance

   • Case 1846 Adjusted the maximum permitted size of a Client X^DR cache to 2.7GB

   • Case 1847 Addressed an internal socket timeout issue

   • Case 1848 Modified the Reptor Virtual Appliance to use a more generic Debian location for updates

   • Case 1853 Addressed an issue which prevented appropriate failover behaviour in the Reptor Virtual Appliance

   • Case 1854 Improved the performance of the ‘cache clear’ functionality.

3. Known Issues

   • Case 1083
     Reptor Client can take a few minutes to make a connection to a Reptor Virtual Appliance via an ISA-VPN

   • Case 1119
     Reptor Enterprise Manager can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios

   • Case 1395
     The Reptor Client will not work “out-of-the-box” on machines that have Check Point SecureClient installed. Please contact us for further information on getting the Reptor Client to work in conjunction with SecureClient.

   • Case 1572
     When changing the operational mode of the VA from DC to BOB the message License Expired may appear. On page reload it should disappear.

   • Case 1818
     If the appliance is started and XDR is disabled due to low disk, then the XDR GUI page will not display correctly.

---

Version 3.2.1

Client Build 9843

Virtual Appliance Build 9843

Enterprise Manager Build 9843

February 2009

---

The information in this Release Note is current as of 17th February 2009 for the Replify Reptor Accelerator, version 3.2.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

1. New Features

   • 
     VA to VA Acceleration (Clientless BOB - DC operation). Provided the ability for the Reptor Virtual Appliance (Branch Office) to optimise traffic to another Virtual Appliance (Data Center) without the need for a Reptor Client.

   • 
     WCCP2 Support Branch Office Reptor can act as a WCCP2 client to provision a capable router of redirecting traffic to it.

   • 
     SSL Interception The Reptor Client and Appliance now transparently support the interception and optimization of secure SSL connections. The previous release required the acceptance of a Replify certificate. The new implementation now supports user provided certificates.

   • 
     SSL Interception The Reptor Appliance now supports optimizing secure SSL services using a certificate management interface. The previous version did not support user provided certificates.

   • 
     HTTPS GUI Access The Reptor Virtual Appliance and Reptor Enterprise Manager now provide https access to their administrative GUIs.

   • CIFS

     • 
       Write Behind Optimization Protocol chatter reduction when performing file uploads/saves.

     • 
       Prefetch Values Extended The range of permitted CIFS prefetch values have been extended up to 200 in the Reptor Client and Reptor Virtual Appliance.

   • 
     Improved lower-latency Windows kernel module reptor.sys

   • 
     Connection Spy The improved Reptor Client Connection Spy utility now presents more information concerning intercepted connections.

   • 
     Tagging The Reptor Enterprise Manager now supports editing and deletion of tags.

   • X^DR

     • 
       Statistic pages now have headline graphs.

     • 
       Provided ability to specify initial X^DR cache size within Reptor Virtual Appliance GUI.

     • 
       Updated stats toggling on the Reptor Virtual Appliance to influence X^DR statistics.

     • 
       Updated the X^DR statistics pages to appropriately reflect changes in unit value.

   • 
     Reptor Enterprise Manager Provided the ability to reset the statistics.

2. Cases Resolved

   • Case 1036
     Reptor Client can now be installed on the same machine as a Reptor Appliance.

   • Case 1252
     Downed VA detection: Resolved an issue whereby a Reptor appliance in branch office mode would sometimes not promptly propagate to connected clients that its peer Reptor (in Data Center mode) had gone down.

   • Case 1575
     Resolved issue were an upgrade available message sits on top of the license expired notice on the VA.

   • Case 1579
     Fixed an issue with application servers containing a subnet of /0

   • Case 1586
     Added the ability to filter historic sessions on the VA when no data has been transferred for a particular Reptor Client.

   • Case 1616
     Provided the ability for the Reptor Virtual Appliance to restart rprx if it encounters difficulties and terminates.

   • Case 1667
     Resolved issue where clients where not appearing as connected on the VA when they were connected.

   • Case 1675
     Issuing the ‘reset-xdr’ command on the Reptor Virtual Appliance no longer reverts all X^DR datastore sizes to their initial default value.

   • Case 1677
     ‘Response Gains’ statistics page on the Reptor Virtual Appliance has been vastly improved and has now become the ‘CIFS Prefetches’ page.

   • Case 1679
     Provided a means of adjusting logging parameters (number of rollovers, max individual size etc) via a configuration file on the Reptor Virtual Appliance.

   • Case 1680
     reset-xdr removed from REM as it is not supported on REM.

   • Case 1694
     Provided the ability for the Reptor Virtual Appliance to generate a self signed certificate.

   • Case 1696
     Activity log on the REM now shows activity in correct order, on restart the order could be reversed.

   • Case 1704
     Updated the Reptor Enterprise Manager logging to the same standard as used in the Reptor Virtual Appliance

   • Case 1705
     Improved caching behaviour with SMB2 messages.

   • Case 1707
     Fixed an issue with the default CIFS prefetch value on the Reptor Virtual Appliance operating in Branch Office mode.

   • Case 1720
     CIFS Response Gains appearing twice on the stats page, this has been resolved.

   • Case 1725
     When a client was disconnected from the REM the delete client button did not work on the REM, this has been fixed.

   • Case 1727
     Fixed a javascript error in the Reptor Virtual Appliance GUI.

   • Case 1729
     Client disconnect time was not being displayed on the Enterprise Manager properly.

   • Case 1731
     GUI issues with IE7 have been fixed.

   • Case 1742
     Updated the Reptor Virtual Appliance’s error pages to provide more detailed information.

   • Case 1747
     Fixed various incorrect VA connection status reporting on the Enterprise Manager GUI.

   • Case 1761
     Prevent the client web update mechanism from being inappropriately cached by downstream caches.

   • Case 1805
     Renamed ‘Volatile’ to ‘Since Reboot’ and updated the default statistical display period to month on the Reptor Enterprise Manager.

   • Case 1814
     Fixed an issue when toggling the order of Reptor Virtual Appliances the associated matching rule would be lost in Internet Explorer.

3. Known Issues

   • Case 1083
     Reptor Client can take a few minutes to make a connection to a Reptor Virtual Appliance via an ISA-VPN.

   • Case 1119
     Reptor Enterprise Manager can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios.

   • Case 1395
     The Reptor Client will not work “out-of-the-box” on machines that have Check Point SecureClient installed. Please contact us for further information on getting the Reptor Client to work in conjunction with SecureClient.

   • Case 1572
     When changing the operational mode of the VA from DC to BOB the message License Expired may appear. On page reload it should disappear.

   • Case 1817
     For large caches the “Clear Cache” GUI button may not work correctly. Use reset-xdr on the command line.

   • Case 1818
     If the appliance is started and X^DR is disabled due to low disk, then the X^DR GUI page will not display correctly.

---

Version 3.1.0

Client Build 8363

Virtual Appliance Build 8363

Enterprise Manager Build 8363

November 2008

---

The information in this Release Note is current as of 14th November 2008 for the Replify Reptor Accelerator, version 3.1.0. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

Replify Release HTTPS Reptor Accelerator

• The Reptor now has HTTPS Acceleration enabled. This enables distributed enterprises to accelerate access to their business critical applications (such as Sharepoint, OWA, CRM and ERP) without the need for VPN access.

1. New Features

   • 
     SSL Interception & Re-encryption has been added. This allows the Reptor Accelerator Suite of optimizations to be applied to https connections. Note: This feature is not enabled by default. It can be enabled in the Reptor Virtual Appliance GUI: ‘Configuration -> Optimization Modules -> SSL Interception’.

   • 
     Reptor Enterprise Manager Disk Capacity Increased the size of the supplied Reptor Enterprise Manager distribution from 1Gb to 2Gb.

   • 
     Tagging Reptor Clients can now be tagged with user-defined labels to perform group operations on Clients.

   • 
     Disk Low Warnings Reptor Virtual Appliance will now display a prominent X^DR warning message if disk space is running low.

   • 
     64bit Support Reptor Enterprise Manager & Reptor Virtual Appliance are now 64 bit distributions.

   • 
     Application Server Hostnames
     Reptor Virtual Appliance will now accept resolvable hostnames when specifying application servers.

   • 
     Connection Spy can now run without administrative privileges.

2. Cases Resolved

   • Case 1019
     Connection Spy now longer incorrectly displays accelerated active FTP connections as escaped.

   • Case 1384
     After a Reptor Virtual Appliance upgrade SNMP configuration was being lost, this has been addressed.

   • Case 1396
     The Reptor Enterprise Manager and Reptor Virtual Appliance maintain the users’ state of ‘logged in’ to their management interfaces across browser restarts.

   • Case 1432
     Contextual Help has now been added to the Reptor Enterprise Manager.

   • Case 1458
     Tray icon could occasionally show the wrong status.

   • Case 1480
     Reptor Client now has notification and warnings disabled by default. Only client errors are reported.

   • Case 1484
     Passwords of more than 8 characters are now accepted in both the Virtual Appliance and Enterprise Manager GUIs.

   • Case 1506
     The Enterprise Manager Licensing page now renders correctly in Mozilla Firefox, Google Chrome and Internet Explorer 7.

   • Case 1515
     When a Virtual Appliance is unlicensed from the Enterprise Manager, it no longer causes a GUI crash. The user is notified of the Virtual Appliance’s non licensed state and warned that it will not optimize traffic.

   • Case 1524
     Application Server Report page displays the volatile statistics for Protocol Optimizations of an Application Server by Virtual Appliance.

   • Case 1531
     Resolved issues when attempting to ‘Delete’ old client history on a Reptor Enterprise Manager Client Report page.

   • Case 1537
     Application server specification on the Reptor Virtual Appliance now permits the use of netmasks.

3. Known Issues

   • Case 1083
     Reptor Client can take a few minutes to make a connection to a Reptor Virtual Appliance via an ISA-VPN.

   • Case 1119
     Reptor Enterprise Manager can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios.

   • Case 1395
     Now intercepts traffic when used in conjunction with Check Point SecureClient VPN client. NOTE: For this update to take effect you must uninstall any previous version of the Reptor Client before installing the new version.

---

Version 3.0.1-HotFix-1

Client Build 7191

Virtual Appliance Build 7208

Enterprise Manager Build 7208

September 2008

---

The information in this Release Note is current as of 19th September 2008 for the Replify Reptor Accelerator, version 3.0.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

1. Cases Resolved

   • Case 947
     Addressed an issue downloading via a browser to a CIFS share on Vista.

   • Case 1118
     add-new-disks previously only worked correctly for SCSI disks (i.e. VMWare), it now should work on all IDE disks (XenServer, Hyper-V etc)

   • Case 1256
     Resolved a memory spike issue when availing of CIFS optimizations.

   • Case 1267
     Addressed an issue were CIFS transfers would fail consistently in Vista.

   • Case 1271
     Updated the upgrade text on the Virtual Appliance and Enterprise Manager GUIs.

   • Case 1281
     Addressed an issue relating to a CIFS transfer where the application requests data which has already been served.

   • Case 1288
     Removed a hard-coded GUID from the Reptor Virtual Appliance.

   • Case 1290
     Modified the upgrade checking mechanism on the Reptor Virtual Appliance and Reptor Enterprise Manager.

   • Case 1291
     Further improvements to the update manager on the Reptor Virtual Appliance and Reptor Enterprise Manager.

   • Case 1297
     If the Reptor Appliance or Reptor Enterprise Manager was firewalled and unable to check for updates this could cause attempts to login to the GUI to sometimes fail.

   • Case 1298
     Intermittent Reptor Client crash after failing to open Connection Spy.

2. Known Issues

   • Case 1315
     Diagnostics -> Generate Error Report does not include some Enterprise Manager logs.

---

Version 3.0

Client Build 7027

Virtual Appliance Build 7027

Enterprise Manager Build 7027

September 2008

---

The information in this Release Note is current as of 4th September 2008 for the Replify Reptor Accelerator, version 3.0. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

Reptor Enterprise Manager Enhancements

• The Reptor Enterprise Manager has had a major makeover in its reporting capabilities. The new Reptor Enterprise Manager Overview page gives a vast amount of system, virtual appliance, protocol and application information.

  • View the Deployment Summary which gives a headline performance rating for the complete system, the number of active virtual appliances, the complete number of application servers configured in the system and the connected clients.

  • Clearly see the performance levels of each Virtual Appliance and the overall performance for each Application Server across all of the virtual appliances.

  • At the bottom of the overview page see a further bar chart representation of the optimization levels for each protocol and a pie chart showing the percentage of the total system traffic of each protocol.

• In the Virtual Appliance report page there is a detailed summary of the system information for each appliance as well as a detailed breakdown of the application server and protocol performance.

Overall Performance Improvements

Overall performance of the Reptor Accelerator Suite has been improved again.

• Further optimizations have been applied to CIFS transfers with support for a greater number of application types.

• X^DR now handles CIFS traffic by stripping the wasteful CIFS boilerplate - massively increasing the cache hit ratio for any repeat traffic and vastly reducing the amount of bytes being sent across the WAN. Hot cache CIFS transfers now jump from a ~16 times improvement to over 100 times improvement.

• HTTP and FTP transfers are also faster following several changes to the core X^DR algorithm.

1. New Features

   • 
     X^DR cache size is now configurable on the Reptor Virtual Appliance, and manageable on a per client basis to facilitate the different capacities of clients machines.

   • 
     Install Log - Reptor Client installs now generate a log file which is included in any error reports.

   • 
     Diagnostic Log now much improved. Captures much more relevant information.

   • 
     X^DR stats now show raw bytes that would have been sent across the WAN without X^DR.

   • 
     Unified passwords The console and GUI passwords are now changed together. If you change one, you will automatically change the other. (You used to have to change them both if you wanted to keep them in sync!)

   • 
     Config Import/Export Added Added new config import/export functionality to the Reptor Virtual Appliance and Reptor Enterprise Manager

   • 
     Network Location Awareness - clients don’t get told about appliances that don’t apply to them, based on where they are (i.e. their IP address)

   • 
     Reptor Client now displays the operational mode of all connected Reptor Virtual Appliances

   • 
     Virtual Appliance GUI is accessible from Reptor Enterprise Manager.

   • 
     FTP optimization can now be enabled/disabled from the Reptor Client GUI.

   • 
     Enabled additional CIFS triggers Updated the CIFS optimization triggers to optimize the Windows command ‘copy’, copy and paste command and network open.

   • 
     CIFS Triggers - Updated the CIFS triggering to cover a ‘right-click copy & paste’ scenario

   • 
     Disk Full Throttle When the disk becomes full X^DR stops using it.

2. Cases Resolved

   • Case 267
     The Reptor Client can now be upgraded from a remote drive which is currently being accelerated.

   • Case 421
     Better integration with Vista LUA

   • Case 519
     Reptor Client upgrades are now completely silent.

   • Case 631
     X^DR stats page should no longer display “Unknown”

   • Case 637
     Reptor Clients now implement a back-off procedure when encountering repeated failed connection attempts to an appliance.

   • Case 779
     It is now possible to create a system snapshot from the error page.

   • Case 795
     Improved the Reptor Virtual Appliance’s resilience when using the “Internal Error” page.

   • Case 826
     Manually requests for an update after declining an automatic update now works correctly

   • Case 851
     Reptor Client configuration changes are now always made using the Reptor Client Service API. This avoids any previous user permissions problems when accessing the configuration files directly.

   • Case 895
     Reduced the time to generate an error report on the Reptor Client.

   • Case 918
     Reptor Client can now configure the managing Reptor Enterprise Manager without requiring a service restart.

   • Case 934
     Reptor Client uninstall now removes all files including it’s installation folder.

   • Case 936
     Client no longer crashes if started before a reboot on an initial install.

   • Case 937
     Client now warns the user when it cannot add itself to the Windows firewall exclusion list.

   • Case 952
     Dramatically improved the handling of the Real-Time Optimization chart in the Reptor Virtual Appliance.

   • Case 959
     Reptor Client no longer inadvertently attempts to redirect UDP packets destined for the defined application servers.

   • Case 963
     Removed ‘proxy uptime’ from the Reptor Enterprise Manager GUI

   • Case 971
     Fixed a Reptor Enterprise Manager GUI issue where the ‘details’ of an unconnected appliance would not display correctly

   • Case 983
     The “configure-network” script now displays the previous network configuration information.

   • Case 989
     Refresh button on the individual cache page now works for all caches.

   • Case 1003
     Using preview button without a name and a rule no longer gives an error on the Reptor Enterprise Manager.

   • Case 1011
     Removed MAPI & FTP from the Reptor Virtual Appliance Real-Time Optimization chart

   • Case 1029
     The Reptor Client installer now ensures that the minimum .NET requirements are met before proceeding with an install.

   • Case 1032
     Addressed an issue on Vista where the Reptor Client displayed an ‘Error Downloading…’ message when attempting to automatically update itself.

   • Case 1035
     Addressed an install issue with the Reptor Client where it requested a restart when none was required

   • Case 1036
     Reptor Client can now be installed on the same machine as a Reptor Appliance.

   • Case 1039
     Addressed a CIFS file transfer issue which manifested itself as a stall, followed by a slow completion stage.

   • Case 1044
     Addressed a formatting issue with the license expiry text on the Reptor Enterprise Manager

   • Case 1047
     Addressed an issue where the Reptor Client would escape all potential optimization connections after an initial user login.

   • Case 1052
     Addressed an issue where repeatedly saving the Reptor Virtual Appliance operational mode would result in disconnects from the Reptor Enterprise Manager.

   • Case 1058
     The Reptor Enterprise Manager will now properly re-license expired Reptor Virtual Appliances currently managed by it.

   • Case 1077
     Diagnostic reports have been improved to help track issues.

   • Case 1120
     Numerous small changes to make the GUI look better at 120dpi on windows. (90dpi, the default, has always been fine.)

   • Case 1154
     Addressed an issue with the Reptor Client Appliance Manager not presenting status updates when accessed via a popup message

3. Known Issues

   • Case 1015
     Connection Spy will display escaped connections for Reptor Virtual Appliance GUI connections.

   • Case 1018
     Active FTP is not currently supported when using a Reptor Virtual Appliance in a Branch Office operational mode

   • Case 1019
     Connection Spy displays misleading ‘escaped connections’ when Active FTP is optimized.

   • Case 1083
     Reptor Client can take a few minutes to make a connection to a Reptor Virtual Appliance via an ISA-VPN

   • Case 1119
     Reptor Enterprise Manager can sometimes indicate the wrong Reptor Client user logged in under certain multi-user scenarios

   • Case 1230
     Reptor Enterprise manager does not persist statistics during a reboot.

---

Version 2.2.1-Hotfix-1

Client Build 6091

July 2008

---

The information in this Release Note is current as of 22nd July 2008 for a Hotfix of the Replify Reptor Client, version 2.2.1. There is no Reptor Virtual Appliance or Reptor Enterprise Manager release with this hotfix.

1. Cases Resolved

   • Case 1032 Addressed an issue on Windows Vista were the Reptor Client displayed an ‘Error Downloading…’ message when attempting to automatically update itself.

   • Case 1033 Fixed an issue preventing Connection Spy from working on a clean install.

---

Version 2.2.1

Client Build 6061

Virtual Appliance Version: 2.2.0 Build 5765

Enterprise Manager Build 6060

July 2008

---

The information in this Release Note is current as of 18th July 2008 for the Replify Reptor Accelerator, version 2.2.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

This release of the Reptor Accelerator contains only a Reptor Enterprise Manager and Reptor Client. These components are fully compliant with the latest version of the Reptor Virtual Appliance, 2.2.0-5765.

Reptor Enterprise Manager now provides client “Location Awareness”

This release of the Reptor Enterprise Manager and Reptor Client introduces location awareness.

The Reptor Enterprise Manager is responsible for providing Reptor Clients with the list of Reptor Virtual Appliances with which they can achieve optimal WAN performance. When deploying a large environment (or even a smaller one) the Enterprise Manager is able to intelligently advise the client which virtual appliances to connect to.

This ensures the client gets maximum application acceleration at the correct location.

1. New Features

   • 
     Client installer ensures optimal confgiuration During an upgrade, the client installer updates the configuration with the optimal values for the new client.

   • 
     Active FTP We now intercept active FTP connections at the Reptor Client. Active FTP connections are silently converted to passive connections to the FTP server. This is configurable.

2. Cases Resolved

   • Case 514
     Fixed a problem whereby Connection Spy might function incorrectly if one or more configured appliances have no applications servers defined.

   • Case 855
     Resolved a logging issue which could have resulted in large log files accumulating in /var/log on Reptor Virtual Appliances

   • Case 959
     Reptor Client no longer inadvertently attempts to redirect UDP packets destined for the defined application servers.

   • Case 966
     Fixed a timing issue whereby the Reptor Client could miss service started/stopped events and continually display the service status as “Querying Reptor service status…”

   • Case 967
     Reduced verbosity in the Reptor Client logs for non critical events.

   • Case 1000
     Fixed a Connection Spy issue which would result in an ‘insufficient privileges’ error message under certain conditions

3. Known Issues

   • Case 267
     A Reptor Client cannot be upgraded from a network drive when it is currently accelerating traffic to that drive.

   • Case 851
     When running the Reptor Client on Vista, some configuration options are unavailable if the Reptor service is not running.

   • Case 933
     Response Gains aren’t displayed on the Reptor Virtual Appliance (Data Center) when instigating CIFS transfers through a Reptor Virtual Appliance (Branch Office)

   • Case 1015
     Connection Spy will display escaped connections for Reptor Virtual Appliance GUI connections.

   • Case 1018
     Active FTP is not currently supported when using a Reptor Virtual Appliance in a Branch Office operational mode

   • Case 1019
     Connection Spy displays misleading ‘escaped connections’ when Active FTP is optimized.

   • Case 1029
     Reptor Client will fail to install or run on a machine that does not have the correct version (2.0) of .NET installed.

---

Version 2.2.0

Client Build 5777

Virtual Appliance Build 5765

Enterprise Manager Build 5765

July 2008

---

The information in this Release Note is current as of 4th July 2008 for the Replify Reptor , version 2.2.0. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor product.

Reptor Virtual Appliance Branch Office Mode Now Available…

Allow all of your remote office workers to reap the benefits of shared network acceleration.

Enjoy a much improved user experience, with faster application response times
resulting from massive WAN data offload.

The Reptor Virtual Appliance is now available in Branch Office Mode.
A Reptor Virtual Appliance can be deployed in every remote
office where two or more workers access the Enterprise’s business critical applications running
in a different geographical location. Common content will whizz down after the first time, when accessed by anyone in the office.

1. New Features

   • 
     All licensing now controlled by the Reptor Enterprise Manager A Reptor Enterprise Manager is now responsible for delivering licenses to all Reptor Virtual Appliances in the system. As each Reptor Virtual Appliance is deployed they will just need to be configured with a Reptor Enterprise Manager’s IP address - from which they will obtain a license.

   • 
     Dynamic disk extension capability added The console command ‘add-new-disks’ has been added to permit the easy addition of more disk space.

   • 
     New X^DR Reporting Page added A new “Reports” -> “X^DR” Reptor Virtual Appliance GUI page has been created to give a summary of the current X^DR resource usage.

   • 
     Reptor Client connection behavior has been improved greatly The Reptor Client now performs a controlled back-off if issues are encountered when connecting to the Reptor Virtual Appliance.

   • 
     Reptor Enterprise Manager awareness added to the Reptor Client GUI The GUI will now display the IP address of the Reptor Enterprise Manager if it is actively controlled by it.

   • 
     Reptor Virtual Appliances order adjustment added to the Reptor Enterprise Manager GUI The ability to adjust the order of Reptor Virtual Appliances within the Reptor Enterprise Manager has been added. Confirmed order updates propagate immediately to all connected Reptor Clients.

   • 
     Direct licensing of a Reptor Virtual Appliance from the Reptor Enterprise Manager It is now possible to obtain a license from the Reptor Enterprise Manager when first browsing to the Reptor Virtual Appliance instead of having to license each individually.

   • 
     Per user logs added to the Reptor Client The Reptor Client has been updated to provide per user logs which can be found under %APPDATA%\Replify\Reptor Client.

   • 
     Clear Cache ability added to Reptor Client GUI It is now possible to clear the local X^DR byte cache via a button added to the Reptor Client GUI.

   • 
     New combined improvement statistic added to the Reptor Enterprise Manager GUI The Reptor Enterprise Manager now has a combined improvement statistic, enabling you to get a complete & concise overview of the benefits all the connected Reptor Virtual Appliances are currently providing.

   • 
     Licensing changed from concurrent users to install based The licensing mechanism has been changed from a concurrent user model to an install based model.

   • 
     Upgrade notification added to the Reptor Virtual Appliance GUI The Reptor Virtual Appliance will now display a message when an upgrade is available.

   • 
     “Response Gains” page is more detailed The Reptor Virtual Appliance’s “Reports” -> “Response Gains” page has been enhanced to list the details of the most recent CIFS optimizations.

   • 
     Reptor Enterprise Manager now identifies a connected Reptor Virtual Appliance’s mode Added a column indicating the operational mode (Data Center / Branch Office) of a connected Reptor Virtual Appliance.

   • 
     Centralised licensing so that Reptor Virtual Appliances must register with Reptor Enterprise Manager It is no longer possible for the administrator to add a Reptor Virtual Appliance to the Reptor Enterprise Manager (REM) via the REM GUI; a Reptor Virtual Appliance must register itself with the REM, via the REM GUI.

   • 
     Old redundant log files are removed during Reptor Virtual Appliance upgrade During an upgrade, the installer will remove all log files from the previous installation.

   • 
     Improved the performance of the Reptor Client service interface This is particularly important for the Microsoft Windows Vista platform.

   • 
     X^DR Statistics presentation revamped The X^DR Statistics pages within the Reptor Virtual Appliance GUI (Data Center & Branch Office mode) have been revamped to make them a lot easier to interpret.

   • 
     Improved Reptor Enterprise Manager control over a Reptor Client Addressed a Reptor Client issue were a user could delete Reptor Virtual Appliance entries while under the control of the Reptor Enterprise Manager.

   • 
     Improved usability of the Web Interface Web interface pages may now be linked to. Previously the act of logging in would have taken the user to the default page. Now the original URL is honored.

   • 
     More responsive Reptor Client Options dialog on Vista The options dialog used to sometimes take over ten seconds to open and close on Vista. It is much quicker now.

2. Cases Resolved

   • Case 165
     Increased the Reptor Client to Reptor Virtual Appliance management link reliability.

   • Case 557
     Reptor Client now reports connected Reptor Virtual Appliances as connected, even if they have no application servers defined. Previously, the client would report a connected appliance as unconnected if it had no application servers defined.

   • Case 581
     Cache state is now synchronised at start-up.

   • Case 598
     Fixed an issue that adversely affected interaction with certain configurations of some client VPNs.

   • Case 621
     Upon Trial License expiry, a user is directed to contact sales@replify.com for details on how to obtain a Production License.

   • Case 654
     vdisk_add has been renamed to add-new-disk.

   • Case 682
     Enhanced the Reptor Client to be more resilient when faced with Mnesia database corruption issues.

   • Case 683
     The Appliance Manager on the Reptor Client will now indicate a warning that a Reptor Virtual Appliance has no application servers configured.

   • Case 691
     When running on Vista, Connection Spy will request elevation if necessary.

   • Case 692
     Reptor Client logging now works under Vista without administrator privileges.

   • Case 699
     The issue with generating a system snapshot from the “System” -> “Diagnostics” page has been resolved in the both the Reptor Enterprise Manager and the Reptor Virtual Appliance.

   • Case 703
     It is now possible to generate an error report on Vista without requiring administrative privileges.

   • Case 729
     Adjusted the Reptor Virtual Appliance Memory statistic to provide a more meaningful value.

   • Case 739
     Improved performance of the X^DR in-memory store.

   • Case 743
     Resolved an issue whereby internal CIFS optimization messages were leaking to the recipient client which caused browsing lag in Vista.

   • Case 750
     Resolved a CIFS issue preventing a user from accessing a Microsoft Small Business Server 2003 shared resource.

   • Case 764
     Port and Subnet fields have been removed from the Application Server entry page as they are currently unused.

   • Case 771
     Sometimes on the X^DR stats page the internal identifier, the guid, was appearing in place of the correct user name. Now if the system does not know the user name “Unknown” will appear.

   • Case 775
     Fixed a minor typo in the Reptor Virtual Appliance GUI - Response Gains page - ‘optimsation’. (It turns out there *is* an “i” in optimization…).

   • Case 791
     People who installed the 2.1.1 Reptor Virtual Appliance need to manually edit their /etc/apt/sources.list and fix a typo.

     Change : packages.replify/com to packages.replify.com

     (See also case 877).

   • Case 804
     Addressed the problems with ‘configure-network’ on the Reptor Enterprise Manager.

   • Case 825
     If a Reptor Virtual Appliance is not in contact with a Reptor Enterprise Manager (REM), and the state of the REM is changed from active to inactive, then the REM will be deleted from the page.

   • Case 831
     Addressed an issue in the Client Session History report on the Reptor Enterprise Manager. We now report when a Reptor Client has disconnected.

   • Case 846
     Removed an erroneous version number from the internal error page.

   • Case 870
     Fixed a typo while performing a package update, output included ‘reliy’ instead of ‘replify’.

   • Case 877
     The apt sources file incorrectly referred to “packages.replify” instead of “packages.replify.com”. The command line upgrade procedure (apt-get update && apt-get upgrade) now works. (See also case 791).

   • Case 889
     Updated the Reptor Client uninstaller to remove the local cache directory when uninstalled.

   • Case 899
     Improved Reptor Virtual Appliance logging to grab more information while producing a snapshot.

   • Case 909
     Fixed an occasional glitch in the uninstall/upgrade procedure where some parts of the Reptor Client suite (mostly ReptorClientLogon) wouldn’t be killed at uninstall.

   • Case 916
     Renamed the Reptor Client ‘Reset’ button to ‘Reset Counters’.

   • Case 931
     Improved the positional behaviour of the Appliance Manager such that it moves into the foreground when appropriate.

3. Known Issues

   • Case 267 A Reptor Client cannot be upgraded from a network drive when it is currently accelerating traffic to that drive.

   • Case 452 There are issues when accessing the Reptor Virtual Appliance Management GUI with IE6.

   • Case 851 When running the Reptor Client on Vista, some options are unavailable if the Reptor service is not running.

   • Case 933 “Reports” -> “Response Gains” aren’t displayed on the server side Reptor Virtual Appliance when instigating CIFS transfers from a branch office.

---

Version 2.1.1 Reptor Enterprise Manager

Client Build 4910

Enterprise Manager Build 4910

June 2008

---

The information in this Release Note is current as of 9th June 2008 for the Replify Reptor Accelerator , version 2.1.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is a special Reptor Accelerator release introducing the Replify Reptor Enterprise Manager product and is in addition to the main 2.1.1 release made on 2nd June 2008. This release also includes an updated Reptor Client.

1. Introducing the Reptor Enterprise Manager

   With this release Replify are adding a new product to the Reptor Accelerator Product Suite. The Reptor Enterprise Manager makes it easy to manage a large Reptor Accelerator deployment comprising many clients and appliances. By describing your Reptor Accelerator deployment using its intuitive web interface, the Reptor Enterprise Manager automatically configures clients and appliances with the necessary rules to ensure optimal WAN performance.

   The Reptor Enterprise Manager, just like the Reptor Virtual Appliance, can reside on the same physical host as other virtual appliances.

   Soon you will be able to define client groups, data centers, appliance groups and remote office deployments in the Reptor Enterprise Manager. Appliances and clients will be configured based on how your network has been described - removing any complicated rule generation. Subsequent changes to the system configuration will be broadcast instantly to all connected clients and appliances.

   Historical management report generation will be available in several formats from the Reptor Enterprise Manager.

   1. Introductory Reptor Enterprise Manager Features

      • Pre-configured Client Download On the Reptor Enterprise Manager login page a pre-configured client can be downloaded which connects to the Reptor Enterprise Manager and automatically gets its virtual appliance list.

      • Multiple Virtual Appliance Configuration A Reptor Enterprise Manager allows several Reptor Virtual Appliances to be listed together. This means that connected clients will be furnished with a list of appliances, with updates to the list being published.

      • Client Reporting Similar to the Reptor Virtual Appliance, the Reptor Enterprise Manager lists all clients using the system. Session history for each client is also provided.

      • Live Activity Feed A live feed of client behaviour is given at the top of the Reptor Enterprise Manager web GUI. This logs clients as they connect and disconnect and also those who are refused a seat because of licensing restrictions.

      • Licensing Production and trial licensing is now supported. Thirty day trial licenses with twenty five seats are available to try today.

   2. Upcoming Reptor Enterprise Manager Features

      The following features are currently being developed and will be available in the Reptor Enterprise Manager very soon…

      • Group Configuration With the introduction of Client Groups, Data Center configuration and Remote Office Identification the system will broadcast the appropriate configuration updates to all components in an instant.

      • Aggregated Historical Performance Reporting Full performance reporting will soon be available:

        • Client Level A complete history of client sessions and activity based on time period, application and protocol.

        • Protocol Level Protocol level performance reporting filtered on client, time period and application.

        • Application Level Application level performance reporting filtered on client and time period.

2. Cases Resolved

   • Case 598 A fix has been made to allow us to intercept traffic for some VPNs which were previously able to bypass the Reptor Client.

---

Version 2.1.1

Client Build 4715

Appliance Build 4718

June 2008

---

The information in this Release Note is current as of 2nd June 2008 for the Replify Reptor , version 2.1.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

1. New Features

   New X^DR Features

   There have been several major improvements to the X^DR functionality…

   • 
     Disk based X^DR Caching Enabled X^DR will now make use of a disk cache on the client and server which allows the system’s cache to be preserved across restarts.

   • 
     System Wide X^DR and Compression Control The X^DR and Compression capabilities can be controlled from the new “Configuration” -> “Optimization Modules” configuration page.

   • 
     New X^DR Reporting Page A new “Reports” -> “X^DR” Virtual Appliance GUI page has been created to give a summary of the current X^DR resource usage.

   Other New Features

   • 
     Reptor Enterprise Manager Registration Page Added The Reptor Virtual Appliance can now discover and connect to the Reptor Enterprise Manager. A new page has been added under “Configuration” -> “Reptor Enterprise Manager”.

   • 
     Time Limited Demo A time limit of 30 days has now been added to the Virtual Appliance. On expiry, the Reptor Virtual Appliance will still be accessible however the clients will become inactive.

   • 
     Licensing Area on Website We now have the ability to give out licenses via the website

   • 
     Multi-CPU support has been enabled Appliance processes will now use all available CPUs.

   • 
     Connection Level Reporting In the “Client Connections” page the number of open connections per client are now displayed. One may also drill down and see the details for each of these connections.

   • 
     Security Update Mechanism The Reptor Virtual Appliance now has a mechanism for downloading signed security updates from a known secure location.

   • 
     Show different uptimes The Reptor Virtual Appliance shows uptime separately from the underlying appliance uptime.

   • 
     Console shows stats The Reptor Virtual Appliance console now shows stats like the number of connected users, the bandwidth improvement, uptime etc.

   • 
     Deactivate Applications in Appliance Management GUI A user can now deactivate an application without having to delete it. Rules for deactivated applications will not be sent to clients.

   • 
     Document Virtual Consoles The Reptor Virtual Appliance console now says how to get to other Linux virtual console (alt-f2).

   • 
     Longer Real Time Graphs on Virtual Appliance The real time graphing period has been increased from 60 seconds to 5 minutes.

2. Cases Resolved

   • Case 447 Updated installer to detect previous installation and used relevant settings (install location, start menu shortcuts, etc.) without prompting the user.

   • Case 449 The client will now dynamically push the user details of the current user to the Virtual Appliance instead of the username used at installation.

   • Case 510 The stat for the number of active connections is now correct again.

   • Case 521 Fixed update frequency combobox so that it is not editable and moved the “every” from the update options to the corresponding label.

   • Case 522 The Appliance config utility now works as expected after a clean install without requiring a reboot.

   • Case 524 When reconfiguring the appliance network configuration from the console you are no longer presented with error messages

   • Case 536 Appliance Failover has been fixed such that it correctly avoids an inactive Appliance at the top of the client list

   • Case 539 Stopped an unnecessary mount attempt which was generating a red failure message when booting the Virtual Appliance.

   • Case 541 The Client Connections page now remembers whether to show or hide disconnected clients. (Previously, hitting refresh would cause it to revert always to “show”.)

   • Case 542 Copying some large (multi-GB) files over CIFS would occasionally fail with an error message due to a bug in the compression engine.

   • Case 544 The appliance log files have been increased to 5Mb

   • Case 545 Appliance log files have been consolidated under a single directory

   • Case 546 Client service is now more resilient in the face of error situations.

   • Case 577 The constraint on using X^DR with CIFS has been relaxed. They are no longer mutually exclusive.

   • Case 581 Cache state is now synchronised at start-up.

   • Case 591 Addressed an issue where it was possible to crash the Appliance via the Realtime Statistics page

   • Case 595 Terminology changed throughout the GUI to be consistent.

   • Case 600 Removed superfluous protocol options from the client GUI

   • Case 601 Response gains are now being reported correctly when we are making CIFS requests.

3. Known Issues

   • Case 267 A Client cannot be upgraded from a network drive when it is currently accelerating traffic to that drive.

   • Case 452 There are issues when accessing the Appliance Management GUI with IE6.

   • Case 543 We currently break Active FTP attempts against certain ftp servers (IIS is known example).

   • Case 518 The network cache in the X^DR functionality is currently fixed to be 128M and cannot be changed.

---

Version 2.1.0

Client Build 4124

Appliance Build 4124

May 2008

---

The information in this Release Note is current as of 7th May 2008 for the Replify Reptor , version 2.1.0. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor Accelerator product.

1. New Features

   • 
     Cross Protocol Data Reduction (X^DR) Added new network byte caching feature to dramatically reduce network traffic. The cross protocol behaviour ensures that all protocols are boosted. NOTE: This feature cannot be enabled with CIFS Optimization in this trial version.

   • 
     SNMP Support Added support for SNMP v3 to the Reptor Virtual Appliance. SNMP is off by default and must be enabled through the Appliance GUI.

   • 
     Reptor Enterprise Manager Support Added Client and Appliance hooks have been added to facilitate the new Reptor Enterprise Manager REM. The REM is a single point from which to Deploy, Configure and Report on your complete network, giving you full network visibility and application metrics. NOTE: For further information on the REM contact sales at replify.com.

   • 
     Control Order of Client Redirection A user can now control the order in which a client redirects to a set of virtual appliances, with the same matching rules, based on the order they are given to the client.

   • 
     Application Availability Tester A user can now ping or nmap a given application server from the Application Servers page to check for availability.

   • 
     Use Generic Application Acceleration The appliance rules have now been updated to apply optimizations using the Reptor auto-detect capabilities. Specific optimizations will be enabled again in subsequent versions of the Reptor Enterprise Manager.

2. Cases Resolved

   • Case 267 Modified installer so that it can now be run from a networked drive without failing if the driver install breaks network connectivity.

   • Case 276 Client now fails over on to the correct alternate appliance when the current working appliance is removed.

   • Case 327 Resolved an issue concerning the monitoring of the Reptor client service. This would cause an exception if the service was not fully initialized.

   • Case 390 Hibernating clients will now correctly be marked as ‘offline’ in the appliance “Client Connections” page.

   • Case 410 Client Session History records are now correct in all instances.

   • Case 418 Corrected the recording of stats to account for possible caching of data.

   • Case 432 In the Reptor Virtual Appliance’s Management GUI, the tab order of form fields now behave as expected.

   • Case 438 Session History page now displays User’s ID when there are no historical sessions.

   • Case 456 Client service logs now show time in localtime.

   • Case 466 Real time compression chart no longer generates 404s when looking for an unknown gif.

   • Case 467 Resolved memory growth in Firefox (2.0) while looking at the Real-Time Compression Chart

   • Case 470 Client connection monitoring now uses much less client CPU

   • Case 486 Prevented Client Start/Stop items from being displayed on the tray icon’s context menu if the application has insufficient privileges to start/stop the Reptor service.

   • Case 491 ‘Uncompressed’ should read ‘Raw’ in Appliance GUI

   • Case 504 Client installer now creates a config dir after a fresh install.

3. Known Issues

   • Case 523 The Virtual Appliance config utility is not working after a clean install. The work around is to reboot the virtual appliance.

   • Case 267 A Client cannot be upgraded from a network drive when it is currently accelerating traffic to that drive.

   • Case 452 There are issues when accessing the Appliance Management GUI with IE6.

   • Case 518 The network cache in the X^DR functionality is currently fixed to be 128M and cannot be changed.

---

Version 2.0.1

Client Build 3422

Appliance Build 3428

April 2008

---

The information in this Release Note is current as of 3rd April 2008 for the Replify Reptor SoftWOC, version 2.0.1. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor SoftWOC product.

1. New Features

   • 
     Automatic update feature added to Reptor Client Update options can be found in the Update tab under ‘Tools -> Options’.

   • 
     Embedded Client Download A user can now browse to an appliance and download the latest available client for that appliance which will automatically configure the client for that appliance.

   • 
     Network Setup facility is now active User can select ‘DHCP’ or select and configure Static IP details from the Appliance GUI.

   • 
     System Rebooting Activated The ability to reboot the system from the management GUI has been activated.

   • 
     Embedded ROI Calculator The performance management pages have been enhanced to allow ROI calculations to be made based on bandwidth saved.

   • 
     Toggle visibility of unconnected clients The ‘SoftWOC Connections’ page allows toggling the visibility of disconnected clients.

   • 
     Client session history browsing added An administrator now has the ability to drill down on a user’s session history.

   • 
     New Diagnostics Page User can download a system snapshot zip file from: ‘System -> Diagnostics’

   • 
     Updated Live Performance Graphs Reports Flash Graphs have been updated to latest version.

2. Cases Resolved

   • Case 195 Fixed “definied” typo in main client dialog.

   • Case 264 Main client installer is now more aware of errors in sub-components.

   • Case 274 Administrators hitting port 80 on the Virtual Appliance Admin gui will be redirected to port 8888.

   • Case 316 Hardcoded ‘53 mins’ replaced with live uptime. ‘System’ tab now labelled ‘Info’.

   • Case 346 svc command not found error when setting static IP on appliance using config script

   • Case 361 ‘Login’ page now correctly displays the page title.

   • Case 368 Reptor Client updated to detect a corrupted configuration file and overwrite it with one containing sensible default values.

   • Case 369 Reptor Clients with a corruputed configuration set will self heal as the functionality is used instead of failing at the first issue.

   • Case 374 Reptor Client now handles statistics value greater than 2,147,483,647 bytes.

   • Case 385 A CIFS regression issue has been resolved.

   • Case 399 Compression Gains Report page now displays compressed data chart and details when there is available data.

   • Case 400 Anchored “key” labels (Created, Updated, Destroyed) to bottom left of Connection Spy form so it now resizes as expected.

   • Case 414 Issues when saving network files greater than 65K have been resolved.

3. Known Issues

   • Case 302 Occassionally the client may not receive events from the Reptor service. This results in stats not being updated and appliances not showing updated states. To recover stop and start the service.

   • Case 410 Session history data totals are sometimes inaccurate. This will be resolved in the next minor release.

---

Version 2.0.0-Hotfix-1

Client Build 3101

March 2008

---

The information in this Release Note is current as of 19th March 2008 for a Hotfix of the Replify Reptor SoftWOC Client, version 2.0.0. There is no appliance release with this hotfix.

1. Cases Resolved

   • Case 382 CIFS writes from the client to the server are now being handled as expected.

---

Version 2.0.0

Client Build 3056

Appliance Build 3055

March 2008

---

The information in this Release Note is current as of 18th March 2008 for the Replify Reptor SoftWOC, version 2.0.0. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is a major release and is not compatible with any previous versions of the Replify Reptor SoftWOC product.
If you have previous versions of the client installed, you must upgrade. Also, old versions of the appliance will not work with
the new client: you must deploy new virtual appliances to work with the new client.

This is the ONLY Release Notes document for the Replify Reptor SoftWOC product.

1. New Features

   • 
     Seamless High Availability A client will now seamlessly failover to an alternate virtual appliance if the current appliance fails.

   • ESX Support We now support (and encourage!) deployment to VMWare’s ESX Server. The appliance is now available in
     ovf format.

   • 
     Reports For All Clients Unconnected client statistics are now being presented.

   • 
     Compression Gains Report Updated Compression Gains report page has been updated to include an X-factor for each protocol.

   • 
     Activated System->Password Page An administrator is now able to change the admin password in the System area of the Reptor management GUI.

   • 
     ROI Calculator A user is now able to estimate the costs saved by taking data off the network.

2. Cases Resolved

   • Case 19 Appropriate version numbers are now displayed consistently across the product.

   • Case 147 Updated the installer to be backwards aware. Clients can now be upgraded without requiring removal of older versions.

   • Case 160 Honour the Client Tray state through an upgrade.

   • Case 278 Updated the main client installer to detect reboot request by driver installer.

   • Case 281 Compressed and Uncompressed totals in header can be toggled between raw bytes and formatted to cater for larger units.

   • Case 287 Prevented exit message from being shown when the Reptor Client is closed down in preparation for an updated install.

   • Case 299 Connected SoftWOCs page now has correctly formatted time and date.

   • Case 305 Updated the installer so that if .NET 2.0 isn’t installed then the user is asked if they want to be directed to the appropriate download site.

   • Case 311 Reports PDF output now displays the correct date.

   • Case 313 Reports graph PDF output now has a white background.

   • Case 318 Fixed bug whereby the Reptor Client would crash when opening the Options dialog when running as a non-administrative user on Vista.

   • Case 324 The stats for traffic coming from the Client to the Server were not being recorded correctly on the appliance.

   • Case 325 Fixed bug whereby resetting statistics on the Reptor Client more than once led to incorrect values being displayed.

   • Case 330 Back to front labels in the table in the Compression Gains page have been corrected.

   • Case 336 X-axis no longer auto scales in performance reports.

   • Case 338 and 329 Exposing the unconnected SoftWOCs means that the totals now add up to the summary values.

   • Case 353 Heartbeating has been implemented between the client and appliance so that the client now ALWAYS notices when an appliance drops out.

   • Case 357 Fixed a bug whereby opening the Appliance Manager from the balloon tip would cause the client to crash if the Appliance Manager was already visible.

   • Case 362 Reports Graphs should not be visible if no relevant data is available

   • Case 364 Typo on “Response Gains” screen. “Reponse times” has become “Response times”.

3. Known Issues

   • Case 302 Occassionally the client may not receive events from the Reptor service. This results in stats not being updated and
     appliances not showing updated states. To recover stop and start the service.

   • Case 374 Client cannot handle statistics value greater than 2,147,483,647.

---

Version 1.1.0

Client Build 2313

Appliance Build 2311

February 2008

---

The information in this Release Note is current as of 26th February 2008 for the Replify Reptor SoftWOC, version 1.1.0. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor SoftWOC product.

1. New Features

   • 
     Windows File Sharing Optimization The latest Replify Reptor has introduced a new protocol specific optimization to reduce CIFS protocol chatter and accelerate files transfers between a Windows File server and Replify Reptor Client machine.

   • 
     New “Response Gains” Performance Reporting Page A new performance reporting page shows the benefits of the CIFS optimization in terms of time (in seconds) saved. There is also a report on the number of files optimized, as well as a single overall Performance Increase value.

   • 
     Exportable Performance Reports Most performance reports can now be exported as an image (png), Pdf, csv or XML file.

   • 
     i386 Virtual Image The virtual appliance is now built in 32 bit mode to enable compatibility with older processor types.

2. Cases Resolved

   • Case 233 The issue with unoptimized pass through traffic being delayed has now been resolved.

   • Case 244 Corrected an issue in the Client GUI that caused the list of appliances to be incorrectly maintained.

   • Case 248 Made changes to the client control plane to improve operational robustness.

   • Case 302 Resolved an issue with the start order of components within the Client. Registered event listeners were being sent events before the system had been correctly initialised.

   • Case 307 The admin user is now forced to authenticate with admin/default when logging into the appliance GUI.

3. Known Issues

   • Case 311 Pdf generation is not operational for all report types. The date and time for the pdf reports have a hardcoded date.

   • Case 308 The administrator is unable to change the admin password.

   • Case 299 Formatting of date and time in the “Connected Softwocs” page is incorrect for single digit minute and second values.

---

Version 1.0.3

Client Build 2313

Appliance Build 2311

February 2008

---

The information in this Release Note is current as of 11th February 2008 for the Replify Reptor SoftWOC, version 1.0.3. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor SoftWOC product.

1. Cases Resolved

   • Case 138: Real-Time graphs page no longer causes a browser to hang if it has been left running for a long time.

   • Case 187: Markup and css improvements to ‘Connected SoftWOCs’ page. Table columns are sortable by content.

   • Case 227: Resizing of the Reptor Appliance browser window now supports resizing to 800×600px without causing illegible page layout.

   • Case 278: Updated the main client installer to detect a reboot request by driver installer.

   • Case 279: When adding an Application Server, the user must now fill in the required fields. Improved user feedback when performing operations.

   • Case 281: Uncompressed and compressed figures in the header have proper display units.

   • Case 296: Made the client installation process simpler and more robust.

2. Known Issues

   • Case 267: During installation of the Reptor Client, the computer may briefly lose network connectivity. For this reason it is strongly recommended that you do not attempt to install the Reptor Client from a networked drive.

---

Version 1.0.2

Client Build 2177

Appliance Build 2185

January 2008

---

The information in this Release Note is current as of January 2008 for the Replify Reptor SoftWOC, version 1.0.2. For the most current versions of all Replify documents refer to the online documentation page located at:

http://www.replify.com/docs/

This is the ONLY Release Notes document for the Replify Reptor SoftWOC product.

1. The Replify Reptor SoftWOC

   • The Replify Reptor SoftWOC is a complete WAN Optimisation solution. The aim of this product is to improve your organisations’ central application response times when access to these servers is by a distributed workforce.

   • The Replify Reptor SoftWOC can dramatically reduce the effects of a high latency network using data reduction and protocol specific optimisations. This not only improves a users experience but removes the necessity for costly bandwidth upgrades.

   • There are 2 separate installable components which make up the Replify Reptor SoftWOC:

     • The Replify Reptor WOC Appliance is a virtual appliance which is placed in the data centre close to the application servers it is accelerating. This component is described in more detail in Section 2 below.

     • The Replify Reptor WOC Client is a Windows installable service which is installed at all endpoints accessing the application server. This client will redirect all traffic aimed at the configured application server to the appliance. The data sent over the WAN between the Client and the Appliance will be optimised. This component is described in more detial in Section 3 below.

2. The Replify Reptor Virtual Appliance

   • The Replify Reptor WOC Appliance is a complete Virtual Appliance in your Data Centre. Replify provide a downloadable virtual machine which allows a user with a prepared host machine to simply copy the Replify Reptor WOC Appliance into an accessible location and start the virtual appliance. Reptor Virtual Appliances can be placed in one or many data centres. A single VMware Server may host many Virtual Appliances.

   • The Replify Reptor Appliance offers a simple yet powerful High Availability solution. Several Reptor Virtual Appliances can be configured to optimise the same Application servers at the same time. If one or more of these Virtual Appliances is unavailable, the Reptor Client will seamlessly try to connect to the next available Virtual Appliance until all options are exhausted. The client will attempt to connect directly to the application server if no Virtual Appliance is available, making sure that the Reptor is never a single point of failure in your network.

   • The Replify Reptor WOC Appliance offers the system administrator extensive visibility to the benefits being offered by the Reptor SoftWOC as well as an easy and incredibly powerful means of controlling the configuration of the Reptor WOC Clients. Each appliance is responsible for keeping the connected clients up to date with the latest rule set. Changes to this rule set via the Appliance’s management interface will be broadcast to all connected client WOCs immediately.

   • For more information on preparing your VMware Server see the Preparation Guide. For more information on downloading and installing the Virtual Appliance see the Download and Installation Guide. The latest version of all documents can be found on the Replify website:

     http://www.replify.com/docs/

3. The Replify Reptor WOC Client

   • The Replify Reptor WOC Client is an installable Windows service which intercepts and optimises application traffic for the configured application servers. The client WOC may optimise traffic for one or several application servers simultaneously while working with one or more Reptor Virtual Appliances.

   • Changes to the Replify Reptor WOC Clients optimisation rules are controlled centrally by the Reptor Appliance. Once a change is made by the administrator on the machine at the datacentre the rules are broadcast immediately to all connected client WOCs. Client WOCs which come online after these changes have been made will receive the updated rules as part of their initial sign in.

   • For more information on installing your WOC Client see the Client Installation Guide:

     http://www.replify.com/dcos/

4. New Features

   This is the first public release of the Replify Reptor SoftWOC. Here are a few of the features available in this release:

   • Increases in response time for some applications of up to 10 times.

   • Immediate deployment of a Virtual WOC Appliance.

   • A simple, unobtrusive WOC Client installation.

   • Single step global client configuration.

   • Immediate broadcasting of configuration updates to all connected clients and future connecting clients.

   • Full and rich performance reporting. Both live and historical performance reporting can be filtered by Protocol, Application or Client.

   • Rich client reporting capabilities, including user details, client machine details and traffic profiling.

   • Seamless High Availability when more than one Virtual Appliance is configured to optimise the same application server.

   • NOTE: Protocol specific optimisations (such as HTTP and Windows File Sharing) have been disabled for this initial release.

5. Known Issues

   • Case 267: During installation of the Reptor Client, the computer may briefly lose network connectivity. For this reason it is strongly recommended that you do not attempt to install the Reptor Client from a networked drive.

   • Case 268: Occasionally after initial install, the Reptor Client may fail to correctly intercept traffic. If this happens, restarting the computer will resolve the issue.

http://www.replify.com/REPTOR-VA-ESX

http://www.replify.com/REPTOR-VA-ESX-32