FAQShop.com : Clients discovered and assigned to a site but client software not installed

Clients discovered and assigned to a site but client software not installed

I have been receiving the following error message for several NT workstations that are physically located in a separate building. Their subnet is within the site boundaries of our SMS 2.0 SP2 site and we do not have any Secondary sites. I have tried numerous times to run the 20clicln.bat file, double checking for folders, SMS-related files, and the registry too.

We run Network Discovery, enabling "Topology, Client and Client operating systems" every night at 10pm and have enabled "Windows NT Remote Client Installation" for NT Workstations. My dilemma lies in the fact that these machines actually get discovered every night, but they just don't get the software installed. (We also run hardware and software inventory at 10pm and 10:30pm).

"CDiscoverDataManager::FilterDDR - Will not create CCR. This resource is already installed
at this site. $$<SMS_DISCOVERY_DATA_MANAGER><Wed Jan 10 22:46:13.828 2001 Central Standard Time><thread=326 (0x146)>"

This error message seems to be a very generic one and covers a variety of problems including this problem and others such as the Clients missing from the database problem.

This particular problem can occur if you've modified the:

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA"

Registry key and added "RestrictAnonymous" with a value of "1". Adding this key into the Registry stops anonymous logon users from being able to list domain user names and enumerate share names (see 143474 "Restricting Information Available to Anonymous Logon Users" for further information on this Registry key).

Setting this Registry key causes problems for SMS as the NT Remote Client Installation does not work at all as Network Discovery sees the client as a "device" and therefore can't discover the OS type (it appears as "NULL"). As a result the DDR is incomplete and cannot be used for Remote Client installation (i.e. the installation will never start). This limits the client discovery process to Logon Discovery only.

If you need to remove/change the value of this Registry key on any of your workstations you'll need to reboot them after the change.