Windows NT Machine not discovered in collection

[Aek]

I just have 4 machines in the lab that I am testing.

Domain controller - Windows 2000 + AD. (Static IP)(Also a DHCP server)
Member Server - Windows 2003 + SMS Server. (Static IP)
Member Server - Windows 2003 + SQL 2000. (Static IP)
Nt Workstation Sp6a - DHCP Assigned

The IP of all machines start with 192.168.10.x
and the subnet on all is 255.255.255.0

I have added 192.168.10.0 in the site boundary. I have also added the lab domain in the discovery options.

I updated the collection membership and in the collection I am seeing NO under assign for the DC and the NT machine.

Now - 1) Why would it not assign the site to NT Machine and the Domain Controller? (I checked the RPC Service and the SL, DP, CAP all are setup and running fine)

2) If SMS 2003 does not assign these 2 machines to the site, how can I install the SMS Client on these machines?

Should I just run the smsman.exe file with the /F option (to force the client installtion) on these machines?

Thanks

Aek

 

[tbrennans]

well if they were discovered by AD only then the nt wouldnt install a client unless you assigned it to a collection and pushed one out to it....the DC i'm not sure...

 

[Jpoandl]

Did you enable the Legacy Client in your SMS 2003 site? The SMS 2003 Advanced client can not be installed on your Windows NT 4.0 machines.

Try enabling the Legacy client. (Although, this totally messes up your security. In a prestine Advanced Security mode using only the Advanced clients, you will have a much higher level of security protection.)



Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)