SMS Client Installs 3

[ulio]

We recently installed SMS with one Site server and about 700 clients. SMS has been having no problems discovering resources, however, it is having a problem installing the client base components on about 1/3 of our W2K and NT workstations. Within the admin console under "All Systems" Collections about a third of the workstations show Assigned=Yes and Client=No. When you look at the client's SMS properties (Components Tab) in Control Panel it shows a status of "Not available" for Client base components with no optional components listed as well. The Site tab shows the Site server name, however, there is no "Last Updated" date. No results when you hit the update configuration or repair installation.

Here's some additional info:

IP Boundries are correct
Windows Networking logon client Installation is enabled

I've reviewed the logs and here's a few line entries I've found:

CCIM32.Log - Base setup status value not set to Installed.

Clicore.Log - Insatll aborted

Launch32.log - Eitehr GetMUILanguage not returning True, or MUI is not detected enabled

Wn_Logon.log - Checking property Client, value="0"; Checking property client version, value=""

Any help would be greatly appreciated. I've search the microsoft sucks, I mean Microsoft knowledge base with no success. Please HELP!!!! I'm going CRAZY

 

[Depdiver]

What SMS Service pack are your running? we were ready to give up on SMS on XP machines until SP5 came out. Is there anything unique between the machines that work and machines that don't? Is the server service running on these machines?

 

[ulio]

We're running SP5. I've only been able to get to one client which is a W2K machine. The server service and workstation service are both running. File and Print sharing is enabled too. The SMS Service account has been added to the local administrators group too. I've spent about a week so far trying to resolve this. I'll start checking other client logs to see if I can find some "Uniqueness"- Thank you for your reply.

 

[asianchic]

I've the same issue...right now, i'm in the process of configuring new pc's to roll out. so far, 1 out of 3 picks up the SMS client install...there doesn't seem to be any sort of uniformity. As for the rest of the PC's on the floor, I've encountered 2 this morning that has everything marked as installed in the control panel except for the SMS base client...that is marked with version pending, and repair pending. i am unable to update the site, though it seems that they were able to update at some point (the most recent date on the 2 pc's is 8/29/2003)

can any shed some light?

 

[manji]

Hello guys,

I have exactly the same pb! (SMS 2.0 SP5)

"Within the admin console under "All Systems" Collections about a third of the workstations show Assigned=Yes and Client=No. When you look at the client's SMS properties (Components Tab) in Control Panel it shows a status of "Not available" for Client base components with no optional components listed as well"

I seach deeply into the MSKB with no result...

Fortunately I have this problem on only one machine running Windows XP SP1
My othe Win98se machines are all ok
one other XP machine also installed ok

Please halp I try everything I read on this forum and on MSKB, nothing helped.

I see this is a quite common issue on SMS 2.0 SP5, why no one has a solution?

Thanks In Advance!

 

[RodTrent]

Not necessarily a common issue to SP5, but generally a common issue for Windows XP and Windows 2000 computers where local policy is overiding domain policy. Check the local computer policies and make sure there's nothing wrong there.

The problem is generally that local policies have put restrictions on the SMS registry keys. You have to take ownership and set the keys' right appropriately. Here's a utility you can try on a computer to see if its a registry permission problem:

http://www.myitforum.com/inc/upload/8131SetSMSRegPermsv3.zip

Rod Trent
Microsoft.MVP.SMS
=======================================
Main site:

http://www.myITforum.com

=======================================

 

[SKent]

Could someone please explain what the local and server domain policies are suppose to look like .. I have downloaded this registery checker and it doesn't seem to help. I still have the exact problems and all my machine clients are Windows 2000 ... I believe my boundaries are correct. My designed diagram shows my subnet servers as login points but there doesn's show a connection between my subnets and the site server ... Thanks ...

 

[evz]

The SetSMSRegPerms utility has worked a treat. Just out of interest is it possible to let me know how on earth this worked, and what keys it does modify permissions on.

I was previously experiencing the problem where I could not take ownership of the NAL and SMS Keys using Regedt32 and Regedit in the normal fashion, but as soon as I used this utility everything worked without any problems at all.

Thank YOu

 

[helidoc]

Funny enough i had the same problem too.Did alot of research and resolved my issues slowly .

here is an interesting article by wally mead on trouble shooting client installation.

http://support.microsoft.com/default.aspx?scid=kb;en-us;815336&Product=SMS200

And again here with network discovery.

http://support.microsoft.com/default.aspx?scid=kb;en-us;325255&Product=SMS200

These may prove usefull .They did for me.

 

[SKent]

Thanks everyone ... I took a look at the webcast above and low and behold there were some setting in the boundary that weren't correct ... the key was to having to put the subnet masks in the boundary. Now and I can move on to my other problems .. like connections to my SQL server ....

 

[solomond]

Greetings,
There is some good information here. I work in and environment that is running Active Directory and have been creating a new ghost install on a Windows 2000 OS. My SMS client has installed but then quits working. I beleive it is a policy issue that was suggested in one of the feeds. I downloaded the tool that RodTrent posted, but it is for Win XP. Does anyone have the a previous version of this utility, or can you tell me exactly which keys are affected. I am aware of three of them in HKLM.

Thanks,
Dave S.