Merge branch 'main' into docs-19.01.2

docs/auto-discovery/cloud-auto-discovery/google-cloud-platform-autodiscovery.mdx

@@ -18,11 +18,6 @@ Device42 can discover your inventory on the Google Cloud Platform (GCP).
 | SQL DB                      |                              | [SQL Admin API](https://www.googleapis.com/discovery/v1/apis/sqladmin/v1beta4/rest) | Tables, instances, etc. |
 | VMs                         | Devices -> All Devices       | [Compute API](https://www.googleapis.com/discovery/v1/apis/compute/v1/rest) | Type, Name, RAM, OS, CPU, cores, etc. |
 
-Data discovered on the Google Cloud Platform is similar to what you might be familiar with on AWS EC2 instances, namely:
-
-- Discovered Google Cloud VMs are added as virtual devices.
-- Cloud information is added inline in Device42 for each CI.
-
 ## Configure a GCP Discovery Job
 
 For Google Cloud Discovery, you need a user account with the built-in Google Cloud Platform "Viewer" role.

docs/auto-discovery/index.mdx

@@ -18,6 +18,24 @@ Running network discovery first is recommended, and is important because it lays
 
 **_WARNING_: Please do not set up an autodiscovery / scan using critical production account credentials!** _Depending on permissions granted & your configured password policies, account lock-out could result in an otherwise completely avoidable outage. You, the customer, are responsible for any such behavior that might result if you choose to ignore this requirement._
 
+### Discovery Exclusion List
+
+Prevent discovery from attempting communication with specific devices by adding them to the global exclusion list under **Tools > Global Settings**.
+
+The exclusion list is automatically copied and displayed on all new jobs to prevent newly created jobs from attempting any discovery action on these IP addresses.  
+
+The list of excluded IPs copied to the job can be seen in the newly created job's **Excluded Server(s)** section.
+
+<ThemedImage
+  alt="Exclude server(s) box in discovery job"
+  sources={{
+    light: useBaseUrl('/assets/images/autodiscovery/exclude-servers-light.png'),
+    dark: useBaseUrl('/assets/images/autodiscovery/exclude-servers-dark.png'),
+  }}
+/>
+
+Note that previously created jobs will not be affected or updated with changes to the exclusion list.
+
 ### Cloning Discovery Jobs
 
 You can now clone an autodiscovery job while editing it to create a copy of the job with all its settings, which lets you replicate the job without having to manually re-enter all the job details. You can then modify the cloned job for your specific purposes. Click on a discovery _Job Name_ in a View listing to select the job you want to clone and then click _Edit_. Click the ellipse menu in edit mode and then click _Clone Job._
@@ -50,24 +68,6 @@ Connect to Amazon AWS, Alibaba Cloud, Microsoft Azure, Digital Ocean, Google Clo
 
 DNS autodiscovery is built into Device42 and can do zone transfer(s) from your DNS server(s). It can be run and scheduled from the Device42 web UI: _Discovery > DNS Zone Sync (One way)_.
 
-## Exclusion List
-
-Prevent discovery from attempting communication with specific devices by adding them to the global exclusion list under **Tools > Global Settings**.
-
-The exclusion list is automatically copied and displayed on all new jobs to prevent newly created jobs from attempting any discovery action on these IP addresses.  
-
-The list of excluded IPs copied to the job can be seen in the newly created job's **Excluded Server(s)** section.
-
-<ThemedImage
-  alt="Exclude server(s) box in discovery job"
-  sources={{
-    light: useBaseUrl('/assets/images/autodiscovery/exclude-servers-light.png'),
-    dark: useBaseUrl('/assets/images/autodiscovery/exclude-servers-dark.png'),
-  }}
-/>
-
-Note that previously created jobs will not be affected or updated with changes to the exclusion list.
-
 ## Hypervisor / \*nix / Windows Autodiscovery
 
 Hypervisors, Windows & Linux/UNIX discovery jobs can all be created using the main menu, _Discovery -> HyperVisors / \*nix / Windows_.

docs/getstarted/installation/getting-started-on-a-mac.mdx

@@ -0,0 +1,118 @@
+---
+title: "Getting Started on a Mac"
+sidebar_position: 13
+---
+
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+import olderVbImage from '/assets/images/getting-started-on-a-mac/1-download-arm64.png'
+import openImage from '/assets/images/getting-started-on-a-mac/2-open-virtualbox.png'
+import successImage from '/assets/images/getting-started-on-a-mac/3-installation-success.png'
+
+## From the Start: How to Setup Device42 from the Beginning on a Mac
+
+### Prerequisites:
+
+To use Device42, use a hypervisor like [VirtualBox](https://www.virtualbox.org), VMWare Workstation, or [VMware Player](https://www.vmware.com/content/vmware/vmware-published-sites/us/products/desktop-hypervisor.html.html.html) to run a virtual machine. We'll use the open-source VirtualBox option in this guide.
+
+For Macs with Intel processors, [click here to download](https://www.virtualbox.org/wiki/Downloads) the latest `.dmg` file from VirtualBox.
+
+![Download VirtualBox](/assets/images/getting-started-on-a-mac/1-download-intel.png)
+
+For Macs with Apple Silicon processors (M1 and M2), download VirtualBox from "[​Developer preview for macOS / Arm64 (M1/M2) hosts](https://www.virtualbox.org/wiki/Download_Old_Builds_7_0)".
+
+<img src={olderVbImage} width="70%"/>
+
+Open the downloaded file, double click the "VirtualBox.pkg" icon, and install VirtualBox.
+
+<img src={openImage} width="70%"/>
+
+<img src={successImage} width="70%"/>
+
+## Installing Device42
+
+To download Device42, visit [Device42](https://www.device42.com/download/) and enter your name and work email address. You will receive a download link in your email momentarily. Choose the download labelled "VMware/Oracle VirtualBox" from the options.
+
+![Download Device42 Virtual Box OVF](/assets/images/getting-started-on-a-mac/4-software-download.png)
+
+Double click the downloaded file and unzip it.
+
+From VirtualBox, click the **Import** icon and follow the on-screen prompts. 
+
+![Import button](/assets/images/getting-started-on-a-mac/8-import-button.png)
+
+Browse to the OVF file you unzipped earlier. 
+
+![Select OVF](/assets/images/getting-started-on-a-mac/8-import-ovf.png)
+
+Visit [Sizing Recommendations](sizing-recommendations.md) for our recommended resource allocation specifications. 
+
+![Settings](/assets/images/getting-started-on-a-mac/9-appliance-settings.png)
+
+Please be patient while the Device42 VM imports, it shouldn't take too long. 
+
+![Importing OVF](/assets/images/getting-started-on-a-mac/10-importing-appliance.png)
+
+After the import completes, click **Power On** from the list on the left to start your new Device42 VM. press the green **Start** arrow at the top, and once the appliance boots, you will see the Device42 console:
+
+![Virtualbox on Mac running D42 VM](/assets/images/vbox_mac_d42_running.png)
+
+Log in to the console using the default credentials:
+- Username: `device42` 
+- Password: `d42adm!n`
+
+## Additional VM Settings
+
+Right-click on the newly created virtual machine in VirtualBox that appears on the left and choose **Settings**. In the window that pops up, select the **System > Processor** tab and click the **Extended Features:** checkbox to **Enable PAE/NX**.
+
+![Enable PAE](/assets/images/2016-01-08-get-started-mac-9.png)
+
+Continue to the **Network** tab, and confirm that **Adapter 1** is enabled and the "Bridged adapter" or "NAT" option is selected. Then choose the **Name** of the physical NIC or network card you will be using.
+
+![Enable Network Adapter](/assets/images/2016-01-08-get-started-mac-10.png)
+
+## Configuring your Device42 VM via the Console
+
+Power on your Device42 main appliance, if you haven't already. If you happen to receive an audio driver warning, you can safely ignore it.
+
+At the login screen, the username is: `device42` and the password is: `adm!nd42`. Please enter option **10** change these credentials when you first login. 
+
+![Device42 Login](/assets/images/getting-started-on-a-mac/14-login.png)
+
+When you are logged in, enter **1** to configure your IP settings (DHCP/Static). Please use a static IP for all production Device42 VMs to avoid connectivity issues.
+
+![Device42 menu](/assets/images/getting-started-on-a-mac/15-logged-in.png)
+
+You can apply updates and do other menu-related work by connecting through SSH using the terminal. Please note that `root` login has been disabled via SSH. 
+
+Finally, point your browser to the address at the top of the console menu.
+
+You will receive a "Your Connection is not private" warning in your browser because you are accessing a local server that is using a self-signed certificate. Your connection _is_ secure, and it is completely safe to click "show advanced" in Chrome or "I understand the risks" in Firefox and proceed through to the Device42 login screen.
+
+On Chrome:
+
+![](/assets/images/2016-01-08-get-started-mac-13.png)
+
+On Firefox:
+
+![](/assets/images/add_self-signed-cert-exception.png)
+
+When you've added your exception, you'll see the login screen. Login using Device42 web UI with the default credentials:
+- Username: `admin` 
+- Password: `adm!nd42`
+
+Now you can start using Device42.
+
+<ThemedImage
+  alt="Device42 UI Login Screen"
+  sources={{
+    light: useBaseUrl("/assets/images/getting-started-on-a-mac/login-light.png"),
+    dark: useBaseUrl("/assets/images/getting-started-on-a-mac/login-dark.png"),
+  }}
+  style={{ width: '70%' }} 
+/>
+
+## What's next?
+
+To continue through our documentation, you may want to view our [tutorials](/getstarted/tutorials/device42-tutorial.mdx) next.

docs/getstarted/installation/installation-amazon-web-services.mdx

@@ -9,7 +9,14 @@ import loginImg from '/assets/images/installation-amazon-web-services/login-appl
 
 ### Overview
 
-Device42 is available on AWS as a manual install or through the AWS Marketplace. The Device42 AWS offering involves an EC2 instance that houses the Device42 Main Appliance, Appliance Manager, and Remote Collector.
+The Device42 Main Appliance is available on AWS, either as a manual install or through the AWS marketplace.
+
+The Device42 Remote Collector is also available but via manual installation only. To get access, please submit a ticket requesting access to the Device42 Remote Collector Amazon Machine Image (AMI) and include the following information:
+
+- AWS Region for Device42 Deployment
+- AWS Account Number
+
+The Device42 AWS offering involves an EC2 instance that houses the Device42 Main Appliance, Appliance Manager, and Remote Collector.
 
 ![AWS architecture](/assets/images/aws-architecture.png)
 

docs/getstarted/installation/installation-microsoft-hyperv.md

@@ -41,8 +41,6 @@ Only HyperV Gen1 VMs are currently supported. In our experience, users have issu
 Power on the new machine and log in to the console using the default credentials:
 - **Username:** `device42`
 - **Password:** `adm!nd42`  
-
-- Use **(ubuntu/default)** for power appliance.
 
 Please change the credentials with option **10** below.
 
@@ -84,7 +82,8 @@ After you download the Device42 virtual appliance file, take the following steps
 
 1. Use 7zip to unzip the downloaded file.
 2. Create a Virtual machine with a **minimum** of 2 vCPU, 8 GB RAM for production use, and one network card. Configure the new VM to use the attached virtual disk file.
-3. Power on the new machine and log in to the console using the default credentials. Use **(ubuntu/default)** for power appliances. Please change the credentials using option **10**.
+
+3. Power on the new machine and log in to the console using the default credentials. Please change the credentials using option **10**.
 
     - **Username:** `device42`
     - **Password:** `adm!nd42`

docs/getstarted/installation/installation-vcenter-server.md

@@ -36,8 +36,6 @@ Download the compressed [Device42 virtual appliance](https://www.device42.com/do
    - **Username:** `device42`
    - **Password:** `adm!nd42` 
 
-   _(Deprecated appliance logins: 32-bit: ubuntu/adm!nd42 -- Power: ubuntu/default)._
-
    ![Device42 console login screen](/assets/images/d42-console-login-screen-v15.png)
 
    **Change the default password using option 10 on the appliance console.**