06-10-2009 03:45 PM
06-11-2009 08:17 AM
In my experience, the IVE calls the login script (slogic.bat) a bit prematurely. It's almost as if the network isn't quite "ready." Since the network isn't ready, the UNC path where your script lives is unavailble and therefore never executed.
The workaround which I've found works pretty well is to reference a script called "wait.bat" in your Network Connect settings. The script basically waits a few seconds, then calls slogic.bat. It delays the login a little, but it always works.
In regards to logging in, be sure your laptop is a member of the domain, or you're certainly encounter other Windows-specific issues. (E.g. locked out accounts, permissions issues, etc.)
Finally, it's also a good idea to make use of a logoff script as well. Just net use delete * (or whatever the syntax is) to delete mapped drives so that when users disconnect from NC, Windows Explorer isn't searching for dead drives every time the user opens My Computer.
06-11-2009 11:08 AM
Hey Crypto I forgot to add this.
When I enable GINA to launch Network Connect during log on it works fine!
When I try launching Network Connect manually (going to the website, logging in and launching) it executes the SLOGIC.bat but it doesn't map the default profile. This was when I was using LDAP as my authentication server I switched it over to Active Directory thinking that when I log in with my username and password it not only logs me into the network but also established like a domain logon.
Is it possible to run the slogic bat and map the drives by launching network connect? and in regards to the wait.bat is that a batch file that you manually created?