Merge pull request #477 from ritza-co/1146-installation

Proposed Installation section improvements

Author: sixhobbits

docs/getstarted/installation/how-do-i-install-device42-xenkvm-appliance-if-import-existing-disk-image-option-is-missing.mdx

@@ -1,12 +1,23 @@
 ---
 title: "Xen or KVM - Import Disk Alternate Install"
-sidebar_position: 17
+sidebar_position: 9
 ---
 
 :::info
 These are **special case** installation instructions for installing the Device42 appliance on Xen- or KVM-based platforms if the **Import existing disk image** option is missing. Otherwise, please refer to the Device42 [guide to Xen and KVM installation](getstarted/installation/installation-xen-or-kvm-using-virt-manager.mdx).
 :::
 
+## Outline of Alternative Installation
+
+1. Download the Device42 image and use bunzip2 to uncompress the image.
+2. Create a new virtual machine using the **Network Boot** option and complete the installation wizard setup. 
+3. Disable **Network (PXE)** from the Device42 virtual machine **Boot Options**.
+4. Log in to the Device42 console and web interface as described in the [Set Up the Main Appliance](installation-xen-or-kvm-using-virt-manager.mdx#set-up-the-main-appliance-and-log-in) section and later of the Virt-Manager installation page.
+
+## Illustrated Installation Steps
+
+The following alternative installation steps are similar to the [standard Virt-Manager installation](getstarted/installation/installation-xen-or-kvm-using-virt-manager.mdx), except that you select the **Network Boot** option instead of importing the Device42 image and then disable the network boot. 
+
 ### Download and Uncompress with bunzip2
 
 The raw image for Xen or KVM has been compressed using bzip2. When you get the file on the KVM host, run the `bunzip2` command to uncompress the file:
@@ -19,31 +30,31 @@ bunzip2 device42-3.2.3-raw.img.bz2
 
 Once you have uncompressed the downloaded raw image, create a new virtual machine. 
 
-Choose the **Network Boot** option. We'll add the disk later. Please make sure you don't have any kind of automated network boot enabled for this machine. You will not see the **Import existing disk image** option.
+Choose the **Network Boot** option. We'll add the disk later. Make sure you don't have some sort of automated network boot enabled for this machine. You will not see the **Import existing disk image** option.
 
 ![Install](/assets/images/wpid2483-Install.png)
 
 ### Choose OS and Version
 
-Choose **Linux** as the **OS type** and **Ubuntu 14.04** for the **Version**. If you don't see the option for **14.04**, choose the latest version available.
+Choose **Linux** as the **OS type** and the latest Ubuntu version in the **Version** field.
 
 ![Choosing OS and version](/assets/images/wpid2480-Choosing_OS_and_version.png)
 
-Allocate at least `8` GB RAM and `2` vCPU for production appliances. See the Device42 [Sizing Recommendations](sizing-recommendations.mdx) page for more information.
+Allocate at least 8 GB RAM and 2 vCPUs for production appliances. See [Sizing Recommendations](sizing-recommendations.mdx).
 
 ![](/assets/images/wpid2484-media_1326264722468.png)
 
-### Choose Disk (bunzipped File)
+### Choose Disk
 
-![Choose disk(bunzipped file)](/assets/images/wpid2479-Choose_disk_bunzipped_file_.png)
+![Choose disk](/assets/images/wpid2479-Choose_disk_bunzipped_file_.png)
 
 Choose your virtualization type under the **Advanced options** and select **i686** as the **Architecture**.
 
 ![](/assets/images/wpid2487-media_1352976855381.png)
 
 ### Disable Network Boot
 
-Go to **Details** (1) > **Boot Options** (2), then uncheck **Network(PXE)** and click **Apply** (4).
+Go to **Details** (1), **Boot Options** (2), uncheck **Network (PXE)**, and click **Apply** (4).
 
 ![Disable network boot](/assets/images/wpid2481-Disable_network_boot.png)
 

docs/getstarted/installation/index.mdx

@@ -2,10 +2,38 @@
 title: "Installation"
 ---
 
-:::danger
-IMPORTANT NOTICE: Device42 is delivered as a virtual appliance. Root access to the appliance is not supported, and the VM will cease to function if you attempt to break into the root account.
-:::
+Welcome to the Device42 installation guide. This page outlines installing Device42 for the purposes of mapping and gaining insight into your IT environment.
 
-In this section, we will discuss how to install Device42 and use it in your organization. To test Device42, we recommend you use the Device42 SaaS platform and properly provisioned and specced hardware. See the general [sizing recommendations](sizing-recommendations.mdx) for details. You can also sign up for a [free trial of Device42](https://www.device42.com/try-device42/) or [join us in a live demo](https://www.device42.com/weekly-demo/?nab=0).
+## Getting Started
 
-The subpages in this category provide platform-specific instructions for various providers, including AWS, Azure, and Citrix, and can be accessed via the sidebar.
+Device42 is delivered as a virtual appliance, which you install on a virtualization platform.
+
+Before you begin:
+- Review the [sizing recommendations](sizing-recommendations.mdx) to ensure your environment is properly provisioned.
+- Visit the [security posture and high-level permissions](security-posture-and-high-level-permissions.mdx) page.
+- See the [discovery port configurations](discovery-port-configurations.mdx) for network requirements.
+
+## Installation Process Overview
+
+Device42 consists of three components to install. First, install the Device42 Main Appliance (the Device42 application and user interface), followed by the Remote Collector (RC) and Windows Discovery Service (WDS). 
+
+When you run a discovery, the Device42 MA uses the WDS to collect information about Windows environments and uses the RC to collect information about all other IT environments.
+
+See the next [Resource and Deployment Architecture](resource-and-deployment-architecture-overview.mdx) page for more information about these core Device42 components and how they fit together.
+
+After you install the Main Appliance, RC, and WDS, you can install the [Device42 NetFlow Collector](installing-the-d42-netflow-collector-as-a-service.mdx) to improve [Application Dependency Mapping](/apps/enterprise-application-dependency-mapping/index.mdx) discovery.
+
+## Choose Your Platform
+
+Select the platform-specific installation guide from the sidebar that matches your environment:
+
+- [VMware vCenter Server](installation-vcenter-server.mdx)
+- [Microsoft Hyper-V](installation-microsoft-hyperv.mdx)
+- [Citrix Xen Server](installation-citrix-xen-server.mdx)
+- [Xen or KVM](installation-xen-or-kvm-using-virt-manager.mdx) 
+- [Amazon Web Services (AWS)](installation-amazon-web-services.mdx)
+- [Microsoft Azure](installation-microsoft-azure.mdx)
+
+## Try Device42
+
+Sign up for a [free trial of Device42](https://www.device42.com/try-device42/) or [join us in a live demo](https://www.device42.com/weekly-demo/?nab=0) to see the platform in action.

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

@@ -1,24 +1,24 @@
 ---
 title: "Amazon Web Services - Installation"
-sidebar_position: 9
+sidebar_position: 10
 ---
 
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 import loginImg from '/assets/images/installation-amazon-web-services/login-appliance-manager.png'
 
-## Overview
+The Device42 Amazon Web Services (AWS) offering involves an EC2 instance that houses the Device42 Main Appliance (MA), Appliance Manager (AM), and Remote Collector (RC).
 
-The Device42 Main Appliance (MA) is available on Amazon Web Services (AWS), either as a manual installation or through the AWS Marketplace.
+![AWS architecture](/assets/images/aws-architecture.png)
 
-The Device42 Remote Collector (RC) is only available via manual installation. To request access, please submit a ticket to the Device42 RC Amazon Machine Image (AMI) and include the following information:
+## Overview
 
-- The AWS region for Device42 deployment.
-- The AWS account number.
+The Device42 Main Appliance is available on AWS, either as a manual installation or through the AWS Marketplace — this guide has instructions for both options.
 
-The Device42 AWS offering involves an EC2 instance that houses the Device42 MA, Appliance Manager (AM), and RC.
+The Device42 RC is only available via manual installation only. To request access, please submit a ticket to the Device42 RC Amazon Machine Image (AMI) and include the following information:
 
-![AWS architecture](/assets/images/aws-architecture.png)
+- The AWS region for Device42 deployment
+- The AWS account number
 
 ## Costs and Licensing
 
@@ -316,9 +316,8 @@ The following is a sample IAM policy (with minimum appropriate permissions) that
 ### Security, Privacy, and Other Considerations
 
 - The Device42 AWS offering does not restrict the Instance Metadata Service version.
-- The Device42 AWS offering does not require AWS data encryption to operate properly.  
+- The Device42 AWS offering does not require AWS data encryption to operate properly.
 - Customer data resides on the instance itself. Customer passwords and secrets are encrypted with AES-256 encryption.
 
   Refer to the Device42 [Secrets, Security, and Permissions](administration/passwords/password-security-and-permissions.mdx) page for additional information on how passwords and secrets are stored.
-
 - The Device42 AWS offering does not require the storage of any secrets in AWS Secrets Manager.

docs/getstarted/installation/installation-citrix-xen-server.mdx

@@ -1,70 +1,115 @@
 ---
-title: "Citrix Xen Server - Installation"
-sidebar_position: 11
+title: "Citrix XenServer - Installation"
+sidebar_position: 7
 ---
 
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-Download the compressed [Device42 virtual appliance](https://www.device42.com/download/) and take following steps:
+This guide walks you through installing the Device42 Main Appliance on Citrix XenServer.
+
+## Outline of Installation Steps
+
+1. Download and unzip the compressed Device42 virtual appliance.
+2. From XenCenter, import the unzipped file.
+3. Follow the Citrix prompts and choose your server, storage location, and network card.
+4. Power on the newly deployed Device42 virtual appliance.
+5. Log in to the Device42 console using the default credentials and update the credentials.
+6. Configure the static IP address from the console.
+7. Log in to the Device42 web interface from a browser: `https://FQDN (Fully Qualified Domain Name) or IP address`. Update the login credentials here as well.
+
+## Illustrated Steps of Installing Device42 on Citrix XenServer
+
+Set up your Device42 instance by following these steps.
+
+### Download and Unzip Device42
+
+Download the compressed [Device42 virtual appliance](https://www.device42.com/download/) and connect to your XenCenter.
+
+Use 7-Zip to decompress the downloaded Device42 virtual appliance image.
+
+### Import Device42 into XenCenter
+
+From XenCenter, right-click the server's name and select **Import**.
 
-1. Use 7zip to unzip the downloaded file.
-2. From XenCenter, right-click the server's name and select **Import**.
-   
     ![Here are the steps in Images:](/assets/images/wpid5942-wpid-media_1331243551635.png)
 
-3. Choose Source.
-   
+Choose the source file you downloaded.
+
     ![Locate the file you you downloaded](/assets/images/wpid5943-wpid-media_1331243622364.png)
 
-4. Choose Server.
+### Configure Server, Storage, and Network
+
+Choose your server (or accept the default pool).
 
     ![Choose a pool, or accept the default (next)](/assets/images/wpid5944-wpid-media_1331243664174.png)
 
-5. Choose Storage.
-   
+Choose a storage location for the VM.
+
     ![Choose a storage location for the VM](/assets/images/wpid5945-wpid-media_1331243689911.png)
 
-6. Choose the network card and click **Finish**.
-   
+Choose the network card and click **Finish**.
+
     ![Choose the network to connect the VM to](/assets/images/wpid5946-wpid-media_1331243717545.png)
     ![Click finish](/assets/images/wpid5947-wpid-media_1331243745178.png)
 
-7. Power on the VM and log in to the console with the default credentials: 
+### Start the Device42 VM
+
+Power on your newly deployed Device42 virtual appliance.
+
+### Log In to the Device42 Console
+
+From the XenCenter interface, open the VM console for your Device42 appliance. The Device42 console login screen will appear automatically.
+
+Log in using the default credentials and change them after logging in: 
 
    - **Username:** `device42`
-   - **Password:** `adm!nd42` 
-  
-   **Change the default password using option 10 on the appliance console.**
+   - **Password:** `adm!nd42`
+
+_(Deprecated appliance logins: 32-bit: ubuntu/adm!nd42 -- Power: ubuntu/default)._
 
-   _(Deprecated appliance logins: 32-bit: ubuntu/adm!nd42 -- Power: ubuntu/default)._ 
+### Configure the Static IP Address
 
-    ![Log in to the VM Console](/assets/images/wpid5950-media_1419606545144.png)
+From the console, configure the IP address. Use a **static IP** for all production Device42 VMs to avoid connectivity issues.
 
-8. Choose option **U** to configure networking. 
-   
     ![Device42 VM console menu v19.05](/assets/images/vm-main-menu.png)
 
-   To avoid connectivity issues, please use a static IP address for all production Device42 Installations.
+    Enter your settings on the Device42 IP address configuration screen:
+
+    ![IP config options](/assets/images/vm-ip-settings.png)
+
+### Create a DNS Entry
+
+This is an optional step: Create a DNS entry for the new IP address of the virtual appliance.
+
+### Log In to the Web Interface
+
+Point your browser to `https://FQDN (Fully Qualified Domain Name) or IP address`.
+
+Log in to the **web interface** using the default credentials:
+
+    - **Username:** `admin`
+    - **Password:** `adm!nd42`
+
+    Please change the username and password as soon as you log in.
+
+    <ThemedImage
+    alt="Device42 Web Interface Login Screen v19.05"
+    sources={{
+        light: useBaseUrl('/assets/images/login-19.05-light.png'),
+        dark: useBaseUrl('/assets/images/login-19.05-dark.png'),
+    }}
+    style={{ width: '70%' }}
+    />
+
+You should be up and running, and are now ready to go! If you have any questions that you can't find answers to in the docs, email [[email protected]](mailto:[email protected]).
 
-    ![IP config options v19.05](/assets/images/vm-ip-settings.png)
+## Using SSH
 
-9.  The default password for user `device42` can now be changed from the console menu using option number **10**. 
-    
-    You can apply updates and do other menu-related work using SSH **port 404**. Please note that root login has been disabled via SSH. Attempting to access the root will cause the VM to disable itself permanently and is not supported.
-10. Point your browser to `https://FQDN(Fully Qualified Domain Name) or IP-address`.
-11. Log in to the **web interface** using the default credentials:
+You can apply updates and do other menu-related work using SSH port 404. Please note that root login has been disabled via SSH. Attempting to access the root will cause the VM to disable itself permanently and is not supported.
 
-    - **Username** `admin` 
-    - **Password:** `adm!nd42` 
+## Next Steps
 
-    **Please change the username and password as soon as you log in.**
+Install the Device42 [Remote Collector](remote-collector-rc-installation.mdx) and [Windows Discovery Service](windows-discovery-service-installation.mdx) before creating your first discovery job.
 
-<ThemedImage
-  alt="Device42 UI Login Screen v19.05"
-  sources={{
-    light: useBaseUrl('/assets/images/login-19.05-light.png'),
-    dark: useBaseUrl('/assets/images/login-19.05-dark.png'),
-  }}
-  style={{ width: '70%' }}
-/>
+You can import data into Device42 using the [Device42 API](https://api.device42.com/) or the [**Import/Export (xls)**](/getstarted/tutorials/tutorial-loading-data-using-spreadsheets.mdx) tool.