After Custom setup is run on a site server, only a few features are enabled. The first task is to configure site boundaries. Site boundaries are the IPX networks and TCP/IP subnets that are considered within the scope of the site. After site boundaries are assigned, resource discovery methods are enabled. Using these discovery methods, SMS finds resources (hardware, user accounts, and user groups) within the site boundaries and assigns these discovered resources to collections. It is also common to distribute SMS roles to other computers immediately after the installation of a site server. In order to make the self-study exercises simple and optimize hardware resources, the site server will serve all site system roles until the exercises in Chapter 10.
The SMS console tree—specifically the site description node, shown as S01 _ Central Site in Figure 2-14—is the post-installation starting point for SMS. You configure site boundaries for the site by selecting the site description node, and then choosing Properties from the Action menu. By default, if the site server is installed on a domain controller, the network containing the site server is the site server's site boundary. Notice in Figure 2-14 that the TCP/IP subnet site boundary for the site server is network 128.1.0.0.
Figure 2-14. Setting or viewing the site boundaries.
Site boundaries should not include inaccessible networks or networks that are not available over a fast, reliable connection. In cases when such networks are included, configure a second site server for this site. SMS is designed to optimize inter-site communications but relies on fast, reliable connections within a site boundary.
WARNING
While it is possible to assign a site boundary to more than one site, it is not advisable, because site configuration conflicts are likely.
Once site boundaries are set, SMS uses a number of discovery methods to find resources. Review Chapter 1, Lesson 1 for details on each SMS discovery method. Discovery methods deliver data about resources to the site database. Resource data is collected by various discovery components and stored in data discovery records (DDR). For example, the NT User Group Discovery Agent finds domain global groups within the site boundaries. After the NT User Group Discovery Agent collects this information, it forwards it to the site database as a DDR. Once resources are discovered, management of those resources can begin. For example, Windows NT/2000 global groups can be assigned to collections and used for software distribution.
Configurable discovery methods are enabled from the Discovery Methods node. Discovery methods are enabled by selecting a discovery method in the details pane and choosing Properties from the Action menu. Each discovery method's properties and the types of DDRs they generate are unique to their function. The remainder of this lesson explores the discovery methods.
This discovery method finds computer resources that log on to Windows NT/2000 domain controllers. When this logon discovery method is enabled, domain controllers are configured as the logon points for computer resources. Windows Networking Logon Discovery can be configured to automatically update logon scripts. Alternatively, users can run a manual SMS discovery program. By default, the site server's domain is added to this discovery method.
This discovery method finds computer resources that log in to a Novell NetWare 3.x server or a Novell NetWare 4.x server running in bindery emulation mode. When this method is enabled, the site server uses NetWare bindery servers or bindery emulating servers as logon points. The NetWare Bindery Logon Discovery method can update the NetWare system login script automatically, or NetWare users can run a manual SMS discovery program.
If a NetWare 4.x server is running native NetWare Directory Services (NDS), this discovery method finds computer resources that log in to the NDS. When this method is enabled, the site server uses NDS volumes as logon points. The NetWare NDS Logon Discovery method can update the container login scripts automatically, or NetWare users can run the manual SMS discovery program.
NOTE
Configuring the site server and NetWare servers for NetWare discovery methods will be explored in Chapter 10, "Configuring Site Systems."
Unlike the previously discussed discovery methods, Windows NT User Account Discovery finds Windows NT/2000 domain user accounts, not computer resources. This discovery method regularly polls Windows NT/2000 domain controllers to keep its list of user accounts current with the user account database of the domain controller(s).
This discovery method is similar to Windows NT User Account Discovery. Rather than collect domain user accounts, this discovery method collects Windows NT/2000 global groups. Note that Windows NT local groups are not part of SMS discovery. Windows NT User Group Discovery polls domain controllers for global groups to keep its list of groups current with the user account database of the domain controller(s).
This discovery method depends on client agents for its operation. Once a computer resource is configured as a client computer, Heartbeat Discovery can update client computer data in the site database. This is especially useful for client computers that rarely log on to the network, for example email servers or print servers. Do not confuse a computer resource with a client computer. Except for the Heartbeat Discovery method, no other discovery method depends on client agents installed on computer resources.
This discovery method is the most robust in function of any of the discovery methods because of all of the providers it queries to discover resources. Network Discovery finds network resources by examining subnets; Domains; SNMP community names; SNMP devices, such as routers; and DHCP servers. This discovery method can be configured to regularly poll the network for resources. The public SNMP community name is added by default.
NOTE
Network Discovery is the only discovery method that is not enabled automatically when an Express setup SMS installation routine has been run. For a Custom setup, no discovery methods are enabled.
The SMS Server Discovery method for finding site systems is SMS Server Discovery. This discovery method never appears in the details pane of the Discovery Methods node. This method is automatically enabled when a site system is created.
If two discovery methods find the same resource, SMS merges the discovered data. Each DDR contains key properties, such as the SMS Unique ID (GUID), which are used to uniquely identify a resource.
These exercises are based on the computer configuration of Computer 1 and Computer 2 running Windows NT, as outlined in "About this Book." Further, you must complete Exercises 1-6 to successfully complete these exercises.
SMS automatically adds the site boundary that contains the site server. You will verify that this site boundary is configured and you will learn how to add additional subnets, networks and zones to the site boundary.
A menu of choices appears.
The sms (Systems Management Server) MMC appears.
The S01 - Central Site Site Properties dialog box appears.
The 128.1.0.0 IP subnet appears. You have successfully verified that the site server's network is automatically added to the site boundary for this site server.
The New Subnet dialog box appears.
This exercise demonstrates how site boundaries are configured using the SMS Administrator console. Do not close the SMS Administrator console, as it will be used in the next exercise.
SMS automatically discovers site system resources using the SMS Server Discovery method. You will verify that Computer 1 (Computer name: SERVER1) has been discovered using the SMS Server Discovery method.
SERVER1 appears in the details pane.
The SERVER1 Properties dialog box appears.
Do not close the SMS Administrator console, as it will be used in the next exercise.
You will enable three resource discovery methods to collect computer resources, domain users, and global groups. Since NetWare support has not been installed, these discovery methods do not appear in the details pane of the Discovery Methods node.
Five discovery methods appear in the details pane.
The Windows Networking Logon Discovery Properties dialog box appears.
Notice that the `Keep logon point lists for discovery and installation synchronized' checkbox is checked. This will be discussed in Lesson 7. Please leave this option checked. Also notice that DOMAIN1 appears in the `Logon Points' box. By default, the site server's domain is configured as a logon point.
In the next part of this exercise you will enable the Windows NT User Account Discovery method.
The Windows NT User Account Discovery Properties dialog box appears.
The Schedule dialog box appears.
In the next part of this exercise you will enable the Windows NT User Account Discovery method.
The Windows NT User Group Discovery Properties dialog box appears.
The Schedule dialog box appears.
A menu of choices appears.
User Manager - DOMAIN1 appears.
The User Properties dialog box appears.
The User Environment Profile dialog box appears.
When the Windows Networking Logon Discovery method was enabled and the `Modify user logon scripts' option was checked, SMSLS was added to this user's User Environment Profile. The SMSLS.BAT file is always added to User Environment Profiles if no logon script is specified.
In the next part of this exercise you will log on from Computer 2. Computer 2 was configured to run Windows NT Workstation version 4.0. TCP/IP is configured to obtain an IP address from a DCHP server. Computer 2 is configured to log on to DOMAIN1 as User1. If Computer 2 is not configured in this way, review "About this Book" and reconfigure the second computer.
The Windows NT Logon Script message box appears as the Windows Networking Logon Discovery program runs.
In this exercise, you will verify that Windows NT domain users and Windows NT global groups have been discovered through Windows NT User Account Discovery and Windows NT User Group Discovery, respectively.
All pre-configured collections appear in the details pane.
The list of domain user accounts in DOMAIN1 appear.
All global groups in DOMAIN1 appear.
Computer2 appears in the details pane. If this computer resource does not appear, wait one hour and check again.
The COMPUTER2 Properties dialog box appears.
This is the general information collected through computer resource logon discovery.
The Systems Management application is automatically installed after discovery runs on the client computer.