Hi,
I have a solution where a lot of users log on to a windows 2003 domain using Dialup networking and a L2TP over IPSec connection client. All communication is via wlan, and the sessions are pre-authenticated through radius. When login on we fire a logon script through a GPO for mapping drives, etc, but it's rather unstable.
A lot of times, the drives are not mapped, and the users get a lot of userenv messages in the event log stating that either the domain controller or the path to the login script is unavailable.
If we try to fire the script manually right after login on everything is working just fine.
My theory is that this is a timing issue.
Have anyone else experienced the same behavior?
I was thinking about making a new client with CMAK, firing the script through a post-connect custom action and pointing to a local script with a delay loop, redirecting to the original login script after a few seconds. The problem is that I have absolutely no experience with this at all, and need some input from you experts out there.
I read something about having to create registry entries for the scripts I want to fire, but I did not completely understand how this works.
Is there any simpler way of handling this? I would really appreciate some input.
Best regards
Jeppedal
I have a solution where a lot of users log on to a windows 2003 domain using Dialup networking and a L2TP over IPSec connection client. All communication is via wlan, and the sessions are pre-authenticated through radius. When login on we fire a logon script through a GPO for mapping drives, etc, but it's rather unstable.
A lot of times, the drives are not mapped, and the users get a lot of userenv messages in the event log stating that either the domain controller or the path to the login script is unavailable.
If we try to fire the script manually right after login on everything is working just fine.
My theory is that this is a timing issue.
Have anyone else experienced the same behavior?
I was thinking about making a new client with CMAK, firing the script through a post-connect custom action and pointing to a local script with a delay loop, redirecting to the original login script after a few seconds. The problem is that I have absolutely no experience with this at all, and need some input from you experts out there.
I read something about having to create registry entries for the scripts I want to fire, but I did not completely understand how this works.
Is there any simpler way of handling this? I would really appreciate some input.
Best regards
Jeppedal