Microsoft KB Archive/302413

From BetaArchive Wiki

Article ID: 302413

Article Last Modified on 7/24/2007



APPLIES TO

  • Microsoft Systems Management Server 2.0 Standard Edition
  • Microsoft Systems Management Server 2.0 Service Pack 1
  • Microsoft Systems Management Server 2.0 Service Pack 2
  • Microsoft Systems Management Server 2.0 Service Pack 3



This article was previously published under Q302413

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


SYMPTOMS

When you use the Systems Management Server Administrator User Wizard to browse for users and groups, no users or groups are listed.

CAUSE

This behavior occurs because an anonymous context is used to request user and group information from the domain, but domain security denies anonymous permissions for user and group information.

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:


The English version of this fix has the file attributes (or later) 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.

  Date         Time   Version        Size     File name     Platform 
  ------------------- -----------------------------------------------
  25-Feb-2003  16:25  2.0.1493.5125  203,968  Sms_musr.dll  X86 
  25-Feb-2003  16:25  2.0.1493.5125  403,728  Sms_musr.dll  Alpha

How to Install the Hotfix Using the Hotfix Installer

Note This method is only for Intel-based computers.

  1. Create a folder in a location that is accessible to your SMS site servers.
  2. Copy the SMS2.0-KB302413-spx-x86-enu.exe update file (where x is the service pack version) and platform folders to the new folder. The folder structure must be arranged so that the update file is located one folder "above" the platform folders.
  3. From each of the primary and secondary SMS site servers and remote SMS Administrator consoles computers in your environment, log on using an account with administrator permissions.
  4. Quit the SMS Administrator console, if it is running.
  5. Run SMS2.0-KB302413-spX-x86-enu.exe, and then follow the instructions in the wizard.

Manual Installation

Manually Update the SMS Site Server

  1. Create a folder in a location that is accessible to your SMS site servers.
  2. Copy the platform folders that contain the hotfixed files to the new folder.
  3. From each of your primary and secondary SMS site servers in your environment, log on to your site server by using an account with administrative privileges.
  4. Quit the SMS administrator console.
  5. Stop all SMS services.
  6. In the SmsRootFolder\bin\Platform folder, run the regsvr32 /u Sms_musr.dll command.
  7. Copy the updated Sms_musr.dll file from the disk or network share to SmsRootFolder\bin\Platform.
  8. In the SmsRootFolder\bin\Platform folder, run the regsvr32 Sms_musr.dll command.
  9. Restart the SMS services.

Manually Update a Remote SMS Administrator Console

  1. Quit the SMS Administrator console, if it is running.
  2. In the SMS_Admin_Root\bin\Platform folder, run the regsvr32 /u Sms_musr.dll command.
  3. Copy the updated Sms_musr.dll file to the SMS_Admin_Root\bin\Platform folder.
  4. In the SMS_Admin_Root\bin\Platform folder, run the regsvr32 Sms_musr.dll command.


WORKAROUND

To work around this issue, turn on anonymous connections. To do this, follow the appropriate set of steps with regard to the domains in question.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

  • For Microsoft Windows NT domains, follow these steps on all domain controllers:
    1. Run Registry Editor (Regedt32.exe).
    2. Navigate to the following registry key:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA

    3. Select the RestrictAnonymous value.
    4. On the Edit menu, click Delete.
    5. Quit the Registry Editor, and then restart the computer.
  • For Windows 2000 domains, follow these steps:
    1. On a domain controller, add the Everyone group to the Pre-Windows 2000 Compatible Access group. This must be done from the following command line:

      net localgroup "Pre-Windows 2000 Compatible Access" everyone /add

    2. Ensure that the Default Domain Policy under Computer|Configuration|WindowsSettings|Local Policies|Security Options|"Additional restrictions for anonymous connections" is set to one of the following:
      • Not defined
      • None. Rely on default permissions
      • Do not allow enumeration of SAM accounts and shares

      NOTE: You may have custom policies enforcing the anonymous setting. If so, you need to modify the respective group policy.

    3. Ensure that the Pre-Windows 2000 Compatible Access group has permissions by resetting permissions using Dsacls.exe from the support directory on the Windows 2000 CD-ROM:

      dsacls DC=MICROSOFT,DC=COM /I:T /G "BUILTIN\Pre-Windows 2000 Compatible Access":LC

      dsacls cn=server,cn=system,dc=MICROSOFT,dc=com /G "BUILTIN\Pre-Windows 2000 Compatible Access":RP

      NOTE: The preceding example uses MICROSOFT as the domain name; please change this name to reflect the correct domain.


STATUS

Microsoft has confirmed this to be a problem in Systems Management Server version 2.0.

MORE INFORMATION

For additional information about the RestrictAnonymous setting, click the article number below to view the article in the Microsoft Knowledge Base:

143474 Restricting Information Available to Anonymous Logon Users



Additional query words: prodsms

Keywords: kbqfe kbhotfixserver kbbug kbenv kbui KB302413