Client Installation Problem

[taoweijia]

Hi there,
Only half of the systems are installed with SMS client. I enabled Networking Logon client Install and windows NT remote client install, however, since I don't want to screw up anything, I didn't enable that modify logon script option so i think the network logon client installation is not working . I tried SMSMAN.exe /A /Q but still half of the clients not installed. and they are all up and running.
what could be wrong? I didn't patch it up yet it is still running SP2.
Thanks
Jeff

 

[snyderj]

Check wnmanual.log on the clients that have run smsman. It should give some indication of what's happening. Look for "Client is assigned to 1 site(s)" and "Verified launch32 event exists - user launcher appears to be running"

If the above are true then check launch32 and clisvc for additional information.

 

[sambusa]

hi all
pls brother what u want us to check on lunche32 and clisvc,u want us to see if it exist , or what pls explain to us to understand this problem because all people facing it .


thanks in advanced

 

[taoweijia]

in the simple way, what could cause systems not to install clients? they are all running win2k and winNT. security problem? service problem? the number of systems without SMS client is many, it is not convenient to walk over to each of them to check, would that be server related issue?
thanks

 

[snyderj]

If you're an admin on the remote device then you could just do a start > run to the UNC (e.g. \\computername\c$ ). Just checking a the logs on a couple devices should be enough.

Some reasons for client not installing:
- not in site boundaries
- security settings
- exising bad SMS installation or not full uninstallation
- lack registry permissions for user (can't create or modify hklm\sofware\microsoft\sms)
- exising %windir%\ms folder
- slow network connection