Hi Andrew, Hi Alex, Hi all.
We're really pleased to announce that in this release (S4 rc5), the
sysvolreset command works fine and returns no errors.
The clients download their GPO fine, and the sysvolcheck return no error
as well !
So our problems with SYSVOL ACL are closed for the moment.
Thanks for your efforts.
-----------------------
*** OB
*** Service Informatique
*** Fondation de la Miséricorde
Le 26/10/2012 11:48, Andrew Bartlett a écrit :
On Fri, 2012-10-26 at 09:36 +0200, Olivier BILHAUT wrote:
Hi Andrew, Hi Alex,
Pleased to see that you figured this out.
We've got exactly the same problem from a blank provisioned domain (not
a migration), with a setup with 2 gpo. (Ubuntu 12.04 - S4 rc3).
Since our instance is in a semi-production environment, we'll wait for
your fix. But if needed, we could give you more level 10 logs.
Note that when the sysvolreset is launched and that sysvolcheck returns
no errors, then the windows clients can't "gpupdate" anymore on some gpo.
Note also that when syslvolreset isn't launched at S4 update, the
sysvolcheck command return the Alex's error but the client can update
their gpo.
This I think is the umask issue I addressed with this patch. A
sysvolreset with this patch applied should fix that. steve noticed that
permissions were missing from the posix ACL that was generated.
(this patch is in master)
Andrew Bartlett
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
