Diagnostic Console Two-Factor Authentication (2FA) allows you to control access to the appliance back-end. When you enable SSH access to the appliance and create a tether, the Quest Support team can log in to the back-end of the appliance using the appliance root password together with an access token. Tokens are provided in the Initial Setup Wizard. They can be viewed and regenerated using the Diagnostic Console Two-Factor Authentication page in the appliance System Console. Each token can only be used once and must be given to the Quest Support contact before they can log in to the appliance through the tether or the console.
To navigate to this page, log in to the appliance System Console. On the left navigation bar, under Settings, click Support, and on the Support page, under Troubleshooting Tools, click Diagnostic Console Two-Factor Authentication.
• |
To replace the secret key and regenerate the offline tokens, click Replace Secret Key. |
• |
To regenerate offline tokens, click Regenerate Offline Tokens. |
Database table names can be used in reports and other database queries.
The following table lists organization-level (ORG1) database table names. Reference these table names when creating custom reports using SQL queries. See Create reports using SQL queries.
Service Desk: User Console | |
Service Desk: User Console | |
The following table shows the System-level (KBSYS) database table names. Reference these table names when creating custom reports using SQL queries. See Create reports using SQL queries.
Database table names can be used in reports and other database queries.
The following table lists organization-level (ORG1) database table names. Reference these table names when creating custom reports using SQL queries. See Create reports using SQL queries.
Service Desk: User Console | |
Service Desk: User Console | |
The following table shows the System-level (KBSYS) database table names. Reference these table names when creating custom reports using SQL queries. See Create reports using SQL queries.
You can add steps to scripts in the Scripting component.
The following tables detail the steps that can be added to the task sections of scripts. Task sections are available on the Script Detail page when you add a task. See Adding and editing scripts.
The column headings V, OS, R, ORS, and ORF indicate whether a particular step is available in the corresponding task sections: Verify, On Success, Remediation, On Remediation Success, and On Remediation Failure.
For example, specify the path for HKEY_LOCAL_MACHINE for 32- and 64-bit Windows devices as follows:
Search for "%{name}" in "%{startingDirectory}" on "%{drives}" and "%{action}". |
||||||
Set the text in the message window named "%{name}" to "%{text}". |
||||||
Verify that the file "%{path}\%{file}" was modified since "%{expectedValue}". |
||||||
Search for "%{name}" in "%{startingDirectory}" on "%{drives}" and "%{action}". |
||||||
Verify that the file "%{path}\%{file}" was modified since "%{expectedValue}". |
||||||
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center