Not sure what’s happening here, but for some reason, AD is now rejecting the
user I created for use with LTB for insufficient privileges (error 50). This
user was specifically created with the minimum rights to change passwords. I’m
using Self-service password v1.1, and this was working fine a couple of weeks
ago. I have not altered the Windows server (other than to install Microsoft’s
patch updates over time) or the special user I set up for the purpose of
letting LTB change passwords. I’m stumped.
If I give the LTB user domain admin rights, everything works just fine, so it
isn’t a communication issue with the server. Any idea what this could be?
One thing I noticed is that the entire delegate control wizard does not seem to
offer the privileges I was used to seeing in the past. For example, Write
lockout time and write shadowlastchange are nowhere to be found…
Thanks!
Gray
Gray McCord
Adapt, Mutate, Migrate, or Die
-C. Darwin
_______________________________________________
ltb-users mailing list
ltb-users@lists.ltb-project.org
https://lists.ltb-project.org/cgi-bin/mailman/listinfo/ltb-users
