Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clients fail to auto discover site

Status
Not open for further replies.
iamwiz82

iamwiz82

IS-IT--Management
Feb 12, 2002
27
0
0
Important stuff:
SMS 2003
Windows NT domain
Windows 2000 workstations

Now my question:
I am having a hard time figuring out what is wrong with my SMS 2003 setup that clients will not automatically discover my site. If i push a client out, it installs, but it never assigns to the site as a client. If I go to the workstation and try to automatically discover the site, i get the following error:

automatic site code discovery was unsuccessful

If I type in my site code manually it works fine. I believe the site boundaries are fine, because in my collection I can see that all of the workstations are assigned to the site, but are not clients. I have also added SMS_SLP to my WINS database but for some reason it is showing up as SMS_SLP[0ah] instead of SMS_SLP[1ah]. Could this be the issue?

I originally had the clients set to auto discover the site using SMSSITECODE=AUTO. I have since tried SMSSITECODE=XXX but that also does not work.

Any suggestions? What am I missing?
 
Sort by date Sort by votes
Have you tried a manual install to see if that works?

A couple of things to check, is your server set up as a management point? Does your install client have proper rights?
 
Upvote 0 Downvote
The same server is MP, SLP, DP, CAP, and RP, since this is a test environment. Are you referring to the Client Installer account? If so, yes it has the proper rights.
 
Upvote 0 Downvote
No, if i run an manual install from the client machine, it will not work because it cannot find the site.

If i push out the install manually and then run over to the machine and type in the site code it works fine. Legacy installs work fine so I am almost positive it has to do with something wrong with WINS, but I am unsure of what.
 
Upvote 0 Downvote
Just an update:

If I install the legacy client on a machine and then remotely send out the advanced client it looks like the install works. Strange.
 
Upvote 0 Downvote
AUTO checks site assignment by using AD or server locator points. Since your not using AD we're left with SLP. You've got your server set up as a SLP, so that shouldn't be a problem.

Hmmm, time to dig through some logs. Look at the ccm.log on your server. Also, look at a ccmsetup.log on a client that didn't install correctly.

Try some of the command-line options available for ccmsetup. In particular look at /mp, ccmenablelogging, and ccmdebuglogging.

Starting to run out of ideas here.
 
Upvote 0 Downvote
Interesting, there were no issues in the ccmexec.log but I did find a problem in ClientLocation.log. Here is a portion of it:


-----------
Failed to resolve IP address from WINS

No NLB default management point is present, attempting to resolve default management point from WINS

Retrieved Default Management Point through WINS: 10.40.4.4 (this is the correct address)

Site Code is RHS; Management Point is 10.40.4.4 (correct again)

Setting Current Management Point

Management Point is 10.40.4.4

Failed to resolve IP address from WINS
---------------


This loops over and over again. So it is failing in WINS, but then picks it up and fails again. Strange....

 
Upvote 0 Downvote
Try 'ccmsetup.exe /mp:rhs' (I think that is the right format) and see what the log says then.
 
Upvote 0 Downvote
Alright, I ran ccmsetup.exe /mp:RHPROD07 (the name of the server) and I got the same results. It HAS to be something with WINS, but I do not know what.
 
Upvote 0 Downvote
Try adding an entry for this server to a clients lmhosts file. Not very pratical for large scale roll out, but might help in determining if it's a resolution problem.
 
Upvote 0 Downvote
I have the same problem and I fixed it by setting the site name in the Client Push Installation properties under Advanced client you can set the site name
SMSSITECODE=putyoursitenameinhere

That will make sure that every advanced client has the sitename when you push it out to the pc's

Kim
 
Upvote 0 Downvote
I tried adding the server into the LMHOSTS file with no luck. The setting for SMSSITECODE is already set to my site code. They still do not get picked up by the server.
 
Upvote 0 Downvote
To manually add the server locator point entry to WINS
At the command prompt, type netsh, and then press ENTER.
Type wins, and then press ENTER.
Type server, and then press ENTER. To manage a remote WINS server, type server [\\servername or XXX.XXX.XXX.XXX].
Type the appropriate command, as in the following example:
add name Name=SMS_SLP endchar=1A rectype=0 ip={static IP of your SLP}

To verify that the server locator point WINS entry was added correctly
At the command prompt, type netsh, and then press ENTER.
Type wins, and then press ENTER.
Type server, and then press ENTER. To manage a remote WINS server, type server [\\servername or XXX.XXX.XXX.XXX].
Type the appropriate command, as in the following example:
show Name name=SMS_SLP endchar=1A
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

ihcc2uni
  • Locked
  • Question
SCCM 2012 Clients not reporting ball all installed software (SCEP)
Replies
1
Views
66
ihcc2uni
ihcc2uni
Imashe
  • Locked
  • Question
SMS 2003 Move Clients New Primary Site
Replies
1
Views
52
SimonDavies
SimonDavies
rebel4k
  • Locked
  • Question
Unable to install SMS Clients
Replies
3
Views
73
mrmovie
mrmovie
shiva2golu
  • Locked
  • Question
Package distribution from DP to Clients
Replies
4
Views
68
Jpoandl
Jpoandl
dbsnole
  • Locked
  • Question
Driver discovery
Replies
0
Views
48
dbsnole
dbsnole

Part and Inventory Search

Sponsor

Back
Top