VPN-Q 2009 is now RTM


Following the success of VPN-Q 2006, VPN-Q 2009 brings remote access NAP/NAC Quarantine to the next level! VPN-Q 2009 maintains the same key benefits of the previous version and introduces new functionality and features that our customers have asked for. VPN-Q 2009 also introduces a new member to the lineup – the Express Edition!

VPN-Q 2009 helps secure your VPN connections by checking the health state of remote endpoint client  PC’s while they are isolated in a quarantine network. Threats from viruses, worms, hackers and malicious users are everywhere, by ensuring that remote PC’s connecting to your network have up-to-date anti virus software, a personal firewall enabled and patches installed (to name a few features) these threats can be significantly reduced.

What’s new in VPN-Q 2009

Included in VPN-Q 2009 is a new quarantine service which removes the dependency on the Microsoft RQS service. The new Winfrasoft VPN-Q 2009 Management Service allows for many new features which were not previously possible due to restrictions of the legacy Microsoft RQS service. Because the services are totally separate, migration from 2006 to 2009 is made easy as they can both co-exist on the same ISA server, making it easy to gradually upgrade your VPN clients.

The licence file is no longer included in the client setup package, which makes it easier to change licence files and also helps to prevent licence file theft. To reduce activation connectivity issues, the new quarantine service will process activation requests with our activation server so that the VPN clients no longer need to do this directly. The new quarantine service also acts a policy server, the new VPN-Q client receives its policy directly from the ISA server and does not require AD group policy. This means that unmanaged & non-domain joined PC’s must also now conform to your VPN security policy. You can still make use of AD group policy if you wish, but any setting explicitly set on the VPN server will take priority.

AD computer groups can also be used to restrict which PC’s are allowed to be used for VPN access – not just users. Simply create an AD group containing computer accounts and tell VPN-Q which group to use. If a VPN connection is not made from a PC in that group they will not be able to clear quarantine regardless of their health state. Manual computer objects can also be created in AD for non-domain joined PC’s by specifying the PC’s hardware GUID.

Head on over to http://www.winfrasoft.com/vpnq2009.htm and download a trial version. I’m sure you’ll like what you find.



Thomas W Shinder, M.D., MCSE
Sr. Consultant / Technical Writer

Prowess Consulting www.prowessconsulting.com

PROWESS CONSULTING | Microsoft Forefront Security Specialist
Email: [email protected]
MVP — Forefront Edge Security (ISA/TMG/IAG)

About The Author

Leave a Comment

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Scroll to Top