You should be able to use samba-tool user enable Testuser2 or possibly
samba-tool user setexpiry (add a --help for more info on how to use it).
Good luck,
Ricky
On Tue, Feb 12, 2013 at 7:17 AM, Thomas Simmons twsn...@gmail.com wrote:
On Mon, Feb 11, 2013 at 6:56 PM, Thomas Simmons
On Mon, Feb 11, 2013 at 6:56 PM, Thomas Simmons twsn...@gmail.com wrote:
I have come across a few accounts (out of 300+) that seem to be locked
that will not unlock. These accounts were migrated from S3. Can someone
advise - what am I missing here?
I've reset the password several times via
Hello Ricky,
These do not seem to work. samba-tool user setexpiry alters the
accountExpires attribute. samba-tool user enable/disable's behavior is
odd. disable appears to add 2 to the current value and enable subtracts 2
from the updated value (only if it's been disabled). Like this:
Running
Hi
On 12 February 2013 16:03, Thomas Simmons twsn...@gmail.com wrote:
Hello Ricky,
These do not seem to work. samba-tool user setexpiry alters the
accountExpires attribute. samba-tool user enable/disable's behavior is
odd. disable appears to add 2 to the current value and enable subtracts 2
The way I understand it, 512 is normal account (my account is set to this
and is fine). 16 is locked out. 512+16=528, so 528 is a normal account,
that is locked out. 2 is disabled and if I disable my account, it adds 2
(514). The real problem is that I cannot find a way to change this back to
512
On Tue, Feb 12, 2013 at 11:30 AM, Thomas Simmons twsn...@gmail.com wrote:
The way I understand it, 512 is normal account (my account is set to
this and is fine). 16 is locked out. 512+16=528, so 528 is a normal
account, that is locked out. 2 is disabled and if I disable my account,
it adds 2
I meant to send this to the list, but my phone had other ideas:
Ah you are right that it means LOCKOUT. I didn't notice that the
article skipped 4 for some reason and went straight to 8. That makes
much more sense. If samba-tool does not currently support toggling
that bit it should be very easy
On 12 February 2013 23:03, Thomas Simmons twsn...@gmail.com wrote:
I figured out a way to correct this via RSAT, though I still think there is
a problem - I'm sure checking Unlock Account should, well, unlock the
account. Anyhow, In RSAT, if you select View Advanced Features, you
will get an
I have come across a few accounts (out of 300+) that seem to be locked that
will not unlock. These accounts were migrated from S3. Can someone advise -
what am I missing here?
I've reset the password several times via RSAT, checking the Unlock
Account checkbox, which has not helped. Resetting the
