search for: b63a

...ers \ USER1XXX> gpupdate / force Updating Policy ... Unable to update user policy successfully. The following errors for found: Group Policy was not processed. Windows was unable to apply the settings registry-based policy for the LDAP Group Policy object LDAP://CN =User,cn={AED3AF6A-D79E-436F-B63A-158BEC3E80B7},cn=policies,cn=system,DC=interno ,DC=XXXX,DC=XXXX,DC=br.. Group Policy settings will not be reso this event is not resolved. View event details for more information about the path name and path of the file that caused the failure. Unable to update computer policy successfully. The fo...

...; Updating Policy ... > > Unable to update user policy successfully. The following errors for > found: > > Group Policy was not processed. Windows was unable to apply the settings > registry-based policy for the LDAP Group Policy object LDAP://CN > =User,cn={AED3AF6A-D79E-436F-B63A-158BEC3E80B7},cn=policies,cn=system,DC=interno > > ,DC=XXXX,DC=XXXX,DC=br.. Group Policy settings will not be reso > this event is not resolved. View event details for more information > about the path name and path of the file that caused the failure. > Unable to update computer p...

Hello, copying idmap is fairly straightforward. 1) on your first DC (that one that has PDC FSMO, and is the source for rsync) create backup of idmap.ldb tdbbackup -s .bak /path/to/samba/private/idmap.ldb it will create idmap.ldb.bak 2) stop samba service on second DC 3) copy idmap.ldb.bak from first dc to second dc, lose the .bak suffix and just copy it over idmap.ldb on second dc 4)

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...8712140CEE (7b0e8b14-41f3-4c58-83b3-d9141d1351d3) on home-client-2 [2017-10-25 10:14:12.496201] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/FA94413080F37030AB04410A9C5AE43184AF5868 (fffc7dcc-bc1a-4061-b63a-1d2396bc550f) on home-client-2 [2017-10-25 10:14:12.506090] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/4000230BFEBED57A1825016C12625C8B165F0C8D (44c2de92-905f-4a32-9ed4-350ef14668b5) on home-client-2...