cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
JoeH
Engaged Sweeper
Hi,

I have about 190 users in Lansweeper. We are not utilizing the helpdesk functions. I saw that I can change user role assignment to be AD group driven instead of having to assign a role each time a user is added. I created 3 new roles with corresponding AD groups. One for full admin, one for view only, and one for view + reports. I added the appropriate users in each AD group as well as one of my test users that has not been added to Lansweeper prior. When I log in with my test user account, I'm redirected to the helpdesk portion of the site. When I look at the test user under the user config, it shows up with a "none selected" for the role. If I change that to any of the available roles, then I can get to the right pages. So it seems like the AD group assignment on the role (under the User Roles section) is not working?
Is it supposed to work?

Thanks,
Joe
1 ACCEPTED SOLUTION
Susan_A
Lansweeper Alumni
There are no known issues with assigning permissions based on AD groups. If you haven't already, I would recommend ensuring your installation is up-to-date and checking the group requirements below. If the issue persists, I would recommend sending some screenshots of your configuration to support@lansweeper.com, so we can troubleshoot from there.
  • UAC (User Account Control) must be disabled on the server hosting the Lansweeper console, as UAC is known to cause issues with group detection.
  • The domains of the Lansweeper server and the user with console access must be trusted/must be in the same forest.
  • Nested groups are not supported.
  • The group must be a universal security group.
  • The group must be a manually created group. Built-in groups like the domain admins group may not work.
  • If a user was only recently added to the group, his user account must be logged out and back in (not just out of Lansweeper) in order for the group changes to take effect.

View solution in original post

1 REPLY 1
Susan_A
Lansweeper Alumni
There are no known issues with assigning permissions based on AD groups. If you haven't already, I would recommend ensuring your installation is up-to-date and checking the group requirements below. If the issue persists, I would recommend sending some screenshots of your configuration to support@lansweeper.com, so we can troubleshoot from there.
  • UAC (User Account Control) must be disabled on the server hosting the Lansweeper console, as UAC is known to cause issues with group detection.
  • The domains of the Lansweeper server and the user with console access must be trusted/must be in the same forest.
  • Nested groups are not supported.
  • The group must be a universal security group.
  • The group must be a manually created group. Built-in groups like the domain admins group may not work.
  • If a user was only recently added to the group, his user account must be logged out and back in (not just out of Lansweeper) in order for the group changes to take effect.

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now