When users are logging in remotely through a VPN connection, they need to be able to run the Desktop Authority (DA) logon script (SLOGIC.bat).
Also when users log into their machines while off-network (using cached credentials) and establish a VPN connection to the network, Desktop Authority will not be executed.
Through the use of certain registry settings, Desktop Authority can be executed when a network connection (e.g., a VPN) is established.
With the implementation of the proper registry keys, the DA Client Service uses the Network Location Awareness (NLA) service to detect when a new network connection becomes available. Once the new connection is detected by the NLA service, Desktop Authority will be notified and can then determine whether it will execute for the user depending on the current configuration. Please note that the implementation varies depending on the Desktop Authority version:
Up to 10.x: It is required to create a registry element to propagate the settings or to do so manually on a per machine basis.
From 11.x: The Desktop Authority manager allows the administrators to configure the settings. They can be found on Client Configuration / Global Options / Network Location Awareness.
NOTE: Desktop Authority is initially configured not react to the events handled by the Network Location Awareness Service.For 32-bit operating systems, use: "HKLM\SOFTWARE\ScriptLogic";
For 64-bit operating systems, use: "HKLM\SOFTWARE\Wow6432Node\ScriptLogic".
These are the available options for the registry keys:
EnableNLA (REG_DWORD) = 0 (Disable) Default setting
= 1 (ON) - Enables or disables NLA for UBM and CBM.
= 2 (ON + Network disconnection detection). Only applies to DA 10.1+ and 10.0 hotfix after 448
Enables NLA as above and includes network disconnection and re-connection detection. The use case for this is when a user disconnects from the direct connect LAN and then goes to wireless. Desktop Authority will want to re-map printers, drives, etc.
NLAAltScript (REG_SZ) = Login.bat or Login,Login.bat,Slogic,Slogic.bat.
Desktop Authority will execute when a new network connection is detected. If the connection is dropped and then re-established within the amount of time state in the registry, Desktop Authority will not execute again.
NLAperiod (REG_DWORD) = 0 (Disabled), 1-86400 (in seconds, default is 1800 seconds/30 minutes)
When a new connection is detected, by default a Refresh even will be triggered, if you want to change that to Logon or Logoff, set the following registry
NLAUBMEvent (REG_SZ) = Logon, Logoff or Refresh (Default)
Dictates the event that shall be invoked. If Logon is specified, then the DA Client Splash screen will be displayed, however the DA Client Splash screen is not displayed during a Refresh event.
NLAUBMLocation (REG_SZ) = path of the logon script (Default - %logonserver%\Netlogon)
Specifies the location of where Slogic.bat resides. The default is "%logonserver%\\Netlogon". So if Slogic.bat is in the Netlogon folder then nothing needs to be specified. However, if Slogic.bat is being replicated to sub folder or different folder than Netlogon, like %logonserver%\\Netlogon\\DA, then the UNC (full) path needs to be configured.
For troubleshooting you can instruct Desktop Authority not to hide the command window when executing Desktop Authority.
NLAShowWindow (REG_DWORD) = 0 (Disable – Default) or 1 (Enable).
A value of "1" will force DA to show the client splash screen. However, if Logon is specified as the NLAUBMEvent then the DA Client Splash screen will be displayed, but the command prompt will not be.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center