Microsoft KB Archive/328358

= SMS Network Discovery Does Not Detect the Operating System If the &quot;RestrictAnonymous=1&quot; Setting Is Being Used =

Article ID: 328358

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
 * Microsoft Systems Management Server 2.0 Service Pack 4

-



This article was previously published under Q328358



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
Network Discovery does not discover the operating system and version information from client computers that have implemented a  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 :

ADM: NtBrowser: New name  found on domain.

ADM: DNS: Name  resolved to address.

ADM: NtBrowser: New name  found on domain.

ADM: NtBrowser: Starting to talk to Device :

ADM: NtBrowser: Failed to retrieve OS info from device  due to insufficient access.



RESOLUTION
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:

http://go.microsoft.com/?linkid=6294451

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:

http://support.microsoft.com/contactus/?ws=support

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.



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



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:

Value:  (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.
 * 1) 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.
 * 2) Log on to your site server by using an account with administrator permissions.
 * 3) On the site server, quit the SMS Administrator console (if it is running).
 * 4) 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

 * 1) Stop the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services on the site server, and then quit the SMS Administrator console.
 * 2) Copy the updated Ad_adm.dll file to the  \Bin\  folder.
 * 3) Copy the updated Ad_cntrl.dll file to the  \Bin\  folder.
 * 4) Copy the updated Ad_sim.dll file to the  \Bin\  folder.
 * 5) Copy the updated Ad_utils.dll file to the  \Bin\  folder.
 * 6) Copy the updated Netdisc.dll file to the  \Bin\  folder.
 * 7) Restart the SMS_SITE_COMPONENT_MANAGER and SMS_EXECUTIVE services.

Keywords: kbhotfixserver kbqfe kbsms200presp5fix kbbug kbfix KB328358

-

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

© Microsoft Corporation. All rights reserved.