> I do not know anything about DirectAccess, but this description scares
> me. It also scares me, but not any more than the present state of the world, or any of the alternatives. ;-) I can think of some really good reasons to hate VPN (despite how much I've grown to love and embrace it.) . When your user visits some other company, generally speaking, the other company's firewall policy will not allow your user to VPN back into your network. I don't know if this restriction will be any different with DirectAccess. I think this must be a wonderful addition, provided that it tunnels on https, and can pass through some other company's https proxy. . I supply all my users with preconfigured VPN clients on their laptops. Most users would prefer to leave their laptop in the office, and just enable another VPN on their home computer. I will not support the random (anti) security software they have at home, and I can't deploy Windows Firewall settings to their home computers via group policy, and I'll only make a tiny little effort to tell them how to manually change their firewall to enable VPN. Long story short, if those problems go away, the average user could benefit from improved connectedness and convenience. Generally speaking, my users VPN in for two main reasons: File access, and RDP. I don't think there are any recent efforts to change RDP across the WAN, but there are two efforts to change the file access. Obviously, the aforementioned DirectAccess would be one. Office Web Apps should go a long way too. ;-) This is definitely accessible via https, and hence, available from within some other company's network. (Yay!)
_______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
