© 2022 Quest Software Inc. ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.
The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document..
If you have any questions regarding your potential use of this material, contact:
Quest Software Inc.
Attn: LEGAL Dept
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (https://www.quest.com) for regional and international office information.
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.
Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx. All other trademarks and registered trademarks are property of their respective owners.
Warning: A WARNING icon indicates a potential for property damage, personal injury, or death.
Caution: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.
Desktop Authority Administrator Guide
Updated - January 2022
Software Version - 11.2.1
In order for the profiles and configuration elements to be processed for users or computers, Desktop Authority must qualify whether a setting should be applied to the client. To do this, a set of rules is created for every profile and configuration element within the Manager. This set of rules, which includes the definition of connection types, class types, operating systems and many other types, is called Validation Logic.
During the logon/logoff, startup/shutdown, refresh, or custom schedules, the Validation Logic of each profile is inspected. If the Validation Logic matches the client environment, the profile is marked for processing. Once each profile's Validation Logic is evaluated, the Validation Logic for all configuration elements in the marked profiles is evaluated. When complete, the resulting qualified configuration elements are executed on the client in the following order.
It is important to keep in mind that not all configuration elements will be executed on a client just because its profile passes the validation test. This is due to the secondary validation logic that is provided on individual configuration elements. If a configuration element has no validation logic rules defined and its profile passes the validation test, the configuration element will automatically be processed on the client.
Use the boxes on the Validation Logic and Validation Logic Rules pages to define the specific rules, classes, operating systems and connection types (not applicable to Computer Management objects), timing (timing is on a separate tab for the Computer Management objects), virtualization, platform and network connection that the rules will apply to.
When the Validation Logic Rules list includes more than one rule, Boolean logic is used between each of the rules to obtain a result. Select either the AND or OR option below the validation logic rules list. The selected logic will apply to all rules defined in the list.
Select this check box to temporarily disable the selected configuration element from executing. Clearing the box will re-enable the configuration setting.
Check this box to execute an element if the computer is running the Windows 7 operating system.
Check this box to execute an element if the computer is running the Windows 8.1 operating system.
Check this box to execute an element if the computer is running the Windows 10 operating system.
Check this box to execute an element if the computer is running the Windows 2008 operating system.
Check this box to execute an element if the computer is running the Windows 2008 R2 operating system.
Check this box to execute an element if the computer is running the Windows 2012 operating system.
Check this box to execute an element if the computer is running the Windows 2012 R2 operating system.
Check this box to execute an element if the computer is running the Windows 2016 operating system.
Check this box to execute an element if the computer is running the Windows 2019 operating system.
Check this box to execute a script element if the computer is directly connected to the network.
Check this box to execute a script element if the computer is connected to the network via a dial-up connection. A dial-up connection includes RAS and VPN connections, provided the client used a dial-up networking session to make the connection.
To disable a specific script element from being processed, clear the Dial-up and LAN connection types. You will be warned that the entry will not execute without at least one of the connection types selected. The entry will appear in gray text to illustrate it has been disabled.