device42 · Nadia-JSch · Feb 3, 2026 · Feb 4, 2026 · Feb 4, 2026 · Feb 4, 2026
diff --git a/docs/administration/tags.mdx b/docs/administration/tags.mdx
@@ -8,7 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 Tags are useful for filtering and grouping objects. For example, you could define a "Project X" tag and associate that tag with all the devices, IP addresses, and other items associated with Project X.
 
-Most objects in Device42 can be tagged, and most reports can be filtered according to tags.
+Main objects in Device42 can be tagged, such as Software Components, Assets, and Devices, but not lower-order related objects like Vendor or User.
 
 Navigate to the Tags list page under **Infrastructure > Organization > Tags** to view, edit, and create tags.
 

diff --git a/docs/apps/application-components/application-component-templates.mdx b/docs/apps/application-components/application-component-templates.mdx
@@ -88,6 +88,7 @@ You can add a new template by clicking **Create** in the top right of the temp
 - Select the **Service Type** (Windows or \*Nix) to specify which platform Device42 autodiscovery searches for the service(s) that the Application Component will be based on.(required).
 - Select, enter, or add (using the **plus sign** icon) the **Associated Service** that autodiscovery will search for and use to create the Application Component (required).
 - Enter a port in the **Only services listening on this port** field to limit autodiscovery to only the services that are listening on your chosen port. Leave the field empty to ignore the port.
+- Select an **Associated Software Component** to limit Application Component creation to instances where the specified software is installed. This is useful when filtering by service alone is too broad, such as when an application uses a common service like Java.
 - For **Match Type**, select **Text** or **Regular Expression** to specify how you want to filter services:
   - You can enter a **Text** string pattern that discovery will use to create more service-specific Application Components by only generating Application Components for services with Service Command Arguments that contain the string.
 

diff --git a/docs/infrastructure-management/certificate-management.mdx b/docs/infrastructure-management/certificate-management.mdx
@@ -6,11 +6,9 @@ sidebar_position: 5
 import ThemedImage from "@theme/ThemedImage";
 import useBaseUrl from "@docusaurus/useBaseUrl";
 
-:::info
-This page is about managing SSL certificates that have already been discovered by Device42. For details on creating a certificate autodiscovery job, visit [Certificate Autodiscovery](/auto-discovery/certificate-auto-discovery.mdx).
-:::
+This page is about managing SSL certificates in Device42, including viewing discovered certificates and importing certificates from files. For details on creating a certificate autodiscovery job, visit [Certificate Autodiscovery](/auto-discovery/certificate-auto-discovery.mdx).
 
-### Certificate List Page
+## Certificate List Page
 
 The list page for certificates, under **Applications > Certificates**, will show you all certificates discovered in Device42 along with their validity details.
 
@@ -37,7 +35,7 @@ You can export certificates by selecting them from the list and choosing the **E
   }}
 />
 
-### Viewing Certificates
+### View Certificates
 
 Click on the name of a certificate from the list page, under **Applications > Certificates**, to view it.
 
@@ -55,7 +53,15 @@ When viewing a certificate that has been imported, you can now associate FQDN, m
   }}
 />
 
-### Certificate Instances
+## Supported File Formats
+
+Device42 supports certificate uploads in the following formats:
+
+- PEM
+- ASN.1 
+- PKCS12 (pfx/p12) 
+
+## Certificate Instances
 
 In addition to seeing all certificates, you can now see certificate instances - allowing you to see device/IP address relationships for individual certificates. Locate certificate instances under **Applications > Certificate Instances**. Filter certificate instances based on device building, service level, and customer.
 
@@ -69,7 +75,7 @@ Certificate instances are also displayed in the device details view.
     }}
   />
 
-### Certificate Reports
+## Certificate Reports
 
 Though you can have multiple valid-to dates associated with a single certificate, Device42 reports still know to alert you based on the oldest date stored for a given certificate.
 

diff --git a/...onmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx b/...onmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx
@@ -14,7 +14,7 @@ To access the functionality described in this section, you need a **Power and En
 
 Install and set up a [Remote Collector](https://www.device42.com/autodiscovery/) if you have not already done so. See the [Remote Collector page](/auto-discovery/remote-collector-rc/#installation-and-configuration) for information.
 
-The process of discovering power-enabled PDUs is similar to [Device42 Network Autodiscovery](auto-discovery/network-auto-discovery.mdx). Begin by navigating to **Discovery > SNMP**. You can then enter an IP address range and a port if not using the default `161`. 
+The process of discovering power-enabled PDUs is similar to [Device42 Network Autodiscovery](auto-discovery/network-auto-discovery.mdx). Begin by navigating to **Discovery > SNMP**. You can then enter an IP address range and a port if not using the default `161`.
 
 <ThemedImage
   alt="Add SNMP discovery job"
@@ -53,6 +53,12 @@ You'll see these options towards the bottom of the SNMP discovery job setup scre
 
 When sensors are discovered, they are created with Asset records in Device42. Navigate to **Resources > Assets > All Assets** to see a list of all assets. Filter the list by `Type="Sensor"` to see a list of all the PDU-attached sensors discovered.
 
+### Geist Power Unit Serial Number Discovery
+
+As of version 19.08, Device42 uses a different OID to discover power unit serial numbers for Geist PDUs, which now match the physical serial numbers on the devices.
+
+If a Geist power unit was discovered before this change and the [device matching level](/auto-discovery/unprocessed-device-records.mdx#device-matching-level) is not set to **Moderate**, a separate device record will be created. If matching is set to **Moderate** and the **Give precedence to hostname** option is not selected, the serial number will be updated but not the name of the device or power unit. 
+
 ## Capacity Considerations
 
 Monitoring is a fairly resource-intensive process, and as a result, each individual monitoring appliance is limited in the number of PDUs, infeeds, and outlets it can handle. When you set up each autodiscovery job, you will choose a polling interval. The primary resource limitation is the number of SNMP polls that can be done in the selected polling. So, if you select 5-minute polling intervals, you monitor 5x the number of PDUs in one monitoring appliance that you could if you selected 1-minute polling intervals.

diff --git a/docs/infrastructure-management/software/software-components.mdx b/docs/infrastructure-management/software/software-components.mdx
@@ -151,11 +151,13 @@ For example, you could select several software components and choose to:
 
 - **Mark selected Software as Ignored** and Device42 would remove the components from the list and ignore them in future discoveries.
 - **Mark selected Software as Prohibited** and Device42 would send alerts whenever prohibited software was found on a user's machine (if the alert was configured).
-_ **Refresh/update Software counts** and the software counts (but not the autodiscovery job) would be run immediately.
+- **Refresh/update Software counts** and the software counts (but not the autodiscovery job) would be run immediately.
 
-:::note
 The **Refresh/update Software counts** action is useful when you have changed the licensing or software count configuration and want to see the impact of the change immediately.
-:::
+
+### Update Ignored Software Discovery Count
+
+The Discovered Count field is automatically recalculated at a regular interval (configured in **Global Settings > Software Licensing**) for Managed, Unmanaged, and Prohibited software types – excluding Ignored software. Use the **Refresh/update Software counts** action to manually update counts for Ignored software.
 
 ### Assign Software to Suite
 

diff --git a/docs/infrastructure-management/software/software-license-management.mdx b/docs/infrastructure-management/software/software-license-management.mdx
@@ -96,7 +96,7 @@ A configuration item (CI) worth noting is **Software Type**. This field controls
 
 - **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.
+- **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. The Discovered Count field is not automatically recalculated for Ignored software; use the **Refresh/update Software counts** action to manually recalculate if needed.
 
 **Unmanaged** is the default option. Select other options as required before saving the autodiscovery job.