1NET Changelog

What's new in 1NET 2.5.1

Aug 22, 2013
  • FIPS Compliant

New in 1NET 2.5.0 (Aug 13, 2013)

  • Added 'Domain Connections Only' feature
  • ADMX file updated to v1.5 to support 'Domain Connections Only' feature
  • ADM file included with 1NET v2.4.x is no longer supported. ADMX must only be used
  • Reliability improvements when enumerating wireless connections
  • Improved detection of Juniper Junos Pulse VPNs
  • Improved detection of Cisco AnyConnect VPNs
  • Improved detection of Forti SSL VPNs
  • Logging improvements
  • Digitally signed

New in 1NET 2.4.1 (May 13, 2013)

  • Fixed issue where the 1NET service may not start on some Windows 8 systems
  • Improved detection of Juniper SSL VPNs

New in 1NET 2.4.0 (Feb 20, 2013)

  • Added a new feature to restrict the number of public networks to one for computers while they are off the Domain network.
  • Improved detection for popular SSL VPN clients
  • Simplified exclusion process for VPNs not automatically detected by 1NET
  • New ADMX file to control new setting 'Single Remote Adapter'

New in 1NET 2.3.0 (Nov 29, 2012)

  • Added the ability to exclude VPNs which appear to Windows standard network adapters and not a VPN adapter

New in 1NET 2.2.0 (Nov 16, 2012)

  • Now automatically reconnects to the corporate wireless network when disconnect from the corporate wired network
  • Fixed licensing issue

New in 1NET 2.1.0 (Oct 23, 2012)

  • Improved support for Remote Access VPNs and Tunnel Adapters
  • New Group Policy ADMX to configure 1NET's VPN and Tunnel support