Article ID: 818739 - Last Review: July 24, 2007 - Revision: 8.7 Groups are displayed by using their SAM account names instead of their display names
On This PageSYMPTOMS
When you view the contents of the
Security
tab in the properties dialog box of an object, or when you view the security permissions of an object by running a command-line utility such as Cacls, the security groups or the distribution groups appear in the following format:
sAMAccountName(Domain\sAMAccountName)
where
sAMAccountName is the value of Active Directory sAMAccountName attribute, and where
Domain
is the name of your domain.
Note The sAMAccountName is the logon name that is used to support clients and servers from an earlier version of Windows (such as Microsoft Windows NT 4.0 and earlier, Microsoft Windows 95, and Microsoft Windows 98). User accounts in the same dialog box are displayed by using their common name. User accounts appear in the following format: User Name (Alias@domain.com)
Because of this, if the group display name is different from the pre-Windows 2000 group name (the
sAMAccountName
attribute), you may not be able to determine the correct group to apply security permissions to.RESOLUTIONTo resolve this problem, you can install the hotfix that is described in this article. After you install the hotfix, Windows Server 2003 uses the object common name (CN) instead of the sAMAccountName attribute at the start of the line that describes the group. Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesNo prerequisites are required.Restart RequirementYou must restart your computer after you apply this hotfix.Hotfix Replacement InformationThis hotfix does not replace any other hotfixes.File InformationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.Windows Server 2003Date Time Version Size File name ---------------------------------------------------------- 05-May-2003 23:10 5.2.3790.9 114,176 Aclui.dll 26-Apr-2003 22:18 211 Branches.inf 05-May-2003 23:45 10,091 Kb818739.cat 05-May-2003 23:12 354 Updatebr.inf 05-May-2003 23:13 5,043 Update_rtmqfe.inf Windows Server 2003 64-bit EditionDate Time Version Size File name Platform -------------------------------------------------------------------- 05-May-2003 21:56 5.2.3790.9 283,648 Aclui.dll IA-64 05-May-2003 23:10 5.2.3790.9 114,176 Waclui.dll x86 26-Apr-2003 22:03 211 Branches.inf 05-May-2003 23:44 10,444 Kb818739.cat 05-May-2003 23:13 354 Updatebr.inf 05-May-2003 23:13 5,303 Update_rtmqfe.inf STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. | Article Translations
|
Back to the top
