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

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
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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, 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!
djyuleAuthor Commented:
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.
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
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 :)
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

djyuleAuthor Commented:
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.
nappy_dThere are a 1000 ways to skin the technology cat.Commented:
Can you post the contents of your current logon scripts?

Do you have roaming profiles?

How large are the users profiles?
djyuleAuthor Commented:
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...
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.
Something is failing.   Did you look in the Windows Event Logs?  Win2K8 RDServices is good about logging all sorts of errors, warning and information.
djyuleAuthor Commented:
Turns out it was bad NIC driver. Updated and all is well.

Thanks for your input.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
djyuleAuthor Commented:
Always something simple....bad NIC driver.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.