diff --git a/docs/auto-discovery/hypervisors-and-containers-supported-in-auto-discovery.md b/docs/auto-discovery/hypervisors-and-containers-supported-in-auto-discovery.md
index 73fa7c0a..acb4dcb4 100644
--- a/docs/auto-discovery/hypervisors-and-containers-supported-in-auto-discovery.md
+++ b/docs/auto-discovery/hypervisors-and-containers-supported-in-auto-discovery.md
@@ -3,16 +3,20 @@ title: "Supported Hypervisors and Containers List"
sidebar_position: 30
---
-If you were looking for how-to instructions to get started with Hypervisor, Linux (\*nix), or Windows discovery, see either:
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+Device42 autodiscovery supports various platforms, operating systems (OSes), and container platforms. The full list, including the details and limitations of the Docker, Cisco ASA/NX OS, and Nutanix autodiscovery processes, can be found below.
+
+If you are looking for instructions to get started with Hypervisor, Linux (\*nix), or Windows discovery, see either:
- the [Windows / Hyper-V Discovery](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx) page
- or the [Linux / UNIX server auto-discovery](/auto-discovery/linux-unix-server-auto-discovery.mdx) page.
-## Supported Hypervisor / Container Platforms
-
-Device42 is constantly expanding its list of hypervisor and container platforms supported by autodiscovery. For instructions on how to configure and run these discovery jobs, please refer to [Hypervisor Autodiscovery](auto-discovery/virtual-machine-auto-discovery.md). The list of supported platforms currently includes:
+## Supported Hypervisor and Container Platforms
-
+Device42 is constantly expanding the hypervisor and container platforms supported by autodiscovery.
+The list of supported platforms currently includes:
- \*nix
- AIX HMC
@@ -36,29 +40,39 @@ Device42 is constantly expanding its list of hypervisor and container platforms
- Windows
- WinRM
-**Note that both Windows and \*nix (Linux/UNIX) can be found in this drop-down as well; use those options to discover Windows servers, Linux servers, guest instances, or VMs themselves, as opposed to their hosts.**
+
+
+Both Windows and \*nix (Linux/UNIX) can be found in this dropdown menu as well. Use those options to discover Windows servers, Linux servers, guest instances, or VMs themselves, as opposed to their hosts.
+
+For instructions on how to configure and run these discovery jobs, please refer to [Hypervisor Autodiscovery](auto-discovery/virtual-machine-auto-discovery.md).
:::tip
If you are using a hypervisor, a container platform, or an orchestration tool you would like to see supported - please let us know! Open a support ticket or email [support@device42.com](mailto:support@device42.com).
:::
-### Notes on Docker / Docker API Autodiscovery
+### Docker and Docker API Autodiscovery Notes
- Docker API discovery returns basic container data with IPs and MAC addresses.
- Regular Docker discovery also returns service ports.
- By running Docker and connecting to the host, you can map connections to the container.
-- You can see on the Docker host how to get the source ports of containers, without having to login to the container to identify the connection.
-- You can use the **docker top** command and supply just the container ID; you would need to use sudo commands for this.
-- We support all standard Docker cloud operating systems such as EKS (AWS Kubernetes), GKE (Google Kubernetes), AKS (Azure Kubernetes), and standalone Kubernetes, as well as Ubuntu, CentOS, Debian, Arch Linux and Fedora.
+- You can see on the Docker host how to get the source ports of containers, without having to log in to the container to identify the connection.
+- You can use the `docker top` command and supply just the container ID; you would need to use `sudo` commands for this.
+- We support all standard Docker cloud operating systems such as EKS (AWS Kubernetes), GKE (Google Kubernetes), AKS (Azure Kubernetes), and standalone Kubernetes, as well as Ubuntu, CentOS, Debian, Arch Linux, and Fedora.
-### Notes on Cisco ASA/NX OS Autodiscovery
+### Cisco ASA/NX OS Autodiscovery Notes
Device42's Cisco ASA/NX OS autodiscovery augments firewall/ASA discoveries with information gathered via SSH. If you run virtual firewall instances, Device42 will discover your virtual firewalls and list them as firewall “contexts” underneath the parent firewall. Note that this discovery method has had only limited testing.
-### Notes on Nutanix Autodiscovery
+### Nutanix Autodiscovery Notes
-If you have previously ran a D42 discovery job, and are discovering new resources, then in some cases, you will need to delete and re-run to have a complete view. Note that this is a discovery workaround for the time being.
+If you have previously run a Device42 discovery job, and are discovering new resources, then in some cases, you will need to delete and re-run to have a complete view. Note that this is a discovery workaround for the time being.
-### Ignore IP/MAC Addresses From Autodiscovery
+### Ignore IP and MAC Addresses From Autodiscovery
You have the option to ignore specific IP and MAC addresses globally and for specific jobs. See [Windows and Hyper-V Autodiscovery](/auto-discovery/windows-and-hyper-v-auto-discovery/#option-to-ignore-ipsmac-addresses.md) for more details.
diff --git a/docs/auto-discovery/remote-collector-rc.mdx b/docs/auto-discovery/remote-collector-rc.mdx
index e08b216f..6f6cc7d1 100644
--- a/docs/auto-discovery/remote-collector-rc.mdx
+++ b/docs/auto-discovery/remote-collector-rc.mdx
@@ -1,64 +1,74 @@
---
-title: "Remote Collector (RC)"
+title: "Remote Collector"
sidebar_position: 24
---
import ThemedImage from '@theme/ThemedImage'
import useBaseUrl from '@docusaurus/useBaseUrl'
-## The Device42 Remote Collector (RC)
+## The Device42 Remote Collector
-The Remote Collector (RC) is a virtual appliance that is deployed separately from the Device42 Main Appliance (MA). The RC is sent autodiscovery jobs and controlled from the MA, executing those jobs remotely. All autodiscovery jobs, including Power SNMP jobs, are supported and can be run remotely on an RC.
+A Remote Collector (RC) is a virtual appliance deployed separately from the Device42 Main Appliance (MA). An RC is controlled from the MA and sent autodiscovery jobs that it executes remotely. All autodiscovery jobs, including Power SNMP jobs, are supported and can be run remotely on an RC.
:::note
Windows discovery requires at least one [Windows Discovery Service](getstarted/installation/windows-discovery-service-installation.md) (WDS) instance to be deployed.
:::
-You may configure an unlimited number of RC appliances as needed across your environment. RCs facilitate SNMP, IPMI, hypervisor, and other autodiscoveries across networks requiring only HTTPS access, eliminating the need to open numerous ports up across network segments.
+You may configure an unlimited number of RC appliances as needed across your environment. RCs facilitate SNMP, IPMI, hypervisor, and other types of autodiscovery across networks requiring only HTTPS access, eliminating the need to open numerous ports across network segments.
-### RC Sizing Recommendations
+### Sizing Recommendations
-For one RC per 1000 workloads, the sizing recommendations are:
-- 2 vCPU
+For one RC per 1000 workloads, the sizing recommendations are as follows:
+
+- Two vCPU
- 4GB RAM
- 50GB vDisk
-## RC Installation and Configuration
+## Installation and Configuration
+
+To download the RC, head to our [**Autodiscovery** software download page](https://www.device42.com/autodiscovery/). In the **D42 Remote Collector (RC)** section at the top of the page, click the **Download** button.
-To download the RC, head to our [**Autodiscovery** tools download page](https://www.device42.com/autodiscovery/). In the **D42 Remote Collector (RC)** section at the top of the page, click the **Download** button.
+We currently offer a `.ovf` image for direct download.
-We currently offer an `.OVF` image for direct download. Should your hypervisor not support the OVF virtual machine (VM) image format, please contact [support@device42.com](mailto:support@device42.com) and we will work with you to provide an image compatible with your hypervisor. Deploy the VM image to your hypervisor, boot it, and log in via the VM console or SSH, Port 22.
+Should your hypervisor not support the OVF Virtual Machine (VM) image format, please contact [support@device42.com](mailto:support@device42.com) and we will work with you to provide an image compatible with your hypervisor.
-The default credentials for the RC are:
+Deploy the VM image to your hypervisor, boot it, and use the following default credentials to log in via the VM console or SSH, Port 22.
Username:
- ```
- client
- ```
+
+```
+client
+```
+
Password:
- ```
- device42
- ```
-After logging in to the console, you will see the main console menu:
+```
+device42
+```
+
+After logging in to the console, you will see the **Device42 Appliance Management Main Menu**.
-### Initial (First-Boot) Network Config
+### Initial (First-Boot) Network Configuration
Upon initial installation, configure your network settings to proceed with setup. It is best to use a static IP for your network, as Device42 can lose contact with RCs that have changing (dynamic) IP addresses.
-On the main console menu, choose **Network Interfaces** and press `enter` on the name of your interface to edit it. Use the `space bar` to unselect DHCP and assign a static IP address using the following screen.
+On the **Main Menu**, choose **Network Interfaces** and press `enter` on the name of your interface to edit it. Use the `space bar` to unselect DHCP and assign a static IP address using the following screen:
-The **PREFIX** field above asks for an integer that represents the subnet mask in slash notation. For example, for `255.255.255.0`, which is a `/24`, you would enter `24`. Note that the **PREFIX** field has been removed, and as soon as your RC connects to Device42, it will be updated.
+The **PREFIX** field above asks for an integer that represents the subnet mask in slash notation. For example, for the subnet mask `255.255.255.0`, which is `/24` in slash notation, you would enter `24`.
+
+:::note
+The **PREFIX** field has been removed, and as soon as your RC connects to Device42, it will be updated.
+:::
### Connect your Remote Collector to Device42
-Each RC must be able to communicate with the main appliance on port 443. After initial communication, a WebSocket connection is established between the RC and MA on an ephemeral port (selected randomly), allowing full-duplex communication between them. The Device42 main appliance can thus talk to and control the RC over the WebSocket.
+Each RC must be able to communicate with the MA on Port 443. After initial communication, a WebSocket connection is established between the RC and the MA on a randomly selected ephemeral port, allowing full-duplex communication between them. The Device42 MA can thus talk to and control the RC over the WebSocket.
-From the main console menu, select **RC Setup** to register your RC with your main Device42 appliance. To do this, you will need to first generate a One Time Password (OTP) from Device42. Visit Device42 in your browser and via the main menu, head to **Discovery > Remote Collectors**. Here you will be able to view any existing registered RCs and generate an OTP to register a new one:
+From the **Main Menu**, select **(r) Remote Collector Setup** to register your RC with your Device42 MA. To do this, you will first need to generate a one-time password (OTP) from Device42. Visit Device42 in your browser and via the main menu, head to **Discovery > Remote Collectors**. Here you will be able to view any existing registered RCs and generate an OTP to register a new one:
Remote Collectors** for the **Select an action** dropdown menu.
+Navigate to the **Remote Collectors** list page under **Discovery > Remote Collectors** and click **Select an action** to access the dropdown menu.
Remote Collectors** for the **S
}}
/>
-Select RC(s) from the table, choose one of the following actions, and click the hammer icon to execute the action:
+Select the relevant RC(s) from the table, choose one of the following actions, and click the **hammer icon** to execute the action:
- **Delete with Detailed Confirmation**: Delete the selected RC(s) with a confirmation prompt.
- **Export Selected Items as CSV**: Export a CSV file with information about the selected RC(s).
- **Clear logs**: Clear the log files for the selected RC(s).
-- **Reboot Collectors**: Reboot the selected connected RC(s). Note that if your RC is exhibiting unusual behavior, rebooting the RC can be a good first step to resolving the problem.
-- **Set Remote Collector Logging Level**: Set the RC logging level. Select **Information** to reduce the log file size. You can also set a Global Logging Level via the RC console.
+- **Reboot Collectors**: Reboot the selected connected RC(s). Note that if your RC is exhibiting unusual behavior, rebooting the RC is a good first step to resolving the problem.
+- **Set Logging Level**: Set the RC logging level. Select **Information** to reduce the log file size. You can also set a Global Logging Level via the RC console.
-## Remote Collector Proxy Settings
+- **Set Proxy Settings**: Edit the RC(s) inherited proxy settings.
+
+### Proxy Settings
-The proxy settings within the MA 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 MA.
+The proxy settings within the MA and RC are set independently but are often identical. To reduce the potential for error, the RC can pick up preconfigured proxy settings. You can also view and edit the RC proxy settings within the RC view of the MA.
## Scalability
-Device42 RCs provide robust scalability by offloading discovery workloads from your MA. You can deploy multiple remote collectors for each main appliance. Device42 recommends one remote collector with one Windows Discovery Service for every 1,000 workloads.
+Device42 RCs provide robust scalability by offloading discovery workloads from your MA. You can deploy multiple RCs for each MA. We recommend using one RC with one WDS for every 1,000 workloads.
-## Remote Collector Deployment Example
+## Deployment Example
-Remote collectors are extremely flexible, and make discovery with Device42 easier than ever. You can deploy one or more, with no logical limit to the number of remote collectors.
+RCs are extremely flexible and make discovery with Device42 easier than ever. You can deploy one or more, with no logical limit to the number of RCs you can use.
-In the deployment example pictured, an RC is deployed within each isolated DMZ Network Segment that, per firewall rules typical of a DMZ, the Device42 appliance is normally unable to directly reach or discover. Deploying a remote collector to these segments bolsters security by saving the Network Administrator from making multiple temporary (or permanent and insecure) firewall rules (aka ‘holes’) to allow discovery traffic to pass from the MA over the wide range of ports used by various vendor APIs.
+In the deployment example pictured above, an RC is deployed within each isolated DMZ network segment that, per firewall rules typical of a DMZ, the Device42 MA is normally unable to reach or discover directly. Deploying an RC to these segments bolsters security by saving the network administrator from making multiple temporary (or permanent and insecure) firewall rules (aka 'holes') to allow discovery traffic to pass from the MA over the wide range of ports used by various vendor APIs.
-Please note that the diagram doesn't show the majority of network connectivity that would be present, and instead focuses mainly on what is discovered by the MA vs. the RC, and the communication between the RC and MA.
+Please note that the diagram doesn't show the majority of network connectivity that would be present, and instead focuses on what is discovered by the MA and the RC, and the communication between them.
As mentioned briefly in the introduction, all communication and discovery information is securely transmitted between the RC and the MA once a connection is established via Port 443 (HTTPS/SSL). This means a single, secure, and easily monitored 1:1 rule allows for comprehensive and continuous discovery of the secured network segment - as often as scheduled or desired - without compromising its isolation or security.
## Running Remote Discoveries
-Once registered, you can schedule any autodiscovery job from the MA and instruct it to run on the remote collector of your choosing. Each autodiscovery screen shows a **Remote Collector** dropdown menu. Click this box to display all registered RCs and choose the RC you would like the discovery job to run from:
+Once registered, you can schedule any autodiscovery job from the MA and instruct it to run on the RC of your choosing. Each autodiscovery screen shows a **Remote Collector** dropdown menu. Click this dropdown to display all registered RCs and choose the RC you would like to run the discovery job:
## Updating Your Remote Collector
-Device42 RCs are updated automatically as long as they are connected to a Device42 MA. Updates to the MA instance include updates to your RC(s), and those updates are pushed out automatically as part of the regular Device42 update process. By keeping your main Device42 instance up to date, can ensure your RCs are up to date as well.
+Device42 RCs are updated automatically as long as they are connected to a Device42 MA. Updates to the MA instance include updates to your RC(s), which are pushed out automatically as part of the regular Device42 update process. By keeping your main Device42 instance up to date, you ensure that your RCs are also up to date.
## Migrating Existing Power Appliance Jobs to a Remote Collector
-Migrating jobs that were created for the original standalone power appliance is possible with existing tools.
+It is possible to use existing tools to migrate jobs that were created for the original, standalone power appliance to RCs.
-Follow the [Power Job Migration Guide](../infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.md) to migrate jobs to the new RC of your choice.
+Follow the [Power Job Migration Guide](../infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.md) to migrate jobs to your choice of RC(s).
diff --git a/docs/auto-discovery/storage-arrays-autodiscovery/storage-arrays.md b/docs/auto-discovery/storage-arrays-autodiscovery/storage-arrays.md
deleted file mode 100644
index 00d27ba1..00000000
--- a/docs/auto-discovery/storage-arrays-autodiscovery/storage-arrays.md
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: "Viewing Storage Arrays"
-sidebar_position: 6
----
-
-## Introduction
-
-Storage Arrays are identified and returned by Device42 [Storage Arrays autodiscovery](./). Storage Arrays also display their resource details, related resources, and topology map.
-
-## View All Storage Arrays
-
-Select _Resources > Storage > Arrays_ from the Device42 menu to display the storage arrays list.
-
-
-
-Device42 displays the Storage Arrays list page. On this page, you can _Search by name_, or filter the list by _Type_.
-
-
-
-**Note**: The Storage Arrays list page also includes an _Advanced Search_ option you can use to construct more specific searches. See the [Advanced Search Feature](/getstarted/advanced-search-feature.mdx) documentation page for instructions.
-
-Click on an array _Name_ to see details about that array. You can use the links in the panel on the right to see details about that related resource.
-
-
-
-
-
-### View Storage Arrays Mapped to Devices
-
-Devices that have attached storage arrays display links to those arrays in the Parts tab of the device view page. The example below shows the Parts tab of a physical device with links to storage.
-
-
-
-Click on a Parts link to see that resource (in this case a LUN).
-
-
-
-## Resource Maps and Trends Graphs
-
-Click _Resource Map_ at the top left of the page to see the topography map for the array. You can select which _Resource Types_ you want to include in the map.
-
-
-
-Click _Trends_ at the top left of the page to see graphs for data such as Read Data Rate, Write Data Rate, IOs Rate, etc., for the storage array.
-
-
-
-Select the _Available Metrics_ drop-down to choose which Trends charts you want to see.
-
-
-
-## Edit Storage Arrays
-
-Click _Edit_ on the Storage Array view page to edit the array. You can add or edit _Notes_ or _Tags_ for the array, select Yes/No for _In Service,_ and select or add a _Service Level_ value_._
-
-
-
-Click _Save_ to save your edits; click _Cancel_ to discard them.
-
-## Delete Storage Arrays
-
-Select one or more arrays from the list, and select either _Fast Background Delete_ or _Delete with Detailed Confirmation_ from the Actions menu, and then click the lightning bolt icon.
-
-
-
-Confirm the deletion if prompted.
-
-
-
-
-
-## Storage Array Discovery Job Import/Export
-
-You can import or export storage array discovery jobs using an Import/Export Excel file.
-
-- Select _Tools > Imports/Exports (xls)_ from the Device42 main menu, and then select _Autodiscovery – Create Storage Array Autodiscovery Jobs > Download Sample Excel File_.
-
-
-
-
-
-- Use the Excel file to set up your storage array discovery job and then use _Upload Excel file_ at the top of the Imports/Exports page to upload the file to Device42.
diff --git a/docs/auto-discovery/storage-arrays-autodiscovery/storage-arrays.mdx b/docs/auto-discovery/storage-arrays-autodiscovery/storage-arrays.mdx
new file mode 100644
index 00000000..b56c1a50
--- /dev/null
+++ b/docs/auto-discovery/storage-arrays-autodiscovery/storage-arrays.mdx
@@ -0,0 +1,162 @@
+---
+title: "Viewing Storage Arrays"
+sidebar_position: 6
+---
+
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+Storage arrays are identified and returned by the Device42 [storage arrays autodiscovery](./). Storage arrays also display their resource details, related resources, and topology maps.
+
+## View All Storage Arrays
+
+Select **Resources > Storage > Arrays** from the Device42 menu to display the **Storage Arrays** list page.
+
+
+
+On this page, you can **Search by name** or filter the list by **Type**.
+
+
+
+:::note
+The **Storage Arrays** list page also includes an **Advanced Search** option you can use to construct more specific searches. See the [Advanced Search Feature](/getstarted/advanced-search-feature.mdx) documentation page for instructions.
+:::
+
+Click on an array **Name** to see details about that array. You can use the links in the panel on the right to see details about that related resource.
+
+
+
+
+### View Storage Arrays Mapped to Devices
+
+Devices with attached storage arrays display links to those arrays in the **Parts** tab of the device view page. The example below shows the **Parts** tab of a physical device with a link to storage.
+
+
+
+
+
+Click on a **Parts** link to see that resource (in this case a LUN).
+
+
+
+## Resource Maps and Trends Graphs
+
+Click **Resource Map** at the top left of the page to see the topography map for the array. On the left panel, you can add, highlight, or search by type or individual items to customize the chart view.
+
+
+
+## Edit Storage Arrays
+
+Click **Edit** on the storage array view page to edit the array. You can add or edit **Notes** (1) or **D42 Tags** (2) for the array, toggle **Yes** or **No** for **In Service** (3), and select or add a **Service Level** value (4).
+
+
+
+Click **Save** to save your edits or click **Cancel** to discard them.
+
+## Storage Arrays Actions
+
+Select one or more arrays from the list and choose an action from the menu.
+
+To delete items, choose **Delete with Detailed Confirmation**, **Fast Background Delete**, or **Fast Background Archive** from the **Select an action** dropdown menu. Click the **hammer icon** to execute the selected action.
+
+You can also select storage arrays to **Add to Business Application**.
+
+
+
+Confirm the deletion if prompted.
+
+
+
+## Storage Array Discovery Job Import and Export
+
+You can import or export storage array discovery jobs using an Import/Export Excel file.
+
+- Select **Tools > Imports/Exports (xls)** from the Device42 main menu. Locate the **Autodiscovery – Create Storage Array Autodiscovery Jobs** row and click **Download Sample Excel File**.
+
+
+
+- Fill in the Excel file to set up your storage array discovery job. Click on the tips in the cell headings for details on what values to enter in each column.
+
+ 
+
+- **Browse** to the Excel file at the top of the Imports/Exports page and click **Upload** to add the storage array discovery jobs to Device42.
+
+
diff --git a/docs/auto-discovery/tcp-port-scan-auto-discovery.md b/docs/auto-discovery/tcp-port-scan-auto-discovery.md
deleted file mode 100644
index 2830c6e3..00000000
--- a/docs/auto-discovery/tcp-port-scan-auto-discovery.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "TCP Port Scan Autodiscovery"
-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, 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.
-
-* * *
-
-
-
-
-
-
-
-## Using TCP Port Scan to Create New Autodiscovery Jobs
-
-The result of a TCP Port Scan is itself a new autodiscovery job.
-
-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.
-
-
-
-
-
-
-
-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.
-
-
-
-Select **Run Now** from the list page to run the job right away.
-
-
-
-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.
-
-:::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.
-:::
diff --git a/docs/auto-discovery/tcp-port-scan-auto-discovery.mdx b/docs/auto-discovery/tcp-port-scan-auto-discovery.mdx
new file mode 100644
index 00000000..d8e76936
--- /dev/null
+++ b/docs/auto-discovery/tcp-port-scan-auto-discovery.mdx
@@ -0,0 +1,89 @@
+---
+title: "TCP Port Scan Autodiscovery"
+sidebar_position: 31
+---
+
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+TCP port scan autodiscovery accelerates autodiscovery by pre-scanning a specified range of IP addresses. Device42 determines which machines exist, which ports the machines have open, and whether they are running \*nix or Windows.
+
+When the scan is complete, Device42 will use the resulting TCP scan data to either create or update an autodiscovery job for the qualifying IPs.
+
+## Using TCP Port Scan to Create New Autodiscovery Jobs
+
+First, configure the TCP port scan. The result of a TCP port scan is itself a new autodiscovery job.
+
+- From the main menu, select **Discovery > TCP Port Scan** to open the **TCP Port Scan** list page.
+
+- Click **+ Add TCP Port Scan**.
+
+- Provide the range of FQDN or IP addresses for the **Server(s)** and specify which **Remote Collector** with Windows Discovery Service (WDS) you want to run the scan on. Optionally, add any servers to exclude from the scan.
+
+
+
+- Under **Settings for auto-created Hypervisors/\*nix/win AD Task**, provide 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 maintain the list of servers based on the results of each TCP port scan run.
+
+
+
+
+
+
+
+:::note
+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.
+
+Select **Add another Autodiscovery Schedule** when editing the job to create a run schedule for the job.
+
+
+
+Return to the **TCP Port Scan** list page and click **Run Now** to run the job immediately.
+
+
+
+Newly created jobs will not run on the first day they are created, to prevent an excessive number of jobs from running simultaneously. If you would like to run a job after its initial creation, click the **Run Now** button next to the job after creation.
+
+:::note
+Setting the schedule on a TCP port scan job will schedule the TCP port scan job itself, but not the autodiscovery jobs created as a **result** of that TCP port scan.
+:::
diff --git a/docs/getstarted/installation/remote-collector-rc-installation.md b/docs/getstarted/installation/remote-collector-rc-installation.md
index 6a12d757..ecf08cf8 100644
--- a/docs/getstarted/installation/remote-collector-rc-installation.md
+++ b/docs/getstarted/installation/remote-collector-rc-installation.md
@@ -1,23 +1,26 @@
---
-title: "Remote Collector (RC) Installation"
+title: "Remote Collector Installation"
sidebar_position: 7
---
-The RC is shipped as a virtual appliance and can be downloaded on our Discovery Software Download page: [https://www.device42.com/autodiscovery/](https://www.device42.com/autodiscovery/).
+The Remote Collector (RC) is shipped as a virtual appliance and can be downloaded from our [**Autodiscovery** software download page](https://www.device42.com/autodiscovery/).
## Installation Instructions
-Visit the [**RC Installation and Configuration**](/auto-discovery/remote-collector-rc/#rc-installation-and-configuration.mdx) section of the [Remote Collector](/auto-discovery/remote-collector-rc.mdx) page for detailed installation instructions.
+The [**Installation and Configuration**](/auto-discovery/remote-collector-rc/#installation-and-configuration.mdx) section of the [**Remote Collector**](/auto-discovery/remote-collector-rc.mdx) page provides detailed instructions for installing an RC.
## Default RC Credentials
-The Device42 RC default login credentials are:
+The default Device42 RC login credentials are as follows:
+
+**Username:**
-**Username:**
```
client
```
-**Password:**
+
+**Password:**
+
```
device42
```
diff --git a/docs/getstarted/installation/sizing-recommendations.md b/docs/getstarted/installation/sizing-recommendations.md
index dacf47ba..1a333f69 100644
--- a/docs/getstarted/installation/sizing-recommendations.md
+++ b/docs/getstarted/installation/sizing-recommendations.md
@@ -3,9 +3,8 @@ title: "Sizing Recommendations"
sidebar_position: 4
---
-| Device42 Item | Sizing/Notes |
+| Device42 Item | Sizing and Notes |
|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 1 Main Appliance (virtual appliance) | **Small to Medium Environments (\<2500 devices):**
- 4 vCPU
- 16GB RAM
- 150GB vDisk (SSD or Flash disk recommended)
**Medium to Large Environments (>2500 devices):**
- 16 vCPU
- 64GB RAM
- 150GB vDisk (SSD or Flash disk recommended)
*For any environments where Application Dependency Mapping (ADM), Resource Utilization (RU) and/or Storage discovery is included, we recommend following the guidelines for the Medium to Large Environments* |
-| Remote Collector (s) (virtual appliance) | **1 RC per 1000 workloads:**
- 2 vCPU
- 4GB RAM
- 50GB vDisk |
-| Windows Discovery Service (WDS) (.NET installer) | **1 WDS per 1000 workloads:**
- 2 vCPU
- 8GB RAM
- 50GB vDisk (minimum) |
-
+| One Main Appliance (virtual appliance) | **Small to medium environments (\<2500 devices):**
- Four vCPU
- 16GB RAM
- 150GB vDisk (SSD or flash disk recommended)
**Medium to large environments (>2500 devices):**
- 16 vCPU
- 64GB RAM
- 150GB vDisk (SSD or Flash disk recommended)
*For any environments that include Application Dependency Mapping (ADM), Resource Utilization (RU), or Storage discovery, we recommend following the guidelines for the medium to large environments* |
+| Remote Collector(s) (virtual appliance) | **One RC per 1000 workloads:**
- Two vCPU
- 4GB RAM
- 50GB vDisk |
+| Windows Discovery Service (WDS) (.NET installer) | **One WDS per 1000 workloads:**
- Two vCPU
- 8GB RAM
- 50GB vDisk (minimum) |
diff --git a/docs/getstarted/installation/windows-discovery-service-installation.md b/docs/getstarted/installation/windows-discovery-service-installation.md
index 1f563ad0..23056a3d 100644
--- a/docs/getstarted/installation/windows-discovery-service-installation.md
+++ b/docs/getstarted/installation/windows-discovery-service-installation.md
@@ -10,51 +10,49 @@ The Windows Discovery Service (WDS) should be connected directly to a Remote Col
The .NET service must be installed on a Windows machine with the .NET runtimes installed.
-* * *
+## Installing the Windows Discovery Service
-## Installing the WDS Service
+1. Download the current WDS `.msi` installer file from the [Device42 **Autodiscovery** software download page](https://www.device42.com/autodiscovery/).
-1) Download the current WDS `.msi` installer file from the [Device42 autodiscovery tools page](https://www.device42.com/autodiscovery/).
-
-2) Run the downloaded `Device42Discovery.msi` installer. Click **Next** and follow the prompts to continue with the installation:
+2. Run the downloaded `Device42Discovery.msi` installer. Click **Next** and follow the prompts to continue with the installation:
-3) Point to your chosen **RC Endpoint**:
+3. In the **Device42 RC Link Setup** dialog, indicate your **RC Endpoint** by entering the RC IP address or FQDN in the first field.
-a. Enter the Remote Collector IP address or FQDN in the first field.
+4. Enter a one-time pin in the **RC Code** field, after generating it as follows:
-b. From the Device42 Main Appliance, navigate to **Discovery > Remote Collectors**.
+ a. From the Device42 MA, navigate to **Discovery > Remote Collectors**.
-
+
-4) Generate a One-Time Pin by clicking the **Generate OTP** button at the upper right of the list page. You'll need the generated OTP during the WDS installation.
+ b. Click **Generate OTP** in the upper-right corner of the **Remote Collectors** list page.
-
+
-5) Accept the default installation directory for the WDS service or specify a custom installation path:
+5. Accept the default installation directory for the WDS service or specify a custom installation path.
-6) Click **Next** to confirm installation:
+6. Click **Next** to confirm installation.
-7) The installation should now be complete. Remote collectors in the Device42 UI should now be renamed to reflect that the WDS has been set up and connected. The WDS Service indicator icon will be green to indicate the WDS is connected and communicating:
+7. Confirm that the installation was successful by checking that RCs in the Device42 UI have been renamed and the WDS indicator icon has turned green to reflect the WDS connection.
Remote Collectors
### Securing WDS Implementation in Device42
-Both the Main Appliance and the Remote Collector ship with a self-signed certificate, making it necessary to support invalid certificates with the default installation of Device42.
+Both the MA and the RC ship with a self-signed certificate, making it necessary to support invalid certificates with the default installation of Device42.
-Install a valid certificate on the Main Appliance and Remote Collector. You can then change the default behavior of WDS to not ignore SSL errors by changing the config file for WDS runtime:
+Install a valid certificate on the MA and the RC. You can then change the default behavior of the WDS to no longer ignore SSL errors by editing the WDS runtime configuration file:
```
@@ -80,23 +78,20 @@ Install a valid certificate on the Main Appliance and Remote Collector. You can
...
```
-* * *
-
## Create a New WMI Autodiscovery Job
-You are now ready to discover using your new WDS. When creating a new Windows WMI autodiscovery job, choose the WDS connected to the Main Appliance or the Remote Collector with WDS, and configure the job settings to discover Windows Devices:
+You are now ready to run discoveries with your new WDS. When creating a new Windows WMI autodiscovery job, choose the WDS connected to the MA or RC with WDS, and configure the job settings to discover Windows devices:
:::caution
Do not set up an autodiscovery scan using critical production account credentials! Please create a separate, dedicated account to use only for discovery.
-Account lock-out could result in an otherwise avoidable outage depending on your permissions and configured password policies. You as a customer are responsible for any such behavior.
+Depending on your permissions and configured password policies, account lockout could result in an otherwise avoidable outage. You as a customer are responsible for any such behavior.
:::
-* * *
## Update Your WDS Installation
-You don't need to update your WDS installation separately. Once it has made its initial connection, updates to the WDS service are pushed automatically and are distributed with regular Device42 Updates.
+You do not need to update your WDS installation separately. After the initial connection, WDS updates are automatically pushed and distributed with regular Device42 updates.
-If you are concerned you aren't running the latest version of WDS, please [update your main Device42 appliance](how-to-videos/update-device42-appliance-how-to.md) to the latest version.
+If you are concerned that you are not running the latest version of WDS, please [update your main Device42 appliance](how-to-videos/update-device42-appliance-how-to.md) to the latest version.
diff --git a/static/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-dark.png b/static/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-dark.png
new file mode 100644
index 00000000..06e96c95
Binary files /dev/null and b/static/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-dark.png differ
diff --git a/static/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-light.png b/static/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-light.png
new file mode 100644
index 00000000..70acb126
Binary files /dev/null and b/static/assets/images/hypervisors-and-containers-supported-in-auto-discovery/platforms-list-light.png differ
diff --git a/static/assets/images/storage-arrays/array-delete-confirmation-dark.png b/static/assets/images/storage-arrays/array-delete-confirmation-dark.png
new file mode 100644
index 00000000..0098a082
Binary files /dev/null and b/static/assets/images/storage-arrays/array-delete-confirmation-dark.png differ
diff --git a/static/assets/images/storage-arrays/array-delete-confirmation-light.png b/static/assets/images/storage-arrays/array-delete-confirmation-light.png
new file mode 100644
index 00000000..14b9ff7d
Binary files /dev/null and b/static/assets/images/storage-arrays/array-delete-confirmation-light.png differ
diff --git a/static/assets/images/storage-arrays/array-example-details-dark.png b/static/assets/images/storage-arrays/array-example-details-dark.png
new file mode 100644
index 00000000..36c49580
Binary files /dev/null and b/static/assets/images/storage-arrays/array-example-details-dark.png differ
diff --git a/static/assets/images/storage-arrays/array-example-details-light.png b/static/assets/images/storage-arrays/array-example-details-light.png
new file mode 100644
index 00000000..b7f8694a
Binary files /dev/null and b/static/assets/images/storage-arrays/array-example-details-light.png differ
diff --git a/static/assets/images/storage-arrays/array-example-related-dark.png b/static/assets/images/storage-arrays/array-example-related-dark.png
new file mode 100644
index 00000000..9a906bff
Binary files /dev/null and b/static/assets/images/storage-arrays/array-example-related-dark.png differ
diff --git a/static/assets/images/storage-arrays/array-example-related-light.png b/static/assets/images/storage-arrays/array-example-related-light.png
new file mode 100644
index 00000000..a223d271
Binary files /dev/null and b/static/assets/images/storage-arrays/array-example-related-light.png differ
diff --git a/static/assets/images/storage-arrays/array-resource-map-dark.png b/static/assets/images/storage-arrays/array-resource-map-dark.png
new file mode 100644
index 00000000..1f71807e
Binary files /dev/null and b/static/assets/images/storage-arrays/array-resource-map-dark.png differ
diff --git a/static/assets/images/storage-arrays/array-resource-map-light.png b/static/assets/images/storage-arrays/array-resource-map-light.png
new file mode 100644
index 00000000..369fa0af
Binary files /dev/null and b/static/assets/images/storage-arrays/array-resource-map-light.png differ
diff --git a/static/assets/images/storage-arrays/device-parts-dark.png b/static/assets/images/storage-arrays/device-parts-dark.png
new file mode 100644
index 00000000..e0f336b1
Binary files /dev/null and b/static/assets/images/storage-arrays/device-parts-dark.png differ
diff --git a/static/assets/images/storage-arrays/device-parts-light.png b/static/assets/images/storage-arrays/device-parts-light.png
new file mode 100644
index 00000000..af7d4e7b
Binary files /dev/null and b/static/assets/images/storage-arrays/device-parts-light.png differ
diff --git a/static/assets/images/storage-arrays/download-sample-excel-dark.png b/static/assets/images/storage-arrays/download-sample-excel-dark.png
new file mode 100644
index 00000000..917789c9
Binary files /dev/null and b/static/assets/images/storage-arrays/download-sample-excel-dark.png differ
diff --git a/static/assets/images/storage-arrays/download-sample-excel-light.png b/static/assets/images/storage-arrays/download-sample-excel-light.png
new file mode 100644
index 00000000..f6c9bff8
Binary files /dev/null and b/static/assets/images/storage-arrays/download-sample-excel-light.png differ
diff --git a/static/assets/images/storage-arrays/edit-options-dark.png b/static/assets/images/storage-arrays/edit-options-dark.png
new file mode 100644
index 00000000..01910499
Binary files /dev/null and b/static/assets/images/storage-arrays/edit-options-dark.png differ
diff --git a/static/assets/images/storage-arrays/edit-options-light.png b/static/assets/images/storage-arrays/edit-options-light.png
new file mode 100644
index 00000000..6a0df9b7
Binary files /dev/null and b/static/assets/images/storage-arrays/edit-options-light.png differ
diff --git a/static/assets/images/storage-arrays/import-excel-sheet-dark.png b/static/assets/images/storage-arrays/import-excel-sheet-dark.png
new file mode 100644
index 00000000..bcbc9ec1
Binary files /dev/null and b/static/assets/images/storage-arrays/import-excel-sheet-dark.png differ
diff --git a/static/assets/images/storage-arrays/import-excel-sheet-light.png b/static/assets/images/storage-arrays/import-excel-sheet-light.png
new file mode 100644
index 00000000..f818db35
Binary files /dev/null and b/static/assets/images/storage-arrays/import-excel-sheet-light.png differ
diff --git a/static/assets/images/storage-arrays/light-page-dark.png b/static/assets/images/storage-arrays/light-page-dark.png
new file mode 100644
index 00000000..016ce4a9
Binary files /dev/null and b/static/assets/images/storage-arrays/light-page-dark.png differ
diff --git a/static/assets/images/storage-arrays/light-page-light.png b/static/assets/images/storage-arrays/light-page-light.png
new file mode 100644
index 00000000..edaca35d
Binary files /dev/null and b/static/assets/images/storage-arrays/light-page-light.png differ
diff --git a/static/assets/images/storage-arrays/linked-resource-dark.png b/static/assets/images/storage-arrays/linked-resource-dark.png
new file mode 100644
index 00000000..225167eb
Binary files /dev/null and b/static/assets/images/storage-arrays/linked-resource-dark.png differ
diff --git a/static/assets/images/storage-arrays/linked-resource-light.png b/static/assets/images/storage-arrays/linked-resource-light.png
new file mode 100644
index 00000000..74c3ebe9
Binary files /dev/null and b/static/assets/images/storage-arrays/linked-resource-light.png differ
diff --git a/static/assets/images/storage-arrays/sample-excel-download.png b/static/assets/images/storage-arrays/sample-excel-download.png
new file mode 100644
index 00000000..cd080358
Binary files /dev/null and b/static/assets/images/storage-arrays/sample-excel-download.png differ
diff --git a/static/assets/images/storage-arrays/search-filter-type-dark.png b/static/assets/images/storage-arrays/search-filter-type-dark.png
new file mode 100644
index 00000000..a5a0ca4e
Binary files /dev/null and b/static/assets/images/storage-arrays/search-filter-type-dark.png differ
diff --git a/static/assets/images/storage-arrays/search-filter-type-light.png b/static/assets/images/storage-arrays/search-filter-type-light.png
new file mode 100644
index 00000000..c4dbfffe
Binary files /dev/null and b/static/assets/images/storage-arrays/search-filter-type-light.png differ
diff --git a/static/assets/images/storage-arrays/storage-array-actions-dark.png b/static/assets/images/storage-arrays/storage-array-actions-dark.png
new file mode 100644
index 00000000..84dfd313
Binary files /dev/null and b/static/assets/images/storage-arrays/storage-array-actions-dark.png differ
diff --git a/static/assets/images/storage-arrays/storage-array-actions-light.png b/static/assets/images/storage-arrays/storage-array-actions-light.png
new file mode 100644
index 00000000..7c8f2dfd
Binary files /dev/null and b/static/assets/images/storage-arrays/storage-array-actions-light.png differ
diff --git a/static/assets/images/storage-arrays/view-physical-device-dark.png b/static/assets/images/storage-arrays/view-physical-device-dark.png
new file mode 100644
index 00000000..bc4077b4
Binary files /dev/null and b/static/assets/images/storage-arrays/view-physical-device-dark.png differ
diff --git a/static/assets/images/storage-arrays/view-physical-device-light.png b/static/assets/images/storage-arrays/view-physical-device-light.png
new file mode 100644
index 00000000..ab10c8b1
Binary files /dev/null and b/static/assets/images/storage-arrays/view-physical-device-light.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/add-tcp-port-scan-dark.png b/static/assets/images/tcp-port-scan-auto-discovery/add-tcp-port-scan-dark.png
new file mode 100644
index 00000000..d1d9e04f
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/add-tcp-port-scan-dark.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/add-tcp-port-scan-light.png b/static/assets/images/tcp-port-scan-auto-discovery/add-tcp-port-scan-light.png
new file mode 100644
index 00000000..cc4faf68
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/add-tcp-port-scan-light.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-1-dark.png b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-1-dark.png
new file mode 100644
index 00000000..26a14cbb
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-1-dark.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-1-light.png b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-1-light.png
new file mode 100644
index 00000000..bab56d1a
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-1-light.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-2-dark.png b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-2-dark.png
new file mode 100644
index 00000000..5cad0ac9
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-2-dark.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-2-light.png b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-2-light.png
new file mode 100644
index 00000000..ff0071a7
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-2-light.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-3-dark.png b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-3-dark.png
new file mode 100644
index 00000000..84f63692
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-3-dark.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-3-light.png b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-3-light.png
new file mode 100644
index 00000000..ff4b38c1
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/auto-create-settings-3-light.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/tcp-run-now-dark.png b/static/assets/images/tcp-port-scan-auto-discovery/tcp-run-now-dark.png
new file mode 100644
index 00000000..89fe4044
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/tcp-run-now-dark.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/tcp-run-now-light.png b/static/assets/images/tcp-port-scan-auto-discovery/tcp-run-now-light.png
new file mode 100644
index 00000000..1141d41f
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/tcp-run-now-light.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/tcp-schedule-dark.png b/static/assets/images/tcp-port-scan-auto-discovery/tcp-schedule-dark.png
new file mode 100644
index 00000000..d9c09664
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/tcp-schedule-dark.png differ
diff --git a/static/assets/images/tcp-port-scan-auto-discovery/tcp-schedule-light.png b/static/assets/images/tcp-port-scan-auto-discovery/tcp-schedule-light.png
new file mode 100644
index 00000000..909b9847
Binary files /dev/null and b/static/assets/images/tcp-port-scan-auto-discovery/tcp-schedule-light.png differ