Client assigned but not installed...sort of

[Hankejp]

Okay, there's probably 50 million of these threads out there, but here it goes:

I have count of 1700 machines with the client installed (SMS2003). All of them are assigned, but not all of them have the client installed. For example in one room with about 20 machines, one will be installed, but the computer right next to it won't have the client installed. Does anyone know what might be causing this problem? I look in the control panel and it show that everything is there (SIte Name, Site code, etc.) Bits is installed on the computers as well.

Thanks for the help

 

[SKent]

I have a similar situation going on ... I have computers that have all the pieces installed and the site update is current and they do not show up in any collection tree ... some do and some don't .. I would be interested in anything that you might find on this ..

Thanks

 

[NoWittyName]

With reference to the first post, are you saying that the SMS client is installed i.e. the icons are there but the components are not installed.

If this is the case then check on the server under site hierarchy->site name->site settings->client agents that the agents are turned on.

Master of Disaster.....Recovery

 

[Hankejp]

CantThink...

Yeah it's showing that the Client is installed and assigned. The icons (Run Advertised, Program Download, Systems mgmt, etc.) are all there. I checked the client agent like you said and they are all turned on. They should be, like I said in the previous post. I can have 2 computers in the same room, going through the same switch, and 1 computer will have the client installed and the other one won't. One thing I have noticed is that pretty much all the computers that don't have the client installed, when you click on the computer in the collections and go to the properties. It seems that where it says Agent Name(0), they all have SMS_Network_discovery listed there. The computers that have the client installed don't have that first. Just something I noticed.

 

[NoWittyName]

OK,

I have never seen this, but to investigate further I would turn off network discovery and only discover via AD (thats how mine is setup) then I would remove the bad clients using the SMS2003 toolkit (can be downloaded from M$), rediscover, and reinstall. Don't be too quick with SMS it can take ages to do stuff as its all interlinked on time delays.

As I say don't know if it would work but appears to be the most logical next investigatory step to me.

If you can get hold of a test lab then this is best. Its well worth getting hold of 3-4 PCs and a hub to form a mini network just to test these things out - I now hardly touch our network as all the fiddling and experimenting is done on the test servers

Good luck!



Master of Disaster.....Recovery

 

[SKent]

well I am running SMS 2.0 not 2003 ... so I don't have AD running and the kit would be of no use ... thanks for the input though .. it may help others ..

Steve