You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/infrastructure-management/assets.mdx
+11-12Lines changed: 11 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ sidebar_position: 5.5
6
6
importThemedImagefrom"@theme/ThemedImage";
7
7
importuseBaseUrlfrom"@docusaurus/useBaseUrl";
8
8
9
-
Assets are useful for tracking items that may not be directly discoverable. Like devices in Device42, assets can support lifecycle events, be racked, and be assigned parts. However, assets do not consume licenses.
9
+
Assets are useful for tracking items that may not be directly discoverable. Like devices in Device42, assets support lifecycle events, can be racked, and can be assigned parts. Unlike devices, assets do not consume licenses.
10
10
11
-
You can search, view, add, and edit assets from the list page under **Resources > All Assets**.
11
+
Navigate to **Resources > All Assets** to search, view, add, and edit assets.
12
12
13
-
## Adding Assets
13
+
## Add an Asset
14
14
15
-
From the Assets list page, click the **Create** button to create a new asset.
15
+
On the Assets list page, click **Create**.
16
16
17
17
<ThemedImage
18
18
alt="Assets list page"
@@ -24,17 +24,17 @@ From the Assets list page, click the **Create** button to create a new asset.
24
24
25
25
### Asset Types
26
26
27
-
Choose an asset **Type** from the dropdown menu or create a custom asset type by clicking **+** to the right. Different options in the Add Asset form will be available depending on the asset type you select.
27
+
Choose an asset **Type** from the dropdown menu, or click the **plus icon** to create a custom asset type. The options available in the Add Asset form depend on the asset type you select.
Name your custom asset type. If you want to associate assets of this new type with devices, check the **Asset Device Relation** checkbox. Designate the types of locations (**Storage Room**, **Server Room**, **Building**, and **Rack**) that assets of this type will be assigned to.
37
+
Name your custom asset type. To associate assets of this type with devices, check the **Asset Device Relation** checkbox. Then designate the location types (**Storage Room**, **Server Room**, **Building**, and **Rack**) that assets of this type will be assigned to.
38
38
39
39
<ThemedImage
40
40
alt="Create a custom asset type"
@@ -70,17 +70,16 @@ Show the **Rack Info** section by choosing **ACL** from the **Type** dropdown (o
70
70
71
71
### Object Category Field
72
72
73
-
In v19.06, the **Object Category** field on individual asset view pages is displayed only when **Role-Based Access Control** (RBAC) is enabled globally.
73
+
The **Object Category** field appears on asset view pages only when **Role-Based Access Control** (RBAC) is enabled globally.
74
74
75
-
A workaround on view pages is to use the **Legacy View** button to see the **Object Category** field.
75
+
As a workaround, click **Legacy View** to see the **Object Category** field.
76
76
77
77
Turn on **Role-Based Access Control** under **Tools > Settings > Global Settings**.
78
78
79
79
## Asset Actions
80
80
81
-
The action menu has options for deleting, exporting, and updating assets. You can also**Generate QR/Barcodes for selected Items**for asset management.
81
+
Select one or more assets from the list, then choose an action from the**Actions**dropdown:
82
82
83
-
Select one or several assets from the table, and select an action from the menu:
84
83
- Delete with Detailed Confirmation
85
84
- Fast Background Delete
86
85
-ExportSelectedItems
@@ -99,4 +98,4 @@ Select one or several assets from the table, and select an action from the menu:
Copy file name to clipboardExpand all lines: docs/infrastructure-management/certificate-management.mdx
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,22 +6,22 @@ sidebar_position: 5
6
6
importThemedImagefrom"@theme/ThemedImage";
7
7
importuseBaseUrlfrom"@docusaurus/useBaseUrl";
8
8
9
-
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).
9
+
Device42 tracks SSL certificates discovered across your infrastructure and lets you view validity details, associate certificates with devices and FQDNs, and run expiry reports. For details on creating a certificate discovery job, see[Certificate Discovery](/auto-discovery/certificate-auto-discovery.mdx).
10
10
11
11
## Certificate List Page
12
12
13
-
The list page for certificates, under **Applications > Certificates**, will show you all certificates discovered in Device42 along with their validity details.
13
+
The certificate list page, under **Applications > Certificates**, shows all certificates discovered in Device42 along with their validity details.
14
14
15
-
The fields include:
15
+
Each certificate entry displays the following fields:
16
16
17
17
- Serial Number
18
-
-Is Key Encipherment
19
-
-Is Key CERT Sign
18
+
- Key Encipherment
19
+
- Key CERT Sign
20
20
- Subject Alternative Name
21
21
- First Detected date and time
22
22
- Encryption method
23
23
24
-
You can export certificates by selecting them from the list and choosing the **Export Selected items as CSV**option from the **Actions** dropdown menu.
24
+
You can export certificates by selecting them from the list and choosing **Export Selected items as CSV** from the **Actions** dropdown.
25
25
26
26
<ThemedImage
27
27
alt="Certificate list page"
@@ -37,9 +37,9 @@ You can export certificates by selecting them from the list and choosing the **E
37
37
38
38
### View Certificates
39
39
40
-
Click on the name of a certificate from the list page, under **Applications > Certificates**, to view it.
40
+
Click the name of a certificate to view it.
41
41
42
-
When viewing a certificate that has been imported, you can now associate FQDN, multiple devices, IPs, and different validity dates with your certificates. This allows you to have a wildcard certificate and easily see the different FQDNs or subdomains associated with it.
42
+
You can associate an FQDN, multiple devices, IPs, and different validity dates with a certificate. This is useful for wildcard certificates, where you can see all the FQDNs or subdomains associated with a single certificate.
43
43
44
44
<ThemedImage
45
45
alt="View certificate"
@@ -63,20 +63,20 @@ Device42 supports certificate uploads in the following formats:
63
63
64
64
## Certificate Instances
65
65
66
-
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.
66
+
Certificate instances show the device and IP address relationships for individual certificates. Navigate to **Applications > Certificate Instances** to view them. You can filter by device building, service level, and customer.
67
67
68
68
Certificate instances are also displayed in the device details view.
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.
80
+
When a certificate has multiple valid-to dates, Device42 reports alert based on the oldest date stored for that certificate.
81
81
82
-
This allows you to run reports to see which devices you still need their certificates updated, allowing you to see your update progressing — which can prove especially useful with very large deployments.
82
+
You can run reports to see which devices still need their certificates updated. This is especially useful in large deployments where you want to track update progress.
Copy file name to clipboardExpand all lines: docs/infrastructure-management/operating-systems.mdx
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ sidebar_position: 4
6
6
importThemedImagefrom'@theme/ThemedImage'
7
7
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
8
8
9
-
Device42 tracks which devices are running which Operating Systems (OS). This module also ties into Software License Management so that you can see how many copies you are licensed for and how many you are actually using.
9
+
Device42 tracks which operating systems (OS) are running on which devices, and integrates with Software License Management so you can compare licensed counts against actual usage.
10
10
11
-
Navigate to **Resources > Operating Systems > All Operating Systems** to locate the Operating Systems list.
11
+
Navigate to **Resources > Operating Systems > All Operating Systems** to view the Operating Systems list.
12
12
13
13
<ThemedImage
14
14
alt="Operating Systems list with Enriched Data icons"
@@ -18,24 +18,24 @@ Navigate to **Resources > Operating Systems > All Operating Systems** to locate
18
18
}}
19
19
/>
20
20
21
-
If the OS is standardized and enriched by the data Normalization and Enrichment Service, an **AI icon**will be displayed to the right of its name.
21
+
If the OS is standardized and enriched by the data Normalization and Enrichment Service, an **AI icon**appears to the right of its name.
22
22
23
-
The Operating Systems list page shows all of your operating systems and includes the **Total Count** of devices running the OS, the **Discovered Licensed Count**, and the number of OSs that are not licensed (named **Discovered Non-Licensed Count**). If you click on one of the listed operating systems, you will see details including which machines are running the OS.
23
+
The list shows all operating systems with the **Total Count** of devices running each OS, the **Discovered Licensed Count**, and the **Discovered Non-Licensed Count**. Click an operating system to see details, including which machines are running it.
24
24
25
25
## Enriched Data Operating System Fields
26
26
27
-
If the OS record has been enriched, key maintenance dates may be displayed in the **Enriched Data** section along with other OS details.
27
+
When an OS record has been enriched, key maintenance dates and other OS details appear in the **Enriched Data** section of the record.
28
28
29
29
<ThemedImage
30
-
alt="Windows device Enriched Data example"
30
+
alt="AI icon hover over on the Operating Systems list"
@@ -47,12 +47,12 @@ See the [Operating System Attributes](auto-discovery/enriched-data/index.mdx#ope
47
47
Note that data will only be populated by the data Normalization and Enrichment Service if it's used by the OS vendor and if the data is available.
48
48
49
49
:::info
50
-
Operating System fields that contain Enriched Data cannot be edited or changed.
50
+
Operating System fields that contain Enriched Data cannot be edited or changed.
51
51
:::
52
52
53
53
### Disable OS Changes via API, Discovery, or EnrichAI
54
54
55
-
You can prevent non-manual changes being made to OS data. On the OS view, click the **Edit**button and turn on the **Don't change via API/Discovery/EnrichAI** option for device OSs.
55
+
Use this option to protect OS data from being overwritten by automated processes. On the OS record, click **Edit** and enable the **Don't change via API/Discovery/EnrichAI** option.
56
56
57
57
<ThemedImage
58
58
alt="Don't change via API/Discovery/EnrichAI option"
@@ -62,6 +62,6 @@ You can prevent non-manual changes being made to OS data. On the OS view, click
62
62
}}
63
63
/>
64
64
65
-
## OS Update Logic for Devices
65
+
## OS Update Logic
66
66
67
-
Each discovery job in Device42 assigns an accuracy score to the OS it detects. Device42 will only update a device's OS information for newly discovered OS on the same device if the accuracy score is equal to or greater than the prior OS accuracy score.
67
+
Each discovery job assigns an accuracy score to the OS it detects. Device42 only updates a device's OS information if the newly discovered OS has an accuracy score equal to or greater than the previously recorded score.
Copy file name to clipboardExpand all lines: docs/infrastructure-management/software/index.mdx
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,14 @@ title: "Software"
5
5
importThemedImagefrom'@theme/ThemedImage'
6
6
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
7
7
8
-
The Software License Management (SLM) module allows you to create and maintain a comprehensive, accurate profile of software deployed across all Windows and Linux machine instances within your IT infrastructure.
8
+
The Software License Management (SLM) module helps you build and maintain an accurate profile of software deployed across Windows and Linux machines in your IT infrastructure. Use it to track installed software, manage license models, and monitor end-of-life status.
9
9
10
-
Navigate to**Resources > Software Components** and select the relevant page for viewing or managing your software:
10
+
Navigate to**Resources > Software Components** and choose the section you need:
*[Software End-of-Life or End-of-Support](software-eol-eos.mdx)
16
16
17
17
<ThemedImage
18
18
alt="The Software Components section in the Resources menu"
@@ -22,9 +22,11 @@ Navigate to **Resources > Software Components** and select the relevant page fo
22
22
}}
23
23
/>
24
24
25
+
The image above shows the four sections available under **Resources > Software Components**.
26
+
25
27
## Discover Software
26
28
27
-
When creating a discovery job, select the **Discover Software** option under **Software and Applications**to ensure that all software information is found.
29
+
The **Discover Software** option under **Software and Applications**is enabled by default when you create a discovery job. Confirm it is checked to ensure software data is collected.
Copy file name to clipboardExpand all lines: docs/infrastructure-management/software/merge-and-assign-software-components.mdx
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,13 @@ sidebar_position: 4
6
6
importThemedImagefrom'@theme/ThemedImage'
7
7
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
8
8
9
-
You can merge software components and assign them to a component suite as follows:
9
+
Software suites let you group related software components together for easier license tracking and reporting. This page covers how to assign components to a suite and how to handle components that share the same name before merging.
10
10
11
-
- Navigate to **Resources > Software Components > All Software Components** to view the **Software Components** list page.
12
-
- Select the components you want to merge, choose **Assign Software to Suite** from the **Actions** dropdown, and confirm to run the action.
11
+
## Assign Software to a Suite
12
+
13
+
1. Navigate to **Resources > Software Components > All Software Components**.
14
+
2. Select the components you want to merge and choose **Assign Software to Suite** from the **Actions** dropdown.
15
+
3. Confirm to run the action.
13
16
14
17
<ThemedImage
15
18
alt="Assign software to suite"
@@ -19,13 +22,13 @@ You can merge software components and assign them to a component suite as follow
19
22
}}
20
23
/>
21
24
22
-
- In the **Assign Software to Suite** dialog, click **Select Software Suite** and search for an existing software component to create the suite that the selected components will be assigned to, then click**Assign** to confirm.
25
+
4. In the **Assign Software to Suite** dialog, click **Select Software Suite** and search for the existing software component that will become the suite. Click**Assign** to confirm.
To merge software components with the same name into a suite, you must first merge them together, then merge them into a suite. A new component suite cannot have the same **name + vendor** combination as an existing software component; it must have a unique **name + vendor** combination.
47
-
49
+
To merge software components with the same name into a suite, you must first merge them, then add them to a suite. A new component suite must have a unique **name + vendor** combination — it cannot match an existing software component.
48
50
49
-
For example, if you had:
51
+
For example, given these three components:
50
52
51
-
1.A software component `ABC`, with the vendor `Cisco`.
52
-
2.A software component `ABC`, with the vendor `MS`.
53
-
3.A software component `ABC-Suite`, with the vendor `None`.
53
+
1.`ABC` — vendor `Cisco`
54
+
2.`ABC` — vendor `MS`
55
+
3.`ABC-Suite` — vendor `None`
54
56
55
-
You could merge either `1.`**or**`2.` into `3.` without problem. However, if you tried to merge `1.`**and**`2.` into `3.`, you would receive a validation error prompting you to merge `1.` with `2.` before trying to merge them into `3.`.
57
+
You can merge either component 1 or component 2 into component 3 without issue. However, merging both 1 and 2 into 3 at the same time will produce a validation error. In that case, merge 1 and 2 together first, then merge the result into 3.
0 commit comments