Merge pull request #376 from ritza-co/docs-19.03.02

Docs 19.03.02 release (Week 41, 2024)

docs/administration/advanced-routing.md

@@ -3,17 +3,30 @@ title: "Advanced Routing"
 sidebar_position: 2
 ---
 
-You can add complex or advanced routing for your Device42 appliance or delete it using the console menu.
+You can add complex or advanced routing for your Device42 appliance or delete it using the virtual machine (VM) console menu. 
 
-1. To configure advanced routing, choose option **15** from the **Device42 Setup/Troubleshooting Menu**. Log in to the console of the Device42 VM to access this menu: 
+To add a new route, follow these steps:
 
-    ![advanced-routing-option](/assets/images/advanced-routing/console-advanced-routing-option.png)
+1. Log in to the Device42 VM console.
+2. Choose **(u) Network, Connectivity and Utilities**.
 
-2. To add a new route, enter option **a**. Print the routing table with option **b**.
+    ![Network options](/assets/images/advanced-routing/1-network.png)
+
+3. Select **(r) Routing**.
+
+    ![Routing options](/assets/images/advanced-routing/2-routing.png)
+
+4. Select **(a) Add a new Route** from the **Routing Configuration Main Menu**.
 
-    ![Advanced routing options](/assets/images/advanced-routing/console-routing-submenu.png)
+    ![Add route option](/assets/images/advanced-routing/3-route-options.png)
+
+5. Fill in the new route details and click **Add Route**. Use the `Tab` key to navigate to the next field. 
+
+    ![Add route details](/assets/images/advanced-routing/4-route-details.png)
 
-3. After configuring the new route, enter option **d** to apply changes. The Device42 VM must be manually rebooted to clear deleted routes.
+6. After configuring the new route, enter option **(p) Apply Routes** from the previous menu to apply the changes. 
+
+The Device42 VM must be manually rebooted to clear deleted routes.
 
 :::info
 Advanced routing instructions are also available [in video format here](how-to-videos/add-a-new-route-to-device42.md).

docs/getstarted/index.md

@@ -3,18 +3,20 @@ title: "The Hitchhiker's Guide to Device42"
 sidebar_postion: 1
 ---
 
-Welcome to _"The Hitchhiker's Guide to Device42"_, AKA the Device42 Docs site. The following pages contain answers to the ultimate questions about infrastructure, the data-center, and everything _(and of course, answers to many common Device42 questions, as well)_.
+Welcome to **The Hitchhiker's Guide to Device42**, AKA the Device42 docs site. 
 
-**Navigate through the D42 documentation topics using either the navigation bar to your left, and/or search for help using the search box found hanging out at the top right of the page - _much in the same way that bricks don't._**
+The following pages contain answers to the ultimate questions about infrastructure, the data center, and everything _(and the answers to many common Device42 questions, too)_.
+
+**Navigate through the Device42 documentation topics using the left-hand navigation bar or the search box found hanging out at the top right of the page - _much the same way that bricks don't_.**
 
 * * *
 
 ## What is Device42?
 
-Device42 is a comprehensive IT infrastructure management software suite with powerful agentless autodiscovery and application dependency mapping tools, a configuration management database (CMDB), a complete data center infrastructure management (DCIM) suite, full IT asset & inventory management (ITAM) functionality, plus IP address management (IPAM), password management and lots more -- all _in a single tool_.
+Device42 is a comprehensive IT infrastructure management software suite with powerful, agentless autodiscovery and application dependency mapping tools, a configuration management database (CMDB), a complete data center infrastructure management (DCIM) suite, full IT asset and inventory management (ITAM) functionality, plus IP address management (IPAM), password management and lots more - all in a single tool.
 
 * * *
 
-If you aren't able to find an answer to your question in the menu or using search, click  [here](https://support.device42.com) to open a support ticket. If you'd prefer, send us a note at [[email protected]](mailto:[email protected]). Our support team _loves_ hearing from customers, and are all especially fond of a good challenge!
+If you don't find an answer to your question in the menu or using search, click  [here](https://support.device42.com) to open a support ticket or send us a note at [[email protected]](mailto:[email protected]). Our support team _loves_ hearing from customers, and they're all especially fond of a good challenge!
 
 

docs/getstarted/installation/resource-and-deployment-architecture-overview.md

@@ -6,35 +6,32 @@ Learn about the Device42 core resources and how they fit into our deployment arc
 
 ## Device42 Resources
 
-**Main Appliance:** The Device42 Main Appliance is the kick off point for all the discovery
-and insights that will proliferate through your environment. It is a pre-configured virtual
-appliance (built on Linux) that is hosted by the end customer, enabling full protection under the
-client’s data center security architecture and policies.
+### Main Appliance
 
-Device42 operates with only 5 ports open to the virtual appliance:
-- Port 80: redirects to 443
-- Port 443: web (HTTPS)
-- Port 4242: redirects to 4343
-- Port 4343: appliance manager (HTTPS)
-- Port 404: SSH for limited console menu operations
+The Device42 Main Appliance (MA) is the kick-off point for all the discovery and insights that will proliferate through your environment. It is a preconfigured virtual appliance (built on Linux) hosted by the end customer, enabling full protection under the client’s data center security architecture and policies.
 
-**Remote Collector:** The Remote Collector (RC), is a much lighter pre-configured virtual
-appliance (built on Linux), used to perform agentless discovery across network segments. It
-also provides scalability by offloading discovery workloads from the MA. We require that you
-install at least 1 RC with any deployment of Device42.
+Device42 operates with only five ports open to the virtual appliance:
 
-**Windows Discovery Service:** The Windows Discovery Service (WDS) is a .net service which
-runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. If
-you’ll be running Windows discoveries, you will need to deploy at least 1 WDS instance and
-connect it to an RC.
+- **Port 80:** Redirects to port 443
+- **Port 443:** Web (HTTPS)
+- **Port 4242:** Redirects to port 4343
+- **Port 4343:** Appliance manager (HTTPS)
+- **Port 404:** SSH for limited console menu operations
 
-## Deployment Architecture 
+### Remote Collector
 
-Device42 deployment architecture is similar to a hub and spoke model, with each RC/WDS
-collecting data and syncing back to the centralized MA. It is typically recommended for RCs
-and WDS instances to be deployed in pairs, if Windows discovery is required.
+The Remote Collector (RC) is a much lighter preconfigured virtual appliance (built on Linux) used to perform agentless discovery across network segments. It also provides scalability by offloading discovery workloads from the MA. We require you to install at least one RC with any deployment of Device42.
 
-Device42 Deployment Example: Segmented Network
+### Windows Discovery Service
 
-![](/assets/images/deployment-architecture.png)
+The Windows Discovery Service (WDS) is a `.net` service that runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. If you’ll be running Windows discoveries, you will need to deploy at least one WDS instance and connect it to an RC.
+
+## Deployment Architecture
+
+Device42 deployment architecture is similar to a hub-and-spoke model, with each RC/WDS collecting data and syncing back to the centralized MA. It is typically recommended that RCs and WDS instances are deployed in pairs if Windows discovery is required.
 
+### Device42 Deployment Example
+
+The following image illustrates the segmented network structure used for Device42 deployments.
+
+![](/assets/images/deployment-architecture.png)

docs/getstarted/installation/security-posture-and-high-level-permissions.md

@@ -7,10 +7,12 @@ The section outlines how Device42 ensures data security in transit and at rest,
 
 ## Security Posture
 
-- All data in transit from WDS to RC and RC to MA is over SSL or HTTPS.
+- All data in transit from Windows Discovery Service (WDS) to Remote Collector (RC), and RC to Main Appliance (MA) is transferred via Secure Sockets Layer (SSL) or HTTPS.
 - All data stays at rest within the MA in an end-user environment.
 - Only data voluntarily shared by the end user leaves the premises.
 
 ## Required Permissions
 
-Device42 uses the principle of least privilege in it’s agentless discovery. For a detailed overview of permissions, please reference our Pre-requisites guide or please see the discovery section on our website and locate the relevant jobs for clarity on required permissions.
+Device42 uses the principle of least privilege in its agentless discovery.
+
+For a detailed overview of permissions, please reference our prerequisites guide or use the **Discovery** section on our website to locate the relevant jobs and view their required permissions.