
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-17-2014 11:00 AM
I've noticed that the new Active Directory Group scanning feature of Lansweeper 5.1 does not scan for nested AD groups. For example, I have an AD group called 'Lansweeper Access' which has individual members and several AD group members. When I find the 'Lansweeper Access' in Lansweeper it only shows the individual members and not the other AD groups.
Is this by design or a bug?
Is this by design or a bug?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2014 08:46 PM
The website access is not related to the active directory scanning.
In the website access you cannot configure nested groups, the user must must be a member of the main group.
Active directory scanning scans nested groups, if they are specified in the OU's to scan.
In the website access you cannot configure nested groups, the user must must be a member of the main group.
Active directory scanning scans nested groups, if they are specified in the OU's to scan.
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2014 08:46 PM
The website access is not related to the active directory scanning.
In the website access you cannot configure nested groups, the user must must be a member of the main group.
Active directory scanning scans nested groups, if they are specified in the OU's to scan.
In the website access you cannot configure nested groups, the user must must be a member of the main group.
Active directory scanning scans nested groups, if they are specified in the OU's to scan.
