Previous Section
 < Day Day Up > 
Next Section


Installing a Primary Site Server

Now that you have created a viable deployment strategy for your SMS 2003 site, decided how to install and configure your SQL Server, and confirmed the hardware and software requirements necessary for a successful installation of SMS 2003, it’s time to begin the installation process itself. This section will concentrate on the installation of an SMS 2003 primary site server. Installing secondary site servers and other site system roles will be discussed in Chapter 3, “Configuring Site Server Properties and Site Systems,” and Chapter 4.

Installation Options

You can install your SMS 2003 site server using a variety of techniques and options. You may install directly from the CD, or you can first copy the source files from CD to the local hard disk of the proposed site server or a network drive. If you choose to copy the source files to a drive location, be sure to copy the entire SMS 2003 CD, as the installation process might require files located in support folders. You can also run a scripted automated setup. Figure 2.1 shows the autorun screen that appears when you insert the SMS 2003 CD. Notice that besides starting the setup wizard, you can also run the integrated Recovery Expert as well as view documentation included as part of the Online Library.

Click To expand
Figure 2.1: The setup screen that appears when you first insert the SMS 2003 CD.

Once you have located the source files, you can run the installation interactively through the Systems Management Server Setup Wizard by inserting the SMS 2003 CD and choosing SMS 2003 from the autorun menu shown in Figure 2.1, or, if you prefer to run Setup.exe from the \SMSSetup\Bin\I386 folder or choose to run an unattended setup, you can also initiate the installation from a Windows command prompt. The command-line syntax is shown here:

SETUP [/?] [/SCRIPT scriptname] [/UPGRADE] [/NODISKCHECK] [/NOACCTCHECK]

The command-line method provides five switch options to initiate the setup process under different circumstances, as outlined in Table 2.2. If you execute the SMS 2003 Setup.exe from the command line, you’ll still launch the Systems Management Server Setup Wizard, which presents you with a series of nice, “user-friendly” installation pages that guide you every step of the way.

Table 2.2: Command-line switch options

Switch

Description

/?

Displays a pop-up dialog box listing that describes each switch along with the command-line syntax.

/SCRIPT scriptname

Allows you to specify a path and script file, which provides the different pieces of information required during setup for unattended installation.

/UPGRADE

Allows to you specify an unattended upgrade from an earlier version of SMS.

/NODISKCHECK

Allows you to perform the installation without having SMS 2003 check for available disk space first. Assumes that you have already confirmed that you have the required amount of disk space available.

/NOACCTCHECK

Allows you to perform the installation without having SMS 2003 check the specified service account for the appropriate level of permission and rights. Assumes that you have already created the account and have given it the appropriate administrative permissions and the Log On As A Service user right.

[Identification]
Action=InstallPrimarySite

[Options]
FullName=Steven Kaczmarek
OrgName=Enact Solutions Corp
ProductID=123-4567890
SiteCode=S00
SiteName=ENACT Primary Site
SiteDomain=ENACTCorp
SecurityMode=Standard
ServiceAccount=smsservice
ServiceAccountDomain=ENACTCorp
ServiceAccountPassword=Scruffy&4315Glem
NumOfClients=100
OptionalUnits=Remote Control
OptionalUnits=Scripts
SMSInstallDir=F:\SMS
InstallSQLServer=0
NumberOfAdminUI=5
SDKServer=ENACT1

[SQLConfigOptions]
SQLServerName=ENACT1
SQLServerVersion=2000
UseSQLIntegratedSecurity=1
CreateSQLDevice=1
DatabaseName=SMS_S00
DatabaseDevice=SMSdata_S00
LogDevice=SMSlog_S00
SQLDevicePath=F:\MSSQL\SMSDATA
NumberOfSqlConnections=75
AutoConfigSqlConnections=1

Express vs. Custom Setup

When you begin the setup process on a server, you’ll be presented with two installation options: Express Setup and Custom Setup. Express Setup installs most SMS 2003 components and features, enables all discovery methods except Network Discovery, enables all client agents except Software Inventory and Software Metering, and creates all applicable service accounts depending on the security mode you choose. Custom Setup lets you choose which components and features to install. Custom Setup doesn’t automatically enable any discovery methods (except Heartbeat Discovery) or client agents.

Table 2.3 describes which SMS components are available with each setup option. Table 2.4 outlines the default values that are set during an express installation versus a custom installation. These features, discovery methods, installation methods, and client agents have additional options that you can configure; these elements are discussed in their respective chapters later in this book.

Table 2.3: SMS 2003 setup option defaults

Option

Express Install— Primary Site

Custom Install— Primary Site

Secondary Site Installation

SMS site server

Installed

Installed

Installed

SMS Administrator Console

Installed

Installed

Available

Remote Tools

Installed

Optional

Optional

Package automation scripts

Installed

Optional

Not Available

Table 2.4: SMS 2003 components installed during setup

Feature

Express Install

Default Value

Custom Install

Discovery Methods

     

Windows Networking User Discovery

Enabled

Once a day at midnight

Disabled

Windows Networking User Group Discovery

Enabled

Once a day at midnight

Disabled

Heartbeat Discovery

Enabled

Once a week for Custom Setup; once a day for Express Setup

Enabled

Network Discovery

Disabled

No default; configured by administrator

Disabled

Active Directory System Discovery

Enabled if Advanced Security mode is selected

Once a day at midnight

Disabled

Active Directory System Group Discovery

Enabled if Advanced Security mode is selected

Once a day at midnight

Disabled

Active Directory User Discovery

Enabled if Advanced Security mode is selected

Once a day at midnight

Disabled

Installation Methods

     

Client Push Installation

Enabled

N/A

Disabled

Client Agents

     

Advertised Programs Client Agent

Enabled

Polls every 60 minutes for advertised programs; scheduled programs have 5-minute countdown; user can make changes to settings

Disabled

Hardware Inventory Client Agent

Enabled

Once a day

Disabled

Software Inventory Client Agent

Disabled

N/A

Disabled

Remote Tools Client Agent

Enabled

All remote options enabled; user permission required; user notified; user can make changes to settings

Disabled

Software Metering Client Agent

Disabled

N/A

Disabled

Express Setup is a fast and easy way to install SMS 2003 and is recommended for evaluation installations or test environments. Express Setup requires that SQL Server 7.0 Service Pack 3 or later or SQL Server 2000 Service Pack 3a or later be already installed on the same server. It then creates and configures SQL Server database files for SMS, sets the SQL Server parameters (as discussed in the section “SQL Server Requirements” earlier in this chapter), and creates all applicable service accounts. When installation is complete, the site server will assume the site system roles of CAP and distribution point.

The Custom Setup option installs SMS 2003 with the basic site server and SMS Administrator Console installed. All other SMS 2003 features and components are options that you can select as desired. You can always leave an option cleared and install it at a later time. If the option is selected, it will be installed, but not enabled, by default. Once an option is installed, however, you can’t uninstall it without removing and reinstalling SMS 2003. The site server will assume the site system roles of CAP and distribution point.

Custom Setup doesn’t require that SQL Server 7.0 or SQL Server 2000 be installed on the same server (if SQL Server isn’t already available). However, if SQL Server has been installed on the same server, Custom Setup creates and configures SQL Server database files for SMS, sets the SQL Server parameters, and creates all applicable service accounts.

Running Setup

To install a primary site server, follow these steps:

  1. Insert the SMS 2003 CD and choose SMS 2003 from the autorun menu (shown in Figure 2.1), or in Windows Explorer navigate to the SMS 2003 source files and execute Autorun.exe to display the autorun menu or execute Setup.exe from a command prompt.

  2. The Welcome page appears, as shown in Figure 2.2.

    Click To expand
    Figure 2.2: The Setup Wizard Welcome page.

  3. Click Next to display the System Configuration page, as shown in Figure 2.3. At this time, Setup checks to see whether you have any earlier versions of SMS installed or if the server is already functioning as an SMS site system.

    Click To expand
    Figure 2.3: The System Configuration page.

  4. Click Next to display the Setup Options page, as shown in Figure 2.4. If no current installation of an SMS site server or site system is detected, the first three options will be enabled. You can install a primary site, a secondary site, or just the SMS Administrator Console and related tools. If an existing SMS 2003 site server is detected, the last three options will be enabled. In this case, you can upgrade the existing installation by adding additional SMS components, remove SMS 2003, or modify or reset the installation—for example, by changing service account names and passwords or rebuilding a site control file. If the Setup Wizard detects a site server installation for an earlier version of SMS, only the Upgrade An Existing SMS Installation option will be enabled. For this example, select Install An SMS Primary Site.

    Click To expand
    Figure 2.4: The Setup Options page.

    Note 

    If the Setup Wizard detects an existing installation of an SMS site system such as a CAP or a server locator point, you will not be able to continue the installation until you remove that site system from the SMS site it is a member of.

  5. Click Next to display the Installation Options page, as shown in Figure 2.5. Choose Express Setup or Custom Setup.

    Click To expand
    Figure 2.5: The Installation Options page.

  6. Click Next to display the License Agreement page, as shown in Figure 2.6. Read this agreement carefully and signify your acceptance by selecting I Agree.

    Click To expand
    Figure 2.6: The License Agreement page.

  7. Click Next to display the Product Registration page, as shown in Figure 2.7, and enter the Name, Organization Name, and the CD Key located on the back of your SMS 2003 CD case.

    Click To expand
    Figure 2.7: The Product Registration page.

  8. Click Next to display the SMS Site Information page, as shown in Figure 2.8, which asks you to supply the three-character site code you want to assign to this site, a descriptive site name, and the Windows domain in which you’re installing the site.

    Click To expand
    Figure 2.8: The SMS Site Information page.

    The site code is limited to three characters and must be unique across your SMS hierarchy. The site name is descriptive, limited to 50 characters (including spaces) and should reflect the site’s location or function, such as Contoso Corp Central Site or Finance Primary Site. It’s usually a good idea to specify whether the site is central, primary, or secondary. Once this information is entered, it sticks.

    Caution 

    Do not use the same site code name for more than one site in your enterprise. If you’re sharing or replicating WINS between two Active Directory forests and you use the same site code in your production SMS site as the site code of a pilot SMS site in a different forest, the WINS registrations for the sites might overwrite each other. This can cause the Advanced Client to use the wrong WINS database and therefore the wrong management point, causing the Advanced Client policy to be reset in the wrong SMS site. The Advanced Client is no longer a member of the pilot site and can’t participate in the pilot project.

    Caution 

    If you need to change the site code, site name, or domain name later, you’ll need to remove this installation of SMS and reinstall it.

  9. Click Next to display the SMS Active Directory Schema page, as shown in Figure 2.9. Here you have the option to extend the Active Directory schema to support the use of automatic site assignment or roaming boundaries for advanced security. As the page implies, the account that you’re performing the installation under must be a member of the Schema Admins group for your forest. In addition, if you’re installing SMS 2003 on a domain controller, you’ll need to use the Windows 2000 Active Directory Schema administration MMC snap- in to allow schema modifications to take place through that domain controller. If you have met these requirements, select the Extend The Active Directory Schema checkbox and then click next. If you’re unable to update the schema, you can update it after installation. In this case, don’t select this option; just click Next.

    Tip 

    You can extend the Active Directory Schema later by running the Extadsch.exe command line tool from the SMS\bin\i386 folder on the site server after you have met the requirements specified in step 9.

    Click To expand
    Figure 2.9: The SMS Active Directory Schema page.

  10. On the SMS Security Information page, shown in Figure 2.10, select the security mode that you plan to implement. If you choose Advanced, go on to step 11; advanced security mode doesn’t require that a service account be created. If you choose Standard, enter the name of the account you’d like SMS to create, for example, SMSService. SMS will automatically assign it the appropriate group memberships and user rights. If you have already created this account using Active Directory Users And Computers, specify it here. Be sure you have already assigned the account the appropriate group memberships in the SMS site domain (Domain Admins, Domain Users, Administrators) and have given the account the Log On As A Service user right using the local group policy editor. Enter and confirm a password (preferably something other than password).

    Tip 

    Always enter account information in SMS using the format domain/ account.

    Click To expand
    Figure 2.10: The SMS Security Information page.

    Note 

    The SMS service account must be a member of the local Administrators group on the site server, the Domain Admins group, and be given the Log On As A Service User Right.

  11. Click Next to display the SMS Primary Site Client Load page, as shown in Figure 2.11. Enter the number of SMS clients that this site will manage, as you determined in your deployment strategy. The number that you enter here ultimately affects the size of the SQL database that SMS will create or that you have created ahead of time. An incorrect database device or file size will cause the installation to fail.

    Click To expand
    Figure 2.11: The SMS Primary Site Client Load page.

  12. At this point, the installation process will vary depending on whether you chose Express Setup or Custom Setup in step 5 above. Let’s continue first with the Express installation options and then look at the Custom installation options.

Express Installation Options

Follow these steps to perform an express installation of SMS:

  1. Click Next to display the Concurrent SMS Administrator Consoles page, as shown in Figure 2.12, and enter the number of concurrent SMS Administrator Consoles you expect to be running in the site. SQL Server will allocate five user connections for each instance of the SMS Administrator Console in addition to the 50 required by the SMS site server and its components.

    Click To expand
    Figure 2.12: The Concurrent SMS Administrator Consoles page.

  2. Click Next to display the Completing The Systems Management Server Setup Wizard page, as shown in Figure 2.13. Confirm your settings, and then click Finish. You can click the Back button from this and any previous pages to go back and modify your entries—and even to switch from Express to Custom installation. You can also double- click any entry in the text box on this page.

    Click To expand
    Figure 2.13: The Completing The Systems Management Server Setup Wizard page.

  3. If you chose Standard Security in step 10, the Setup Wizard will ask whether it is to create the SMS Service Account for you, if you haven’t already created it. Choose Yes. Setup will then proceed with the SMS installation.

Custom Installation Options

Follow these steps to perform a custom installation of SMS:

  1. If you’re performing a Custom installation, the next page you’ll see after the SMS Primary Site Client Load page will be the Setup Installation Options page, as shown in Figure 2.14. You can select which SMS components you want to install at this time. As you check each option, a brief description is displayed in the Description box.

    Click To expand
    Figure 2.14: The Setup Installation Options page.

    The Setup Wizard will automatically select the NTFS partition with the most free disk space as the installation directory. Click the Browse button to select a different location.

  2. Click Next. The SQL Server Information For SMS Site Database page is displayed, as shown in Figure 2.15. This page requires that you identify the name of the computer running SQL Server, the version (7.0 or 2000) that’s installed, and whether to use Windows Authentication to access the SMS site database. You may choose either Yes, the default, or No. Make your selections as appropriate on this page and click Next. Depending on your selections, one or more of the following steps will follow.

    Click To expand
    Figure 2.15: The SQL Server Information For SMS Site Database page.

  3. If you chose No for the Windows Authentication option, you need to specify the SQL Server Login ID or accept the default sa account and supply the password for SMS to use. In this case the SQL Server Account for SMS Site Database page is displayed, as shown in Figure 2.16. Supply the appropriate information and then click Next.

    Click To expand
    Figure 2.16: The SQL Server Account For SMS Site Database page.

  4. If you choose to create the SMS site database, select Yes in the Creation of SMS Site Database page, as shown in Figure 2.17. Enter the name you’d like to use for the SMS site database or accept the defaults and then click Next.

    Click To expand
    Figure 2.17: The Creation of the SMS Site Database page.

  5. The SMS Site Database Name page is displayed, as shown in Figure 2.18. Enter the name you’d like to use for the SMS site database and then click Next.

    Click To expand
    Figure 2.18: The SMS Site Database Name page.

  6. Clicking Yes in step 4 triggers the display of the SQL Server Directory Path For SMS Site Database page, as shown in Figure 2.19. Enter the location and path to the directory in which you intend to store the database. Again, the Setup Wizard defaults to the partition with the most free disk space.

    Click To expand
    Figure 2.19: The SQL Server Directory Path For SMS Site Database page.

  7. Click Next to display the Concurrent SMS Administrator Consoles page, as shown in Figure 2.20, and enter the number of concurrent SMS Administrator Consoles you expect to be running in the site. SMS will add five user connections for each instance of the SMS Administrator Console to its default of 50 when configuring this parameter in SQL Server. If you leave the check box selected that allows the Setup Wizard to automatically configure SQL Server for the correct number of user connections, SMS will dynamically fill in the correct number in the Minimum Number Of SQL Server Connections text box. If you clear the check box, be sure to enter an appropriate number of user connections or your site server might not be able to access the SMS database.

    Click To expand
    Figure 2.20: The Concurrent SMS Administrator Consoles page.

  8. If the SMS site database has been installed on a different server, clicking Next will take you to the SMS Provider Information page, as shown in Figure 2.21. If the SMS site database is installed on the same computer, go on to step 9.

    Click To expand
    Figure 2.21: The SMS Provider Information page.

    Recall from Chapter 1 that the SMS Provider effects access to the SMS database through the WMI Common Information Model (CIM) repository for the SMS Administrator Console. In this page, you specify whether to install the SMS Provider on the site server or the server running SQL. In general, optimum performance access is achieved when the SMS Provider is installed on the server running SQL. However, if doing so would result in poorer performance, if the server running SQL is home to other SMS site databases, or if security on the server running SQL prevents the administrator from directly accessing that computer, you should place the SMS Provider on the site server.

  9. Click Next to display the Completing The Systems Management Server Setup Wizard page, as shown in Figure 2.13, and confirm your choices. You can click the Back button in any of these pages or double-click any entry in the list box to return to a previous page and modify your entries. Click Finish to complete the installation.

    Note 

    If you chose standard security mode during setup, the Setup Wizard will ask whether it is to create the SMS Service Account for you, if you haven’t already created it. Choose Yes. Setup will then proceed with the SMS installation.

If you have followed these steps closely, you have now successfully installed an SMS 2003 primary site server! If you performed a custom installation, you made choices as to which SMS components you wanted to install. The next section discusses what to do when you need to add components to your site server.



Previous Section
 < Day Day Up > 
Next Section