Multiple Bugs in Security Configuration Manager MMC Snap-In
ID: Q218934
|
The information in this article applies to:
-
Microsoft Windows NT Server version 4.0 SP4
SYMPTOMS
Several issues have been found when using the Security Configuration Manager (SCM) MMC Snap-in that ships with Windows NT 4.0 Service Pack 4:
- When using SCM to perform a system analysis, groups that have been configured to restrict membership are not being flagged when their membership violates the security attributes that has been set within SCM.
- When setting DACL properties on a folder to not inherit from its parent and then changing SACL properties on the same object, the DACL inherit property will change from not to inherit to inherit.
- After adding a registry key with SCM and then setting permissions on that key, the user is presented with file permissions rather than registry permissions.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual software update. For information on obtaining the
latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft
Product Support Services. For a complete list of Microsoft Product Support
Services phone numbers and information on support costs, please go to the
following address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed
at the beginning of this article. This problem was first corrected in Windows NT 4.0 Service Pack 6.
Additional query words:
4.00
Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0 SP4
Platform : winnt
Issue type : kbbug