‎12-17-2018 11:19 PM
Solved! Go to Solution.
‎12-20-2018 02:32 PM
‎12-20-2018 02:32 PM
‎12-21-2018 03:55 PM
Charles.X wrote:
I did some digging, I found one similar issue from 2016 where we were able to reproduce this.
We could reproduce this error by creating a test user and filling in the userWorkstations attribute in AD for the user with a computer that is not the Lansweeper server. This attribute is not filled in by default in AD. This specifically might not be what is causing the error in your case though. But it will be an AD user setting or an applied group policy most likely.
‎12-18-2018 06:07 PM
‎12-18-2018 02:41 PM
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now