Provising VPN Client Settings in Group Policy
"...Today, Microsoft VPN client can be configured in two ways as discussed in this article - a) in-built VPN client b) CM based VPN client.
The first method requires end user to know the VPN settings and then create a VPN connection - which needs to be repeated by each user and prone to errors.
The second method requires VPN server administrator to create a VPN connection package (called as CM profile) and then send to end user through some mechanism (like uploading to a web server).
The end user then manually installs the CM profile. The problem in this mechanism is end user may forget to do the same step when the configuration changes and VPN server administrator has no way to automatically push the changes..."
Check out the details of this solution over at the RRAS Team Blog at:
Thomas W Shinder, M.D., MCSE
Sr. Consultant / Technical Writer