Microsoft KB Archive/886053

= Two user or user group entries exist on a Systems Management Server 2003 central site after you create one user or user group with a double-byte character set (DBCS) name on the domain controller =

Article ID: 886053

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-





SYMPTOMS
You have installed the English edition of Microsoft Systems Management Server 2003 on a parent site and the Japanese edition of SMS 2003 on a child site. Both sites are in the same domain. When you try to create a user or a user group with a double-byte character set (DBCS) name on the domain controller, two new entries may appear in the All Users or All User Groups collections on the central site that is running the English edition of SMS 2003. These entries appear if you have enabled the Windows User Account Discovery or Windows User Group Discovery features on the parent site and on the child site.



CAUSE
This problem occurs because the Windows User Account Discovery and Windows User Group Discovery features in the English edition of SMS 2003 do not support Unicode. Therefore, the discovery functions could not obtain the correct string for those names that contain the DBCS characters, such as Chinese, Japanese, or Korean names.

Additionally, there may be two entries for each user or for each user group on the central site. One entry appears as &quot;???&quot; and is discovered by the parent site that is running the English edition of SMS 2003. The other entry appears with the correct name if you have installed Asian language support on the parent site. The second entry is discovered by the Japanese language edition child site. Therefore, the SMS 2003 central site server treats these entries as different users or different user groups and will not merge the data.



WORKAROUND
To work around this problem, create the user or the user group in English, or install a localized version of SMS 2003 on the central site.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

