Matthieu,
The following change has been made to the section 3.1.5.5.7.2 of MS-ADTS. It
will appear in the next public release of MS-ADTS on MSDN.
Section 3.1.1.5.5.7.2 (Tree-delete Constraints)
-- The second bullet, which has been changed as follows:
Before:
- - - - - - - - - - - - - - - -
Hi Hongwei,
I'm not sure I have 100% understood, please allow me to try to reformulate.
So the basic rule for isCriticalSystemObject is correct when you use the
subtree delete control, but if the object has one of its objectclass in
the SAM specific object list (3.1.1.5.2.3) then
Matthieu,
I finished the investigation on this behavior. As per MS-ADTS 3.1.5.5.7.2
, when a tree deletion is performed , every object in the tree will be checked
to see if it has isCriticalSystemObject set to TRUE, including the root node on
which the delete operation is performed. But
