Merge pull request #388 from ritza-co/docs-19.03.07

Docs 19.03.07 release (Week 46, 2024)

docs/administration/appliance-manager/enable-or-disable-tls-versions-from-appliance-manager.md

@@ -7,10 +7,14 @@ sidebar_position: 8
 
 Device42 allows you to restrict TLS versions for Appliance Manager Access. The radio buttons shown below control this feature.
 
-**Note:** As of v16.23.00, all users will be upgraded to **TLS v1.2 by default** for the Appliance Manager and Device42. You can still change your setting to _Enable TLS v.1.1 and v1.2_ or _Enable All TLS_.
+:::note
+The appliance manager now defaults to **Enable TLS v1.2 only**. You an change the TLS settings in the appliance manager to **Enable TLS v.1.1 and v1.2** or **Enable All TLS**.
+:::
 
-- To apply TLS version restrictions, log into the Device42 Appliance Manager by clicking the link at the bottom of the main login page, and enter your Device42 Appliance Manager credentials. The default username and password for the Appliance Manager is _d42admin/default_. ![](/assets/images/TLS-appliance-mgr-login.png)
-- From the main menu on the left side of the Appliance Manager, select _Global Settings_ and then _TLS versions for Web Console_ or _TLS versions for_ _Appliance Manager_.
-- Select the appropriate radio button and click _Submit_ to apply your changes.
+- To apply TLS version restrictions, log into the Device42 Appliance Manager by clicking the link at the bottom of the main login page, and enter your Device42 Appliance Manager credentials. The default username and password for the Appliance Manager is `d42admin/default`. 
+
+    ![](/assets/images/TLS-appliance-mgr-login.png)
+- From the main menu on the left side of the Appliance Manager, select **Global Settings** and then **TLS versions for Web Console** or **TLS versions for Appliance Manager**.
+- Select the appropriate radio button and click **Submit** to apply your changes.
 
-![](/assets/images/16.23.00_TLS_Settings.png)
+    ![](/assets/images/16.23.00_TLS_Settings.png)

docs/administration/passwords/burnt-secret-password-storage.md

@@ -13,7 +13,7 @@ If a 'burnt' secret/password is forgotten, it MUST be reset & regenerated. Stori
 
 ### Storing a Password as a Burnt Secret
 
-Creating a "burnt" secret/password is very similar to the creation of a 'normal' stored secret. Simply head to the _Secrets_ menu and add a new secret/password. In v15.07.00+, the _Password Storage_ option can be set to "Burnt" (as opposed to the default of "Normal") which will cause a secret to be stored non-retrievable:
+Creating a "burnt" secret/password is very similar to the creation of a 'normal' stored secret. Simply head to the _Secrets_ menu and add a new secret/password. The _Password Storage_ option can be set to "Burnt" (as opposed to the default of "Normal") which will cause a secret to be stored non-retrievable:
 
 ![](/assets/images/Secrets-5-add-burnt-700x303.png)
 

docs/apps/enterprise-application-dependency-mapping/cloud-application-dependency-mapping.mdx

@@ -6,7 +6,7 @@ sidebar_position: 2
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-In v18.06.00, you can now map connections between your on-prem and AWS databases. Cloud Application Dependency Mapping can help customers with hybrid environments to better understand their infrastructure, improve troubleshooting, ease migration frustrations, and optimize resource utilization, ultimately leading to better performance and cost savings. 
+You can map connections between your on-prem and AWS databases. Cloud Application Dependency Mapping can help customers with hybrid environments to better understand their infrastructure, improve troubleshooting, ease migration frustrations, and optimize resource utilization, ultimately leading to better performance and cost savings. 
 
 Currently, we support the following AWS Databases: RDS, DynamoDB and Redshift
 

docs/auto-discovery/cloud-auto-discovery/aws-autodiscovery.mdx

@@ -338,7 +338,7 @@ If you don't want to follow the steps above, you can either:
 
 ## Using AWS Roles To Discover Accounts Within Discovery Jobs
 
-AWS Cloud Discovery Jobs can use AWS roles to discover accounts. When the job includes the AWS role, the discovery job will dynamically grab multiple accounts from AWS. We previously (before v18.13) aimed to maintain a 1:1 relationship between roles and accounts. Now, a single role can discover multiple accounts. This enables AWS users to set up discovery and specify the precise account to create, or leave the account empty to have the discovery job create cloud accounts as a result of the discovery.
+AWS Cloud Discovery Jobs can use AWS roles to discover accounts. When the job includes the AWS role, the discovery job will dynamically grab multiple accounts from AWS. We previously aimed to maintain a 1:1 relationship between roles and accounts. Now, a single role can discover multiple accounts. This enables AWS users to set up discovery and specify the precise account to create, or leave the account empty to have the discovery job create cloud accounts as a result of the discovery.
 
 ## Setting Up Environment Credentials using EC2 Instance Profiles
 

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

@@ -7,7 +7,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 ## About Database Discovery
 
-Database (DB) discovery was introduced in Device42 v16.02.00 and currently supports Windows and \*nix-based discovery jobs detecting Microsoft SQL (aka MSSQL), Oracle, Postgres SQL, and DB2 databases.
+Database (DB) discovery currently supports Windows and \*nix-based discovery jobs detecting Microsoft SQL (aka MSSQL), Oracle, Postgres SQL, and DB2 databases.
 
 :::note
 Database discovery requires an **Application Dependency Mapping** license. Go to **Tools > Settings > Licensing** to see if the license is enabled. Contact [[email protected]](mailto:[email protected]) for licensing assistance.
@@ -20,7 +20,7 @@ By default, the target machine ports are defined by the database vendors as foll
 - Postgres: 5432
 - Oracle: 1521
 
-Dynamic discovery detects which ports to use. As of v16.17.00, Device42 supports MSSQL and Oracle database discovery for customers with database instances configured to listen on non-standard ports, especially on shared database servers that host multiple instances. During database discovery, Device42 will identify and connect via the discovered active listening port.
+Dynamic discovery detects which ports to use. Device42 supports MSSQL and Oracle database discovery for customers with database instances configured to listen on non-standard ports, especially on shared database servers that host multiple instances. During database discovery, Device42 will identify and connect via the discovered active listening port.
 
 If you want to specify database discovery details yourself, including the database server port, server IP address, and database access credentials, use [Database Connections Discovery](#database-connections-discovery-jobs) jobs (see below) to discover databases.
 
@@ -224,9 +224,9 @@ If your environment includes SQL cluster databases, discovery returns the follow
 
 ## Oracle Database Discovery (on Windows and \*nix targets)
 
-Oracle database discovery (introduced in v16.04.00) is supported for Windows and \*nix discovery targets. Oracle discovery jobs require a separate set of credentials to authenticate to the database instance itself. Ensure these additional credentials have the appropriate permissions for viewing the databases you want to discover.
+Oracle database discovery is supported for Windows and \*nix discovery targets. Oracle discovery jobs require a separate set of credentials to authenticate to the database instance itself. Ensure these additional credentials have the appropriate permissions for viewing the databases you want to discover.
 
-As of v16.14.01, Device42 now supports autodiscovery on Windows and \*nix platforms for the following Oracle database versions:
+Device42 supports autodiscovery on Windows and \*nix platforms for the following Oracle database versions:
 
 **Oracle 10g**
 
@@ -255,7 +255,7 @@ As of v16.14.01, Device42 now supports autodiscovery on Windows and \*nix platfo
 - Windows 64 bit
 - CentOS 7 64 bit
 
-As of v16.17.00, Device42 database autodiscovery for Windows and \*nix targets supports discovery for Oracle RAC clustered database environments, which helps users better assess their cluster databases and understand all The IT assets tied to critical business applications. Discovery returns data about the RAC configuration, the RAC database, and the nodes (physical servers) running the RAC software. You can run the autodiscovery against one or more nodes in the Oracle RAC and return information about all connected nodes. Device42 requires the use of sudo for Oracle discoveries to mitigate the risk of lockout.
+Device42 database autodiscovery for Windows and \*nix targets supports discovery for Oracle RAC clustered database environments, which helps users better assess their cluster databases and understand all The IT assets tied to critical business applications. Discovery returns data about the RAC configuration, the RAC database, and the nodes (physical servers) running the RAC software. You can run the autodiscovery against one or more nodes in the Oracle RAC and return information about all connected nodes. Device42 requires the use of sudo for Oracle discoveries to mitigate the risk of lockout.
 
 ### Minimum Permissions Requirements for Oracle Discovery
 
@@ -391,7 +391,7 @@ If a candidate database instance is detected to be a child of a CDB we skip the
 
 ## Postgres SQL Database Discovery (on \*nix targets)
 
-From v17.11.00 onward, Device42 offers Postgres SQL database discovery for \*nix discovery targets, although it requires a separate set of credentials to authenticate to the database instance itself. Ensure these additional credentials have the appropriate permissions for viewing the databases you are interested in discovering.
+Device42 offers Postgres SQL database discovery for \*nix discovery targets, although it requires a separate set of credentials to authenticate to the database instance itself. Ensure these additional credentials have the appropriate permissions for viewing the databases you are interested in discovering.
 
 ### Minimum Permissions Requirements for Postgres SQL Discovery
 
@@ -463,7 +463,7 @@ sources={{
 
 ## DB2 Discovery (on \*nix targets)
 
-DB2 database discovery (introduced in v18.02.00) is for \*nix discovery targets and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have the appropriate permissions for viewing the databases you are interested in discovering.
+DB2 database discovery is for \*nix discovery targets and requires a separate set of credentials to authenticate to the database instance itself. Ensure these credentials have the appropriate permissions for viewing the databases you are interested in discovering.
 
 ### Permissions for DB2 Discovery
 
@@ -556,7 +556,7 @@ sources={{
 
 ## Database Connections Discovery Jobs
 
-Device42 v18.01.00 adds a new database discovery job type for discovering information about the databases in your environment. Database discovery is based on the database connection information, such as the application components and DB server details, that you supply for the job. Returned database information is added to the **On-Prem Databases** list page.
+Discover information about the databases in your environment using the database discovery job type. Database discovery is based on the database connection information, such as the application components and DB server details, that you supply for the job. Returned database information is added to the **On-Prem Databases** list page.
 
 This database discovery job type is useful when the main detailed database discovery (in OS jobs) cannot determine the proper connection settings for a specific database, because the database connection discovery job instead uses a string containing connection settings provided by the user.
 

docs/auto-discovery/enrichai-data/index.md

@@ -28,7 +28,7 @@ From Device42 version 18.12, the following vendor attributes, operating system a
 | OS Version Number           | General version number of the release                          |
 | Key Support Dates  | See the table below for details on the available date fields  |
 
-Note that from the v18.12 release, the **OS Architecture: 32 vs 64 bit** field is no longer part of EnrichAI data. Both the 32 and 64-bit architectures will coalesce into a single entry since OS dates, licensing, patches, and risk profiles are not affected by architecture.
+The **OS Architecture: 32 vs 64 bit** field is no longer part of EnrichAI data. Both the 32 and 64-bit architectures will coalesce into a single entry since OS dates, licensing, patches, and risk profiles are not affected by architecture.
 
 ### Key Support Dates
 

docs/auto-discovery/ibm-i-as400.mdx

@@ -131,7 +131,7 @@ AS400 support does _not_ currently include:
 - Parts support
 
 :::info
-As of Device42 v15.10.00, AS400 discovery has been verified and functionality tested with IBM i/AS400 operating system deployments configured with the Spanish language setting. AS400 discovery should also work with other non-English locale configurations. 
+AS400 discovery has been verified and functionality tested with IBM i/AS400 operating system deployments configured with the Spanish language setting. AS400 discovery should also work with other non-English locale configurations. 
 
 Please let us know about your experiences with other foreign language configurations or any issues you encounter; we love hearing from our users. Email [[email protected]](mailto:[email protected]).
 :::

docs/auto-discovery/jamf-autodiscovery.mdx

@@ -6,7 +6,7 @@ sidebar_position: 15.5
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-Device42 supports [Jamf](https://www.jamf.com/) autodiscovery from v19.02 of the Main Appliance. Run a Jamf cloud autodiscovery job to bring in your Apple ecosystem data.
+Device42 supports [Jamf](https://www.jamf.com/) autodiscovery. Run a Jamf cloud autodiscovery job to bring in your Apple ecosystem data.
 
 ## Jamf Autodiscovery Items
 

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.mdx) or our [Remote Collector documentation](remote-collector-rc.mdx). If you want to use the standalone Linux discovery tools, continue reading below.
+**Note:** Device42 supports 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.mdx). If you want to use the standalone Linux discovery tools, continue reading below.
 
 # Linux Based Autodiscovery Software
 

docs/auto-discovery/microsoft-dhcp-discovery.mdx

@@ -8,7 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 # Microsoft DHCP Discovery
 
-As of v18.14, Microsoft DHCP Discovery has been added as an additional discovery type under **Discovery > DHCP** of the Main Appliance. 
+Select the Microsoft DHCP discovery type by navigating to **Discovery > DHCP** on the Main Appliance. 
 
 <ThemedImage
   alt="DHCP menu location and list page"

docs/auto-discovery/operating-systems-supported-in-auto-discovery.md

@@ -33,7 +33,7 @@ Other UNIX distros should also work well with autodiscovery (via SSH).
 
 Major **Windows releases (7, 8, 10, Server 2000+) are all supported** and should all work well with autodiscovery (via WMI/WinRM).
 
-If you are running Device42 v15.14.02+, discovery of the **IBM i powered mid-range** line and **IBM z/OS** powered mainframes are also supported.
+Discovery of the **IBM i powered mid-range** line and **IBM z/OS** powered mainframes are also supported.
 
 ## Tested Distros and Operating Systems
 

docs/auto-discovery/packet-capture.md

@@ -11,7 +11,7 @@ Device42 packet capture supports both individual and promiscuous interfaces, all
 
 You need the following to use the Device42 Packet Capture tool:
 
-- A Device42 Main Appliance (MA) running v16.00.00 or above.
+- A Device42 Main Appliance (MA).
 - Network communication allowed from the machine you'll be capturing packets on to your Device42 MA.
 - An active network adapter connected to the target traffic capture network.
 - A packet capture library installed on your operating system: