Microsoft KB Archive/284849

= Permissions Are Incorrect After Installing Security Configuration Manager =

PSS ID Number: 284849

Article Last Modified on 10/3/2003

-

The information in this article applies to:


 * Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
 * Microsoft Windows NT Server 4.0 Terminal Server Edition SP5
 * Microsoft Windows NT Server 4.0 Terminal Server Edition SP6

-



This article was previously published under Q284849



SYMPTOMS
After you install Security Configuration Manager (SCM), you may experience the following symptoms:  Folder permissions may appear incorrect when you view them in Windows Explorer. For example, when you view existing permissions, the users and groups (if applied) are listed but none of the check boxes (such as Full Control, Read, or Write) are selected, even though the user or group may have those permissions. Existing folder permissions may be incorrect after you use Windows Explorer to add or change permissions. You may not be able to use Windows Explorer on that computer to remotely administer file permissions on other Windows NT-based computers on the network. This problem most commonly occurs on computers that are running localized versions of Windows NT when you try to view permissions on computers that are running the English-language version of Windows NT. The problem may also occur when both computers are running the same language version of Windows NT. When you try to view file permissions on a remote computer over the network after installing SCM, you may receive the following error message:

Unable to display security information

In the French-language version of Windows NT, the error message is:

Impossible d'afficher les informations de securite

In the German-language version of Windows NT, the error message is:

Die Sicherheitseinstellungen konnen nicht angezeigt werden



Note that these issues occur only on partitions that use the NTFS file system. Partitions that use the FAT file system do not have folder or file-level permissions.



CAUSE
The version of SCM that is included with Windows NT 4.0 service packs starting with Service Pack 4 runs as part of Explorer.exe and provides compatibility with Windows 2000. The new version of SCM incorrectly interprets existing folder security information.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows NT Server 4.0, Terminal Server Edition, service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:   Date         Time   Version         Size     File name 29-Mar-2001 14:29  4.0.1381.33472   70,928  Aclui.dll 29-Mar-2001 14:29  4.0.1381.33472  156,432  Lsasrv.dll 29-Mar-2001 14:29  4.0.1381.33472   84,240  Ntmarta.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbfix kbQFE KB284849

Technology: kbNTTermServ400 kbNTTermServ400sp4 kbNTTermServ400sp5 kbNTTermServ400sp6 kbNTTermServSearch kbWinNT400search kbWinNTS400search kbWinNTsearch kbWinNTSsearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.