Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WMI is not installed on NT4

Status
Not open for further replies.

Rasslor

Technical User
Dec 13, 2000
52
US
I am trying to install SMS for the first time and everything seems to work fine except for 2 servers that are part of the domain, but they log on locally to work with these machines. It was a manual installation on the machines. The client installation appears to have run properly, but under systems management we get an error saying "SMS client base components not available". Network discovery is enabled and nt remote client is enabled. The servers are within the subnet boundaries, the machines are discovered and network discovery assigns them to the site. The only thing that I've noticed that is diffrent from the servers that work properly is WMI is not a service on the two non working servers. I'm pretty sure this is supposed to be installed during the SMS client installation, and maybe I'm not looking in the right place but I can't find anything that says it failed the installation of WMI. Any help that could be given on this situation is greatly appreciated.

Thanks
Brendan
brendan_conway@hotmail.com
 
I would check the c:\WinNT\MS\SMS\LOGS directory on the problematic servers. Take a look at the CCIM32, CliCore, CLiSVC, and SMSlci logs... at first perform a search for ERROR..then just read the logs.

Also verify that the Admin$ share is there. Without this share being avaible, SMS can not install the client.

I had a problem that sounds similar to this. In my case, I knew the servers were in the proper subnet; however, after running the SMS installation many times, I noticed that the server didn't think it belonged to a site. Check Control Panel- Systems Manangement -> Site Tab Is your site listed here?

In my case, the server did not know what site it belonged to even though it was in the proper site. I eventually called Microsoft. They advised me to remove the TCP/IP stack and remove the NIC logically. Reboot and reinstall the NIC and TCP/IP. After doing this, the client installed without any problems.

---hope this helps.

Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top