→ The Lansweeper Customer Excellence Awards 2024 - Submit Your Project Now! Learn More & Enter Here
‎02-20-2020 04:35 PM
‎03-03-2020 02:24 PM
‎02-26-2020 07:41 PM
‎02-26-2020 07:30 PM
‎02-26-2020 07:32 PM
francisswest wrote:
Current Version: 7.2.108.3
Website Version: 7.2.100.23
Just checked too, created 2 new user accounts in AD last week, on the same day, in the same OU. One account has the issue, the other does not.
Its...its friggin wonky.
‎02-26-2020 07:21 PM
I'm seeing the same thing. It's not mapping the AD user name. It appears that LS isn't properly scanning the AD users.
‎02-26-2020 07:28 PM
francisswest wrote:I'm seeing the same thing. It's not mapping the AD user name. It appears that LS isn't properly scanning the AD users.
Which is very odd, because it is (at least in our environment) mapping some folks, but not others.
For instance, we created a new user account for someone that started in March of 2019. Their account has the same issue described here, but another user, in the exact same OU, created in April of 2019, works 100% fine.
‎02-26-2020 07:05 PM
‎02-26-2020 07:15 PM
francisswest wrote:
I want to give this a +1, and add some further detail that may aid in troubleshooting.
We are experiencing a very similar problem. In that, a new user is created in AD (lets say usernameX1) and their email address is "usernameX1@contoso.com"
When "usernameX1@contoso.com emails our helpdesk, rather than binding it to the scanned AD user in LS (which has all the info, including assigned equipment) it will use a 'new user' style of user, without any of the AD binding. Examples included in these screenshots (personal info blocked out, obviously)
Here is the scanned AD info, which is the same username and email as the second screenshot. Notice here, there is no Helpdesk tab, and none of the user's tickets are mapped to this 'user'.
Now the second screenshot is the same user, with what looks like a LS generated amount of info, rather than binding the 2 together with the same name, email, and username:
This has only started happening recently, and is frustrating beyond belief.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now