Merge pull request #329 from ritza-co/docs-18.14.2

Docs v18.14.2 release (week 15, 2024)

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

@@ -0,0 +1,25 @@
+---
+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.
+
+![](/assets/images/update-device42/updgrade-options-AM.png)
+
+- **Enter URL:** Enter the provided URL from the update notification and click **Download**.
+- **Upload D42 upgrade package:** 
+  - Click the **Check for latest version** link or visit the [Device42 update page](https://www.device42.com/update) and enter your name, surname, and email address.
+  - Download the update package using the "Device42 MA Update File" link emailed to 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.
+
+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**.
+
+![](/assets/images/update-device42/vm-console-options.png)

docs/auto-discovery/microsoft-dhcp-discovery.md → docs/auto-discovery/microsoft-dhcp-discovery.mdx

@@ -3,21 +3,36 @@ title: "Microsoft DHCP Discovery"
 sidebar_position: 4.8
 ---
 
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
 # Microsoft DHCP Discovery
 
 As of v18.14, Microsoft DHCP Discovery has been added as an additional discovery type located under **Discovery > DHCP**. 
 
+<ThemedImage
+  alt="DHCP menu location and list page"
+  sources={{
+    light: useBaseUrl('/assets/images/microsoft-dhcp-discovery/dhcp-menu-and-list-page-light.png'),
+    dark: useBaseUrl('/assets/images/microsoft-dhcp-discovery/dhcp-menu-and-list-page-dark.png'),
+  }}
+/>
+
 Microsoft Dynamic Host Configuration Protocol (DHCP) is a service provided by the Microsoft Windows Server operating system. DHCP is a network management protocol used to dynamically assign IP addresses and other network configuration parameters (such as subnet mask, default gateway, DNS servers, etc.) to devices on a network.
 
 If you are already using Microsoft DHCP Servers in your environment, Microsoft DHCP Discovery can automatically populate records on discovered DHCP Servers, IP Addresses, and subnets, including additional DHCP details like DHCP Scope, State, Lease Duration, DNS information, and Start/End address ranges. 
 
-![](/assets/images/microsoft-dhcp-discovery/microsoft-dhcp-3.png)
-
 ## Discovery
 
-Microsoft DHCP Discovery uses WMI by default but WinRM is also supported and can be optionally enabled in the job configuration. (Example Below)
+Microsoft DHCP Discovery uses WMI by default but WinRM is also supported and can be optionally enabled in the job configuration. 
 
-![](/assets/images/microsoft-dhcp-discovery/microsoft-dhcp-1.png)
+<ThemedImage
+  alt="DHCP WinRM option"
+  sources={{
+    light: useBaseUrl('/assets/images/microsoft-dhcp-discovery/enable-winrm-discovery-light.png'),
+    dark: useBaseUrl('/assets/images/microsoft-dhcp-discovery/enable-winrm-discovery-dark.png'),
+  }}
+/>
 
 :::note
 If **Discover Using WinRM** is not enabled, you must have a WDS paired with the selected Remote Collector to use WMI. 
@@ -26,4 +41,10 @@ If **Discover Using WinRM** is not enabled, you must have a WDS paired with the
 ## Miscellaneous
 The following miscellaneous discovery options are also available:
 
-![](/assets/images/microsoft-dhcp-discovery/microsoft-dhcp-2.png)
+<ThemedImage
+  alt="DHCP WinRM option"
+  sources={{
+    light: useBaseUrl('/assets/images/microsoft-dhcp-discovery/dhcp-miscellaneous-options-light.png'),
+    dark: useBaseUrl('/assets/images/microsoft-dhcp-discovery/dhcp-miscellaneous-options-dark.png'),
+  }}
+/>

docs/auto-discovery/remote-collector-rc.md

@@ -83,7 +83,7 @@ The Remote Collector list page Actions Menu contains commands you can use for se
 
 ![](/assets/images/D42-23170_RC-list-page-set-log-level-2.png)
 
-## Remote Controller Proxy Settings
+## Remote Collector Proxy Settings
 
 The proxy settings within the Main Appliance and RC are set independently but are often identical. To reduce the potential for error, the RC can pick up proxy settings that have been configured. You can view and edit the RC proxy settings within the RC view of the Main Appliance.
 

docs/auto-discovery/storage-arrays-autodiscovery/dell-emc-autodiscovery.md

@@ -69,52 +69,55 @@ Login to SMIS provider using `http://<SMIS-Provider-IP>:5988/ECOMConfig` or `
 
 ### Isilon
 
-Create a new role and add the following read-only permissions.
-
-- ISI\_PRIV\_LOGIN\_CONSOLE
-- ISI\_PRIV\_LOGIN\_PAPI
-- ISI\_PRIV\_LOGIN\_SSH
-- ISI\_PRIV\_SYS\_SHUTDOWN
-- ISI\_PRIV\_SYS\_SUPPORT
-- ISI\_PRIV\_AUTH
-- ISI\_PRIV\_AUDIT
-- ISI\_PRIV\_CLUSTER
-- ISI\_PRIV\_DEVICES
-- ISI\_PRIV\_FTP
-- ISI\_PRIV\_HDFS
-- ISI\_PRIV\_HTTP
-- ISI\_PRIV\_MONITORING
-- ISI\_PRIV\_NETWORK
-- ISI\_PRIV\_NFS
-- ISI\_PRIV\_REMOTE\_SUPPORT
-- ISI\_PRIV\_SMARTPOOLS
-- ISI\_PRIV\_SMB
-- ISI\_PRIV\_STATISTICS
-- ISI\_PRIV\_NS\_TRAVERSE
-- ISI\_PRIV\_NS\_IFS\_ACCESS
-- ISI\_PRIV\_NDMP
+Create a new role and add the following read-only permissions:
+
+- ISI_PRIV_LOGIN_CONSOLE
+- ISI_PRIV_LOGIN_PAPI
+- ISI_PRIV_LOGIN_SSH
+- ISI_PRIV_SYS_SHUTDOWN
+- ISI_PRIV_SYS_SUPPORT
+- ISI_PRIV_AUTH
+- ISI_PRIV_AUDIT
+- ISI_PRIV_CLUSTER
+- ISI_PRIV_DEVICES
+- ISI_PRIV_FTP
+- ISI_PRIV_HDFS
+- ISI_PRIV_HTTP
+- ISI_PRIV_MONITORING
+- ISI_PRIV_NDMP
+- ISI_PRIV_NETWORK
+- ISI_PRIV_NFS
+- ISI_PRIV_NS_TRAVERSE
+- ISI_PRIV_NS_IFS_ACCESS
+- ISI_PRIV_QUOTA
+- ISI_PRIV_REMOTE_SUPPORT
+- ISI_PRIV_SMARTPOOLS
+- ISI_PRIV_SMB
+- ISI_PRIV_STATISTICS
 
-You can also use CLI commands to create such roles.
-
-1\. Login to the cluster using SSH.
-
-2\. Run the following commands.
-
-3\. To create a read-only role:
-
-- isi auth roles create –name readonly\_role –description “Read-only role for D42”
 
-4\. To give permissions to this role. Add all the permissions from above:
-
-- isi auth roles modify readonly\_role –add-priv-ro=ISI\_PRIV\_LOGIN\_PAPI
-
-5\. Create a USER:
-
-- isi auth users create readonly\_user –enabled yes –password xxxxxx
-
-6\. Add user to the role:
+You can also use CLI commands to create such roles.
 
-- isi auth roles modify readonly\_role –add-user=readonly\_user
+1. Login to the cluster using SSH.
+
+2. Run the following commands:
+
+   - To create a read-only role:
+       ```
+       isi auth roles create –name readonly_role –description “Read-only role for D42”
+       ```
+   - To give permissions to this role add all the permissions from above:
+       ```
+       isi auth roles modify readonly_role –add-priv-ro=ISI_PRIV_LOGIN_PAPI
+       ```
+   - Create a USER:
+       ```
+       isi auth users create readonly_user –enabled yes –password xxxxxx
+       ```
+   - Add user to the role:
+       ```
+       isi auth roles modify readonly_role –add-user=readonly_user
+       ```
 
 **Creating the Role/User via Web UI**
 

docs/auto-discovery/tcp-port-scan-auto-discovery.md

@@ -5,9 +5,9 @@ sidebar_position: 31
 
 ## TCP Port Scan Autodiscovery
 
-TCP Port Scan autodiscovery helps speed up autodiscovery by pre-scanning the specified range of IP Addresses. Device42 can determine what machines exist, what ports the machines have open, if they are running \*NIX or Windows, and most importantly, if they don’t exist. When the scan is complete, Device42 will utilize the resultant TCP Scan data to either create or update an autodiscovery job for the qualifying IPs.
+TCP Port Scan autodiscovery helps speed up autodiscovery by pre-scanning the specified range of IP Addresses. Device42 can determine what machines exist, what ports the machines have open, and whether they are running *nix or Windows. When the scan is complete, Device42 will utilize the resultant TCP Scan data to either create or update an autodiscovery job for the qualifying IPs.
 
-Select _Discovery > TCP Port Scan_ from the menu and then click _Add TCP Port Scan_ from the TCP Port Scan list page.
+Select **Discovery > TCP Port Scan** from the menu and then click **Add TCP Port Scan** from the TCP Port Scan list page.
 
 * * *
 
@@ -17,30 +17,34 @@ Select _Discovery > TCP Port Scan_ from the menu and then click _Add TCP Port
 
 ![](/assets/images/WEB-762_TCP-add-new-3.png)
 
-## Using TCP Port Scan to Create New Autodiscovery jobs
+## Using TCP Port Scan to Create New Autodiscovery Jobs
 
-The result of a TCP Port Scan is itself new autodiscovery jobs.
+The result of a TCP Port Scan is itself a new autodiscovery job.
 
-While creating a new TCP Port Scan, you may provide the servers range in any supported format and specify which Remote Collector with Windows Discovery Service (WDS) you want to run the scan on. In addition, you can provide all the settings you want the \*nix or Windows autodiscovery job to be created with. This will create the appropriate auto-discovery job for you with the provided naming template and specified settings, and will continue to maintain the list of servers based on the results of each TCP port scan run.
+While creating a new TCP Port Scan, you can provide the servers range in any supported format and specify which Remote Collector with Windows Discovery Service (WDS) you want to run the scan on. In addition, you can provide all the settings you want the *nix or Windows autodiscovery job to be created with. This will create the appropriate autodiscovery job for you with the provided naming template and specified settings, and will continue to maintain the list of servers based on the results of each TCP port scan run.
 
 ![](/assets/images/WEB-762_TCP-view-1.png)
 
 ![](/assets/images/WEB-762_TCP-view-2.png)
 
 ![](/assets/images/WEB-762_TCP-view-3.png)
 
-You can schedule TCP Port scans, similarly to all other autodiscovery jobs.
-
-**Note:** Setting the schedule on a TCP Port Scan job schedules the TCP Port Scan Job ITSELF, NOT the auto-discovery jobs that are created as a _result_ of that TCP Port Scan!
+Note that new secrets added to TCP port scans will not be added to their corresponding hypervisors, *nix, or win discovery jobs.
 
 ## Run Now or Schedule
 
+You can schedule TCP Port scans similarly to all other autodiscovery jobs.
+
 ![](/assets/images/WEB-762_TCP-list-page-run-now.png)
 
 Select **Run Now** from the list page to run the job right away.
 
 ![](/assets/images/WEB-762_TCP-list-page-add-schedule.png)
 
-Select **Add another Autodiscovery Schedule** from the when editing the job to create a run schedule for the job.
+Select **Add another Autodiscovery Schedule** when editing the job to create a run schedule for the job.
+
+A note on autodiscovery scheduling behavior: Newly created jobs will not run on the first day they are created to prevent an unintended large number of jobs from running initially. If you would like to run a job after its initial creation, simply select the **Run Now** button next to the job after creation.
 
-A note on autodiscovery scheduling behavior: newly created jobs will not run on the first day they are created, to prevent an unintended large amount of jobs from running initially. If you would like to run a job after its initial creation, simply select the _Run Now_ button next to the job after creation.
+:::note
+Setting the schedule on a TCP Port Scan job schedules the TCP Port Scan Job itself, not the autodiscovery jobs that are created as a _result_ of that TCP Port Scan.
+:::

docs/integration/external-integrations/device42-confluence-connector.md

@@ -19,6 +19,10 @@ This integration connects Device42 to your Atlassian Confluence instance with th
 
 Device42's Atlassian Confluence add-on (aka "Device42 CMDB Connector for Confluence") can be found [in the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1213754/device42-cmdb-connector-for-confluence?hosting=server&tab=overview). You can easily install it using the UPM (Universal Plugin Manager) built in to Confluence. However, if you have some special requirements (e.g. an environment that blocks Confluence from access to the internet), it is possible to install the Device42 Confluence integration plugin manually. Please note that the plugin requires a stable connection between the servers hosting your Confluence application and that which is hosting Device42 for successful operation.
 
+:::info
+The Confluence plugin is now certified for Data Center and is available on the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1213754/device42-cmdb-connector-for-confluence?hosting=datacenter&tab=overview).
+:::
+
 ### Automatic installation
 
 **Installing the add-on:**