Bug 5358 - Group policy objects can be created, but neither edited or deleted
Summary: Group policy objects can be created, but neither edited or deleted
Status: RESOLVED INVALID
Alias: None
Product: Samba 4.0
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: x86 Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Andrew Bartlett
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-28 06:24 UTC by Robert Porl
Modified: 2008-06-11 02:48 UTC (History)
1 user (show)

See Also:


Attachments
SMBD Level 9 debug log (138.54 KB, text/plain)
2008-03-28 06:25 UTC, Robert Porl
no flags Details
Wireshark capture (88.21 KB, application/octet-stream)
2008-03-28 06:27 UTC, Robert Porl
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Porl 2008-03-28 06:24:26 UTC
After installing & configuring samba4, Windows XP SP2 (with all current updates) can join and log on to the domain perfectly. When trying the group policy functionality, i can create a GPO in any OU. However, both editing and deleting such a GPO fails with error messages "path not found" and "folder not empty" respectively.

Attached find a level 9 debug log from smbd as well as a wireshark trace of the actions described above (create a GPO in OU=TestOU, attempt to edit it, attempt to delete it).

Regards,

-Robert
Comment 1 Robert Porl 2008-03-28 06:25:40 UTC
Created attachment 3222 [details]
SMBD Level 9 debug log
Comment 2 Robert Porl 2008-03-28 06:27:04 UTC
Created attachment 3223 [details]
Wireshark capture
Comment 3 Matthias Dieter Wallnöfer 2008-05-22 05:38:58 UTC
Please retest! On my Windows 2000 environment it works.
Comment 4 Matthias Dieter Wallnöfer 2008-06-02 17:29:36 UTC
The informations don't seem very helpful to me because I don't realize a strange behaviour or error cases. If the problem persists, try to provide more informations. Otherwise please close!
Comment 5 Matthias Dieter Wallnöfer 2008-06-11 02:48:41 UTC
I'm going to close this, because the reporter didn't provide more informations. If the problem persists, please reopen and add more indications.