Im attemtping to call a login script script from a batch file, but i cant seem to get it to work. When I point the user role to the startup script at \\server\share, the log indicates it attempts to execute the file, but nothing happens. It appears that it attempts this call before intializing the connection, so it fails out. If I place the same script onto the users local drive and point the startup script location to it, it works. I know its possible to use a UNC path for startup scripts, but I cant seem to accomplish this. How have others accomplished this?
Any ideas on this? i dumped the file locally on the PC's i needed it, but is there a good way to call this via UNC path?
I found those KB articles when I was initially researching the issue, but the solution in them is to place the script locally to then call the remote script at the UNC path. It sort of defeats the purpose of having the UNC script at all. I want to invoke the UNC script directly, not launch a local script that calls a unc script.
Hi Antioch, not sure if this will help you but you are welcome to try. We had the exact same issue when we first launches Pulse 5.0.2. There were a few things we did: Add a delay into the login script so it gives Pulse a chance to execute login before calling the script, allow ESP on the firewall with 'no fallback to SSL', and finally, we removed location awareness.
Hope it helps.
How can a startup script be delayed? There is no option to do it from the admin console, and I can't put a delay into the .bat file becasue it never opens it. I should have specified that I am doing this via the web portal and WSAM, we dont use the pulse client. So if its possible to put a delay within the pulse client this is not available in the web portal.
Im using WSAM through the web portal, We do not use the pulse client at all, ever. I'm not sure if this is considered legacy or not, but my guess is that it is.So there is no way to launch a .bat file from a unc path? That is very poor design.
This should work. Is there anything in the debuglog.log stating an issue with the bat file? It should attempt to copy the bat file from the network drive to the local temp directory, then try to launch it.