Go Premium for a chance to win a PS4. Enter to Win


Server 2008 Terminal Servicer user SLOW login and access to mapped network drive to server 2003

Posted on 2012-03-26
Medium Priority
Last Modified: 2013-11-21
I've added a windows server 2008 terminal server to a windows server 2003 domain. When RDPing into ts2008 from lan or logging in at the console the logon script (which resides on the 2003 DC, NETLOGON share) takes a while to start (well after desktop is displayed), and then runs very slowly. The script simply deletes 5 drives net use f: /delete..... and then maps 5 drives   net use f: \\appsrv01\path

During RDP Logon when the script finally starts, takes about 40 seconds to complete.

Once logged on, if the script is run manually, takes about 2 seconds, but access to files over the mapped drive(s) is slow.

Loading programs from our app server through the mapped drive takes Minutes rather than seconds.

The 2008 TS will replace our current 2003 TS, which has the same logon script, same mappings but everything smooth and fast....

Any advice? or more info required? Perhaps a DNS problems but DNS looks OK
...scratching my head
Question by:djyule
  • 5
  • 2
  • 2
  • +1
LVL 29

Expert Comment

ID: 37789387
I'm probably not going to tell you anything you want to hear,...but you really need to ween the users off of the whole idea of Mapped Drives and get them thinking in terms of "Network Locations" instead of expecting something to be on a "Drive Letter" somewhere.  The whole idea of a "Mapped Drive" is a left-over curse foisted upon the world by Novell back in the 1990s.

Mapped Drives, by the very nature of how they work, are horrible on performance and how they occupy resources in the networking layers of the OS.  They always have been,..and they always will.  They drag down Windows Explorer every time a "Browse" dialog box is called up because the OS has to scan the "drive" to show the contents even if it isn't the drive you are looking for at that moment in time.

Instead use Shortcuts based on the UNC Network Path.  Point the Shortcut to the Server itself (not any Shares),...the Shares will show up as "Folders" after the Shortcut is opened and the NTFS Permission will control what the user has access to.  Put the Shortcut in the "All Users" Desktop.  Change the Icon of the Shortcut to look like a Folder icon or a Network Attached Folder icon.  When the user opens a Browse Dialog to they go to the "Desktop" and it will look and behave just as if it was a "Folder" on their desktop.  There is absolutely no performance loss at all in any way,..and they do not occupy any resources or hold a "connection" when they are not being used.  They do not require any action within any Login Scripts, Startup Scripts, Batch Files, or anything else.  The Shortcuts will also help correct the User's thinking in terms of Resources being stored in Locations as technology moves into the future,...drive letters are certainly not the future.  

What are you going to do if you end up with more that 23-24 locations?,...there aren't that many letters in the alphabet left after you subtract out the local drives, memory card readers, Thumb Drives, USB Hard Drives, and anything else that create a temporary drive letter while it is connected!

Author Comment

ID: 37789451
Thanks for your reponse. I of course agree with your assessment of "mapped drives", and would get rid of them if the 3rd party application that my users use didn't depend on them. My users don't browse the network, pretty much just run the application.

Major issue seems to be related to either the domain active directory, dns, or combination of both.

Current system looks like this:

2003 server running Terminal Services.

2003 file server also domain controller.

Each TS user runs the same login script stored in the domain controller NETLOGON share

Logon script simply maps 5 file server drives.

When a user logs in to TS, the login script runs immediately and quickly.

When user starts their application which resides on the file server/mapped drive, application starts immediately.

NEW scenario looks like this:

2008 server running Terminal Services added to the domain.

Everything else the same.

When user logs in to TS, the login script does not start until a significant delay after the desktop is displayed, then takes 40-50 seconds to complete.

When user starts their application (still residing on the 2003 server/mapped drive), application takes 1-2 minutes to start..

My expectation was that timing for a server 2008 TS login would be at least the same as the 2003 TS login, and that file access would be at least the same.

I've tried many "solutions" based on other similar problems/posts and have not yet landed on an answer that makes any difference.
LVL 32

Expert Comment

ID: 37791467
My suggestion:
Don't delete and remap your drives every time.  Create one logon script as this example:
net use x: \\servernName\shareName /persistent:no  By using the /persistent:no means that when you logoff, the drive will be deleted.

I use mapped drives all the time and they just work great and don't have these performance hits but everyone's different :)
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.


Author Comment

ID: 37791763
Thanks nappy_d, makes sense..I'll do this.

Any suggestion on why the logon script itself takes so long to even fire up? As mentioned on my 2003 terminal server logon, it's virtually immediate and fast, just a problem on the 2008 terminal server logon.
LVL 32

Expert Comment

ID: 37791924
Can you post the contents of your current logon scripts?

Do you have roaming profiles?

How large are the users profiles?

Author Comment

ID: 37792140
net use f: /delete
net use g: /delete
net use h: /delete
net use i: /delete
net use f: //appsrv01/policyworks
net use g: //trmsrv01/applied
net use h: //appsrv01/tam_data
net use i: //appsrv01/tam_images

Only difference when logging on from the 2008 terminal server is g: is mapped to //trmsrv02/applied

trmsrv01 is windows server 2003 with TS, appsrv01 is windows server 2003 (domain controller)

trmsrv02 is the new windows server 2008 with TS.

Profiles are on the terminal server, users log on from thin clients.

In the grand scheme of things, profiles are not large. Biggest file would be their outlook .pst files.

Again, no problems logging in to the 2003 terminal server, just the 2008 terminal server...
LVL 29

Expert Comment

ID: 37796779
I of course agree with your assessment of "mapped drives", and would get rid of them if the 3rd party application that my users use didn't depend on them.

Half the time those 3rd parties are wrong when they claim their App needs a Mapped Drive.  I 12 years I have only found one that truly required the mapped drive, and a second one that was a "fuzzy" maybe.  Sometimes you just have to try it instead and find out for yourself.

Expert Comment

ID: 37808828
Something is failing.   Did you look in the Windows Event Logs?  Win2K8 RDServices is good about logging all sorts of errors, warning and information.

Accepted Solution

djyule earned 0 total points
ID: 37858375
Turns out it was bad NIC driver. Updated and all is well.

Thanks for your input.

Author Closing Comment

ID: 37877383
Always something simple....bad NIC driver.

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

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

I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Suggested Courses

916 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