I am trying to invoke nclauncher at Windows logon screen before user logon into WIndows. The nclauncher returns error "Unable to connect to the Secure Gateway. The Secure Gateway may not be configured to support NCLauncher." The nclauncher works when invoked after user logon into user profile. Similarly, invoking dsNetworkConnect.exe when logon into the Windows, its GUI pop up and works. However, invoking dsNetworkConnect.exe at Windows logon screen before logon into Windows, the GUI won't pop up at all. Since at Windows logon screen the SYSTEM user profile is being used, it may be some restrictions or limitation of the SYSTEM account even it is the superuser account.
Has anyone know what may be the reason and how to get this to work?
Thanks in advance for your help!
I use a custom credential provider to bring up a command prompt at Windows logon screen. From that command prompt, nclauncher command is invoked with the parameters that were previously verified using a user profile. I have not tried or enabled NC credential provider yet.
The goal is that if user has forgotten the domain password, he or she can login into vpn with VPN credential (different from domain credential) and be able to access some type of password reset self-service. Does the credential provider can help in this regard? Thanks!
After enable NC Credential Provider, the client application session can be established using VPN credential which is different from the domian credential. That means the client application session was established without logon into a user profile. It properly means nclauncher has a chance to work that way as well. Any hints how to make that happen?