Logon Scripts over VPN

Greetings

We currently have a 2003 RRAS box that users VPN into the network. When
they click on the shortcut on their desktop for the VPN connection, put in
their uid and pwd, and click connnect they connect just fine....

The thing that does not happen is their login script running. It will run
if they choose the Connect over dial-up connection from the CTRL-ALT-DEL
screen when windows starts and login to the VPN but not when they just click
on the icon from the desktop.

Any ideas/solutions/etc?

Making a VPN connection is not a login. All you are doing is setting up
an IP connection.

It is possible to do a domain login at the same time by using the "login
using a dialup connection" option from the login dialog box. But most people
don't like to do that. They like to do their local login first, then
connect.

If you are in that situation you will have to find some other event to
trigger off the script when they connect.

Charlie Saliba wrote:
> Greetings
>
> We currently have a 2003 RRAS box that users VPN into the network.
> When they click on the shortcut on their desktop for the VPN
> connection, put in their uid and pwd, and click connnect they connect
> just fine....
>
> The thing that does not happen is their login script running. It
> will run if they choose the Connect over dial-up connection from the
> CTRL-ALT-DEL screen when windows starts and login to the VPN but not
> when they just click on the icon from the desktop.
>
> Any ideas/solutions/etc?

Do you have any suggestions?

"Bill Grant" wrote:

> Making a VPN connection is not a login. All you are doing is setting up
> an IP connection.
>
> It is possible to do a domain login at the same time by using the "login
> using a dialup connection" option from the login dialog box. But most people
> don't like to do that. They like to do their local login first, then
> connect.
>
> If you are in that situation you will have to find some other event to
> trigger off the script when they connect.
>
> Charlie Saliba wrote:
> > Greetings
> >
> > We currently have a 2003 RRAS box that users VPN into the network.
> > When they click on the shortcut on their desktop for the VPN
> > connection, put in their uid and pwd, and click connnect they connect
> > just fine....
> >
> > The thing that does not happen is their login script running. It
> > will run if they choose the Connect over dial-up connection from the
> > CTRL-ALT-DEL screen when windows starts and login to the VPN but not
> > when they just click on the icon from the desktop.
> >
> > Any ideas/solutions/etc?
>
>
>

"Charlie Saliba" <(E-Mail Removed)> wrote in message
news:42AA0321-3D5B-4915-9B0C-(E-Mail Removed)...
> Do you have any suggestions?

Send them a batch file to copy to their desktops and show them how to launch
it. Cheap & cheerful. Or, don't use a login script for them.
>
> "Bill Grant" wrote:
>
>> Making a VPN connection is not a login. All you are doing is setting
>> up
>> an IP connection.
>>
>> It is possible to do a domain login at the same time by using the
>> "login
>> using a dialup connection" option from the login dialog box. But most
>> people
>> don't like to do that. They like to do their local login first, then
>> connect.
>>
>> If you are in that situation you will have to find some other event
>> to
>> trigger off the script when they connect.
>>
>> Charlie Saliba wrote:
>> > Greetings
>> >
>> > We currently have a 2003 RRAS box that users VPN into the network.
>> > When they click on the shortcut on their desktop for the VPN
>> > connection, put in their uid and pwd, and click connnect they connect
>> > just fine....
>> >
>> > The thing that does not happen is their login script running. It
>> > will run if they choose the Connect over dial-up connection from the
>> > CTRL-ALT-DEL screen when windows starts and login to the VPN but not
>> > when they just click on the icon from the desktop.
>> >
>> > Any ideas/solutions/etc?
>>
>>
>>

Do you know if Microsoft will have a Fix for this in the near future?

"Lanwench [MVP - Exchange]" wrote:

>
> "Charlie Saliba" <(E-Mail Removed)> wrote in message
> news:42AA0321-3D5B-4915-9B0C-(E-Mail Removed)...
> > Do you have any suggestions?
>
> Send them a batch file to copy to their desktops and show them how to launch
> it. Cheap & cheerful. Or, don't use a login script for them.
> >
> > "Bill Grant" wrote:
> >
> >> Making a VPN connection is not a login. All you are doing is setting
> >> up
> >> an IP connection.
> >>
> >> It is possible to do a domain login at the same time by using the
> >> "login
> >> using a dialup connection" option from the login dialog box. But most
> >> people
> >> don't like to do that. They like to do their local login first, then
> >> connect.
> >>
> >> If you are in that situation you will have to find some other event
> >> to
> >> trigger off the script when they connect.
> >>
> >> Charlie Saliba wrote:
> >> > Greetings
> >> >
> >> > We currently have a 2003 RRAS box that users VPN into the network.
> >> > When they click on the shortcut on their desktop for the VPN
> >> > connection, put in their uid and pwd, and click connnect they connect
> >> > just fine....
> >> >
> >> > The thing that does not happen is their login script running. It
> >> > will run if they choose the Connect over dial-up connection from the
> >> > CTRL-ALT-DEL screen when windows starts and login to the VPN but not
> >> > when they just click on the icon from the desktop.
> >> >
> >> > Any ideas/solutions/etc?
> >>
> >>
> >>
>
>
>

It isn't a bug, there is nothing to "fix". It is the way VPN is,...VPN is a
"dialup" technology and has the characteristics of using the old modem
dialup technology,...which didn't run login scripts either. As might has
been said earlier if I am not confusing this with another post, VPN
credentials only create the VPN link and make it "alive",...they do not, nor
have anything to do with a Windows Domain logon.

MS already has the solution and it has been around for a log time. At the
Crtl-Alt-Del prompt on the client, check the box that says "Log on with
Dialup Connection" (or something like that). It will ask which Connection to
use,..choose the VPN connection. This will let you log into the Machine, the
Domain, and activate the VPN link all at the same time.

I don't remember for sure, but the logon Scripts still may not run anyway
due to the link speed. The system, if I remember correctly, due to
bandwidth, does not run those scripts when the client is comming over a slow
"dialup connection" which is what VPN is classified as,...this would be by
design,...on purpose,... intensionally.

Putting a BatchFile on the user's desktop and instructing them to run it
after establishing a VPN link is the probably the best way, and it is not
hard for them to do. User lazyness is annoying,..don't let them use "it is
too hard" as an excuse.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------



"Charlie Saliba" <(E-Mail Removed)> wrote in message
news:0185FB96-742E-45DD-8A3D-(E-Mail Removed)...
> Do you know if Microsoft will have a Fix for this in the near future?
>
> "Lanwench [MVP - Exchange]" wrote: