search for: whom

PS: I could share information about what should be modified to modify the very same GPO, I didn't yet as I'm not sure anyone there would be interested and because that would work only for that kind of GPO. 2016-07-06 17:08 GMT+02:00 mathias dufresne <infractory at gmail.com>: > Context: several teams have to manage only a a bunch of the company's > computers, so these

You may be able to edit the GPO's completely from the linux side. They contain registry.pol files whom's syntax is not so difficult to read and write. https://msdn.microsoft.com/en-us/library/windows/desktop/aa374407%28v=vs.85%29.aspx Am 06.07.2016 um 17:24 schrieb mathias dufresne: > PS: I could share information about what should be modified to modify the > very same GPO, I didn't...

...D at DOMAIN.TLD - ticket and session encryption RC4 > #1 krbtgt/DOMAIN.TLD at DOMAIN.TLD - ticket encryption RC4 and session > encryption AES256 > These keys use only AES256 on my 4.4.5 test environment which ran on > 2008 R2 level all the time. > So there must be an domain account whoms keys must also be > regenerated. I have no idea how to reset that. Just to be sure i added an third dc (different site and subnet) and reset this dc's password using the one storde on that dc in secrets.tdb. This also worked. Here is the error message which appears once during replicatio...

...ncryption RC4 >>> #1 krbtgt/DOMAIN.TLD at DOMAIN.TLD - ticket encryption RC4 and session >>> encryption AES256 >>> These keys use only AES256 on my 4.4.5 test environment which ran on >>> 2008 R2 level all the time. >>> So there must be an domain account whoms keys must also be >>> regenerated. I have no idea how to reset that. >> Just to be sure i added an third dc (different site and subnet) and >> reset this dc's password using the one storde on that dc in secrets.tdb. >> This also worked. Here is the error message whic...

...tion. #0 krbtgt/DOMAIN.TLD at DOMAIN.TLD - ticket and session encryption RC4 #1 krbtgt/DOMAIN.TLD at DOMAIN.TLD - ticket encryption RC4 and session encryption AES256 These keys use only AES256 on my 4.4.5 test environment which ran on 2008 R2 level all the time. So there must be an domain account whoms keys must also be regenerated. I have no idea how to reset that.

...cket and session encryption RC4 >> #1 krbtgt/DOMAIN.TLD at DOMAIN.TLD - ticket encryption RC4 and session >> encryption AES256 >> These keys use only AES256 on my 4.4.5 test environment which ran on >> 2008 R2 level all the time. >> So there must be an domain account whoms keys must also be >> regenerated. I have no idea how to reset that. > Just to be sure i added an third dc (different site and subnet) and > reset this dc's password using the one storde on that dc in secrets.tdb. > This also worked. Here is the error message which appears once...

...t;>> #1 krbtgt/DOMAIN.TLD at DOMAIN.TLD - ticket encryption RC4 and session >>>> encryption AES256 >>>> These keys use only AES256 on my 4.4.5 test environment which ran on >>>> 2008 R2 level all the time. >>>> So there must be an domain account whoms keys must also be >>>> regenerated. I have no idea how to reset that. >>> Just to be sure i added an third dc (different site and subnet) and >>> reset this dc's password using the one storde on that dc in >>> secrets.tdb. >>> This also worked....

Am 17.09.2016 um 04:53 schrieb Achim Gottinger via samba: > > > Am 17.09.2016 um 03:24 schrieb r moulton via samba: >> On Fri, Sep 16, 2016 at 6:08 PM, Achim Gottinger via samba >> <samba at lists.samba.org> wrote: >>> >>> Am 17.09.2016 um 02:36 schrieb Achim Gottinger via samba: >>>> >>>> >>>> Am 17.09.2016 um 02:19