Microsoft Systems Management Server 2.0 Training Kit

[Previous] [Next]

If hardware resources are at a premium or a site does not require a primary site server, a secondary site server is ideal. Understanding how to remove SMS is important for either changing the role of a site system or removing all software installed to run SMS. For example, if a primary site server will be reconfigured as a secondary site server, SMS must be removed before SMS is installed to make the computer a secondary site server.

After this lesson, you will be able to Estimated Completion Time: 40 minutes

Preparing for a Secondary Site Server Installation

A secondary site server can be installed in one of two ways:

Running the Create Secondary Site Wizard

As in SMS 1.2, a secondary site can be installed entirely from a primary site, allowing you to install a secondary site server without requiring a physical presence at the secondary site.

A new option in SMS 2.0 allows for the installation of a secondary site to be initiated through the Create Secondary Site Wizard and completed using installation files on the network that will become a secondary site.

Preparing for a Secondary Site Installation Using the Create Secondary Site Wizard

It should be verified that the computer that will become a secondary site server contains an NTFS formatted partition with at least 55 MB of available space. Also, the Windows NT/2000 Server boot partition (the partition containing the Windows NT/2000 operating system files) should contain at least 100 MB of free disk space. Only Windows NT/2000 Server can be a site server.

The SMS Service account is necessary for a secondary site server, just as it is necessary for a primary site server. If the domain in which the secondary site server resides trusts the domain containing its parent primary site server, you can use a trusted domain user account from the primary site. If a trust relationship does not exist or if you prefer to use a local domain user account at the secondary site, create an SMS Service account on the secondary site server with the following characteristics:

If the secondary site server is a member of the primary site server's domain, you can use a domain user account in the primary site server's domain.

From the primary site, verify that the account and password to be used for the installation are valid. Explicitly use the user name and password of the secondary site. The following command line demonstrates how to test the connection with a net use command:

net use \\secondary_site_server\c$ /user:smsacct password

Using the account and password for the primary site, verify that the proposed secondary site server can connect back to the primary site server. The following command line demonstrates how to test the connection with a net use command:

net use \\primary_site_server\c$ /user:smsacct password

Installing a Secondary Site Server Using the Create Secondary Site Wizard

The Create Secondary Site Wizard is used to install the secondary site server. Start the wizard by selecting the primary site. Then from the Action menu, select New and then Secondary Site, as shown in Figure 11-22.

Figure 11-22. How to create a secondary site from a primary site.

Choosing to both initiate and install a secondary site from a primary site can overwhelm a heavily utilized or low-bandwidth WAN connection. When a secondary site installation is completed from a primary site, the secondary site installation files are compressed into a package of about 55 MB before being transferred to the secondary site.

There are three strategies for addressing the bandwidth utilization inherent in installing a secondary site.

Installing the Secondary Site Server Via a CD-ROM_based Installation

A CD-ROM_based installation starts by running SMS Setup from the SMS installation CD-ROM. This setup procedure is designed to initiate and install a secondary site server from the network where the secondary site server is located.

'Install an SMS secondary site' is an option available in the SMS Setup Wizard Setup Options dialog box, as shown in Figure 11-23.

Figure 11-23. The 'Install an SMS secondary site' option in the SMS setup routine.

The installation procedure will prompt you for the SMS service account to use at the secondary site, the site connection account to use from the secondary site to the primary site, and the primary site server site code.

Installing a secondary site server via the CD-ROM_based installation method requires that an address to the secondary site be configured at the primary site. Installing a secondary site from the primary site server does not require this additional step because the Create Secondary Site Wizard automatically creates the address.

The SMS Service account and the site connection account can be the same user account. However, site-to-site communication only requires that the site connection account be given full access permission to the SMS_SITE share (smsdir\INBOXES\DESPOOLR.BOX\RECEIVE) on the primary site and the 'Log on as a service' advanced user right on the primary site server.

Changes to the Secondary Site Server

A secondary site server configuration is similar to a primary site server configuration with some differences relating to the lack of local administration.

The following processes are installed on a computer to make it a secondary site server:

NOTE

SMS SQL Monitor is not installed on a secondary site because secondary sites do not require a SQL Server database.

Shares are created on the secondary site server to support internal systems management access and access by the parent site.

Registry entries are added to the secondary site server. These entries are the same as a primary site except that the following value names are missing from the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\ COMPONENTS key:

Removing SMS from a Computer Serving the Site Server Role

As shown in the earlier discussion, modern software installations do more than simply install files in a directory structure. Changes to the registry and other parts of the operating system are typical modifications made by modern Windows 32-bit installation programs. Thus, a full deinstallation of an installed program can be difficult. To address this problem, deinstalla-tion routines are becoming common additions to most programs, including SMS. If it is necessary to remove SMS, one of two methods is used, depending on whether SMS is installed as a primary or secondary site server.

Removing a Primary Site Server

Removing a primary site requires completion of three tasks: deleting the site from any site hierarchy that exists, removing the site itself, and removing client computer core components and client agents. Additional tasks may also be performed. The tasks are described next.

Deleting the Site from Any Site Hierarchy that Exists

Remove any secondary sites that are direct child sites of the site you want to remove. If you do not remove the direct secondary sites, the secondary site will be orphaned, an orphaned secondary site cannot be administered.

Remove the site from the site hierarchy. If the site that will be removed is part of a site hierarchy (that is, if the site has subsites below it or a parent site above it), adjust the hierarchy to account for the removed site. For example, if the site to be removed has a parent site and primary site children, detach the site to be removed from its parent site, then detach the two primary child sites from the parent being removed. Then attach the two primary sites that were previously children of the removed site to a new parent site.

IMPORTANT

Make sure that the parent site has received and completed the detach instructions from the site you want to remove. To verify that this has happened, make sure that the site to be removed is no longer displayed under the Site Hierarchy node of the parent site.

Remove the Site Itself

The SMS Setup program allows you to remove all SMS files from the site server and all site systems within the site boundary. Notice that if the site server or other site systems have client components installed, these client components must be removed using other methods—SMS Setup does not remove client components that have been installed on site systems. The SMS Setup program contains a 'Remove SMS' option.

During the process of removal, you can request SQL Server to drop the site database, software metering database, and log devices. In SQL Server 7.0, when the database is removed, SQL Server 7.0 automatically removes the device files.

Remove Client Computer Core Components and Client Agents

To remove the client computer agents in the secondary site, disable all of the client agents for the site using the SMS Administrator console. The client agents will be removed from client computers in the site. Alternatively, user's at client computers can run the Systems Management Installation wizard (SMSMAN.EXE or SMSMAN16.EXE for 16-bit Windows client computers), and select the 'Remove systems management components' option.

To remove all SMS components, including the SMS core client component, on a client computer, first disable all client agents using the SMS Administrator console. Then, run the 20clicln.bat batch file at the client computer. This batch file and its support files (HAMMER.EXE, KILL.EXE, SETEVNT.EXE, and SYSNAMES.EXE) are found on the SMS installation CD-ROM in the \SUPPORT\RESKIT\BIN\platform\CLEANCLI directory.

On Windows 32-bit client computers there is an additional method for removing all client components by adding an entry to the client computer's registry. In the key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\SMS\CLIENT\CONFIGURATION\CLIENT PROPERTIES, add the value name SMS CLIENT DEINSTALL, with a data type of string (Reg_SZ) and a value of True. This will cause the SMS Client Service and all client agents to be removed.

Additional Clean-up Tasks at Remaining Site Servers

If client computers in the site are being completely removed from the hierarchy, you should remove these computers from the site databases of all parent sites above the removed site.

This can be completed automatically by the Delete Aged Discovery Data task. This task is configured from the Database Maintenance node. Database Maintenance will be explored in Chapter 13.

Verify that any addresses defined at the parent site for the child site are removed, and remove the package distribution directory on the child site if it will no longer be used.

Reestablish the Site Hierarchy

Once the primary site has been removed, attach any orphaned child sites to a new parent site. Also, reinstall any secondary sites that were removed.

Exercise 55: Removing SMS from a Primary Site Server

In this exercise, you will deinstall a primary site server that will then be installed as a secondary site server in Exercise 56.

NOTE

Complete this procedure from Computer 2 using the SMS Administrator console.

  1. In the SMS console tree, select S02 — Primary Site.

  2. From the Action menu, select Properties.

    3. The S02 — Primary Site Site Properties dialog box appears. Notice that the parent site is listed in the properties of the child site.

  3. Click Set Parent Site.

    4. The Set Parent Site dialog box appears.

  4. Select the 'Central site' radio button, and then click OK.

    5. The S02 — Primary Site Site Properties dialog box appears. Notice there is no parent site listed in the properties.

  5. Click OK.

    6. The SMS Administrator console appears.

In the following steps, you will verify that the child has detached from the parent site and then remove the child site server from the All Systems collection. This will allow verification of the secondary site server installation.

NOTE

Complete this procedure from the SMS Administrator console on Computer 1 only.

  1. In the SMS console tree, expand Site Hierarchy, and then select S01 — Central Site.

  2. From the Action menu, select Refresh.

    3. The site hierarchy refreshes. The child site should not be displayed.

NOTE

Do not proceed until the child has been removed from the parent site's hierarchy.

  1. In the SMS console tree, expand the Collections node, and then select the All Systems collection.

    2. The list of discovered system resources appears in the details pane. This should include both site server computers.

  2. In the details pane, click SERVER2. Then from the Action menu, select Delete.

    3. A Confirm Delete message box appears prompting you to confirm the deletion.

  3. Click Yes.

    4. The list of discovered system resources appears in the details pane. Only SERVER1 should be listed.

In the following steps, you will remove the SMS client computer software installation on the computer running Windows NT Server.

NOTE

Complete this procedure from Computer 2 only.

  1. Start Regedt32.exe, and then open the following key: HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\SMS\CLIENT\CONFIGURATION\CLIENT PROPERTIES.

  2. Add the value SMS Client Deinstall with a string (Reg_SZ) of True.

  3. Close Registry Editor.

  4. Stop and then start the SMS Client service.

    5. This forces the SMS Client service to process any pending commands, such as the deinstallation request.

  5. Verify that the SMS Client service is no longer running.

    6. This is the indication that the deinstallation has completed.

TIP

An efficient method for removing the client computer software is running the 20CLICLN.BAT batch file on all client computers in the site.

In the following steps, you will deinstall a primary site server.

NOTE

Complete this procedure from Computer 2 only.

  1. Close the SMS Administrator console.

  2. From the Start menu, select Programs — Systems Management Server. Then choose SMS Setup.

    3. The Systems Management Server Setup Wizard dialog box appears.

  3. Click Next.

    4. The Systems Management Server Setup Wizard System Configuration dialog box appears indicating an existing installation of an SMS primary site on the computer.

  4. Click Next.

    5. The Systems Management Server Setup Wizard Setup Options dialog box displays options to deinstall or modify the current installation.

  5. Click Remove SMS, and then click Next.

    6. The Systems Management Server Setup Wizard SMS Database Deinstallation Options dialog box prompts for actions regarding the SMS database during deinstallation.

  6. Verify that the 'Delete SMS site database' and 'Delete software metering database' options are both selected, and then click Next.

    7. The Systems Management Server Setup Wizard dialog box appears indicating it is ready to start removing SMS.

  7. Click Finish.

    8. The SMS Setup — Deinstallation dialog box displays the status of the deinstallation.

    The SMS primary site installation is removed, and a Systems Management Server Setup Wizard message box appears indicating the deinstallation was successful.

  8. Click OK.

In the following steps, you will remove any remaining SMS software after the deinstallation of the primary site server.

NOTE

Complete this procedure from Computer 2 only.

  1. From the SMS installation CD-ROM, open \SUPPORT\RESKIT\BIN\I386\CLEANCLI directory.

  2. Run the 20CLIcln.bat batch file.

    3. A command prompt will appear and the deinstallation process runs. Allow the deinstallation routine to finish before moving to the next step.

  3. Delete the following directories and any files and shares remaining:

    4. D:\SMSPKGD$

    D:\Smspkg

  4. Delete the following files:

    5. C:\SMSSETUP.LOG

    C:\Temp\*.*

    WINDIR\SMScfg.ini

  5. Shut down and restart Windows NT Server 4.0, and then log on as ADMINISTRATOR.

  6. Remove the following registry keys from HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT:

    7. MMC

    NAL

    SMS

    SNMP_EVENTS

  7. Delete all user accounts that start with "SMS" from the domain.

  8. Delete the following group accounts:

    9. SMSAdmins

    SMSInternalCliGrp

Removing a Secondary Site Server

Removing a secondary site is significantly easier than removing a primary site. From the SMS Administrator console at the parent site, remove a secondary site by selecting the secondary site. Then from the Action menu, select Delete, as shown in Figure 11-24.

Figure 11-24. Deleting a secondary site.

There are two secondary site removal options: 'Delete the site' and 'Deinstall the site.' Deleting the site removes the secondary site server and its resources from the primary site's hierarchy. Deinstalling the site deletes the site and deinstalls SMS from the computer acting as the secondary site server.

If deinstalling the site is selected, SMS automatically creates a bootstrap job to send to the remote site to remove SMS from the site. This removes only server files on the secondary site server and site systems contained in the secondary site. It does not remove client computer files or packages installed on the client computers. Therefore, the tasks outlined under the previous section, "Remove Client Computer Core Components and Client Agents" should be completed after removing a secondary site. Computer resource entries from the secondary site are automatically removed from the primary site server site database.

Exercise 56: Installing a Secondary Site Server

In this exercise, you will install a secondary site server. The installation will be performed at the secondary site itself, rather than being initiated from the primary site server.

NOTE

Complete this procedure from Computer 2 only.

  1. From the SMS installation CD-ROM, start AUTORUN.EXE. Or, if Autorun is enabled, skip to step 2.

    2. The Systems Management Server 2.0 Setup dialog box appears.

  2. Select Set Up SMS 2.0.

    3. The Systems Management Server Setup Wizard dialog box appears.

  3. Click Next.

    4. The Systems Management Server Setup Wizard System Configuration dialog box appears indicating Setup did not find any existing SMS installation on the computer.

  4. Click Next.

    5. The Systems Management Server Setup Wizard Setup Options dialog box displays options for installation.

  5. Select 'Install an SMS secondary site,' and then click Next.

    6. The Systems Management Server Setup Wizard Product Registration dialog box requests registration information.

  6. In the 'Name' box, type your name.

  7. In the Organization box, type Education.

  8. In the CD Key box, type 111-1111111 and then click Next.

    9. The Systems Management Server Setup Wizard SMS Site Information dialog box appears prompting for site information.

  9. Type the following configuration information in the appropriate boxes.

    10. In this field/box Supply
    Site code S03
    Site name Secondary Site 3
    Site domain Leave at default (should be Domain1)

  10. Click Next.

    11. The Systems Management Server Setup Wizard SMS Service Account Information dialog box appears prompting for SMS Service account information.

  11. Type the following configuration information in the appropriate boxes.

    12. In this field/box Supply
    Account name Domain1\SMSSERVICE
    Password and Confirm password PASSWORD

  12. Click Next.

    13. The Systems Management Server Setup Wizard SMS Server Platform dialog box appears prompting installation of support for Alpha and Intel x86 servers.

  13. Click Next.

    14. The Systems Management Server Setup Wizard Setup Installation Options dialog box appears prompting the components to install on the site server.

  14. Under Options, verify that only Systems Management Server is selected, and then click Next.

    15. The Systems Management Server Setup Wizard Parent Site Information/Identification dialog box appears requesting the parent site's information, which is required for the secondary site installation.

  15. Type the following configuration information in the appropriate boxes.

    16. In this box Supply
    Parent site code S01
    Parent site server name Server1
    Select the initial network connection type from this secondary site to its parent site Local Area Network

  16. Click Next.

    17. The Systems Management Server Setup Wizard Connection Account Information dialog box appears prompting for the account to use when connecting to the parent site.

  17. Type the following configuration information in the appropriate boxes.

    18. In this box Supply
    Account name DOMAIN\SMSREMOTE_S03
    Password PASSWORD
    Confirm password PASSWORD

  18. Click Next.

  19. A dialog box requesting creation of service account will appear. Select Yes.

    20. The Systems Management Server Setup Wizard dialog box appears displaying the complete set of installation information that will be used to install SMS 2.0.

  20. Click Finish to complete the installation.

    21. A Systems Management Server Setup Wizard message appears indicating setup has been completed successfully.

  21. Click OK.

  22. While the installation runs on Computer 2, create the SMSREMOTE_S03 account on Computer 1 and configure the user account using the following information.

    23. Setting Supply or Enable
    Account name SMSREMOTE_S03
    Password PASSWORD
    Confirm password PASSWORD
    Password Never Expires Checked

  23. Assign SMSREMOTE_S03 the 'Log on as a Service' advanced user right.

  24. Grant SMSREMOTE_S03 full NTFS permissions to the D:\SMS\INBOXES\DESPOOLR.BOX\RECEIVE directory on Computer 1.

NOTE

If you are not sure how to complete the last three steps, consult a Windows NT Administration guide. Proficiency with Windows NT Server is a prerequisite for the successful completion of this course.

  1. From the SMS Administrator console on Computer 1, create a Standard Sender address from S01 to S03. Enter the following settings in the Standard Sender Address Properties dialog box:

    2. Setting Supply
    Destination Site Code S03
    Site server name SERVER2
    Account DOMAIN1\SMSSERVICE

In the following steps, you will verify the secondary site server installation was successful by viewing it from the primary site server.

NOTE

Complete this procedure from the SMS Administrator console on the primary site server (Computer 1) only.

  1. In the SMS console tree, select S01 — Central Site.

  2. From the Action menu, select Refresh.

    3. The site hierarchy refreshes. The child site should appear.

NOTE

It may take a few minutes for the secondary site files to be sent to and processed by the parent site before the site appears in the hierarchy. If the site does not appear, read the section entitled "Secondary Site" in Chapter 14, "Monitoring and Troubleshooting SMS"

  1. In the SMS console tree, select S03 — Secondary Site.

  2. From the Action menu, select Properties.

    3. The S03 Secondary Site Site Properties dialog box appears.

  3. How can you tell whether the site is a primary or secondary site?

    4. Answer

In the following steps, you will view log file activity at the parent site server resulting from the installation of a secondary site server.

NOTE

Complete this procedure from the primary site server (Computer 1) only. For log file viewing, you may use the SMS Tracer application or a text editor.

  1. View the contents of D:\SMS\LOGS\HMAN.LOG.

  2. Search for detach.

    3. The first occurrence of detach is highlighted. This line indicates that the child primary site is detaching from the parent site. This message occurred prior to the deinstallation of the child site as a primary, and installation as a secondary site server.

  3. Search for S02.

    4. The first occurrence of the child site code is highlighted. This line indicates that the child primary site is being deleted from the sites table as a result of the detaching. Later lines indicate the forwarding of its site control file to the parent site.

NOTE

You may need to search for the child site's site code several times to arrive at the appropriate line.

  1. Search for Secondary.

    2. The first occurrence of Secondary is highlighted. This line is a logged status message. The previous few lines indicate a new child site is reporting to the local site.

  2. Open DDM.LOG.

    3. Notepad displays the contents of the SMS Discovery Data Manager's log file.

  3. Search for updating site S03.

    4. This line indicates it is updating the child site that is reporting to the local site.

In the following steps, you will use SMS status messages generated by the site server installation. You can use these steps throughout the rest of the exercises in this book to view status messages generated by any SMS components.

NOTE

Complete this procedure from the primary site server (Computer 1) only.

  1. Display the status messages for SMS_HIERARCHY_MANAGER.

    2. Notice messages with IDs of 3306. These messages describe the processing of site control files. There are many in the status system. Look for messages that occur around the time of the child attaching to the parent. You should find messages for the child primary site as well as the child secondary site.

  2. Open the details for one of the messages.

    3. The Status Message Details dialog box appears. Notice the reference to the child site code under Description.

  3. Close the Status Message Details dialog box.

  4. Display the status messages for SMS_DISCOVERY_DATA_MANAGER.

    5. Notice messages with IDs of 2611 and 2634. These messages describe the process of updating assignment rules, and the resumption of normal discovery data record (DDR) processing. These events occurred as the child site discovery data was sent to the parent site for processing.

  5. Close the SMS Status Message Viewer window.

In the following steps, you will view SMS status messages generated by the secondary site server installation.

NOTE

Complete these steps from the primary site server (Computer 1) only.

  1. Select the Site Status node. This node is below the System Status node.

  2. From the Action menu, select Refresh.

    3. Notice two sites now appear: the local site and the secondary site.

  3. Select S03 — Secondary Site 3.

  4. From the Action menu, select Show Messages and then choose All.

    5. The SMS Status Message Viewer for S03 appears displaying all messages received from the child site. Notice a message with an ID of 4000. This message describes the replication of data to the parent site.

  5. Close the SMS Status Message Viewer window.

Related

Категории