SMS Client Not Being Installed?

[delorca]

Hello There,

Can anyone help with a question i have about SMS client installs.

Currently i use SMS 2.0 SP5 and have one Primary Site feeding two Secondary Sites.

Although, i believe, that i have set up the boundary ip subnets ok on the primary site i have arround 8 laptops that see their site code as the secondary site?

Although i can easily see these laptops being discovered, Assigned = Yes, i cannot get the clients installed on them, Client = No.

Does anyone have any suggestions on what i can try to get the rogue laptops on the correct site and then get the client installed on them.

All other PC's are all ok for site code and client and this is what makes this one difficult for me to solve.

Any help would be greatly appreiated.

Many Thanks,

Del...

 

[wellsnet]

The best way I know to troubleshoot client installs is to grab the client logs during the installs. Often, when the client fails to install, it begins, writes an install log (wn_logon.log or other) and at some point a ccim32.log. I have found these the best 2 logs for troubleshooting installs, although others help also. The logs will tell you what the client software thinks is the problem. You can compare these against a working client also. Hope this helps.

 

[mojo31]

We had a similar problem here, and we found out in the end it was down to environment variable strings fro the command prompt beeing incorrect-thus a batch script(smsls.bat) wouldnt run, but the net discovery see's them because they are on the subnet defined in the site boundaries.