search for: dd392260

Displaying 4 results from an estimated 4 matches for "dd392260".

2016 Jun 28
0
unique index violation on objectSid
...> default 180 days to only 1 day. Doing that tomorrow all deleted objects > > will be deleted and if you are lucky - I can't guaranty that will work - > > you will able to reuse these RIDs. > No, to only 1 day is it impossible: > https://technet.microsoft.com/en-us/library/dd392260(v=ws.10).aspx If > the value is less than 3 days, the tombstone lifetime is 3 days. > 1 day is accepted by Samba DB. I did tried : ) I'm not sure if my objects were deleted just 24 hours after the change or earlier or later. Anyway 1 or 3 days could be an acceptable delay to auto-solve a...
2016 Jun 28
1
unique index violation on objectSid
...0 days to only 1 day. Doing that tomorrow all deleted objects >> > will be deleted and if you are lucky - I can't guaranty that will work - >> > you will able to reuse these RIDs. >> No, to only 1 day is it impossible: >> https://technet.microsoft.com/en-us/library/dd392260(v=ws.10).aspx If >> the value is less than 3 days, the tombstone lifetime is 3 days. >> > > 1 day is accepted by Samba DB. I did tried : ) > I'm not sure if my objects were deleted just 24 hours after the change or > earlier or later. Anyway 1 or 3 days could be an accep...
2016 Jun 28
1
unique index violation on objectSid
Hi Valery, First thank you for this detailed information about your searches. I find them very interesting. Here I'm thinking of two workarounds. The first one would be to list deleted objects RIDs, to verify RID=2002 is really the last one used, being sure there is no deleted object with RID=2003 and so on. Then once you get the last RID used, you could change RidNextRid to match this
2016 Jun 28
6
unique index violation on objectSid
27.06.2016 18:45, mathias dufresne: > Perhaps you don't have yet duplicate objectSid as that's not supposed to be > possible. > Rather than scripting something to look for objectSid used twice I would > start with dbcheck and other tools to verify that your database is > consistent and identical on all servers. [root at pdc ~]# samba-tool dbcheck Checking 3346 objects