We have alleviated this issue by writing a script that waits for the mapped drive, then launches a shortcut to the application. This will work 99% of the time (you will very rarely get an error). I cannot speak for version 5's ability to do this on its own.
Code:
' Application Launching Script Version 1.0
Sub Delay(DelaySeconds)
SecCount = 0
Sec2 = 0
While SecCount < DelaySeconds + 1
Sec1 = Second(Time())
If Sec1 <> Sec2 Then
Sec2 = Second(Time())
SecCount = SecCount + 1
End If
Wend
End Sub
' Initialize File System Object
Set filesys = CreateObject("Scripting.FileSystemObject")
s=0
Do Until filesys.DriveExists("X:")
s=s+1
Delay 1
If s=10 Then Exit Do
Loop
If filesys.DriveExists("X:") Then
Dim objWshShell
Set objWshShell = CreateObject("WScript.Shell")
objWshShell.Run """C:\Program files\Program\program.lnk"""
Set objWshShell = nothing
Else
'Give user error
msgbox "Unable to locate file. Please try again. If the issue persists, please contact support."
End If
You'll want to change this line:
Code:
objWshShell.Run """C:\Program Files\Program\Program.lnk"""
and place the path to your program. You will also need to replace x: anywhere you see it with the network drive letter you are using. Creating a shortcut to launch from this code actually seems to work much better than pointing directly to the executable on the mapped drive. The line
Code:
If s=10 Then Exit Do
means the script will wait for 10 seconds before timing out. Change that line to the wait you are comfortable with.
Just paste the code into a text file and save as a .vbs file, and point the appserver to the .vbs file on the terminal server (I usually create a folder in Program Files and set permissions accordingly)
