Logon script mapping important drive fails in a 2003-terminal-server farm

On our Windows Server 2003 farm logon scripts that are processed via Logon Scripts map drives succsesfully in almost any situation.

Periodically though it doesn't work, and now I discovered that for one particular group of users this is almost allways the case, and those are users that have a startup-link placed in their profile (<userprofile>\Start Menu\Programs\Startup).

Whats happening in the state of Denmark?
LVL 1
jmateknikAsked:
Who is Participating?
 
DaeltCommented:
Let the Run Logon Scripts synchronously to off

Stay in the same "System" tree of group policies :
- Check that Netlogon>Netlogon share compatibility is off or not configured
- Try enabling scripts>Run logon scripts Asynchronously, see the results

AND if I remove all user-data on a test-user with similar gropu policy settings, the drive is mapped.
Can you be more specific and give details please?
0
 
DaeltCommented:
i dont get it very clearly.

Did you copy a script on their (<userprofile>\Start Menu\Programs\Startup)?
What is the purpose of this special setting in this group only?

0
 
jmateknikAuthor Commented:
The terminal-server farm is a hosting-solution for our customers, that use the same specialized Navision product from their terminal sessions.

The script fails in rare cases/periodically for users, but for one particular group of users it fails often. This group of users have this URL in their profile\Start Menu\Programs\Startup folder.

The script has nothing to do with the URL being initiated from the startup folder, but the URL points to an intranet site outside the network.

Hope this clarifies...

0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
DaeltCommented:
do you see the login script window when it fails?

On good test to do is also to try to launch the script manually from one of this user session.
Try to launch it from the netlogon folder and try to launch it locally (paste the script file in their session)

You should be able to see if there is any problem executing the script into the cmd window.
0
 
jmateknikAuthor Commented:
do you see the login script window when it fails?
Nope, but I have tried enabling the policy 'Run logon scripts visible", and then it shows a commandprompt (the script is loaded)"
On good test to do is also to try to launch the script manually from one of this user session.
Try to launch it from the netlogon folder and try to launch it locally (paste the script file in their session)
Both scenarios maps the drive (runs the script correctly).

AND if I remove all user-data on a test-user with similar gropu policy settings, the drive is mapped.

I tried enabling the group policy "Run Logon Scripts synchronously" to .. [citat:] "..direct the system to wait for the logon scripts to finish running before it starts the Windows Explorer interface program and creates the desktop". This causes the script to not being run even without the URL in the startup-folder.

So - I'm still in trouble...
0
 
jmateknikAuthor Commented:
I found the culprit which hadn't anything to do with Group Policy, but simply our script calling a different script to set global uservariables, but since this script then runs synchronously with the "motherscript", unfortunately in some situations the variables are set, and some they're not.

I give you a good and partyially for your effort - thanks for trying to help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.