SMS Network Discovery Does Not Detect the Operating System If the "RestrictAnonymous=1" Setting Is Being Used (328358)

SYMPTOMS

Network Discovery does not discover the operating system and version information from client computers that have implemented a RestrictAnonymous setting of 1. For additional information about the RestrictAnonymous setting, click the following article number to view the article in the Microsoft Knowledge Base:

246261 How to Use the RestrictAnonymous Registry Value in Windows 2000

For example, the Netdisc.log file contains entries that are similar to these for a client named ComputerName:

ADM: NtBrowser: New name ComputerName found on domain DomainName.
ADM: DNS: Name ComputerName resolved to address IP Address.

ADM: NtBrowser: New name ComputerName found on domain DomainName.
ADM: NtBrowser: Starting to talk to Device ComputerName:
ADM: NtBrowser: Failed to retrieve OS info from device ComputerName due to insufficient access.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server service pack that contains this hotfix.

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/contactus/?ws=support

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 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
   ------------------------------------------------------------------
   01-May-2002  14:20  2.0.1493.4132  204,048  Ad_adm.dll    Alpha
   01-May-2002  14:20  2.0.1493.4132  125,712  Ad_cntrl.dll  Alpha
   01-May-2002  14:20  2.0.1493.4132  125,200  Ad_sim.dll    Alpha
   01-May-2002  14:20  2.0.1493.4132  347,408  Ad_utils.dll  Alpha
   01-May-2002  14:20  2.0.1493.4132   77,584  Netdisc.dll   Alpha
   01-May-2002  14:20  2.0.1493.4132  120,672  Ad_adm.dll    x86
   01-May-2002  14:20  2.0.1493.4132   69,440  Ad_cntrl.dll  x86
   01-May-2002  14:20  2.0.1493.4132   76,128  Ad_sim.dll    x86
   01-May-2002  14:20  2.0.1493.4132  205,776  Ad_utils.dll  x86
   01-May-2002  14:20  2.0.1493.4132   48,112  Netdisc.dll   x86

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

MORE INFORMATION

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.

To use this fix, you must add the following registry key to each site server from which Network Discovery runs. This registry change modifies the account credentials under which Network Discovery tries to connect to the clients. The account credentials are changed from using a null account to using Network Abstraction Layer (NAL) to make sure that the account credentials used have appropriate permissions. When using NAL, Network Discovery will first try the SMS site system connection accounts, and then finally the SMS service account. Add the following value and set its data value to 1:

Key: HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Components\AutoDiscovery
Value: DisableNullSessions (REG_DWORD)
Data value: 1

To Install the Hotfix

To install the hotfix, use either of the following methods.

Using the Hotfix Installer

Note This method works on only Intel-based computers.

Copy the hotfix folder structure to a share on your network. The Q328358.exe file is a Microsoft Windows Installer file that updates specific files on your site server.
Log on to your site server by using an account with administrator permissions.
On the site server, quit the SMS Administrator console (if it is running).
Start Q328358.exe, and the follow the instructions in the wizard. You can run the program in Quiet mode by using the /s switch.

Using a Manual Installation

Stop the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services on the site server, and then quit the SMS Administrator console.
Copy the updated Ad_adm.dll file to the Sms_root_folder\Bin\Platform folder.
Copy the updated Ad_cntrl.dll file to the Sms_root_folder\Bin\Platform folder.
Copy the updated Ad_sim.dll file to the Sms_root_folder\Bin\Platform folder.
Copy the updated Ad_utils.dll file to the Sms_root_folder\Bin\Platform folder.
Copy the updated Netdisc.dll file to the Sms_root_folder\Bin\Platform folder.
Restart the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services.