SMS-Client is installed but appears as not installed 1

[GerhardR]

Hi!

Some computers have the SMS client installed - but in the sms admin console the clients are appearing as not installed.

I checked all the logfiles - no errors. I can connect to the computers and look at the "systems management" in the control panel - everything seems to be allright.
I also had a look at the MS-FAQs and did some MP-testing - it also seems fine.
On the clients I performed all the actions (machine policy retrieval etc.) without any luck. WMI also seems to work fine.

Any suggestions why the computers not reporting as "client installed"? I am talking just about 20 computers which have this problem out of 550.
Maybe this helps: One of them works - the others are "clones" (made with Ghost).

Any suggestions? What can I check/do now?

Thanks in advance!
Gerhard

 

[ncotton]

Right click on the All Systems collection in the resource tree on the left, i think Actions > Update Collection Memberships, check the box that ask if you wish to update sub collections. Press ok. Click inside the collection window on the right and press F5. You're clients wont show up as installed straight away cause that would just be to easy. I take it you have hardware inventory configured to run. Just to check the installation. Go onto one of the clients, open Control Panel > Systems Management > Actions, highlight and run :
Discovery Data Collection Cycle
Users Policy Retrieval Cycle
Machine Policy Retrieval Cycle

wait about 5/10 minutes. Go back on to your SMS Admin Console. And rerun the steps at the top. Update the collection, and refresh the collection pane display view.
Note, before refreshing, make sure you select the actual collection pane view (the bit with the machines listed, NOT the collections tree), and then hit refresh, otherwise it may just refresh the collections tree, which wont have changed.

Hope this helps

Neil J Cotton
njc Information Systems
Systems Consultant

 

[GerhardR]

Hi!

Thank you for your quick response. Hardware inventory is configured to run (Simple Shedule - once per day). I performed some days ago a
Discovery Data Collection Cycle, a Users Policy Retrieval Cycle and a Machine Policy Retrieval Cycle. And afterwards I updated the collection membership (and later F5). Nothing changes so far. But I will try again.

I think that it maybe is a problem with the registry because the 20 computers are cloned (with the software "ghost").
Now I perform the actions and write in 20minutes back.

Thank you.

 

[GerhardR]

I think I know now what the problem is:

I compared two clients - they have the same SMS Unique ID!

Now I have to find a way to change the IDs...

I am searching - so far I found a registry key:
HKLM\Software\Microsoft\SMS\Client\Configuration\Client Properties\SMS Unique Identifier

Will write back with news...

 

[ncotton]

yeah, if you cloned the machines with SMS installed, then you will get that problem.

Rather than modify this, go back to your Admin console, and do a manual push installationg from the collection list onto these machines, when it asks you your client type, make sure you select "Always install or repair", this should overwrite the old IDs. Then do your refreshes.

If that doesn't work, download the SMS 2003 Toolkit 2 from MS, stick the CCMClean.exe on a share, then run in on each client, this will remove the SMS Client agent from the client machine, then either push, or let heartbeat/client install do its job.

DONT MESS WITH THE REGISTRY UNLESS YOU HAVETO. Especially when it concernes GUIDs.

Hope this helps

Neil J Cotton
njc Information Systems
Systems Consultant

 

[GerhardR]

Hi!

A manual client push installation with "always install" definitely does not overwrite the old IDs.

I try it now with ccmclean.exe and a reinstallation of the client.

Thanks for you help!

 

[ncotton]

Let us know how it goes

Hope this helps

Neil J Cotton
njc Information Systems
Systems Consultant

 

[GerhardR]

Hi!

GOT IT!

Way it works best:

1.) uninstall the client (ccmclean works fine)
2.) delete the file smscfg.ini in the windows folder
3.) reinstall the client

You have to delete the smscfg.ini! Otherwise after reinstalling the client you'll have the same old problem...

Ok - I have now some work to do... ;-)

Thanks for help Neil!
Gerhard

 

[ncotton]

Don't thank me, pay me. You know how...you have the acocunt

Hope this helps

Neil J Cotton
njc Information Systems
Systems Consultant

 

[GerhardR]

if you ever visit austria - drop me a line. at least one beer for free! ;-)

 

[ncotton]

hehehe....I dont drink beer, in fact, I don't drink alcohol.

I accept payment in cash, credit, musical instruments, forum votes, squiral nests, and at a push...cheques.

It's gone very quiet in here over hte last few months. Everyone furiously reading up on pre-release material for SMS v4.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[ncotton]

Hehehee....found another tool that would have sorted this for you.

Again, in the same place as the CCMClean.exe on the SMS 2003 Toolkit 2 is a program called TranGUID.exe, which would have done exactly what you needed. Sorry, never really looked on in the toolkit to see whats there, just looked for what I wanted so only just come across this. I had the same problem as you before Toolkit 2 was released.



Peace

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[GerhardR]

Hi!

Cool - found it too... I will check it next time (because we'll keep on cloning cause I know now what do do... ).

Take care!
Gerhard