Merge pull request #452 from ritza-co/19.06.06

Docs 19.06.06 release (Week 24, 2025)

Author: sixhobbits

docs/administration/appliance-manager/api-limits.mdx

@@ -3,8 +3,8 @@ title: "API Limits"
 sidebar_position: 2
 ---
 
-Released in 18.08.00, there is a now a setting in the Appliance Manager that will limit how many remote agents can attempt to update at once. This is intended for customers with hundreds of agents so that those agents will not simultaneously attempt to update causing the Main Appliance to be overloaded.
+From the Appliance Manager, you can set a limit on the number of remote agents that can attempt to update at once. This option is intended for administrators who have hundreds of agents and need to prevent those agents from simultaneously attempting to update, possibly causing the Main Appliance to become overloaded.
 
-The default setting for the API limit is 16 concurrent agent updates. Customers can configure this number to best suit their needs, between 8 and 128.
+The default setting for the API limit is 16 concurrent agent updates. You can configure this number to best suit your needs, choosing a value between `8` and `128`.
 
-![](/assets/images/API-Limits-700x733.png)
+![](/assets/images/api-limits/api-limits.png)

docs/administration/appliance-manager/enabling-ssl-in-appliance-manager.mdx

@@ -3,14 +3,15 @@ title: "Enabling SSL in Appliance Manager"
 sidebar_position: 9
 ---
 
-# Enabling SSL in Appliance Manager
+Device42 now has the ability to use HTTPS in the Appliance Manager, in addition to the existing HTTPS in the Main Appliance.
 
-Device42 now has the ability to use HTTPS in the Appliance Manager in addition to the existing HTTPS in the main appliance.
+To enable this functionality, log in to the Device42 Appliance Manager by clicking the link at the bottom of the main login page and entering your Device42 credentials. The default username and password for the Appliance Manager are `d42admin` and `default`. For details about which URL to use and how to update the default password, see [Appliance Manager Login](device42-appliance-manager-login.mdx).
 
-To enable this functionality, log into the Device42 Appliance Manager by clicking the link at the bottom of the main login page, and entering your Device42 credentials. The default name and password for the Appliance Manager is d42admin/default. ![Appliance Manager Login](/assets/images/2015-12-17-Appliance-Manager-SSL-04.png)
+- From the main menu (left panel) of the Appliance Manager, select **Appliance Manager SSL**: 
+- Check **Enable HTTPS** to enable SSL and click **Set**. You'll see a success message prompting you to restart the appliance from the VM console.
 
-From the main menu on the left side of the Appliance Manager, select "Appliance Manager SSL": ![Appliance Manager SSL](/assets/images/2015-12-17-Appliance-Manager-SSL-06.png)
+    ![HTTPS enabled](/assets/images/enabling-ssl-in-appliance-manager/appliance-manager-ssl.png)
 
-This will bring you to a screen with the option to enable SSL. ![HTTPS enabled](/assets/images/2015-12-17-Appliance-Manager-SSL-02.png)
+- Log in to the VM console and select **Reboot Server**. 
 
-Upon doing so, you will see a success message at the bottom, and will need to restart the appliance by logging into the console and selecting option 4. ![Reboot appliance](/assets/images/2015-12-17-Appliance-Manager-SSL-01.png)
+    ![Reboot appliance](/assets/images/enabling-ssl-in-appliance-manager/console-reboot-services.png) 

docs/administration/appliance-manager/generate-log-bundle.mdx

@@ -1,41 +1,41 @@
 ---
-title: "Generate log bundle"
+title: "Generate Log Bundle"
 sidebar_position: 10
 ---
 
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-To generate log bundle for a support call:
+If you are experiencing issues with discovery, you can generate a log bundle and send it to support for further analysis.
 
-1. If you are experiencing autodiscovery issues, enable debug in the discovery job settings. For issues unrelated to autodiscovery, keep debug mode off and proceed to step three.
+1. Edit the discovery job and set the debug mode to **Debug On**. For issues unrelated to autodiscovery, you can keep debug mode off and proceed to Step 3.
 
     <ThemedImage
     alt="Enable debug by editing discovery job settings"
     sources={{
-        light: useBaseUrl('/assets/images/generate-log-bundle/discovery-job-enable-debug-light.png'),
-        dark: useBaseUrl('/assets/images/generate-log-bundle/discovery-job-enable-debug-dark.png'),
+        light: useBaseUrl('/assets/images/generate-log-bundle/edit-debug-level-light.png'),
+        dark: useBaseUrl('/assets/images/generate-log-bundle/edit-debug-level-dark.png'),
     }}
     />    
 
-2. If your issue is autoDiscovery related, re-run the failing autodiscovery job now that you've enabled the debug flag.
-3. Login to the appliance manager via the main menu, **Tools > Appliance Manager** or follow the [Device42 Appliance Manager login](device42-appliance-manager-login.mdx) directions.
+2. If the issue is discovery-related, rerun the failing discovery job now that you've enabled the debug flag.
+3. Log in to the Appliance Manager via the main menu, **Tools > Appliance Manager**, or by following the [Device42 Appliance Manager Login](device42-appliance-manager-login.mdx) directions.
 4. Generate the log bundle via the Appliance Manager. Navigate to **Application > Generate Log Bundle** and click **Run**.
 
-    ![Generate Log Bundle via Appliance Manager](/assets/images/generate-log-bundle/am-generate-log-bundle.png)
+    ![Generate Log Bundle via Appliance Manager](/assets/images/generate-log-bundle/generate-log-bundle-19.06.png)
 
 5. Upload the generated log file at [upload.device42.com](https://upload.device42.com/).
 
 ### Remote Collector Log Bundle
 
-If you were also using the Remote Collector (RC) for the job, please get and upload the RC log using the [same upload link](https://upload.device42.com/) above. 
+If you were also using the Remote Collector (RC) for the job, please get and upload the RC logs using the [same upload link](https://upload.device42.com/) above. 
 
-Navigate to **Discovery > Remote Collectors** and click on the **Logs** link for the corresponding RC under the **Actions** column. Let us know when the file has been uploaded and we'll continue investing the issue.
+Navigate to **Discovery > Remote Collectors** and click on the **Logs** link for the corresponding RC under the **Actions** column. Let us know when the file has been uploaded, and we'll continue investigating the issue.
 
 <ThemedImage
-  alt="Download RC log button"
+  alt="Download RC logs button"
   sources={{
-    light: useBaseUrl('/assets/images/generate-log-bundle/rc-log-download-light.png'),
-    dark: useBaseUrl('/assets/images/generate-log-bundle/rc-log-download-dark.png'),
+    light: useBaseUrl('/assets/images/generate-log-bundle/rc-log-download-19.06-light.png'),
+    dark: useBaseUrl('/assets/images/generate-log-bundle/rc-log-download-19.06-dark.png'),
   }}
-/>
+/>

docs/administration/appliance-manager/generating-ipmi-output-for-troubleshooting.mdx

@@ -3,12 +3,13 @@ title: "Generating IPMI output for troubleshooting"
 sidebar_position: 11
 ---
 
-You can collect IPMI output for a device right from the GUI and send us the output for further troubleshooting.
+You can collect Intelligent Platform Management Interface (IPMI) output for a device right from the Appliance Manager GUI and send us the output for further troubleshooting.
 
-### Collect IPMI output
+## Collect IPMI Output
 
-![Collect IPMI output](/assets/images/2016-04-07-Generate-IPMI-output-01.png)
+[Log in to the Appliance Manager](device42-appliance-manager-login.mdx), and navigate to **Application > Generate IPMI Output**.
 
-Go to: Application > Generate IPMI output
+![Collect IPMI output](/assets/images/generating-ipmi-output-for-troubleshooting/generate-ipmi-output.png)
+
+Add the **FQDN or IP Address**, **Username**, and **Password**, and click **Generate**. The file will take a few minutes to generate. Once downloaded, please send us the generated file.
 
-Add the FQDN or IP address, name and password, click generate, wait as it might take few minutes and send us the file it generates.

docs/administration/appliance-manager/global-and-password-manager-session-timeout.mdx

@@ -1,20 +1,41 @@
 ---
-title: "Global and Password manager session timeout"
+title: "Global and Password Manager Session Timeout"
 sidebar_position: 12
 ---
 
-The global session timeout in device42 is set to 30 minutes by default and can be changed as discussed below. Password pages have an additional check for inactivity time (for enhanced security) and if user is inactive for a minute, it logs them out of the session.
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
 
-### Global session timeout
+By default, the global session timeout in Device42 is set to 30 minutes. You can change it from the [Appliance Manager](device42-appliance-manager-login.mdx).
 
-![wpid2153-Global_session_timeout.png](/assets/images/wpid2153-Global_session_timeout.png)
+For enhanced security, pages containing Secrets and credentials have an additional check for inactivity – if a user is inactive for 500 seconds (8 minutes), it logs them out of the session. You can change this setting from the Main Appliance.
 
-Global session timeout can be set between 1 to 60 minutes as shown above. Once you choose and save optimal value for you, you will need to restart the application to see the new session timeout in effect.
+## Global Session Timeout
 
-### Password pages inactivity timer
+You can set timeout values for the Main Appliance and Appliance Manager:
 
-All password pages(list, view, edit etc.) also have an inactivity timer. If there is no mouse or keyboard activity for 1 minute, the user will be logged out of the session.
+- [Log in to the Main Appliance](device42-appliance-manager-login.mdx) and navigate to **Global Settings > Set Inactivity logout time**. 
 
-You can change the password page inactivity timer from main app from Tools > Settings > Password timeout.
+- Set a new value (in minutes) for the session timeout. 
 
-The global session timeout is independent and must be changed separately.
+  ![Global Session timeout](/assets/images/global-and-password-manager-session-timeout/global-inactivity-timeout.png)
+
+- Once you have chosen and saved the optimal value(s) for your purposes, you need to restart the application to bring the new session timeout into effect.
+
+## Password Pages Inactivity Timer
+
+All password pages (the list, view, and edit pages) also have an inactivity timer. If there is no mouse or keyboard activity for 500 seconds (8 minutes), the user will be logged out of the session.
+
+- You can change the password page inactivity timer from the Main Appliance, under **Tools > Settings > Global Settings**. 
+
+- Set a new **Password Timeout** value (in seconds) under the **Secrets** section. 
+
+<ThemedImage
+  alt="Secrets section of Global Settings"
+  sources={{
+    light: useBaseUrl('/assets/images/global-and-password-manager-session-timeout/global-settings-password-timeout-light.png'),
+    dark: useBaseUrl('/assets/images/global-and-password-manager-session-timeout/global-settings-password-timeout-dark.png'),
+  }}
+/>
+
+Note that the appliance global session timeouts are different from the password page inactivity timers and must be changed separately.

docs/administration/appliance-manager/pendo-guided-tours-and-usage-information-collection.mdx

@@ -3,11 +3,14 @@ title: "Guided Tours and Usage Information Collection"
 sidebar_position: 14
 ---
 
-Device42 collects certain usage information to help us better assist users, prioritize future product updates, and provide guided product tours for Device42 features.
+Device42 collects certain usage information to better assist users, prioritize future product updates, and provide guided product tours of Device42 features.
 
-You can use the Device42 Appliance Manager to disable the collection of usage data if you so choose.
+You can use the Device42 Appliance Manager to disable the collection of usage data, which will also disable guided product tours, as usage data is needed for guided Device42 tours. However, you can keep usage metric sharing enabled and opt out of guided tours.
 
-- Log into the Appliance Manager, and select _Global Settings_ and then _Misc. Settings_.
-- Uncheck _Allow guided product tours (shares usage data)_ and then click _Update Settings_.
+- [Log in to the Appliance Manager](device42-appliance-manager-login.mdx), and navigate to **Global Settings > Misc. Settings**.
 
-![](/assets/images/D42-25467_pendo-setting-in-app-mgr.png)
+- To disable the collection of usage data, uncheck the **Allow usage metric sharing** option – the **Allow Guided Product Tours** option will also be disabled.
+- To opt out of guided tours, uncheck the **Allow Guided Product Tours** option.
+- Click **Update Settings** to save your changes.
+
+![Misc. Settings in Appliance Manager](/assets/images/pendo-guided-tours-and-usage-information-collection/misc-settings-appliance-manager.png)

docs/administration/appliance-manager/set-fqdn-for-web-access.mdx

@@ -3,6 +3,10 @@ title: "Set FQDN for Web Access"
 sidebar_position: 16
 ---
 
-![](/assets/images/set-fqdn.png)
+You can limit access to the Device42 Main Appliance to a specific FQDN. Using this setting will prevent anyone from accessing Device42 via IP address or another hostname or domain.
 
-Use this feature to restrict access to Device42 application (web UI) to a specific FQDN. Use of this setting will deny access to Device42 via IP address or other hostname and/or domain.
+[Log in to the Appliance Manager](device42-appliance-manager-login.mdx), then navigate to **Global Settings > Set Hostname for Web Console**. 
+
+Enter the FQDN you want to use, check **Enable Hostname Checking**, and click **Submit**. 
+
+![](/assets/images/set-fqdn-for-web-access/set-hostname-for-web-console.png)

docs/administration/appliance-manager/setting-up-backup-device42-appliance-manager.mdx

@@ -163,15 +163,18 @@ find /device42/backup/directory -type f -mtime +7 -delete
 
 For Windows Servers, the following PowerShell script can be used to delete files older than seven days from the targeted directory:
 
-```
-# Delete all Files in C:temp older than 7 day(s)
-
-$Path = "C:device42backups"
-$Daysback = "-7"
-$CurrentDate = Get-Date
-$DatetoDelete = $CurrentDate.AddDays($Daysback)
-Get-ChildItem $Path | Where-Object { $_.LastWriteTime -lt $DatetoDelete } | Remove-Item
-```
+<details>
+  <summary>Click to expand the code block</summary>
+  ```
+  # Delete all Files in C:temp older than 7 day(s)
+
+  $Path = "C:device42backups"
+  $Daysback = "-7"
+  $CurrentDate = Get-Date
+  $DatetoDelete = $CurrentDate.AddDays($Daysback)
+  Get-ChildItem $Path | Where-Object { $_.LastWriteTime -lt $DatetoDelete } | Remove-Item
+  ```
+</details>
 
 ## Restore the Backup
 

docs/administration/appliance-manager/update-device42.mdx

@@ -3,9 +3,9 @@ title: "Updating Device42"
 sidebar_position: 18.5
 ---
 
-When you log in to the Appliance Manager you'll see two methods for updating your Device42 Main Appliance. You only need to complete one of the options.
+When you [log in to the Appliance Manager](device42-appliance-manager-login.mdx) and go to **Application > Update Software**, you'll see two methods for updating your Device42 Main Appliance. You only need to complete one of the options:
 
-![](/assets/images/update-device42/updgrade-options-AM.png)
+![](/assets/images/update-device42/updgrade-options-AM-19.06.png)
 
 - **Enter URL:** Enter the provided URL from the update notification and click **Download**.
 - **Upload D42 upgrade package:** 
@@ -14,12 +14,16 @@ When you log in to the Appliance Manager you'll see two methods for updating you
   - Head back to the Appliance Manager and **Browse** your machine for the downloaded package file.
   - Click **Upload** and wait for the progress bar to complete.
 
-The URL option automates the process of downloading and uploading the upgrade package. The manual upload option is available for when you've already downloaded the package file or are using an instance without internet access.
+The URL option automates the process of downloading and uploading the upgrade package. The manual upload option is available for when you have already downloaded the package file or when you are using an instance without internet access.
 
 In both cases, a green status message will appear instructing you to complete the upgrade from the VM console.
 
 ### Apply the Update
 
-From the VM console, enter option **3**.
+From the VM console, enter option **(a) Apply Update**:
 
-![](/assets/images/update-device42/vm-console-options.png)
+- Click **Yes** to confirm the upgrade process.
+- Wait for the process to complete.
+- Once the update is applied, you can log in to the Device42 Main Appliance and go to **Tools > Settings > Update** to verify the new version number. 
+
+![](/assets/images/update-device42/vm-console-options-19.06.png)

docs/administration/auto-clean-feature.mdx

@@ -118,8 +118,6 @@ Build search criteria for the selected object type using the basic dropdown filt
 
 Select the actions to perform on CIs matching added object types and its criteria. The available Auto Clean Rule **Action** options vary depending on which **Object type** you select for the rule. The example below shows the action options for Device objects.
 
-![](/assets/images/AutoClean-device-action-options.png)
-
 <ThemedImage
   alt="Auto Clean Rules Action options for Devices"
   sources={{