Windows 2003 Terminal Services Logon Script / Application Issue

I am trying to setup a 2003 Terminal Server.  I want the sessions to launch a program upon logon, however, the application depends on mapped drives.  The application launches before the computer can finish mapping the drives and causes an error.

Is there any way to slow the application launch after login part down, or is there another way around this?
Who is Participating?
Set the Group Policy setting to run logon scripts synchronously, and put the drive mappings in \Windows\System32\USRLOGN1.CMD (create it if it's not there. It's called by Usrlogon.cmd)

The Group Policy options is in User Configuration - Administrative Templates\System\Scripts

If you apply this to an OU containing the server, you'll also need to set "User Group Policy loopback processing mode" to "Merge" or "Replace", which is in Computer Configuration - Administrative Templates\System\Group Policy
coxcomputerAuthor Commented:
Forgot to mention, the mapped drives are coming from a script that is launched domain wide upon user login.
Hi coxcomputer,

im fairly sure that if you can put the application in the startup folder rather than in the script, that SHOULD solve your problem - if not can you alter your script to make it "not run until...."

coxcomputerAuthor Commented:
I changed the Group Policy options for the Domain as a whole, now the script runs properly before the application is launched.  Thanks Darwinian.
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.