Solved

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

Posted on 2011-09-05
6
467 Views
Last Modified: 2012-05-12
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?
0
Comment
Question by:jmateknik
  • 3
  • 3
6 Comments
 
LVL 4

Expert Comment

by:Daelt
ID: 36483127
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
 
LVL 1

Author Comment

by:jmateknik
ID: 36483317
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
 
LVL 4

Expert Comment

by:Daelt
ID: 36483398
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
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 1

Author Comment

by:jmateknik
ID: 36483779
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
 
LVL 4

Accepted Solution

by:
Daelt earned 500 total points
ID: 36484076
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
 
LVL 1

Author Closing Comment

by:jmateknik
ID: 36486939
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

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
Synchronize a new Active Directory domain with an existing Office 365 tenant
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now