VPN group policy

You don't. They are called logon scripts because they are run at logon time. They are not called runatvpnconnectiontime scripts.

Make a copy of the login script batch file and make it available on each pc - make an icon or something on the desktop. Run this after the vpn connection is established. That will map the drive letters and printers or whatever else your script does.

Turn on auditing.

I have 4 domain controllers. Please tell me how to configure the auditing.

No, I won't. You tell us what your environment is, operating system(s) used, service pack levels etc and related info then we can see what we can do for you. I am not playing at guessing games - for all we know you could be using a Linux back end.

The domain controllers are all windows 2003 Standard SP2
All clients are vista/ xp.
I want to be able to log all users who attempt to login using the vpn. My apologies for not providing all the details.

I enabled RRAS logging in the routing and remote access snap in.
Thanks for your help, if I join the remote computers to the domain and ask users to check the "dial in" checkbox in the windows login box before logging in, will that apply the login scripts ?

As long as they are part of the domain - and the connection is established to the vpn as the login takes place then this should allow the login script to operate. As i stated, if you cannot achieve this, then you can simply place a copy of the logon script onto each pc with an icon and run it afterwards.

One last question, if I enable ISA site to site VPN (with ISA at both ends) am I assuming correctly that  Users will not need to dial in to the vpn ?

That is correct - A site to site vpn traditionally means that the connection is established between the two end points rather than having been established individually by each client. I have a number of sites with 5 or more sites and these are permanently connected and established as if they were point-to-point links.

Keith

Will I have to do any port forwarding on the remote branch's DSL modem ?

By configuring the site to site vpn does this mean that remote clients will need to utilize the main office broadband connection for internet access ?

That will depend upon your site requirements, your security policy, bandwidth availability, dns configurations etc.
Yes, you will want to pass through all ports on the dsl to the remote ISA external nic.

Keith, One last question, what is your personal take on vpn solutions ? Would you go for ISA solution or Cisco / sonicwall / hardware vpn router?
Are there any disadvantages by using ISA ?
I will be going with ISA 2006 standard edition in all branches in site - site VPN. Hope I don't need the enterprise version.

lol - I think you have done quite well already for a 50 point question anarine.....

There is no where near enough information to make a choice here. - nor is this the right place to do so. The last time I did an installation of the size you are discussing it was a six month implementation activity and I ran a team of 8. The design stage alone took over two months just working out exactly what the company needed to achieve, the applications and services that would be shared, the DNS and the security considerations that needed to be factored in plus the likely bandwidth implications.

The choice of solution was the last activity and we opted for Cisco ASA at the edge (providing the VPN/SSL connectivity with ISA acting as the internal firewall/proxy.

Every installation is different and the requirements for each will determine the solution needed.

Thanks for the help keith. I will open a new question on  ISA site to site VPN

Welcome mate