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:
0 commit comments