Logon point not specified?

[Guest_imported]

I've just createed a test lab with following:
SMS site on Win2k, SQL2k
PDC nt4sp5
bdc nt4sp5
client win2ksp2
client nt4sp5
client win98se
client win95

Now, one problem is SMS has not specified a logon point, from what I understand is it should list my PDC under site systems as a logon point. I can add it manually but not specify it as a logon point (no option).
Secondly, my 98 + 95 clients do not receive the components I've specified, just the base. When I look in control panel under system management I see nothing under the components tab. Any help would be appreciated.

 

[Jpoandl]

In Site Settings, you have to define your site. Choose how the client should get installed on each client machine... For example, Remote Control configurations (Beep on remote control initiation, Show connections icon, etc.) After you do this, you should see more components show up on the client machines.

For Logon points, you have to enable this in Site Settings too. Once you enable Networking Logon Discovery, you will see the SMSLS.bat show up in the Netlogon directory of you DC.(Check off "Keep logon point lists for discovery and installation synchronized" and add your domain. I would suggest NOT to modify logon scripts unless you don;t already have logon scripts in your domain.

Many people have problem setting up the SITE BOUNDARIES. You have to consider that the SUBNETs that define your site, will always use the client SUBNET MASK. Here's an example:

Say your everyone subnet starts with 10.x.x.x You might think that this is a class A address scheme. However, all clients are configured with a 255.255.0.0 subnet mask. Therefore, if you were to put 10.0.0.0 in your site boundaries, you would only pick up the client in the 10.0.x.x subnet...eventhough you have clients in the 10.1.0.0, 10.2.0.0, 10.3.0.0, 10.4.0.0...etc. Unfortunately, in the scenerio, you will have place all of your subnets into your SITE BOUNDARIES (10.0.0.0, 10.1.0.0, 10.2.0.0, 10.3.0.0, 10.4.0.0...etc)

Check your boundaries...this is the most common mistake. Also, check you schedule for network discovery...make sure that it has already tried to run. If not, schedule network discovery to run for a few hours...

Your clients should start appearing under COLLECTIONS...

-hope this helps. Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.esavio.com