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/auto-discovery/windows-and-hyper-v-auto-discovery.mdx
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Device42 discovery uses multiple protocols to communicate with the target device
10
10
11
11
## Prerequisites
12
12
13
-
When using WMI, you need to install Windows Discovery Service (WDS) and connect to your Remote Collectors (RCs) before setting up your Windows discovery job. For WDS installation instructions and information, visit the [Windows Discovery Service Installation](/getstarted/installation/windows-discovery-service-installation.mdx) documentation.
13
+
When using WMI, you need to install the Windows Discovery Service (WDS) and connect to your Remote Collectors (RCs) before setting up your Windows discovery job. For WDS installation instructions and information, visit the [Windows Discovery Service Installation](/getstarted/installation/windows-discovery-service-installation.mdx) documentation.
14
14
15
15
### WinRM Network Requirements
16
16
@@ -374,7 +374,7 @@ If you discover servers that do not belong to a domain, your User Account Contro
374
374
375
375
### Windows ADM Minimum Permissions
376
376
377
-
There are two options for configuring ADM permissions. The first option uses local administrative permissions and the `IPC$` and `ADMIN$` shares. The second option lets users configure their own shares.
377
+
There are two options for configuring ADM permissions for admin users. The first option uses local administrative permissions and the `IPC$` and `ADMIN$` shares. The second option lets users configure their own shares.
378
378
379
379
For the local administrator method:
380
380
@@ -398,6 +398,20 @@ sources={{
398
398
}}
399
399
/>
400
400
401
+
While it's best to use an admin account for complete discovery, you can try the following workaround to grant a non-admin user permission for service discovery.
402
+
403
+
Use the `sc.exe sdset scmanager` command to grant `SC_MANAGER_CONNECT` permission to the user:
404
+
405
+
- First, [find the SID](https://www.ninjaone.com/blog/how-to-find-user-security-identifier/) of the non-admin user account that you want to grant permission.
406
+
407
+
- Next, as an admin user, add the non-admin user's SID to the following command and execute it in PowerShell:
Copy file name to clipboardExpand all lines: docs/reports/reports/periodic-jobs-page.mdx
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,23 @@
2
2
title: "Periodic Jobs Page"
3
3
sidebar_position: 12
4
4
---
5
+
importThemedImagefrom'@theme/ThemedImage'
6
+
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
5
7
6
-
##Periodic Job View Page
8
+
The Periodic Jobs page also lets you view and manage the periodic sampling that discovery jobs perform on objects. Find the Periodic Jobs list page under **Analytics > Discovery Status > Periodic Jobs**.
7
9
8
-
Find the periodic jobs page by navigating to **Analytics > Discovery Status > Periodic Jobs**.
10
+
Using the **Actions** menu options, you can quickly disable:
9
11
10
-
The Periodic Jobs page offers a quick view of resource utilization (RU), Service Port (SP), Database Connections(DC) job configurations. This makes it easy to exactly which you have scheduled, and when. The Periodic Jobs page also allows you to manage your RU, SP, and DC periodic discovery jobs. You can easily disable or delete one or more jobs from this page:
12
+
- Resource utilization for PDU items
13
+
- Metrics for storage arrays
14
+
- SP sampling for devices
15
+
- DB sampling for app components
11
16
12
-
Copy file name to clipboardExpand all lines: docs/reports/reports/relutech-for-aws-migration.mdx
+65-22Lines changed: 65 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,58 +3,101 @@ title: "Relutech for AWS Migration"
3
3
sidebar_position: 13
4
4
---
5
5
6
-
## Introduction
6
+
importThemedImagefrom'@theme/ThemedImage';
7
+
importuseBaseUrlfrom'@docusaurus/useBaseUrl';
7
8
8
-
Relutech and Device42 have teamed up to ease migrations to AWS. Device42’s deep discovery provides Relutech with the information required to price your on-premise physical assets for purchase and leaseback as well as third-party maintenance. Relutech then purchases those assets and provides them back to the customer on a leasing schedule. As you migrate those workloads to AWS, the workload is then rolled off of your lease thereby reducing your on-premises costs as you increase consumption in AWS.
9
+
Relutech and Device42 have teamed up to ease migrations to AWS. Device42's deep discovery provides Relutech with the information required to price your on-premise physical assets for purchase and leaseback, as well as third-party maintenance. Relutech then purchases those assets and provides them back to the customer on a leasing schedule. As you migrate those workloads to AWS, the workload is then rolled off of your lease, thereby reducing your on-premises costs as you increase consumption in AWS.
9
10
10
11
## Getting Started
11
12
12
-
The instructions below provide a recommended approach to capture your Physical (bare metal) server inventory. Using Device42’s Operating System-level discovery, you will be able to collect inventory data relating to each server targeted on the network. Subsequent SNMP scans against a BMC (e.g., iDRAC, HP iLO, etc) will augment the data collected from OS-level scanning by identifying management MAC’s and IP’s as well as discovering the parts installed on each targeted server. Please follow the steps below to create and execute these inventory jobs.
13
+
The instructions below provide a recommended approach to capture your Physical (bare metal) server inventory. Using Device42's Operating System-level discovery, you will be able to collect inventory data relating to each server targeted on the network. Subsequent SNMP scans against a BMC (for example, iDRAC, HP iLO, and so on) will augment the data collected from OS-level scanning by identifying management MACs and IPs, as well as by discovering the parts installed on each targeted server. Please follow the steps below to create and execute these inventory jobs.
13
14
14
-
The initial recommended approach starts by performing Operating System level scans, followed by SNMP scans against a BMC, then by the Warranty sync (if applicable).
15
+
The initial recommended approach starts by performing OS-level scans, followed by SNMP scans against a BMC, then by the Warranty sync (if applicable).
15
16
16
-
1.**Hypervisor/*nix/Windows** - You'll want to ensure that these sets of Operating System level jobs are configured and run first. This discovery process will create the device record and capture parts that include CPU and HBA Card information.
17
-
2.**SNMP**- Once the OS-level scans have been completed, create and execute SNMP scans against the management IP’s of the targeted servers. These jobs will update the existing devices by adding additional parts as well as the management MAC Address and IP Address.The SNMP scan captures part information such as Ram, Disk(s) and PSU.
18
-
3.**Warranty** - Depending on the vendor, these particular jobs will retrieve service contracts associated with each server from the vendor system. If the vendor system is unavailable, the warranty data can be added manually via the UI or via spreadsheet imports. Please see the referenced link below for documentation on this discovery in Device42.
17
+
1.**Hypervisor/\*nix/Windows:**Ensure that these sets of OS-level jobs are configured and run first. This discovery process will create the device record and capture parts that include CPU and HBA Card information.
18
+
2.**SNMP:** Once the OS-level scans have been completed, create and execute SNMP scans against the management IPs of the targeted servers. These jobs will update the existing devices by adding additional parts, as well as the management MAC Address and IP Address.The SNMP scan captures part information such as RAM, Disk(s), and PSU.
19
+
3.**Warranty:** Depending on the vendor, these particular jobs will retrieve service contracts associated with each server from the vendor system. If the vendor system is unavailable, the warranty data can be added manually via the UI or via spreadsheet imports. Please see the referenced link below for documentation on this discovery in Device42.
- Set up Discovery jobs for device inventory discovery with the [*Hypevisor / *nix / Windows](/auto-discovery/linux-unix-server-auto-discovery.mdx) jobs. Set up a standard discovery scan for each type of device focusing on the physical devices (Hypervisors, *nix and Windows).
26
-
- For the Windows and *nix jobs, ensure that the Discover Parts is checked. In the Host Discovery section.
27
-
- For the Hypervisor jobs, the “Discover Parts” option is enabled as default and not changeable.
32
+
- Set up Discovery jobs for device inventory discovery with the [Hypervisor / *nix / Windows](/auto-discovery/linux-unix-server-auto-discovery.mdx) jobs. Set up a standard discovery scan for each type of device, focusing on the physical devices (Hypervisors, *nix, and Windows).
33
+
- For the Windows and *nix jobs, in the **Host Discovery** section, ensure that **Discover Parts** is checked.
34
+
- For the Hypervisor jobs, the **Discover Parts** option is enabled as default and is not changeable.
- See the [Warranty Sync](auto-discovery/warranty-autodiscovery.mdx) documentation for instructions on setting up the Warranty Sync autodiscovery.
47
84
48
85
## Recommended Automated Scheduling
49
86
50
-
- For the Hypervisor/*nix/Windows scan jobs, the jobs should be scheduled to run **_daily_**.
51
-
- For the SNMP scan jobs, the jobs should be scheduled to run **_weekly_**.
52
-
- For the Warranty Sync, the jobs should be scheduled to run **_weekly_**.
87
+
- For the Hypervisor/*nix/Windows scan jobs, the jobs should be scheduled to run **daily**.
88
+
- For the SNMP scan jobs, the jobs should be scheduled to run **weekly**.
89
+
- For the Warranty Sync, the jobs should be scheduled to run **weekly**.
53
90
54
91
## Run the Relutech Report
55
92
56
-
After the discovery jobs have been completed, navigate to _Insights+_ to extract the data for Relutech. The Relutech report is located under _Advanced Reporting_ -> _Integrations_ > _IT Asset Disposition_ > _Relutech_.
93
+
After the discovery jobs have been completed, navigate to **Insights+** to extract the data for Relutech. The Relutech report is located under **Advanced Reporting** > **Integrations** > **IT Asset Disposition** > **Relutech**.
57
94
58
-
Copy file name to clipboardExpand all lines: docs/reports/reports/run-book.mdx
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,9 @@ title: "Run Book"
3
3
sidebar_position: 14
4
4
---
5
5
6
-
The Tools>Reports menu contains a Generate Run Book entry. This menu entry will generate a run book containing most of your critical data. The format will an Excel spreadsheet with one tab per object. See an example below...
7
6
8
-
### Example
7
+
A run book contains most of your critical data. Create a run book under **Analytics > Reports > Generate Run Book**. The run book will take a few minutes to generate, depending on the size of your CMDB, and will be delivered as an Excel spreadsheet with data organized into sheets according to object categories.
0 commit comments