Microsoft Windows 2000 Server Clustering Interoperability with SMS

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Technical Paper

Abstract

This technical paper describes using Microsoft® Systems Management Server (SMS) 2.0 SP3 with Microsoft Windows 2000 Advanced Server in a clustered server environment.

On This Page

Introduction
Discovering and Installing SMS Clients on a Server Cluster
Using SMS Clients with Clusters
Using SMS Site Servers in a Clustered Environment
Using the SMS Administrator Console in a Clustered Environment
For More Information

Introduction

Computers running Windows 2000 Advanced Server can be interconnected using Windows server cluster technology, which provides high availability of applications through the failover of resources. Because server clusters contain more than one physical server and can host multiple "virtual" servers, special consideration is required when using Microsoft Systems Management Server (SMS) in a clustered environment. This technical paper is intended for SMS and Windows 2000 system administrators who are familiar with Windows server cluster technology and SMS. This paper outlines SMS compatibility with server clustering and explains how to implement SMS in a clustered environment, in addition to implementing server clustering in your SMS site.

SMS and server clustering can successfully coexist if you follow the recommendations outlined in this paper. Note that cluster failover (a feature provided by the Cluster service) is not supported for SMS site servers or SMS components, with the exception of distribution points.

System requirements

The information in this paper is relevant only to SMS 2.0 Service Pack 3 (SP3) with Windows 2000 Advanced Server or later. There is no support for SMS with clustering on Windows NT 4.0 or earlier. When planning your hardware and system requirements, see the Microsoft SMS Administrator's Guide and the Windows 2000 Server documentation.

Overview

A server cluster is a group of independent computers, called server nodes (or nodes), working together as a single system to ensure that critical applications and resources remain available to clients. Server clusters are enabled by the Cluster service. Computers in a server cluster are physically connected by cables and programmatically connected by cluster software. Figure 1 illustrates a typical two-node cluster.

Figure 1: Two-node server cluster running Windows 2000 Advanced Server

In a server cluster, any software or hardware component that can be managed by the server cluster is called a resource. A group is a collection of cluster resources that have the following two characteristics:

• It defines a unit of failover

• It is always owned by one node at any point in time

Typically, a group contains all of the resources needed to run a specific application or service. Resources and groups can be in an online state or an offline state. In an online state, the resources and groups are available to the cluster. In an offline state, the resources and groups are unavailable to the cluster.

Failover is the process of moving a group to another node in response to a node or resource failure, or it can be a move initiated by the administrator. Failback is the process of moving a cluster group back to its preferred node when the node returns to an active state following a failure. When a node becomes inactive for any reason, the Cluster service fails over any groups hosted by the node to ensure application availability. When the node becomes active again, the Cluster service can fail back the groups that were originally hosted by the node.

The Cluster service fails back a group using the same procedures it performs during failover—that is, the Cluster service takes all of the resources in the group offline, moves the group, and then brings all of the resources in the group online.

A virtual server is a group that contains an IP address resource and a network name resource and acts as a server. When a client application connects to an application running on the virtual server, it uses the virtual IP address or network name in the group to connect to the virtual server. Unlike a physical server, a virtual server is not associated with a specific computer. Also, it can be failed over like a group. If the node hosting the virtual server fails, clients can still access its resources using the same server name (or IP address). Thus, users and clients cannot distinguish between connecting to a virtual server and connecting to a single, physical server. A server cluster can contain multiple virtual servers running different applications. Applications that support the cluster application programming interface (API) are cluster-aware. Applications that do not support the cluster API are cluster-unaware. With the exception of distribution points, SMS is a cluster-unaware application.

A virtual server acts like a physical server in the following ways:

• Allows access to network resources

• Is published to network clients under a unique server name

• Is associated with a network name and an IP address

Because of those attributes, SMS cannot distinguish virtual servers from the nodes that manage the Cluster service. (See Figure 2.)

Likewise, most SMS components do not function correctly when installed on the shared disks ("cluster disks") of a cluster because services such as the SMS_Executive service were not written to handle the failure of a clustered system. A cluster disk is any disk on a shared bus connected to the cluster nodes. In general, you should not install any SMS components on a cluster disk. With the exception of distribution points, you should configure SMS components to work only with an unshared disk available to the server nodes. An unshared disk is a disk on the same bus as the system drive and is not connected to a shared bus.

For more details about Windows clustering, see the Windows 2000 Advanced Server documentation.

Figure 2: Two-node server cluster running three virtual servers (no SMS components installed)

Discovering and Installing SMS Clients on a Server Cluster

SMS provides limited support for SMS clients on computers running Windows 2000 Advanced Server with the Cluster service enabled. Support is provided if the following are true:

1. Network Discovery is disabled.

   -OR-

   Network Discovery is enabled but the server nodes and their virtual servers are excluded from SMS client installation. (This is described later in this paper.)

2. The SMS client is installed only on the server node's unshared disk and not on any of its cluster disks.

Network Discovery cannot determine whether or not a given server name or IP address is associated with a real computer or a virtual server. Therefore, regardless of the client installation method in use, if Network Discovery is enabled and configured to discover the server nodes, the discovery data of the virtual servers can become merged with the discovery data of the server nodes, depending upon the cluster configuration at the time of discovery. The workaround is to exclude the virtual servers from the SMS site. (This workaround is described in the "Implementing SMS clients on clustered servers" section.)

Implementing SMS clients on clustered servers

In a cluster, the SMS client software must be installed on an unshared disk. Do not install SMS client software on a cluster disk. On clustered computers, the only supported methods of client installation are:

• Windows Networking Logon Client Installation

• Manual Client Installation

Note: The Windows NT Remote Client Installation method is conditionally supported. This is described later in this section.

Windows Networking Logon Client Installation

SMS supports the Windows Networking Logon Client Installation method of SMS client installation in a clustered environment because it automatically installs the client on the system drive of the server node.

Manual Client Installation (SMSman.exe)

SMS supports the Manual Client Installation method of SMS client installation in a clustered environment because it automatically installs the client on the system drive of the server node.

Windows NT Remote Client Installation

Another client installation option, Windows NT Remote Client Installation, is supported in a clustered environment only when you exclude the server nodes and virtual servers from client installation. The procedure for excluding systems from client installation is described in this section.

Thus, in order to enable Windows NT Remote Client Installation in a clustered environment (for support of your client systems that are not clustered), you must exclude each server node and all virtual servers in the server cluster from SMS client installation. This cuts down on excess network traffic because it prevents SMS from attempting client installation on the virtual servers of the cluster configuration.

Excluding server nodes and virtual servers from remote client installation

The following is an explanation of how an administrator specifies computers to be excluded from discovery and installation by the Windows NT Remote Client Installation service.

Warning: This procedure contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to restore the registry or registry keys, see Regedit.exe Help and Regedt32.exe Help.

To exclude servers from being discovered and installed as SMS clients,

1. On the site server, start Registry Editor by executing Regedt32.exe.

2. Locate and double-click the following key in the registry:

   HKEY_LOCAL_MACHINE \Software \Microsoft \SMS \Components SMS_DISCOVERY_DATA_MANAGER

3. In the right pane, double-click the ExcludeServers value to open the Multi-String Editor box.

4. Modify the value to add or remove the computer names that you want to exclude from receiving SMS client components, delineating multiple entries with a <Return> tag to place them on separate lines.

5. Click OK when finished, and then close Registry Editor.

For more information about excluding computers from SMS client installation, see Microsoft Knowledge Base article 207729.

Using SMS Clients with Clusters

This section contains information about the issues you might encounter when using SMS clients in a clustered environment and the impact that Network Discovery has in a site containing server clusters.

Collections and queries

If Network Discovery is enabled on your SMS site, it polls the network and populates the SMS site database with discovery data records (DDRs) for the computers it finds. Since SMS cannot distinguish virtual servers from real servers, the DDRs include the network name and IP address of the virtual servers configured in the cluster.

Thus, when you use Network Discovery in a clustered environment, the resources that appear in collections do not accurately represent the resources of servers that are part of a cluster. The membership in some collections might change in unexpected ways. Similarly, the details for collection members might change over time as the discovery data for a virtual server overwrites the discovery data for the server node.

For example, if you have a two-node server cluster with three virtual servers defined, Network Discovery creates up to five DDRs, and Discovery Data Manager merges these into just two records (one per server node) in the SMS site database. However, virtual server names and other attributes can appear in one or more of these records. Hence, your All Systems collection will display the clustered system nodes only. However, the properties for those clients might display multiple IP addresses, depending upon which virtual server was active on the server node at the time Network Discovery was run. Likewise, if you create a collection based on the IP address or network name of a virtual node, the collection displays only the server node that owned the group at the time the client record last updated.

As the administrator, you should be aware of this issue when you create collections and queries based on system resource attributes such as IP address or NetBIOS name. This issue exists as long as Network Discovery is enabled, unless you exclude the server nodes and virtual servers from client installation, as described earlier in this paper.

Software distribution

There is no support for distributing software to the virtual servers of a cluster. (For more information, see the "Collections and queries" section earlier in this paper.)

Remote Tools

SMS Remote Tools might exhibit connectivity issues in a clustered environment. Since SMS Remote Tools uses network-level name resolution and attempts to connect to remote clients through known IP, IPX, and NetBIOS names and addresses in the SMS database, SMS attempts to connect correctly to client and server workstations. However, due to address replication timing and the general nature of IP, WINS, and DHCP information, it is possible for a Remote Tools session to connect to a defunct or failed-over node.

Software metering

There is no support for software metering on any computers participating in a server cluster.

Software and hardware inventory

Software and Hardware Inventory Client Agents are supported in a Windows 2000 clustered environment provided the SMS client is installed properly on the server nodes. (See the "Discovering and Installing SMS Clients on Server Clusters" section earlier in this paper.) Inventory is collected from the server nodes in the same way that it is collected from computers that are not part of a cluster. Virtual server information is not collected.

Event to Trap Translator

The Event to Trap Translator is supported in a Windows 2000 clustered environment provided the SMS client is installed properly on the server nodes. (See the "Discovering and Installing SMS Clients on Server Clusters" section earlier in this paper.) Simple Network Management Protocol (SNMP) traps are created on server nodes in the same way as they are on computers that are not part of a cluster.

Using SMS Site Servers in a Clustered Environment

SMS 2.0 SP3 provides the following support for SMS site servers and site systems running on Windows 2000 Advanced Server with the Cluster service enabled. Generally, no SMS server component can be installed on a cluster disk (a shared disk participating in the server cluster), with the exception of a cluster-aware distribution point, as described in the "Site Systems" section later in this paper. A distribution point is the only SMS component that can participate in the failover feature provided by the Cluster service. However, some SMS server components can be installed locally on an unshared disk on a server node in a cluster if the proper steps are followed. Note that failover is not supported for those components.

Warning: Custom SMS Setup installs SMS on the disk that you specify during installation, even if that disk is shared. The same is true for other individually installed or specified SMS components (for example, SQL Server). It is recommended that you do not use Express Setup to install SMS on a clustered system because Express Setup might target a cluster disk for the installation. Express Setup automatically installs SMS on the largest partition formatted with the NTFS file system found, whether or not it exists on a shared disk.

Preparation

Before you install SMS site server components on a clustered system, you must make certain the SMS components are not installed on a cluster disk by ensuring the target installation node has no access to the cluster disks.

To ensure that the target installation node has no access to the cluster disks

1. Exclude the target virtual server and all nodes of the server cluster from Windows NT Remote Client Installation so that the SMS client does not attempt to perform an installation in the cluster. To do this, follow the procedure in the "Windows NT Remote Client Installation" section earlier in this paper.

2. Determine which groups the target node owns by running Cluster Administrator on the target node. In the left pane, click the Groups item. In the right pane, the cluster groups and their owners are displayed.

3. For any group that is assigned ownership by the target node, do the following: Right-click the group name owned by the target node, and then click Move Group. After the process has completed, verify that a non-target node now owns the group.

4. Verify that each group is configured to prevent failback (so that if the cluster server detects a failure it does not attempt to fail over to the node to which you are installing SMS). To do this: right-click the group name, and then click Properties. On the Failback tab, make sure the Prevent Failback check box is selected.

5. Verify that you cannot access any of the cluster disks. To do this: On the target node, start Windows Explorer. Attempt to access each of the cluster disks. Verify that Windows Explorer returns the following message when you click a cluster disk:

   "<driveletter>:\ is not accessible. The requested resource is in use."

Primary and secondary site servers

SMS supports installation of an SMS site server on a computer running Windows 2000 Advanced Server with the Cluster service enabled provided the site server is installed on an unshared disk of one of the server nodes. For information about installing the site database server, see the "Site database server" section later in this paper.

Installing an SMS (primary or secondary) site server in an existing cluster

Using this procedure, you can safely install a site server on a clustered server.

To install an SMS site server in an existing server cluster

1. Verify that the SMS component installation will take place on the targeted unshared disk of the server node. (See the "Preparation" section earlier in this paper.)

2. Install the primary or secondary site on the target node.

   For a Primary Site, run Setup from the SMS 2.0 SP2 compact disc (or disc image), ensuring that the SMS site is installed on the unshared disk. Then, upgrade the primary site to SP3 or later.

   For a Secondary Site, run the Secondary Site Creation Wizard by selecting the appropriate option from the setup program on the SMS 2.0 SP3 compact disc (or disc image). Alternatively, you can navigate to the primary site in the SMS Administrator console of an existing SMS 2.0 SP3 site. Right-click the <site code - site name>, point to New, and then click Secondary Site. When specifying the installation directory for the secondary site, make sure you specify an unshared disk in the path.

3. If this new site server is going to participate as a site database server, client access point (CAP), or logon point, then those SMS components must be installed before proceeding to step 4. Do not return the server cluster to its original configuration until you have configured all of the SMS component roles. For verification steps, refer to the appropriate sections later in this paper.

4. Return the server cluster to its original configuration.

Warning: Remember that if you plan to add another SMS component role to the site server, the cluster disks must remain inaccessible to the target node while the SMS component is installed. Also, it is important that you keep the node in this state until logon point installation is completed if the server is or will become a domain controller. (See the "Logon point" section later in this paper.)

Installing the Cluster service on an existing SMS site server

If you plan to install the Cluster service on a site server and then later convert that computer to a clustered node, make sure that all SMS components are installed only to an unshared disk before you enable and configure the Cluster service.

Site systems

This section describes support for the following SMS site systems on computers running Windows 2000 Advanced Server with the Cluster service enabled:

• Site database server

• Client access point

• Distribution point

• Logon point

Note: There is no support for running the software metering server (or its database) on any part of a cluster.

Site database server

SMS supports the installation of SQL Server as the SMS site database on computers running Windows 2000 Advanced Server with the Cluster service enabled. However, SQL Server must be installed to an unshared disk in the server cluster and must not participate in the cluster. Also, the SMS site database cannot be created on a cluster disk. This means that failover of the computer running SQL Server and the SMS site database is not supported.

Client access point

SMS supports the creation of a CAP on a computer running Windows 2000 Advanced Server with the Cluster service enabled provided the CAP is installed on an unshared disk of one of the server nodes and does not participate in the cluster.

SMS supports the following methods for creating a CAP in a cluster:

• Windows NT share method

• Windows NT server method

• Important: Due to the automatic nature of the installation process for this component, SMS might target unsupported drives during the creation of the CAP. You should follow the procedures in this section to ensure that the CAP is not installed to a cluster disk.

To install a CAP using the Windows NT share method

1. On the target server node, in Windows Explorer, create a folder on a local (unshared) disk. Name the folder CAP_<sitecode>. Right-click the folder, and then click Properties. On the Sharing tab, click Share this folder, and then click OK.

2. Verify that the SMS component installation will take place on the targeted drive of the server node. This requires that no cluster disk be accessible during the CAP installation. (Follow the steps outlined in the "Preparation" section earlier in this paper.)

3. On your SMS site server, in the SMS Administrator console, navigate to Site Systems.

4. Right-click Site Systems, point to New, and then click Windows NT Share. Click Set, type the server and share name you created in step 1, and click OK.

5. On the Client Access Point tab, select the Use this site system as a client access point check box, and then click OK to start the installation.

6. On the targeted server node, verify that the share was created on an unshared disk using the share name specified in step 1.

   Note: In Windows Explorer, the resulting share appears on the CAP as

   <driveletter>:\CAP_<sitecode>\ CAP_<sitecode>

7. Return the server cluster to its original state as needed.

To install a CAP using the Windows NT server method

1. Verify that the SMS component installation will take place on the targeted disk of the server node. This requires that no cluster disk be accessible during the CAP installation. (Follow the steps outlined in the "Preparation" section earlier in this paper.)

2. In the SMS Administrator console, navigate to Site Systems.

3. Right-click Site Systems, point to New, and then click Windows NT Server. Click Set, type the server node name, and then click OK. Or, if the site system already exists, right-click the site system, and then click Properties.

4. On the Client Access Point tab, select the Use this site system as a client access point check box, and then click OK.

5. On the targeted server node, verify that the share was created on an unshared disk.

6. Return the server cluster to its original state as needed.

Distribution point

SMS supports the creation of a distribution point on a computer running Windows 2000 Advanced Server with the Cluster service enabled. You can install distribution points on any server node or virtual server in a cluster. This means you can install a distribution point on a cluster disk. However, the share must be created in advance as a cluster resource on a virtual server, and it must be specified when the distribution point is created.

Distribution points installed on a server cluster are either cluster-aware or cluster-unaware. A cluster-aware distribution point is available to SMS clients when the share's group or node fails. A cluster-unaware distribution point coexists with the cluster, but it does not support failover or otherwise participate in the cluster.

The following scenarios are supported for creating a distribution point in a cluster:

• Installing a cluster-aware distribution point on a cluster disk

• Installing a cluster-unaware distribution point on an unshared disk on a server node

To install a cluster-aware distribution point

Use this procedure to create a distribution point that will be available to SMS clients when the share's group or node fails.

1. Using Cluster Administrator, in an existing cluster group that contains a disk resource, verify that you have an IP Address resource and a Network Name resource.

2. On the server node, in Windows Explorer, click the cluster disk where you want to create the distribution point.

3. On the File menu, click New Folder, and then name the folder. For example, Shared_DP. (Do not enable sharing.)

   Create the File Share Resource in the cluster. In Cluster Administrator, right-click the group you want the distribution point share to be a member of, point to New, and then click Resource. Complete the wizard as prompted, specifying the following where appropriate:

   1. In the New Resource dialog box, name the resource and choose File Share as the Resource Type.

   2. In the Dependencies dialog box, add the Physical Disk Resource on which the share was created to the Resource dependencies list. Also add the Network Name resource to the dependencies list.

   3. In File Share Parameters dialog box, type in the share name for the distribution point and the directory path to the shared folder. Also, if necessary, click Permissions and assign share level permissions as appropriate for your SMS environment.

   Note: Any current or future modifications to the share permissions must be configured in Cluster Administrator, not in Windows Explorer, as described in step 4b, in order for them to persist after a failover.

4. After the shared resource is created, in Cluster Administrator, right-click the new resource, and then click Bring Online.

5. In the SMS Administrator console, navigate to Site Systems. Right-click Site Systems, point to New, and then click Windows NT Share.

6. Click Set, and then type the server name and the share name you created for the distribution point in Cluster Administrator in step 4c. For example:

   \\<virtual server name>\Shared_DP

7. On the Distribution Point tab, select the Use this site system as a distribution point check box, and then click OK.

There are two methods for installing cluster-unaware distribution points.

• Windows NT share method

• Windows NT server method

To install a cluster-unaware distribution point using the Windows NT share method

1. Verify that the SMS component installation will take place on the targeted unshared disk of the server node. This requires that no cluster disks be accessible during the distribution point installation. (Follow the steps outlined in the "Preparation" section earlier in this paper.)

2. On the target node, in Windows Explorer, click on the unshared disk drive where you want to create the distribution point.

3. On the File menu, click New Folder, and then name the folder. For example, SMS_DP. Right-click the folder, and then click Properties. On the Sharing tab, click Share this folder, and then click OK.

4. In the SMS Administrator console, navigate to Site Systems. Right-click Site Systems, click New, and then click Windows NT Share.

5. Click Set, and then type the server and share name you created in step 3, and click OK. For example:

   \\< virtual server name >\SMS_DP

6. On the Distribution Point tab, select the Use this site system as a distribution point check box, and then click OK to establish the distribution point on the targeted drive.

7. Return the server cluster to its original state as needed.

To install a cluster-unaware distribution point using the Windows NT server method

1. Verify that the SMS component installation will take place on the targeted unshared disk of the server node. This requires that no cluster disks be accessible during the distribution point installation. (Follow the steps outlined in the "Preparation" section earlier in this paper.)

2. In the SMS Administrator console, navigate to Site Systems.

3. Right-click Site Systems, click New, click Windows NT Server, click Set, type the name of the target server node, and then click OK. Or, if the site system already exists, right-click the site system, and then click Properties.

4. On the Distribution Point tab, select the Use this site system as a distribution point check box, and then click OK.

   In order for the distribution point to be created, you must send a package containing source files to it. (Note that the package must contain source files.) To do this, in the SMS Administrator console navigate to Packages. Navigate to an existing package that contains source files and proceed to step 6. If a package containing source files does not exist, you must first create a test package as follows:

   1. Navigate to Packages. Right-click Packages, point to New, and then click Package.

      In the Package Properties dialog box, complete the settings in these tabs:

      • On the General tab, specify general data for a package, such as the package name and version.

      • On the Data Source tab, select the This package contains source files check box, then specify the data source settings, such as the package source directory

      • On the Data Access tab, configure access to the package's data files, such as the distribution point share name.

      • On the Reporting tab, configure how you want SMS to identify package status information.

      • On the Security tab, specify security settings for the new package.

5. Double-click the package that you chose (or created) in step 5.

6. In the package sub-tree, right-click Distribution Points, point to New, and then click Distribution Points. In the New Distribution Points wizard, in the Copy Package dialog box, click the server node, and then click Finish.

7. Verify the creation of the SMSPKG<driveletter>$ share on an unshared disk of the target node.

8. Return the server cluster to its original state as needed.

Logon point

To act as an SMS logon point, a server must be a domain controller. If any of the server nodes in a cluster is a domain controller in a domain targeted for Windows Networking Logon Client Installation or Windows Networking Logon Discovery, SMS automatically creates a logon point on a disk in the cluster. SMS targets the NTFS drive with the most available disk space for the SMSLOGON folder creation.

SMS supports Windows 2000 Advanced Server domain controllers with the Cluster service enabled in either native or mixed-mode Active Directory™ domains as logon points provided they are installed on an unshared disk. You can do this by creating a logon point share on an unshared disk of the clustered domain controller in your SMS site prior to enabling Windows Networking Logon Discovery or Windows Networking Logon Installation. Or, you can create a logon point share on an unshared disk of the clustered member server prior to promoting it to a domain controller.

Note: See your cluster documentation before changing a member server to a domain controller after installing the Cluster service.

To create the logon point share on an unshared disk in the cluster

1. On the targeted server node, in Windows Explorer, select the local NTFS drive where you want to create the SMS logon point.

2. On the File menu, click New Folder. Name the folder SMSLOGON.

3. Right-click the SMSLOGON folder, click Properties, click the Sharing tab, and then click Share this folder.

4. Ensure that the share name is SMSLOGON. In the Comment field, type:

   SMS NT logon service, and then click OK.

Warning: To prevent a logon point from being installed on a cluster disk:

• Do not promote a clustered member server to a domain controller while Windows Networking Logon Discovery and/or Windows Networking Logon Installation is enabled on your SMS site without first creating a logon point share on an unshared disk of the clustered domain controller.

• Do not enable Windows Networking Logon Discovery or Windows Networking Logon Installation when a domain controller exists on a server cluster in your SMS site without first creating a logon point share on an unshared disk of the clustered domain controller.

In the event that a logon point is inadvertently created on a cluster, you must move the logon point from the cluster disk to an unshared disk.

To move the logon point from a cluster disk to an unshared disk

1. On the logon point, make a note of the NTFS permissions and inheritance policy assigned to the SMSLOGON folder and each of its subfolders. Also, make a note of the SMSLOGON share permissions.

2. Stop the SMS NT Logon Discovery Agent service on the computer that has the logon point that you want to move.

3. Then, depending upon whether or not you are sharing logon points among multiple sites, stop the SMS Executive and Site Component Manager services on the site servers as follows:

   If you have a single SMS site, stop the SMS Executive and Site Component Manager services on your site server.

   1. -OR-

      If you have multiple SMS sites that share logon points and the logon point is a backup domain controller (BDC), you must stop the SMS Executive and Site Component Manager services on the senior site. For more information on senior sites, see article 235726, "How to Specify Senior Site for WinNT Logon Point Management in a Single Domain with Multiple Sites," in the Microsoft Knowledge Base at https://support.microsoft.com/default.aspx?scid=kb;en-us;235726&sd=tech

   2. -OR-

      If you have multiple sites that share logon points and the logon point is a primary domain controller (PDC), then you must stop the SMS Executive and Site Component Manager services on the SMS site server in each site prior to proceeding to the next step.

4. Move the SMSLOGON folder to an unshared disk, and then share the folder. To share the folder, in Windows Explorer, right-click the folder, and then click Properties. On the Sharing tab, click Share this folder. In the Share name box, type the following, exactly as it appears here:

   SMSLOGON
   Then, in the Comments box, type the following, exactly as it appears here:
   SMS NT logon service

5. Manually reset the NTFS permissions and inheritance policies on the new share and its subfolders to match the original settings, as noted in step 1.

6. If Windows Networking Logon Discovery is enabled, do the following:

   In the registry, set the correct path to the new logon point share by changing the drive letter in the ImagePath value to the new drive in the following key:

   HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services SMS_NT_Logon_Discovery_Agent

   In the registry, redirect the log file tracing to point to the new folder by changing the drive letter in the TraceFilename value to the new drive in the following key:

   HKEY_LOCAL_MACHINE \Software \Microsoft \SMS Tracing\SMS_NT_LOGON_DISCOVERY_AGENT

7. Restart the SMS services that were stopped in step 2.

Using the SMS Administrator Console in a Clustered Environment

SMS 2.0 SP3 supports the SMS Administrator console on all nodes of a server cluster running Windows 2000 Advanced Server. The SMS Administrator console can also connect to an SMS primary site server running on a server node of a cluster. The installation process for a remote SMS Administrator console on a server node is the same as for a non-clustered system, but it must not be installed on a cluster disk.

For More Information

For more information about SMS, visit the SMS Web site at

https://technet.microsoft.com/en-us/sms/default.aspx

For a roadmap of SMS Technical Resources, see article 269345, "Systems Management Server Technical Resources," in the Microsoft Knowledge Base at

https://support.microsoft.com/kb/269345

For more information about Windows clustering technologies, see

https://www.microsoft.com/windows2000/guide/server/features/clustering.asp

• If you obtained SMS through the Select or Open program, you can order copies of the SMS 2.0 Administrator's Guide by calling Microsoft World Wide Fulfillment at 1-800-248-0655. Use part number 271-00617.

If you did not get SMS through the Select or Open programs, you can call Microsoft Supplemental and Replacement Parts, at 1-800-360-7561 and request the SMS 2.0 Administrator's Guide, Part No. 271-00617.