XP dial up logis scripts and secure remote

  • Thread starter Thread starter Ian C
  • Start date Start date
I

Ian C

I'm sorry if this has been answered before but after spending an hour
or two searching I can't find an answer that helps.

I need to get an XP laptop to connect to our NT Domain and execute a
logon script.

This sounds easy until you add a dial up connection and Secure remote
software to the equation.

The laptop dials the number and authenticates on the RAS server then
XP logs on but because secure remote hasn't granted access to the
domain resources the laptop logs on with cached information.
Subsequently when the secure remote access has been granted the logon
script and drive mappings are not then made.

I have tried selecting 'wait for network connection' for logging on
within the registry and the laptop won't even log on far enough to run
the SecuRemote software.

Unfortunately the rules here where I work are such that I can't just
write a batch file to kick off the script. The users need to be able
to log onto their laptops using cached information when they are
working remotely so I can't just disable caching of profiles. Local
user accounts are not permitted.

This all worked with windows 98 as the logon script would run after
the domain password was entered after connection had been made. Is
there any way of attaining the same functionality from XP?? And if so
How??

Thanks in advance for any help in this.
 
I don't know if this will help--probably not--but:
My understanding is that you won't get logon scripts unless the user chooses
to logon via the dialup connection, at the initial logon screen.

I'm not familiar with secure remote, so I have no idea whether this is
possible with your restrictions. Rereading, I'm pessimistic!
 
Unfortunately even when checking the logon via dial up check box the
Laptop has already connected to the network before the SecuRemote asks
for authentication so as XP cannot access any lonon server it logs on
with cached info and if you turn off asynchronous login the laptop
won't logon at all.

Is there no way to force XP to run the logon script when it carries
out the background refresh once the network is available??
 
Unfortunately even when this option is selected the Laptop dials up
and connnects but because the SecuRemote software has not yet granted
access the laptop still logs on with cached information and therefore
doesn't map home drives or run the login script. I was hoping there
was a way to force XP to run all the logon processes as part of the
background refresh.
 
I don't know of a way around this, I'm afraid. You might want to inquire in
a server-related forum, where it'd be more likely you'd find folks familiar
with both SecuRemote and with esoterica related to logon scripts.
 
Back
Top