The best answer to a "do it all at the client" question is answered with
a combination of RQS/RQC scripts:
http://www.microsoft.com/isaserver/techinfo/guidance/2004/vpn.asp
..and
http://www.microsoft.com/downloads/details.aspx?FamilyId=3396C852-717F-4

B2E-AB4D-1C44356CE37A&displaylang=en

..as well as judicious application of CM:
http://www.microsoft.com/downloads/info.aspx?na=22&p=2&SrcDisplayLang=en

&SrcCategoryId=&SrcFamilyId=&genscs=&u=%2fdownloads%2fdetails.aspx%3fFam

ilyID%3d93fd20e7-e73a-43f6-96ec-7bcc7527709b%26DisplayLang%3den

Jim Harrison
Security Business Unit (ISA SE)

-----Original Message-----
From: Matt Bazan [mailto:Mbazan (at) onelegal (dot) com [email concealed]]
Sent: Thursday, March 24, 2005 2:41 PM
To: focus-ms (at) securityfocus (dot) com [email concealed]
Subject: quarantine vpn clients

Hello,
Anybody out there using quarantining/policy enforcement
solutions with MS' vpns? We run ISA 2004 and I see they have a
quarantine feature with limited functionality. I'd like something that
can be used to enforce a security policy on the client side. Ideas?
Thanks.

------------------------------------------------------------------------

---
------------------------------------------------------------------------

---

------------------------------------------------------------------------
---
------------------------------------------------------------------------
---

[ reply ]