This content has been marked as final. Show 3 replies
SBGINA needs to be the first in the chain normally. Enabling the VPN likely moves it from the front and put's its own Gina in place. If there are switches to enable the VPN not to put its dll in front, then use those, then tell EEPC/SafeBoot to pass the logon details on to it (see SBGINA.ini).
Or you can disable the SSO options in EEPC/SafeBoot completely, and also override any behaviour for EEPC to force itself in the front of the chain. See the admin guide for the registry entry settings to force that.
thanks for the info, as I'm not sure exactly what secure client is trying to do I'll look at disabling the SSO options in the reg
OK - had a quick look at the ini files, but slightly in the dark as to what needs changing, any other info?