The BigFix Query feature allows you to retrieve information and run relevance queries on client workstations from the WebUI BigFix Query Application or by using REST APIs. Getting client information by using BigFix Query.In air-gapped environments, to download and transfer files to the main BigFix server, use the Airgap utility and the BES Download Cacher utility. Downloading files in air-gapped environments.You can gather license updates and external sites by using the HTTP or HTTPS protocol on a BigFix server or in an airgapped environment.īigFix Console, Server and Relay components of the architecture perform high volume file operations. The BigFix server generates unique IDs for the objects that it creates: Fixlets, tasks, baselines, properties, analysis, actions, roles, custom sites, computer groups, management rights, subscriptions. Here are some of the important elements of multiple server installations: Starting from Version 9.5.5, BigFix supports SAML V2.0 authentication via LDAP-backed SAML identity providers. Enabling SAML V2.0 authentication for LDAP operators.You can add Lightweight Directory Access Protocol (LDAP) associations to BigFix. In BigFix there are two basic classes of users. BigFix Site Administrator and Console Operators.This guide explains additional configuration steps that you can run in your environment after installation. Messages are written to the windows event log (rather than a file) in: EventViewer > Application and Service Logs > AppDNA > Source = AppDNA Service.Learn how to configure BigFix according to your needs. In step 5, find or create the registry value QueueProcessorVerboseLogging. To enable verbose logging for the QueueProcessor service, follow steps 1-4 above. To disable the verbose logging, change the VerboseLogging registry value to 0.Ī similar process can be followed to turn on verbose logging for the Citrix AppDNA Service, QueueProcessor. Use a text editor to read the contents of the AppDNAVerboseLog.log file. Logs are captured separately for the client and server processes (unless they are running as the same user). By default this will be the build in "ApplicationPoolIdentity" and the temporary directory will be C:\windows\temp. Note that for the server processes this will be the temp directory for the identity that the AppDNAAppPool is running under in IIS. When AppDNA detects that this registry value has been set, it writes the verbose logs to %temp%\AppDNAVerboseLog.log. In the registry editor, browse to the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\AppDNA\appTitude\common\.įind or create the registry setting VerboseLogging (REG_DWORD) and change the value to 1. To enable verbose logging on the AppDNA server, complete the following procedure:Ī User Access Control dialog is displayed. Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
0 kommentar(er)
