Merge pull request #331 from ritza-co/18.14.4-link-fixes

hotfix links

docs/apps/application-components/application-component-templates.md

@@ -5,7 +5,7 @@ sidebar_position: 1
 
 ## Introduction
 
-You can use Application Component Templates to create and define your own application components based on services discovered by Device42 [Hypervisor /\*nx/Windows](auto-discovery/windows-and-hyper-v-auto-discovery.md) autodiscovery jobs run against \*nix and Windows platforms. Device42 adds any application components created based on your templates to the [Application Components](apps/application-components/application-component-templates.md) list page.
+You can use Application Component Templates to create and define your own application components based on services discovered by Device42 [Hypervisor /*nx/Windows](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx) autodiscovery jobs run against *nix and Windows platforms. Device42 adds any application components created based on your templates to the Application Components list page.
 
 ## View Application Component Templates
 

docs/auto-discovery/auto-discovery-system-requirements.md

@@ -21,8 +21,8 @@ The following are pre-requisites and other general requirements and guidelines f
 
 Detailed permission info:
 
-- Windows & WMI namespace: [Windows & HyperV Discovery](auto-discovery/windows-and-hyper-v-auto-discovery.md) page
-- Linux / sudo usage info: [Linux & Unix Server Discovery](auto-discovery/linux-unix-server-auto-discovery.md) page
+- Windows & WMI namespace: [Windows & HyperV Discovery](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx) page
+- Linux / sudo usage info: [Linux & Unix Server Discovery](/auto-discovery/linux-unix-server-auto-discovery.mdx) page
 
 Contact [email protected] with any further questions regarding specific privilege level requirements for WMI Namespaces, and \*nix commands run with/without sudo.
 

docs/auto-discovery/database-discovery/index.mdx

@@ -66,7 +66,7 @@ The snippet shown below is necessary to get data from some of the preceding view
 
 ![](/assets/images/D42-21939_Unencrypted-conns-for-SQL-db-2.png)
 
-Be sure to fill out both sets of credentials – the first set (_Database Username / Password_) to authenticate to the Microsoft SQL database itself and the second (_Discovery Targets Credentials_) to authenticate to the Windows server itself (like you’re used to for [regular Windows-based discovery targets](auto-discovery/windows-and-hyper-v-auto-discovery.md)).
+Be sure to fill out both sets of credentials – the first set (_Database Username / Password_) to authenticate to the Microsoft SQL database itself and the second (_Discovery Targets Credentials_) to authenticate to the Windows server itself (like you’re used to for [regular Windows-based discovery targets](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx)).
 
 You can enter an ordered list of preferred _Discovery Target(s) Credential(s)_ when you create a database discovery job. When the job runs, it will use the credentials in the order in which you enter them, stopping at the first successful authentication. Subsequent job runs use the last successful credential and then the remaining credentials in the ordered list.
 

docs/auto-discovery/hypervisors-and-containers-supported-in-auto-discovery.md

@@ -4,8 +4,8 @@ sidebar_position: 30
 ---
 
 If you were looking for how-to 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.md) page 
-- or the [Linux / UNIX server auto-discovery](auto-discovery/linux-unix-server-auto-discovery.md) page.
+- 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
 

docs/auto-discovery/index.md

@@ -56,7 +56,7 @@ Hypervisors, Windows & Linux/UNIX discovery jobs can all be created using the ma
 - VMWare hypervisor host and guest VM details are discovered using appropriate APIs <small(VMware, WMI)
 - Hyper-V hypervisors / guests are discovered as Windows machines using WinRM, and documented separately.
 
-Click here for the [VMware & VM discovery docs](virtual-machine-auto-discovery.md) page, and find the [Linux/UNIX discovery page](auto-discovery/linux-unix-server-auto-discovery.md) here. Finally, learn more about [Windows (and HyperV) discoveries are documented here](auto-discovery/windows-and-hyper-v-auto-discovery.md).
+Click here for the [VMware & VM discovery docs](virtual-machine-auto-discovery.md) page, and find the [Linux/UNIX discovery page](linux-unix-server-auto-discovery.mdx) here. Finally, learn more about [Windows (and HyperV) discoveries are documented here](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx).
 
 ## IPMI Autodiscovery
 

docs/auto-discovery/linux-based-autodiscovery-software.md

@@ -3,7 +3,7 @@ title: "Linux Based Autodiscovery Software"
 sidebar_position: 17
 ---
 
-**Note:** Since v13.2, Device42 has supported Linux (and UNIX) based autodiscovery from within the main UI. If you are simply trying to run discovery against Linux or UNIX, see our [Linux and UNIX Server AutoDiscovery Instructions.](./linux-unix-server-auto-discovery.md) or our [Remote Collector documentation](remote-collector-rc.md). If you want to use the standalone Linux discovery tools, continue reading below.
+**Note:** Since v13.2, Device42 has supported Linux (and UNIX) based autodiscovery from within the main UI. If you are simply trying to run discovery against Linux or UNIX, see our [Linux and UNIX Server AutoDiscovery Instructions.](linux-unix-server-auto-discovery.mdx) or our [Remote Collector documentation](remote-collector-rc.md). If you want to use the standalone Linux discovery tools, continue reading below.
 
 # Linux Based Autodiscovery Software
 

docs/auto-discovery/linux-unix-server-auto-discovery.mdx

@@ -6,7 +6,7 @@ sidebar_position: 16
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-Device42 supports SSH-based Linux and UNIX discovery from within the main appliance (v13.2+). For a full list of supported Linux/UNIX operating systems, please visit [Device42 Supported Operating Systems.](auto-discovery/operating-systems-supported-in-auto-discovery.md)
+Device42 supports SSH-based Linux and UNIX discovery from within the main appliance (v13.2+). For a full list of supported Linux/UNIX operating systems, please visit [Device42 Supported Operating Systems.](operating-systems-supported-in-auto-discovery.md)
 
 ## Information Discovered
 
@@ -97,7 +97,7 @@ sources={{
 **Domains to strip**: Ordered list of domains to strip from hostname, one per line - if blank, full domain stripped; if specified, the first match is stripped.  
 **Set the device name as the name given in the server field of the autodiscovery job**: if checked & discovering via hostname/FQDN, the device will be named using the discovery target name provided.  
 **Overwrite existing device hostname with discovered hostname**: Check this option to give precedence to the discovered hostname.  
-**Device Name Format**: select desired device naming format; see ["Configuring hostname discovery details"](auto-discovery/linux-unix-server-auto-discovery.md#section-7) below for explanations.
+**Device Name Format**: select desired device naming format; see ["Configuring hostname discovery details"](/auto-discovery/linux-unix-server-auto-discovery.mdx#section-7) below for explanations.
 
 ### Host Discovery
 

docs/auto-discovery/storage-arrays-autodiscovery/snmp-san-server-auto-discovery.md

@@ -5,9 +5,9 @@ sidebar_position: 5
 
 ## SNMP Discovery Overview
 
-The SNMP autodiscovery method can be used for any SNMP-compatible devices. For [SNMP Network Device discovery, see our Network Device discovery documentation here](../network-auto-discovery.mdx). For SNMP based Server autodiscovery, read below. This page discusses discovery of servers and SANs via SNMP. This method will also find Windows and Linux servers. However, more information will be retrieved by the [Linux & UNIX Server Auto-Discovery documentation pages](../linux-unix-server-auto-discovery.md). For Linux and Windows servers, this method retrieves the name, MAC & IP addresses, and IP properties. If the servers happen to be Dell machines and have Dell OpenManage installed, it will additionally find serial #, model, and some other relevant information.
+The SNMP autodiscovery method can be used for any SNMP-compatible devices. For [SNMP Network Device discovery, see our Network Device discovery documentation here](/auto-discovery/network-auto-discovery.mdx). For SNMP based Server autodiscovery, read below. This page discusses discovery of servers and SANs via SNMP. This method will also find Windows and Linux servers. However, more information will be retrieved by the [Linux & UNIX Server Auto-Discovery documentation pages](/auto-discovery/linux-unix-server-auto-discovery.mdx). For Linux and Windows servers, this method retrieves the name, MAC & IP addresses, and IP properties. If the servers happen to be Dell machines and have Dell OpenManage installed, it will additionally find serial #, model, and some other relevant information.
 
-**Note:** Device42 recommends that you execute Hypervisor server discovery using our specialized Hypervisor job types. See the  [Windows / Hyper-V Discovery](auto-discovery/windows-and-hyper-v-auto-discovery.md) page and the [Linux / UNIX server auto-discovery](auto-discovery/linux-unix-server-auto-discovery.md) page for more information.
+**Note:** Device42 recommends that you execute Hypervisor server discovery using our specialized Hypervisor job types. See the  [Windows / Hyper-V Discovery](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx) page and the [Linux / UNIX server auto-discovery](/auto-discovery/linux-unix-server-auto-discovery.mdx) page for more information.
 
 ## NetApp, EMC, & Dell NAS/SAN Storage Discovery
 

docs/auto-discovery/windows-and-hyper-v-auto-discovery.mdx

@@ -10,7 +10,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 Device42 discovery can utilize multiple protocols to communicate with the target devices. Either WinRM or WMI can be utilized for windows discovery. As of 18.10.00, WMI is the default protocol.
 
-When using WMI and before setting up your Windows Discovery job, you must first install WDS and connect to your Remote Collectors. For WDS installation instructions and information, visit the [Windows Discovery Service (WDS) installation](getstarted/installation/windows-discovery-service-installation.md) documentation.
+When using WMI and before setting up your Windows Discovery job, you must first install WDS and connect to your Remote Collectors. For WDS installation instructions and information, visit the [Windows Discovery Service (WDS) installation](/getstarted/installation/windows-discovery-service-installation.md) documentation.
 
 Your OS must be at Windows 8.1, Windows Server 2012 R2 or above with the latest patches installed.
 

docs/auto-discovery/z-os-ibm-mainframe.md

@@ -54,7 +54,7 @@ As of v15+, Device42 can discover IBM mainframes running the z/OS operating syst
 **Software and Applications**: Options to discover software and services.  
 **Miscellaneous**: Select service level, service customer, device VRF group, and tags
 
-For information on other jobs that can be run via this screen, see the dedicated [Linux / Unix Discovery Docs page](auto-discovery/linux-unix-server-auto-discovery.md). Note that discovery jobs for the [IBM mid-range AS/400 platform](auto-discovery/ibm-i-as400.md) can also be created via this job screen!
+For information on other jobs that can be run via this screen, see the dedicated [Linux / Unix Discovery Docs page](/auto-discovery/linux-unix-server-auto-discovery.mdx). Note that discovery jobs for the [IBM mid-range AS/400 platform](ibm-i-as400.md) can also be created via this job screen!
 
 ## Run Now or Schedule
 

docs/infrastructure-management/ipam/index.md

@@ -10,9 +10,9 @@ title: "IPAM"
 
 There are multiple ways Device42 can discover IP Addresses and related information:
 
-- [Network SNMP Discovery](auto-discovery/network-auto-discovery.mdx): Configuring and running SNMP autodiscovery to gather subnets, IP to MAC Address relationships, and MAC Address to Switch Port relationship information.
-- [Device42's Auto Discovery](auto-discovery/windows-and-hyper-v-auto-discovery.md): Using the autodiscovery client to discover Microsoft Windows and Linux and/or UNIX devices on your network, including their IP and MAC Address details.
-- [Device42's Ping Sweep Tool](auto-discovery/d42-ping-sweep.md): This page details usage of the ping sweep utility to keep your IP Address information up-to-date.
+- [Network SNMP Discovery](/auto-discovery/network-auto-discovery.mdx): Configuring and running SNMP autodiscovery to gather subnets, IP to MAC Address relationships, and MAC Address to Switch Port relationship information.
+- [Device42's Auto Discovery](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx): Using the autodiscovery client to discover Microsoft Windows and Linux and/or UNIX devices on your network, including their IP and MAC Address details.
+- [Device42's Ping Sweep Tool](/auto-discovery/d42-ping-sweep.md): This page details usage of the ping sweep utility to keep your IP Address information up-to-date.
 
 ## Importing IP addresses into Device42
 

docs/integration/external-integrations/microsoft-laps-integration.md

@@ -7,6 +7,6 @@ sidebar_position: 18
 
 Device42 integrates with and can pull a password from the Microsoft LAPS (Local Admin Password Solution). Microsoft LAPS refers to a method which secures Active Directory member servers by randomly generating each server’s local admin password, and storing the generated PW as an attribute of that servers AD object in Active Directory. This password can then be looked up on demand via an Active Directory / LDAP query, and is often used to support scripted / automated actions that iterate through lists of AD member servers.
 
-**[Click here to jump to the Microsoft LAPS section of the Windows Discovery documentation page!](auto-discovery/windows-and-hyper-v-auto-discovery.md)**
+**[Click here to jump to the Microsoft LAPS section of the Windows Discovery documentation page!](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx)**
 
-If you want to [Download LAPS from Microsoft, click here.](https://www.microsoft.com/en-us/download/details.aspx?id=46899) For further resources/information on LAPS, see the [Microsoft LAPS Section of the Windows Discovery docs page](auto-discovery/windows-and-hyper-v-auto-discovery.md) (also linked above)!
+If you want to [Download LAPS from Microsoft, click here.](https://www.microsoft.com/en-us/download/details.aspx?id=46899) For further resources/information on LAPS, see the [Microsoft LAPS Section of the Windows Discovery docs page](/auto-discovery/windows-and-hyper-v-auto-discovery.mdx) (also linked above)!

docs/reports/reports/relutech-for-aws-migration.md

@@ -13,25 +13,24 @@ The instructions below provide a recommended approach to capture your Physical (
 
 The initial recommended approach starts by performing Operating System level scans, followed by SNMP scans against a BMC, then by the Warranty sync (if applicable).
 
-1. **Hypervisor/\*nix/Windows**  - You'll want to ensure that these sets of Operating System level jobs are configured and run first. This discovery process will create the device record and capture parts that include  CPU and HBA Card  information.
+1. **Hypervisor/*nix/Windows**  - You'll want to ensure that these sets of Operating System level jobs are configured and run first. This discovery process will create the device record and capture parts that include  CPU and HBA Card  information.
 2. **SNMP** - Once the OS-level scans have been completed, create and execute SNMP scans against the management IP’s of the targeted servers.  These jobs will update the existing devices by adding additional parts as well as the management MAC Address and IP Address.The SNMP scan captures part information such as Ram, Disk(s) and PSU.
 3. **Warranty** - Depending on the vendor, these particular jobs will retrieve service contracts associated with each server from the vendor system. If the vendor system is unavailable, the warranty data can be added manually via the UI or via spreadsheet imports. Please see the referenced link below for documentation on this discovery in Device42.
 
 ![Discovery menu](/assets/images/relu-discovery-menu.png)
 
 
-## Hypervisor/\*nix/Windows Job Creation
+## Hypervisor/*nix/Windows Job Creation
 
-- Set up Discovery jobs for device inventory discovery with the [\*Hypevisor / \*nix / Windows](auto-discovery/linux-unix-server-auto-discovery.md) jobs. Set up a standard discovery scan for each type of device focusing on the physical devices (Hypervisors, \*nix and Windows).
-    - For the Windows and \*nix jobs, ensure that the Discover Parts is checked. In the Host Discovery section.
+- Set up Discovery jobs for device inventory discovery with the [*Hypevisor / *nix / Windows](/auto-discovery/linux-unix-server-auto-discovery.mdx) jobs. Set up a standard discovery scan for each type of device focusing on the physical devices (Hypervisors, *nix and Windows).
+    - For the Windows and *nix jobs, ensure that the Discover Parts is checked. In the Host Discovery section.
     - For the Hypervisor jobs, the “Discover Parts” option is enabled as default and not changeable.
 
 ![Host discovery](/assets/images/relu-host-discovery.png)
 
 ## SNMP Job Creation
 
 
-
 For the [SNMP](auto-discovery/storage-arrays-autodiscovery/snmp-san-server-auto-discovery.md) autodiscovery job:
 
 - First enter the IP/FQDN of all the devices that the credentials and access apply to under "servers".
@@ -48,7 +47,7 @@ For the [SNMP](auto-discovery/storage-arrays-autodiscovery/snmp-san-server-auto-
 
 ## Recommended Automated Scheduling
 
-- For the Hypervisor/\*nix/Windows scan jobs, the jobs should be scheduled to run **_daily_**.
+- For the Hypervisor/*nix/Windows scan jobs, the jobs should be scheduled to run **_daily_**.
 - For the SNMP scan jobs, the jobs should be scheduled to run **_weekly_**.
 - For the Warranty Sync, the jobs should be scheduled to run **_weekly_**.