There are several ways to control the mode in which Desktop Authority executes on the client workstation. This is done with the use of option files that may exist on workstation.
An option file is simply an ASCII file created using any text editor, including Microsoft’s Notepad. The file has no contents and the filename has no extension.
The easiest way to create a special option file is using Windows Explorer. Right-click in the appropriate folder. Choose New and select Text Document from the shortcut menu.
When using Windows Explorer (New / Text Document) to create a Special Option File, make sure you deselect the Hide file extensions for known file types option under Folder Settings. This will allow you to create the file without the ".txt" extension.
To tighten overall security and prevent users/students, etc. from using these special option files to change the behavior of Desktop Authority, you can disable them in the Desktop Authority Manager. This is done in the Global Options Visual, Exceptions and Troubleshooting objects. Clearing the check box disables Desktop Authority from determining if the corresponding option file exists.
The presence of this file, (SLNOGUI., no file extension) specifies the selected visual startup option displayed during the logon process is overridden with a textual version of the logon window. If there are problems with any Desktop Authority client configurations, use this option file to figure out what in the logon process is problematic. The use of this file requires the Allow any client to override this setting and always display the text logon screen option to be set. This is done on the Visual object within Global Options.
To turn the SLNOGUI mode on for all clients without the use of this file, select the Display Text Logon check box on the Visual object within Global Options. Setting this global option provides the text dialog for all workstations.
This feature can be enabled for either a specific user or a specific workstation by using this special option file. To enable this feature for all users logging in from a specific workstation, place this file in the root directory of the workstation’s hard drive. To enable this feature for a specific user regardless of which machine they logon from, place this file in the user’s home directory.
The presence of this file, (SLBYPASS., no file extension) allows you to exclude certain computers from ever executing Desktop Authority regardless of the options selected in the Desktop Authority Manager.
The use of this file requires the Allow any client to selectively bypass Desktop Authority execution option to be set. This is done on the Exceptions object of Global Options. If this file is present on the client, the Desktop Authority Pre-Flight-Check (SLOGIC.BAT), will detect its presence and immediately exit before launching the main script engine and/or applying any configuration changes to the client.
To enable this feature for all users logging in from a specific workstation, place this file in the root directory of the workstation’s hard drive.
The presence of this file, (SLNOCSD., no file extension) allows you to exclude certain computers from automated Service Pack installations, regardless of the Validation Logic applied to the Service Pack configurations by the Desktop Authority Manager.
If this file is present on the client, Desktop Authority will NOT install the Service Pack to the client, regardless of whether or not the user/computer satisfies the criteria specified by the Validation Logic settings for the Service Pack.
To enable this feature for all users logging in from a specific workstation, place this file in the root directory of the workstation’s hard drive.
This option can be used by admins to delay the initial execution of user elements (eg. printers, drive mappings etc). In some cases, this will help to avoid login delays and potentially resolve timing conflicts. However for this option to be utilized, the applicable user object element MUST be set to be executed at Refresh. This option is configured in the Registry profile object.
Configure the Registry element as follows:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center