diff --git a/docs/auto-discovery/agent-based-discovery.mdx b/docs/auto-discovery/agent-based-discovery.mdx
index e653039b5..e9bfbdb64 100644
--- a/docs/auto-discovery/agent-based-discovery.mdx
+++ b/docs/auto-discovery/agent-based-discovery.mdx
@@ -6,25 +6,15 @@ sidebar_position: 3
import ThemedImage from '@theme/ThemedImage'
import useBaseUrl from '@docusaurus/useBaseUrl'
-# Device42 Discovery Agent
-
-:::tip
-To learn about using the agent for **offline** discovery, see [Agent-Based Offline Discovery](agent-based-offline-discovery.mdx).
-:::
-
There are special situations where using an agent for discovery makes more sense. The IT environment may be unreachable from the network or security-hardened rules may be in place that limit traffic flow. Device42 offers many optional auto-discovery agents across several [supported platforms](#supported-platforms).
As a best practice, we recommend using agentless discovery over agent-based discovery when possible. The information gathered is the same, but the agent does not support Resource Utilization (RU).
-:::warning
-**Discovery Account warning: Please do _not_ set up an autodiscovery scan using critical or production account credentials! Please create a separate, dedicated account to use _only_ for discovery**
-
-Doing so, depending on permissions granted and configured password policies could result in account lock-out, therefore causing an otherwise completely avoidable outage.
-:::
+To learn about using the agent for **offline** discovery, see [Agent-Based Offline Discovery](agent-based-offline-discovery.mdx).
## Supported Platforms
-**Device42 autodiscovery agents are available for deployment on the following platforms:**
+Device42 autodiscovery agents are available for deployment on the following platforms:
- Windows 64-bit (Recommended)
- Windows 32-bit
@@ -39,8 +29,12 @@ Doing so, depending on permissions granted and configured password policies coul
- Solaris Sparc 64-bit
- Encrypted config file for Agent
-:::info
See **[Windows Discovery Agent Service Wrapper](/getstarted/installation/windows-service-installation)** and **[Mac Agent Service Launcher](/auto-discovery/mac-agent-service-launcher)** for information on installing versions of the Windows and Mac discovery agent as a service.
+
+:::warning
+Do not set up an autodiscovery scan using critical or production account credentials. Please create a separate, dedicated account to use only for discovery.
+
+Doing so, depending on permissions granted and configured password policies could result in account lock-out, therefore causing an otherwise completely avoidable outage.
:::
## Proxy Environment Variables
@@ -73,6 +67,8 @@ The agent can be run from the command line or can be scheduled using the relevan
```bash
-capture-host-files
capture hosts files
+ -config-file string
+ reads the config from an encrypted file (Only works for signed binaries. Ignored Otherwise)
-debug
prints the data being sent and result of post operation
-device-customer string
@@ -91,8 +87,6 @@ The agent can be run from the command line or can be scheduled using the relevan
doesn't do a post, just prints the data to be sent
-extended-logs
enables extended logs
- -host string
- specifies the Main Appliance or Remote Collector target (overrides built-in host)
-hostname-precedence
sets device name as 'new name' to prevent creation of new device if only hostname was changed
-ignore-domain
@@ -113,24 +107,26 @@ The agent can be run from the command line or can be scheduled using the relevan
default IP VRF group
-light-mode
reduces CPU utilization by cost of discovery speed
- -new-device-object-category
- updates/overwrites the object category for the device
+ -new-device-object-category string
+ new device object category
-offline
doesn't connect with Device42, just prints the encrypted data to be sent
+ -prioritize-dns-name
+ Prioritize DNS domain name
-quiet
disables all logs
-service-ports-only
returns only service ports data
- -skip-aws-instance-info
- disables AWS instance info discovery (default true)
-skip-bios
disables bios discovery
-skip-cluster-info
- disables cluster info discovery (Windows only) (default true)
+ disables cluster info discovery (Windows only)
-skip-cpu-info
disables CPU info discovery
-skip-database-info
- disables database discovery (default true)
+ disables database discovery
+ -skip-gpu-info
+ disables GPU info discovery
-skip-hardware-info
disables hardware discovery
-skip-hba
@@ -145,8 +141,12 @@ The agent can be run from the command line or can be scheduled using the relevan
disables network discovery
-skip-os-details
disables OS discovery
+ -skip-other-data
+ disables other data
-skip-parts
disables parts discovery
+ -skip-provider-unique-identifier
+ disables instance unique identifier lookup
-skip-serials
disables serial numbers discovery
-skip-service-ports
@@ -155,30 +155,24 @@ The agent can be run from the command line or can be scheduled using the relevan
disables services discovery
-skip-software
disables software discovery
+ -skip-tpm-info
+ disables TPM info discovery
-skip-virtual-machines
disables VM discovery
-software-initial-group string
default software group
-store-config-files
store configuration files
- -store-filesystem-info
- store filesystem information
- -store-registry-info
- store registry information
- -store-software-config-files
- store software configuration files
-sudo-password string
sudo password used in some OSes (Mac, Linux) to get information about the system
- -use-aws-token
- use generated token to get AWS instance info
-use-global-ignore-software-file
use global ignore software file
-use-global-ignore-software-pattern-file
use global ignore software pattern file
+ -use-provider-token
+ use generated token to get instance info
-version
print version number and exit
- --wmi-timeout
- timeout for Windows WMI calls (default is 120 seconds if not supplied)
```
diff --git a/docs/auto-discovery/auto-discovery-system-requirements.mdx b/docs/auto-discovery/auto-discovery-system-requirements.mdx
index 08a84e8fb..471c52060 100644
--- a/docs/auto-discovery/auto-discovery-system-requirements.mdx
+++ b/docs/auto-discovery/auto-discovery-system-requirements.mdx
@@ -40,23 +40,4 @@ Contact [support@device42.com](mailto:support@device42.com) with any questions r
## Ports and Protocols Used By Discovery
-Device42 uses the following ports and protocols for discovery. Ensure the appropriate ones are allowed through main and target machine firewalls for proper discovery functionality:
-
-- **UDP/161 - Device42 Appliance**
- - Networking (SNMP)
- - Blade Systems (SNMP)
- - Power (SNMP)
-- **TCP/443 - Device42 Appliance and Communication between RC and Main Appliance**
- - vServers (VMware, OVirt/Redhat, Citrix/Xen)
- - Cisco UCS Manager
-- **TCP/22 - Standalone Discovery Tool and Device42 Appliance**
- - SSH for *nix and select hypervisor discovery
- - KVM/libvirt
-- **ICMP - Device42 Appliance or Standalone Discovery Tool**
-- **UDP/623 - Device42 Appliance - IPMI**
-- **TCP/389 or TCP/636 - Device42 Appliance**
- - Active Directory or AD SSL
- - LDAP: Default is port 389 or 636 for LDAPs or LDAPs with SSL
-- **TCP/135 and 445 - Standalone Discovery Tool - WMI**
- - Random ephemeral TCP port(s) between 1024 and 65535 may also be used
-- **TCP/5985 and 5986 - Device42 Appliance - WinRM HTTP & HTTPS Discovery**
+See [Discovery Port Configurations](/getstarted/installation/discovery-port-configurations/) for a complete list.
\ No newline at end of file
diff --git a/docs/auto-discovery/warranty-autodiscovery.mdx b/docs/auto-discovery/warranty-autodiscovery.mdx
index 5f5614c70..561b671a5 100644
--- a/docs/auto-discovery/warranty-autodiscovery.mdx
+++ b/docs/auto-discovery/warranty-autodiscovery.mdx
@@ -49,7 +49,9 @@ Device42 supports warranty autodiscovery for the following vendors:
/>
-2. The Device42 **Model** field must be set to **Dell**, **IBM**, **Lenovo**, or **Meraki**. Hardware with different vendor name variations will not return a warranty. You can easily add the proper **Vendor Aliases** to the vendors if your vendors are named differently. On the vendor edit screen, update the vendor entries. Enter `dell` for Dell, `ibm` for IBM, `meraki` for Meraki, and `lenovo` for Lenovo:
+2. The EnrichAI module has largely automated this requirement: Set the **Model** field to **Dell**, **IBM**, **Lenovo**, or **Meraki**. Hardware with different vendor name variations will not return a warranty.
+
+You can easily add the proper **Vendor Aliases** to the vendors if your vendors are named differently. On the vendor edit screen, update the vendor entries. Enter `dell` for Dell, `ibm` for IBM, `meraki` for Meraki, and `lenovo` for Lenovo:
+[Set the time zone and configure NTP](/administration/setting-time-zone-and-ntp/) to ensure autodiscovery scheduling and log history work correctly.
+
Make sure your AMI is running the latest version of Device42 and update it if necessary:
- From the Device42 web UI, head to **Tools > Update**.
@@ -129,10 +131,12 @@ Make sure your AMI is running the latest version of Device42 and update it if ne
light: useBaseUrl('/assets/images/installation-amazon-web-services/update-software-light.png'),
dark: useBaseUrl('/assets/images/installation-amazon-web-services/update-software-dark.png'),
}}
- style={{ width: '70%' }}
+ style={{ width: '70%' }}
/>
-And you're all set! Now is a good time to check out our documentation for [Getting Started](getstarted/index.mdx) with Device42. If you have any questions or issues that the documentation doesn't address, visit the [Device42 Support page](https://support.device42.com) or email [support@device42.com](mailto:support@device42.com) to open a ticket.
+And you're all set!
+
+If you have any questions or issues that the documentation doesn't address, visit the [Device42 Support page](https://support.device42.com) or email [support@device42.com](mailto:support@device42.com) to open a ticket.
* * *
diff --git a/docs/getstarted/installation/installation-citrix-xen-server.mdx b/docs/getstarted/installation/installation-citrix-xen-server.mdx
index ad1161761..b3a9d6d17 100644
--- a/docs/getstarted/installation/installation-citrix-xen-server.mdx
+++ b/docs/getstarted/installation/installation-citrix-xen-server.mdx
@@ -16,7 +16,8 @@ This guide walks you through installing the Device42 Main Appliance on Citrix Xe
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.
+7. Set the time zone and configure NTP.
+8. 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
@@ -82,6 +83,10 @@ From the console, configure the IP address. Use a **static IP** for all producti
This is an optional step: Create a DNS entry for the new IP address of the virtual appliance.
+### Set the Time Zone and Configure NTP
+
+After setting a static IP address, [set the time zone and configure NTP](/administration/setting-time-zone-and-ntp/) to ensure autodiscovery scheduling and log history work correctly.
+
### Log In to the Web Interface
Point your browser to `https://FQDN (Fully Qualified Domain Name) or IP address`.
diff --git a/docs/getstarted/installation/installation-microsoft-azure.mdx b/docs/getstarted/installation/installation-microsoft-azure.mdx
index 67fd9b9a4..ae624586a 100644
--- a/docs/getstarted/installation/installation-microsoft-azure.mdx
+++ b/docs/getstarted/installation/installation-microsoft-azure.mdx
@@ -12,6 +12,7 @@ To install Device42 within your Microsoft Azure environment, you need to:
1. Download the Device42 virtual appliance from the Azure Marketplace.
2. Configure the virtual machine with proper resources and set up networking and deployment.
3. Log in to the Device42 instance using the vmID as the default password and configure the setup.
+4. Set the time zone and configure NTP.
## Detailed Installation Steps
@@ -69,6 +70,8 @@ Use the value of **vmId** as a password with the following default account user
-Change the **device42** console user password to something of your own choosing from the console..
+Change the **device42** console user password to something of your own choosing from the console.
+
+[Set the time zone and configure NTP](/administration/setting-time-zone-and-ntp/) to ensure autodiscovery scheduling and log history work correctly.
You should now have a fully functioning Device42 Main Appliance hosted on Microsoft Azure. You can run updates on this instance to get it to the latest version. You have to supply your license to get full functionality.
diff --git a/docs/getstarted/installation/installation-microsoft-hyperv.mdx b/docs/getstarted/installation/installation-microsoft-hyperv.mdx
index 124bdd672..252e3f1bc 100644
--- a/docs/getstarted/installation/installation-microsoft-hyperv.mdx
+++ b/docs/getstarted/installation/installation-microsoft-hyperv.mdx
@@ -15,8 +15,9 @@ After you [download the Device42 virtual appliance file](https://www.device42.co
1. Use 7-Zip 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, then update the credentials.
-4. On the console, configure the IP and choose your settings. Please use a static (non-DHCP) IP address for all Device42-related appliances. Create a DNS entry that points to the IP address of the new virtual appliance.
-5. Point your browser to `https://FQDN (Fully Qualified Domain Name) or IP address` and log in to the **web interface** using the default credentials. Update the login credentials here as well.
+4. On the console, configure the IP and choose your settings. Please use a static (non-DHCP) IP address for all Device42-related appliances.
+5. Set the time zone and configure NTP.
+6. Point your browser to `https://FQDN (Fully Qualified Domain Name) or IP address` and log in to the **web interface** using the default credentials. Update the login credentials here as well.
You are now ready to start discovering and documenting your IT infrastructure!
@@ -61,7 +62,7 @@ Please change these credentials as soon as you've logged in.
### Configure a Static IP and Networking Options
-Configure an IP address for the Device42 appliance. Use a static IP or a DHCP address reservation. Ensure that DNS entries are created for every appliance to be used in a production setting. DNS server configuration is a necessary step.
+Configure an IP address for the Device42 appliance using either a static IP or a DHCP reservation. Ensure that DNS server settings are configured on the appliance for production use, as these are required for autodiscovery to resolve hostnames.
@@ -69,7 +70,9 @@ Configure an IP address for the Device42 appliance. Use a static IP or a DHCP ad
Change the default password for the user `device42` from the console menu before proceeding.
-You can apply updates and perform 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.
+### Set the Time Zone and Configure NTP
+
+After setting a static IP address, [set the time zone and configure NTP](/administration/setting-time-zone-and-ntp/) to ensure autodiscovery scheduling and log history work correctly.
### Log In to the Web Interface
@@ -82,7 +85,7 @@ Log in to the **web interface** using the default credentials:
Please change these credentials as soon as you've logged in.
-You are now ready to start discovering your IT infrastructure!
+You are now ready to start discovering your IT infrastructure!
+## Using SSH
+
+You can apply updates and perform 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.
+
## Next Steps
-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.
+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.
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.
diff --git a/docs/getstarted/installation/installation-vcenter-server.mdx b/docs/getstarted/installation/installation-vcenter-server.mdx
index 67475897d..c895ff131 100644
--- a/docs/getstarted/installation/installation-vcenter-server.mdx
+++ b/docs/getstarted/installation/installation-vcenter-server.mdx
@@ -11,12 +11,13 @@ This guide walks you through installing the Device42 Main Appliance on the VMwar
## Outline of Installation Steps
1. Download and unzip the compressed Device42 virtual appliance.
-2. From the vCenter Server interface, select the unzipped `.ovf` file.
+2. From the vCenter Server interface, select the unzipped `.ovf` file.
3. Follow the VMware prompts and choose your location, datastore, and NIC.
-4. Power on the newly deployed Device42 virtual appliance.
+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.
+7. Set the time zone and configure NTP.
+8. 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 for Installing Device42 on vCenter Server
@@ -64,10 +65,10 @@ Log in using the default credentials and change them once you've logged in:
### Configure the Static IP Address
From the console, configure the IP address. Use a **static IP** for all production Device42 VMs to avoid connectivity issues.
-
+
- Enter your settings on the Device42 IP address configuration screen:
+ Enter your settings on the Device42 IP address configuration screen:
@@ -75,6 +76,10 @@ From the console, configure the IP address. Use a **static IP** for all producti
This is an optional step: Create a DNS entry for the new IP address of the virtual appliance.
+### Set the Time Zone and Configure NTP
+
+After setting a static IP address, [set the time zone and configure NTP](/administration/setting-time-zone-and-ntp/) to ensure autodiscovery scheduling and log history work correctly.
+
### Log In to the Web Interface
Point your browser to `https://FQDN (Fully Qualified Domain Name) or IP-address`.
@@ -103,6 +108,6 @@ You can apply Device42 updates and perform other menu-related work using **SSH**
## Next Steps
-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.
+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.
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.
diff --git a/docs/getstarted/installation/installation-xen-or-kvm-using-virt-manager.mdx b/docs/getstarted/installation/installation-xen-or-kvm-using-virt-manager.mdx
index e691c12bc..4e06a34e7 100644
--- a/docs/getstarted/installation/installation-xen-or-kvm-using-virt-manager.mdx
+++ b/docs/getstarted/installation/installation-xen-or-kvm-using-virt-manager.mdx
@@ -12,8 +12,9 @@ Install the Device42 Main Appliance on Xen- or KVM-based platforms by following
1. Download the Device42 image and unzip the image using bunzip2.
2. Import the disk image and follow the wizard to create a new virtual machine.
-3. Log in to the Device42 console and configure the Main Appliance.
-4. Log in to the Device42 Main Appliance from the browser.
+3. Log in to the Device42 console and configure the Main Appliance.
+4. Set the time zone and configure NTP.
+5. Log in to the Device42 Main Appliance from the browser.
## Illustrated Steps of Installing Device42 using Virt-Manager
@@ -57,17 +58,17 @@ bunzip2 device42--raw.img.bz2
Change the default password after signing in to the appliance console.
-
+3. Configure a static IP address for the Device42 appliance.
-You can apply updates and perform other menu-related tasks using SSH. Please note that root login has been disabled.
+
-* * *
+4. (Optional) Create a DNS entry for the new IP address for the new virtual appliance.
-You can also create a DNS entry for the new IP address for the new virtual appliance.
+You can apply updates and perform other menu-related tasks using SSH. Please note that root login has been disabled.
-Access the Device42 web UI by pointing your browser to `https://FQDN(Fully Qualified Domain Name) or IP-address` and logging in with the default credentials:
+### Set the Time Zone and Configure NTP
-4. (Optional) Create a DNS entry for the new IP address for the new virtual appliance.
+After setting a static IP address, [set the time zone and configure NTP](/administration/setting-time-zone-and-ntp/) to ensure autodiscovery scheduling and log history work correctly.
### Log in to the Web Interface
diff --git a/docs/getstarted/installation/sizing-recommendations.mdx b/docs/getstarted/installation/sizing-recommendations.mdx
index a6559b7be..8ddfc0150 100644
--- a/docs/getstarted/installation/sizing-recommendations.mdx
+++ b/docs/getstarted/installation/sizing-recommendations.mdx
@@ -12,3 +12,5 @@ The sizing requirements depend on the size of the environment and the Device42 f
| One Main Appliance (virtual appliance) | **Small to medium environments (\<2500 devices):**
- Four vCPU
- 16GB RAM
- 150GB vDisk (SSD or flash disk recommended)
**Medium to large environments (>2500 devices):**
- 16 vCPU
- 64GB RAM
- 150GB vDisk (SSD or flash disk recommended)
For any environments that include Application Dependency Mapping (ADM), Resource Utilization (RU), or Storage discovery, follow the medium to large environment guidelines |
| Remote Collector(s) (virtual appliance) | **One RC per 1000 workloads:**
- Two vCPU
- 4GB RAM
- 50GB vDisk |
| Windows Discovery Service (.NET installer) | **One WDS per 1000 workloads:**
- Two vCPU
- 8GB RAM
- 50GB vDisk (minimum) |
+
+Depending on your environment, we may recommend a dedicated resource pool for the virtual appliance to ensure there is no resource contention.
\ No newline at end of file
diff --git a/docs/getstarted/installation/windows-service-installation.mdx b/docs/getstarted/installation/windows-service-installation.mdx
index 4f3fbf7af..a135043eb 100644
--- a/docs/getstarted/installation/windows-service-installation.mdx
+++ b/docs/getstarted/installation/windows-service-installation.mdx
@@ -12,7 +12,7 @@ The Device42 Windows Service Wrapper is an executable (available separately for
You will need three separate files to install the service.
-1. **The service executable itself**: This is named `d42_winservice_P_V.exe`. Its default path is `C:\Program Files\Device42`.
+1. **The service executable itself**: This is named `d42_winservice_x64_v1_0_0.exe`. Its default path is `C:\Program Files\Device42`.
2. **The d42config.json file**: This dictates the various settings needed to run the service. Its default path is `C:\ProgramData\Device42`.
3. **The agent executable**: This is called `d42_winagent_x(bit).exe`. It can be downloaded from the Device42 MA under **Discovery > Agent Based Scans (Win7+)**.
diff --git a/docs/infrastructure-management/software/software-license-management.mdx b/docs/infrastructure-management/software/software-license-management.mdx
index 4df17001c..a0873dc84 100644
--- a/docs/infrastructure-management/software/software-license-management.mdx
+++ b/docs/infrastructure-management/software/software-license-management.mdx
@@ -1,16 +1,181 @@
---
-title: "Software License Models and Management"
+title: "Software License Management With Device42"
sidebar_position: 1
---
import ThemedImage from '@theme/ThemedImage'
import useBaseUrl from '@docusaurus/useBaseUrl'
-The Device42 Software License Management (SLM) module enables the easy creation and management of software licensing models by automatically scanning Windows and Linux machine instances for software; whether running or not. The SLM module can compare counts of running instances against purchased or licensed counts and detect prohibited software without any need for agents. There is absolutely no need to install software agents on each machine that you require monitoring on!
+:::tip
+This guide covers the complete software license management workflow in Device42, from discovery configuration through to reporting and alerts.
+:::
+
+IT organizations use software license management systems to create and maintain a comprehensive, accurate profile of the software deployed across all systems in an entire IT infrastructure. Using a software license manager (SLM) has several benefits:
+
+- **Cost Savings:** SLMs help optimize software use, reducing unnecessary expenses on unused licenses.
+- **License Compliance:** SLMs ensure an organization remains compliant with software license policies, which reduces the legal and financial risks associated with non-compliance.
+- **Security Improvements:** SLMs help to promptly identify end-of-life and vulnerable software by maintaining an inventory of software versions and ensuring all are up to date.
+- **Centralized Management:** SLMs offer a centralized platform for managing software licenses across an organization, which streamlines administrative tasks and reduces complexity.
+- **Inventory Transparency:** In addition to centralized management, having software data in a central location unlocks the ability to report and alert on software in use for auditing and transparency purposes.
+
+The Device42 software license management system has powerful features designed to help you efficiently manage your software licenses with these goals in mind. Let's take a look at how the Device42 SLM can help you ensure compliance, reduce costs, and streamline the software license management process.
+
+## Overview of Capabilities
+
+Device42 automatically scans Windows and Linux machine instances to detect software, whether the software is running or not. The software license management system compares counts of running instances against purchased or licensed counts and detects prohibited software. What's more, this is all accomplished without any need for agents installed on the scanned systems.
+
+Specifically, Device42 can do the following:
+
+- Scan and automatically discover installed software on devices.
+- Import these found software components into Device42.
+- Manage these software components through licensing policies and by software suite.
+- Track which software is in use on which devices.
+- Track the licenses for these software components by various methods, as needed for varying licensing models.
+- Configure alerts for when licenses are about to run out or when prohibited software is found.
+- Generate reports and dashboards to visualize license data and software use.
+
+## How It Works
+
+At a high level, managing software licenses with Device42 involves following these steps:
+
+- Configure an autodiscovery job.
+- Run the autodiscovery job to find and import software components (alternatively, you can manually import software components).
+- View the imported software components and categorize the results based on your organization's needs. This step may include assigning a software type to a component or assigning software to suites.
+- Configure licensing information for the imported software to establish license inventory.
+- Set up alerts for license status and discovered software types.
+
+## What Is Supported
+
+For device scanning, all major Linux distributions are supported, and software registered across various package managers is discovered.
+
+Once software components are imported, Device42 supports the following features for software management:
+
+- Software component management
+- Software-in-use tracking by device
+- Software suite assignment
+- License management of varying models
+- End-of-life and end-of-service tracking
+- Prohibited software detection
+- Licensing usage alerts
+
+## Configuring Software Discovery
+
+To import software components into Device42 so that they can be inventoried, managed, and reported on, you first need to configure Device42 for software discovery.
+
+### Autodiscovery Job Configuration
+
+In Device42, configure an autodiscovery job to scan systems for installed software under **Discovery > Hypervisors/\*nix/Windows > Create**.
+
+Configure the autodiscovery job for the system's platform and network location. To enable software discovery, ensure the **Discover Software** option is selected under the **Software and Applications** section.
+
+
+
+
+
+Note that for this option to appear, you must first select a supported platform, such as **\*nix** or **Windows**, for the autodiscovery job.
+
+### Software Type
+
+A configuration item (CI) worth noting is **Software Type**. This field controls how newly discovered software is initially treated. There are four options for the initial **Software Type** field:
+
+- **Unmanaged:** Software that is present on the scanned hosts but not actively tracked or managed in Device42. Unmanaged software typically includes software that has been installed without formal IT approval or is not part of the standard operating system images. Select this software type to identify and control software not formally approved in your organization and gain visibility into software that may pose security or compliance issues.
+
+- **Managed:** Software that is actively tracked, monitored, and managed in Device42. The managed software type allows you to track use, versions, licenses, and compliance and ensure that critical software installations are up to date and compliant with licensing agreements. You can set up alerts and automate tasks for managed software.
+
+- **Prohibited:** Software that is disallowed within an organization. Prohibited software is blocked by IT policies and is actively monitored to ensure it is not installed or used in an environment. This helps enforce security and compliance policies by preventing the installation of software that poses security risks or violates licensing agreements.
+
+- **Ignored:** Software that is intentionally excluded from management in Device42. Select this software type for software that doesn't need active management or for which you want to reduce noise in a software inventory.
+
+**Unmanaged** is the default option. Select other options as required before saving the autodiscovery job.
+
+Finally, run the autodiscovery job to discover installed software components and import them into Device42.
+
+## Viewing and Managing Discovered Software
+
+Discovered software can be found under **Resources > Software Components > All Software Components**.
+
+It's worth understanding the difference between the **All Software Components** and **Software In Use** views in Device42.
+
+- **All Software Components:** This page lists all discovered software components, regardless of whether they are actively used. A given software component can be assigned to multiple devices, but this page only lists each software component once.
+- **Software In Use:** This page lists the software components assigned to or in use on a particular device. A software component in use on multiple devices would appear multiple times on this page.
+
+The All Software Components view represents a library of all the software managed by an organization, whereas the Software In Use view is a record of one of those pieces of software in active use by some managed device.
+
+### All Software Components
+
+As with other list views in Device42, you can sort the Software Components table by the column headers, select filters for the view from the top-right of the page, search components using the search box in the top-left corner, and perform bulk actions on items in the list.
+
+
+
+Some of the bulk actions that can be taken here include:
+
+- **Change the software type:** A review of the found software components may include recategorizing components according to their software type.
+- **Update software counts:** You might want to change the software counts if you're considering a licensing change and want to see the impact of this change immediately.
+- **Assign software to suite:** Use this option to group related software components. For example, multiple Adobe products could be grouped under a single software suite for easier management and auditing.
+
+You can merge software components by assigning them to a suite. Select the components to merge from the list view, then select **Assign Software to Suite** from the **Actions** dropdown. Select the software suite from the list and submit the form.
+
+
+
+You can manually add software components in the All Software Components view. Click the **Add Software Component** button at the top-right. In the form that opens, enter the name of the component, type, license model, vendor, and other needed fields, then save the form. The newly created software component will be displayed in the list alongside any discovered software.
+
+
+
+### Software In Use
+
+The Software In Use page lists the software components assigned to or used by each device, including when it was first detected on the device and when it was last updated. As with the All Software Components page, this view can be sorted by column headers, filtered, and searched, and you can perform bulk or individual **Actions**.
+
+
+
+You can manually add a piece of software to the Software In Use page by clicking the **Create** button at the top-right of the page. In the form that opens, find and select the created software component that represents the software in use, any licensing information, and the device that it is used on, then save the form. The newly created software-in-use record will be displayed in the list alongside other records.
+
+
## Software License Models
-The flexible Device42 license models enables you to track any type of licensing you use. Navigate to **Resources > Software License Models** and click **Create**.
+The flexible Device42 license models enable you to track any type of licensing you use. Navigate to **Resources > Software License Models** and click **Create**.
The **Track By** field enables you to specify whether the licenses should be tracked by **User**, **Device**, **Client Access** (CALs), or **Device CPU/Core**.
@@ -29,9 +194,27 @@ The **Track By** field enables you to specify whether the licenses should be tra
light: useBaseUrl('/assets/images/software-license-management/track-by-light.png'),
dark: useBaseUrl('/assets/images/software-license-management/track-by-dark.png'),
}}
- style={{ width: '50%' }}
+ style={{ width: '50%' }}
/>
+With Device42, you can track software components by their licensing models. Licensing models are created as needed and customized to a particular piece of software. By matching a software component to its type of license, you can select to track software components and their associated licensing models by:
+
+- **User:** Documents whether a license is unlimited, purchased in bulk, or purchased individually. This field is only for documentation purposes and does not affect how Device42 counts the instances of software components with a license that it finds.
+- **Client Access License (CAL):** The **Count CAL by** field captures whether licenses should be counted on a per-seat (device or user), per-server, per-processor, or per-mailbox basis.
+- **Device:** The **Count Devices by** field captures how licenses are counted for each device, by volume, volume with a multiplier, single, unlimited, or OEM. This field is also used only for documentation purposes.
+- **Device CPU:** Similar to the track-by-device option above, the **Count Devices by** field has the same options for how to count the number of devices with this software. However, this license type also allows you to configure how multiple CPUs factor into the count for both physical and virtual systems. Valid options here are number of CPU cores on the host, number of sockets on the host, number of cores on virtual machines, and number of sockets on virtual machines.
+
+Additionally, for each license type, the following options are configurable to further document and manage licenses:
+
+- **License Type:** Either subscription or perpetual. This field is only for documentation purposes and does not affect how Device42 counts the instances of software components with a license that it finds.
+- **Node Locked:** If each licensed instance of a software component is restricted to a specific device.
+- **User Locked:** If each licensed instance of a software component is restricted to a specific user.
+- **Free Software:** If the software component is free or open source.
+- **Concurrent Access:** If the software component is licensed by the number of concurrent users rather than by the total number of users with access to it.
+- **Count Major Versions Separately:** If instances of the software component with different major versions should be counted separately.
+
+Device42 comes with the license models outlined above predefined in **Resources > Software Components > Software Licensing Models**. You can also define custom license models if none of the predefined models suit your needs by selecting **Create** from the Software Licensing Models list page.
+
### Tracking By User
If you choose to track by **User**, you will see the options:
@@ -42,12 +225,12 @@ If you choose to track by **User**, you will see the options:
light: useBaseUrl('/assets/images/software-license-management/track-by-user-light.png'),
dark: useBaseUrl('/assets/images/software-license-management/track-by-user-dark.png'),
}}
- style={{ width: '50%' }}
+ style={{ width: '50%' }}
/>
-The **License Type** field lets you specify whether this is a **Perpetual** license or a **Subscription**. This is just a documentation field and doesn’t affect how Device42 counts the instances it finds of the software components.
+The **License Type** field lets you specify whether this is a **Perpetual** license or a **Subscription**. This is just a documentation field and doesn't affect how Device42 counts the instances it finds of the software components.
-The **Count Users by** field enables you to specify the purchase method. This is also just a documentation field and doesn’t affect how Device42 counts the instances it finds of the software components.
+The **Count Users by** field enables you to specify the purchase method. This is also just a documentation field and doesn't affect how Device42 counts the instances it finds of the software components.
The checkbox options do the following when enabled:
@@ -69,12 +252,12 @@ The **Count CAL by** field specifies how the licenses should be counted; that is
light: useBaseUrl('/assets/images/software-license-management/count-cal-by-light.png'),
dark: useBaseUrl('/assets/images/software-license-management/count-cal-by-dark.png'),
}}
- style={{ width: '50%' }}
+ style={{ width: '50%' }}
/>
### Tracking By Device
-With the **Device** track by option, you see the **Count Devices by** field. This field is used solely for documentation and has five options:
+With the **Device** track by option, you see the **Count Devices by** field. This field is used solely for documentation and has five options:
- **Volume**
- **Volume with a multiplier**
- **Single**
@@ -87,7 +270,7 @@ With the **Device** track by option, you see the **Count Devices by** field. Thi
light: useBaseUrl('/assets/images/software-license-management/device-count-by-light.png'),
dark: useBaseUrl('/assets/images/software-license-management/device-count-by-dark.png'),
}}
- style={{ width: '50%' }}
+ style={{ width: '50%' }}
/>
### Tracking By Device CPU
@@ -100,7 +283,7 @@ If you choose **Device CPU/Core** track by option, you will see four additional
light: useBaseUrl('/assets/images/software-license-management/track-by-device-cpu-light.png'),
dark: useBaseUrl('/assets/images/software-license-management/track-by-device-cpu-dark.png'),
}}
- style={{ width: '45%' }}
+ style={{ width: '45%' }}
/>
The **Count Devices by** field has five choices as listed above.
@@ -110,11 +293,124 @@ The **CPU core factor field** is for the core factor rating used by some softwar
The **CPU Count** field defines how CPUs are counted: **Total sockets** or **Total # of cores**.
The **CPU count virtual** field defines how software found on virtual machines is counted:
-- **Total # of cores on host**
+- **Total # of cores on host**
- **Total sockets on host**
- **Total # of cores on VM**
- **Total sockets on VM**
+## Alerts and Notifications
+
+You can configure several automations to help you manage software components and their licenses. For instance, you might like to receive an alert when a given piece of software is reaching its number of available licenses.
+
+Device42 distinguishes between **alerts** and **notifications** for software components. An alert is configured to define a set of criteria that require attention and what actions to perform when those criteria are met. A notification is more or less a log of alert rules that were triggered.
+
+To create an alert, navigate to **Analytics > Alerts > Setup Alerts > Create**. Switch the **Rule Type** field to **Software**. The following alert types can be set in the **Trigger** field:
+
+- **Count:** When the count of a piece of software is greater than, less than, equal to, or not equal to an expected value.
+- **License Percent Used:** When the number of licenses for a piece of software is greater than, less than, equal to, or not equal to an expected value.
+- **Prohibited Software Installed:** Whenever any prohibited software is detected on a scanned system.
+
+The recipient for an alert is set in the **Escalation Profile** field. If a profile is already configured, you can select it from the prepopulated list. If not, click the plus icon next to the **Escalation Profile** field to open a form to configure one.
+
+
+
+Once an alert has been created and its criteria met, both open and acknowledged notifications for these alerts can be viewed at **Analytics > Reports > Notifications**.
+
+## End of Life and End of Service
+
+Manage end-of-life (EOL) and end-of-service (EOS) information for your software components in **Resources > Software Components > EOL / EOS**.
+
+EOL and EOS dates are imported manually. To define EOL or EOS for a software component, select **Create** at the top right of the page. In the Add Software EOL / EOS form, select the relevant software component and its corresponding EOL or EOS dates.
+
+
+
+Note that it's not necessary to specify both end-of-life and end-of-service dates. These are similar concepts, but not all software will have both.
+
+- **End of Life Date:** The date on which a software component will no longer be actively developed, maintained, or supported by its vendor.
+- **End of Service Date:** The date on which a software vendor will stop providing customer support or technical assistance for a particular version of the software, even though the software itself may still receive updates and bug fixes.
+
+## Reporting
+
+Once your software components have been imported and categorized, the Device42 reporting system can be used to better visualize and analyze the software in use throughout your organization.
+
+Let's illustrate this by creating a simple report that finds all managed Adobe software.
+
+- First, create a new report via **Analytics > Standard Reports > Create**. Name the report.
+
+- Choose **Guided Report** and select **Software In Use** as the object of the report.
+
+
+
+- Under the **More Filters** dropdown, select **Software > Vendor** to add the vendor dropdown filter.
+
+
+
+- Search for the vendors (for example, **Adobe**) in the new **Software -> Vendor** dropdown filter and select the matching items.
+
+
+
+- Apply the **Managed** option from the **Software -> Software Type** dropdown filter.
+
+
+
+- Select the columns that match the previously selected filters to include them in the report, such as the **Software -> Software type** and **Software -> Vendor** columns.
+
+
+
+- Finally, click **Save and Display On Screen** to view the report immediately. You can also **Export** the report and configure a **Report Schedule** if you want regular updates.
+
+
+
+There are, of course, many other reporting configurations that Device42 supports. See the [full documentation on creating reports in Device42](https://docs.device42.com/reports/) for more details.
+
## Licensing
The software licensing module is licensed as an add-on to the core product. You can contact us about the pricing from the [Device42 website](https://www.device42.com/contact/).
diff --git a/docs/solution-guides/software-license-management.mdx b/docs/solution-guides/software-license-management.mdx
deleted file mode 100644
index 7992328a1..000000000
--- a/docs/solution-guides/software-license-management.mdx
+++ /dev/null
@@ -1,311 +0,0 @@
----
-title: "Software License Management With Device42"
-sidebar_position: 2
----
-
-import ThemedImage from '@theme/ThemedImage'
-import useBaseUrl from '@docusaurus/useBaseUrl'
-
-IT organizations use software license management systems to create and maintain a comprehensive, accurate profile of the software deployed across all systems in an entire IT infrastructure. Using a software license manager (SLM) has several benefits:
-
-- **Cost Savings:** SLMs help optimize software use, reducing unnecessary expenses on unused licenses.
-- **License Compliance:** SLMs ensure an organization remains compliant with software license policies, which reduces the legal and financial risks associated with non-compliance.
-- **Security Improvements:** SLMs help to promptly identify end-of-life and vulnerable software by maintaining an inventory of software versions and ensuring all are up to date.
-- **Centralized Management:** SLMs offer a centralized platform for managing software licenses across an organization, which streamlines administrative tasks and reduces complexity.
-- **Inventory Transparency:** In addition to centralized management, having software data in a central location unlocks the ability to report and alert on software in use for auditing and transparency purposes.
-
-The Device42 software license management system has powerful features designed to help you efficiently manage your software licenses with these goals in mind. Let's take a look at how the Device42 SLM can help you ensure compliance, reduce costs, and streamline the software license management process.
-
-## Overview of Capabilities
-
-Device42 automatically scans Windows and Linux machine instances to detect software, whether the software is running or not. The software license management system compares counts of running instances against purchased or licensed counts and detects prohibited software. What's more, this is all accomplished without any need for agents installed on the scanned systems.
-
-Specifically, Device42 can do the following:
-
-- Scan and automatically discover installed software on devices.
-- Import these found software components into Device42.
-- Manage these software components through licensing policies and by software suite.
-- Track which software is in use on which devices.
-- Track the licenses for these software components by various methods, as needed for varying licensing models.
-- Configure alerts for when licenses are about to run out or when prohibited software is found.
-- Generate reports and dashboards to visualize license data and software use.
-
-## How It Works
-
-At a high level, managing software licenses with Device42 involves following these steps:
-
-- Configure an autodiscovery job.
-- Run the autodiscovery job to find and import software components (alternatively, you can manually import software components).
-- View the imported software components and categorize the results based on your organization's needs. This step may include assigning a software type to a component or assigning software to suites.
-- Configure licensing information for the imported software to establish license inventory.
-- Set up alerts for license status and discovered software types.
-
-## What Is Supported
-
-For device scanning, all major Linux distributions are supported, and software registered across various package managers is discovered.
-
-Once software components are imported, Device42 supports the following features for software management:
-
-- Software component management
-- Software-in-use tracking by device
-- Software suite assignment
-- License management of varying models
-- End-of-life and end-of-service tracking
-- Prohibited software detection
-- Licensing usage alerts
-
-## Configuring Software Discovery
-
-To import software components into Device42 so that they can be inventoried, managed, and reported on, you first need to configure Device42 for software discovery.
-
-### Autodiscovery Job Configuration
-
-In Device42, configure an autodiscovery job to scan systems for installed software under **Discovery > Hypervisors/\*nix/Windows > Create**.
-
-Configure the autodiscovery job for the system's platform and network location. To enable software discovery, ensure the **Discover Software** option is selected under the **Software and Applications** section.
-
-
-
-
-
-Note that for this option to appear, you must first select a supported platform, such as **\*nix** or **Windows**, for the autodiscovery job.
-
-### Software Type
-
-A configuration item (CI) worth noting is **Software Type**. This field controls how newly discovered software is initially treated. There are four options for the initial **Software Type** field:
-
-- **Unmanaged:** Software that is present on the scanned hosts but not actively tracked or managed in Device42. Unmanaged software typically includes software that has been installed without formal IT approval or is not part of the standard operating system images. Select this software type to identify and control software not formally approved in your organization and gain visibility into software that may pose security or compliance issues.
-
-- **Managed:** Software that is actively tracked, monitored, and managed in Device42. The managed software type allows you to track use, versions, licenses, and compliance and ensure that critical software installations are up to date and compliant with licensing agreements. You can set up alerts and automate tasks for managed software.
-
-- **Prohibited:** Software that is disallowed within an organization. Prohibited software is blocked by IT policies and is actively monitored to ensure it is not installed or used in an environment. This helps enforce security and compliance policies by preventing the installation of software that poses security risks or violates licensing agreements.
-
-- **Ignored:** Software that is intentionally excluded from management in Device42. Select this software type for software that doesn't need active management or for which you want to reduce noise in a software inventory.
-
-**Unmanaged** is the default option. Select other options as required before saving the autodiscovery job.
-
-Finally, run the autodiscovery job to discover installed software components and import them into Device42.
-
-## Viewing and Managing Discovered Software
-
-Discovered software can be found under **Resources > Software Components > All Software Components**.
-
-It's worth understanding the difference between the **All Software Components** and **Software In Use** views in Device42.
-
-- **All Software Components:** This page lists all discovered software components, regardless of whether they are actively used. A given software component can be assigned to multiple devices, but this page only lists each software component once.
-- **Software In Use:** This page lists the software components assigned to or in use on a particular device. A software component in use on multiple devices would appear multiple times on this page.
-
-The All Software Components view represents a library of all the software managed by an organization, whereas the Software In Use view is a record of one of those pieces of software in active use by some managed device.
-
-### All Software Components
-
-As with other list views in Device42, you can sort the Software Components table by the column headers, select filters for the view from the top-right of the page, search components using the search box in the top-left corner, and perform bulk actions on items in the list.
-
-
-
-Some of the bulk actions that can be taken here include:
-
-- **Change the software type:** A review of the found software components may include recategorizing components according to their software type.
-- **Update software counts:** You might want to change the software counts if you're considering a licensing change and want to see the impact of this change immediately.
-- **Assign software to suite:** Use this option to group related software components. For example, multiple Adobe products could be grouped under a single software suite for easier management and auditing.
-
-You can merge software components by assigning them to a suite. Select the components to merge from the list view, then select **Assign Software to Suite** from the **Actions** dropdown. Select the software suite from the list and submit the form.
-
-
-
-You can manually add software components in the All Software Components view. Click the **Add Software Component** button at the top-right. In the form that opens, enter the name of the component, type, license model, vendor, and other needed fields, then save the form. The newly created software component will be displayed in the list alongside any discovered software.
-
-
-
-### Software In Use
-
-The Software In Use page lists the software components assigned to or used by each device, including when it was first detected on the device and when it was last updated. As with the All Software Components page, this view can be sorted by column headers, filtered, and searched, and you can perform bulk or individual **Actions**.
-
-
-
-You can manually add a piece of software to the Software In Use page by clicking the **Create** button at the top-right of the page. In the form that opens, find and select the created software component that represents the software in use, any licensing information, and the device that it is used on, then save the form. The newly created software-in-use record will be displayed in the list alongside other records.
-
-
-
-## License Models
-
-With Device42, you can track software components by their licensing models. Licensing models are created as needed and customized to a particular piece of software. By matching a software component to its type of license, you can select to track software components and their associated licensing models by:
-
-- **User:** Documents whether a license is unlimited, purchased in bulk, or purchased individually. This field is only for documentation purposes and does not affect how Device42 counts the instances of software components with a license that it finds.
-- **Client Access License (CAL):** The **Count CAL by** field captures whether licenses should be counted on a per-seat (device or user), per-server, per-processor, or per-mailbox basis.
-- **Device:** The **Count Devices by** field captures how licenses are counted for each device, by volume, volume with a multiplier, single, unlimited, or OEM. This field is also used only for documentation purposes.
-- **Device CPU:** Similar to the track-by-device option above, the **Count Devices by** field has the same options for how to count the number of devices with this software. However, this license type also allows you to configure how multiple CPUs factor into the count for both physical and virtual systems. Valid options here are number of CPU cores on the host, number of sockets on the host, number of cores on virtual machines, and number of sockets on virtual machines.
-
-Additionally, for each license type, the following options are configurable to further document and manage licenses:
-
-- **License Type:** Either subscription or perpetual. This field is only for documentation purposes and does not affect how Device42 counts the instances of software components with a license that it finds.
-- **Node Locked:** If each licensed instance of a software component is restricted to a specific device.
-- **User Locked:** If each licensed instance of a software component is restricted to a specific user.
-- **Free Software:** If the software component is free or open source.
-- **Concurrent Access:** If the software component is licensed by the number of concurrent users rather than by the total number of users with access to it.
-- **Count Major Versions Separately:** If instances of the software component with different major versions should be counted separately.
-
-Device42 comes with the license models outlined above predefined in **Resources > Software Components > Software Licensing Models**. You can also define custom license models if none of the predefined models suit your needs by selecting **Create** from the Software Licensing Models list page. The screenshot below demonstrates adding a new licensing model for open-source software.
-
-
-
-## Alerts and Notifications
-
-You can configure several automations to help you manage software components and their licenses. For instance, you might like to receive an alert when a given piece of software is reaching its number of available licenses.
-
-Device42 distinguishes between **alerts** and **notifications** for software components. An alert is configured to define a set of criteria that require attention and what actions to perform when those criteria are met. A notification is more or less a log of alert rules that were triggered.
-
-To create an alert, navigate to **Analytics > Alerts > Setup Alerts > Create**. Switch the **Rule Type** field to **Software**. The following alert types can be set in the **Trigger** field:
-
-- **Count:** When the count of a piece of software is greater than, less than, equal to, or not equal to an expected value.
-- **License Percent Used:** When the number of licenses for a piece of software is greater than, less than, equal to, or not equal to an expected value.
-- **Prohibited Software Installed:** Whenever any prohibited software is detected on a scanned system.
-
-The recipient for an alert is set in the **Escalation Profile** field. If a profile is already configured, you can select it from the prepopulated list. If not, click the plus icon next to the **Escalation Profile** field to open a form to configure one.
-
-
-
-Once an alert has been created and its criteria met, both open and acknowledged notifications for these alerts can be viewed at **Analytics > Reports > Notifications**.
-
-## End of Life and End of Service
-
-Manage end-of-life (EOL) and end-of-service (EOS) information for your software components in **Resources > Software Components > EOL / EOS**.
-
-EOL and EOS dates are imported manually. To define EOL or EOS for a software component, select **Create** at the top right of the page. In the Add Software EOL / EOS form, select the relevant software component and its corresponding EOL or EOS dates.
-
-
-
-Note that it's not necessary to specify both end-of-life and end-of-service dates. These are similar concepts, but not all software will have both.
-
-- **End of Life Date:** The date on which a software component will no longer be actively developed, maintained, or supported by its vendor.
-- **End of Service Date:** The date on which a software vendor will stop providing customer support or technical assistance for a particular version of the software, even though the software itself may still receive updates and bug fixes.
-
-## Reporting
-
-Once your software components have been imported and categorized, the Device42 reporting system can be used to better visualize and analyze the software in use throughout your organization.
-
-Let's illustrate this by creating a simple report that finds all managed Adobe software.
-
-- First, create a new report via **Analytics > Standard Reports > Create**. Name the report.
-
-- Choose **Guided Report** and select **Software In Use** as the object of the report.
-
-
-
-- Under the **More Filters** dropdown, select **Software > Vendor** to add the vendor dropdown filter.
-
-
-
-- Search for the vendors (for example, **Adobe**) in the new **Software -> Vendor** dropdown filter and select the matching items.
-
-
-
-- Apply the **Managed** option from the **Software -> Software Type** dropdown filter.
-
-
-
-- Select the columns that match the previously selected filters to include them in the report, such as the **Software -> Software type** and **Software -> Vendor** columns.
-
-
-
-- Finally, click **Save and Display On Screen** to view the report immediately. You can also **Export** the report and configure a **Report Schedule** if you want regular updates.
-
-
-
-There are, of course, many other reporting configurations that Device42 supports. See the [full documentation on creating reports in Device42](https://docs.device42.com/reports/) for more details.
diff --git a/docs/what-is-device42.mdx b/docs/what-is-device42.mdx
index 1e04c2959..ac89f49ed 100644
--- a/docs/what-is-device42.mdx
+++ b/docs/what-is-device42.mdx
@@ -29,7 +29,7 @@ Discover physical servers, VMs, network devices, containers, end-user devices, s
Device42 delivers robust IT asset management (ITAM) documentation for all infrastructure deployments. Its powerful tools ensure that IT teams have instant access to complete, accurate, and up-to-date inventories of their entire IT environments.
-### [Software License Management](solution-guides/software-license-management.mdx)
+### [Software License Management](infrastructure-management/software/software-license-management.mdx)
Organizations can create and maintain a comprehensive, accurate profile of the software deployed on Windows and Linux machines across their entire IT estates — from the server to desktop level.
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 8e53472d1..9b9f132d2 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -839,7 +839,7 @@ const config = {
},
{
to: '/infrastructure-management/software/software-license-management/',
- from: ['/apps/software/software-license-management/'],
+ from: ['/apps/software/software-license-management/', '/solution-guides/software-license-management/'],
},
{
to: '/infrastructure-management/software/software-licensing-alerts-and-notifications/',