SMS Implementation

[kirtv]

We're implementing SMS in our Network that uses Novell for authentication. Our workstations do not belong to a domain. We use a VLAN infrastructure. SMS Server in a domain. Bounderies have been setup. Network Discovery has been turned on. Logon discovery turned on. Role of SMS Server does not include Logon Point Role. SMSman cannot find the logon point. Is there a way to add this role to the server? Is it something I should of checked when I installed SMS? Any assistance would be appreciated.

Thanks.

Kirt

 

[ceigl]

Kirt,
only DCs can become LogonPoints by enabling the appropiate method.

Cheers,
Chris

 

[kirtv]

Thanks for the feedback. Does this mean that all of the discovery machines need to be members of the domain?

Thanks,
Kirt

 

[ceigl]

No, the machines (SMS-clients) do not be members of a domain but you need one DC who functions as a LogonPoint.

 

[kirtv]

Thanks.

How do I get my DC to assume that role? This is where my challenge is.

Kirt

 

[ceigl]

Hope this helps you out:
___
Defining Logon Points
Because logon discovery methods discover computers when they log on to the network, you must specify where on the network you want to discover computers. You do this by specifying a set of logon points. A logon point is a Windows NT domain controller, NetWare NDS container and volume, or NetWare bindery server against which users verify logon scripts. You modify the logon scripts on these logon points to initiate the discovery process. Then, when users log on to these logon points, their computers are discovered.

To specify logon points, navigate to Discovery Methods in the SMS Administrator console:

Systems Management Server
-Site Database (site code - site name)
--Site Hierarchy
---site code - site name
----Site Settings
-----Discovery Methods

In the details pane, right-click the discovery method you want to configure and then select Properties. On the General tab, click New. In the New Logon Point dialog box, specify the identity of the domain, container and volume, or bindery server to use as a logon point.

When you specify a Windows NT domain, SMS installs all domain controllers in the domain as logon points. When a server or volume becomes a logon point, it becomes a site system with the logon point role and appears under Site Systems in the SMS Administrator console.

The logon discovery methods are each paired with an equivalent client installation method (Windows Networking Client Installation, NetWare NDS Client Installation, or NetWare Bindery Client Installation). If you have enabled both the discovery and installation methods, you can also choose to keep the lists of logon points for discovery and installation synchronized. With this approach, changes to the logon points for the discovery method will be reflected in the list of logon points for the client installation method and vice versa. As a result, you can be sure that you are using the same set of logon points for both discovery and installation.
___

for more information got to:

http://www.microsoft.com/technet/tr...technol/sms/proddocs/smsadm/part2/smsad09.asp

and then scroll down a bit

Cheers,
Chris

 

[kirtv]

I finally resolved the logon point issue. But why doesn't the client install when I run SMSMan.exe from the logon point? It says when it finishes that everything installed successfully. The workstation was discovered and shows in the collections area with a "no" on client installed. What am I missing?

Need help.

Thanks.
Kirt

 

[ceigl]

Kirt,
it seems that you did not set up the boundaries to match your settings....Take a look at the settings for "Network Discovery" and for the boundaries directly in the properties of your Site.

Cheers,
Chris

 

[kirtv]

We use a VLAN infrastructure here. I'm wondering if this may be part of the problem. My boundries are set to the IP address of that VLAN as well as the IP address the SMS server and logon points sit in. I'm able to discover ok, but the client won't show as being installed. Do you know of any good documentation on SMS?

Thanks.
Kirt