Published App

[MikeW]

I have a published app on our system (well hope so...) that keeps giving out an error. The second time I go to run the app, it runs like a charm, so I've narrowed it down to the fact that the app starts running before the system logs the user in to the network fully.

Any ideas on how I can change that. I tried to set the GPO "run logon scripts synchronously" however, that doesn't seem to do anything for Win2K3 Server.

 

[nixu]

By any chance are you running a published application from mapped network drive??

Nixu

 

[MikeW]

More or less.

I simply did a drag and drop of the shortcut from the TS Agent to the Gateway/App Server. Below are the properties

Target: \\<servername>\d$\FSTHIN\SYSTEM\FSGUIAPP.EXE
Start In: T:\
Parameters: -N ServerName 5442 -C T:\Mfgsys\fsWSSBC.cfg -A monitor.dll

T: is the mapped drive of course.

The only thing I can think of doing is creating a quick VBScript that starts off with a sleep command and then invokes the app itself. Is there a more simple way?

 

[nixu]

Hi there,

Although I do not like having a script that sleeps and then runs the application, It should work...

Just for your information..
If you run an application from a mapped network drive, the system will wait for that drive to load before running the application, but in your case the data file is on the mapped network drive and not the application.

Nixu

 

[MikeW]

Thanks nixu... That actually fixed the problem.

If you run an application from a mapped network drive, the system will wait for that drive to load before running the application, but in your case the data file is on the mapped network drive and not the application.

I actually changed the target.

OLD Target: \\<servername>\d$\FSTHIN\SYSTEM\FSGUIAPP.EXE
NEW Target: M:\Mfgsys\System\fsguiapp.exe

Where OLD shows FSTHIN...The application, when installed gives you an option to change the shortcut so it loads faster... I changed it fully to run off the mapped network drive after seeing your last answer (and after searching the forums and saw that the mapped drive/published app issue was fixed in a previous version (I'm evaluating v6x)).

All works great now! Thanks Again