Multiple Bugs in Security Configuration Manager MMC Snap-In

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.

Windows NT Server or Workstation 4.0

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:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

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:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.