SMS-PROD Installation and Configuration


  1. Extending the SMS Schema

  1. Setting a security mode

  1. Assigning SMS console permissions

  1. Configuring addresses and senders

  1. Configuring client agents

  1. Setting up connection accounts

  1. Configuring client discovery methods

  1. Installing SMS clients

  1. Adding secondary and primary sites – only primary site is required

  1. Adding site systems – not required

  1. Removing sites

Schema extension had been performed during pvalentino-SMS install so it is not required for the new installation

Install SMS 2003 Server


  1. Servername – pvalentino-SMSII

  1. IP –

  1. GW -

  1. DNS – and 47.20

  1. WINS – and 47.21

  1. iLO –

  1. 2003 Standard Server Installation Key:

rbrbc rvjcr 96ddt 4xx4b tydhm

  1. IIS, ASP.NET, BITS, and WebDAV

Drive Array Distribution


Array A (4 disks) Raid 5

  1. OS on C: @ 16GB

  1. SMS on E: @ 16GB

  1. Utilities & Pagefile on F: @ 8GB

  1. DB on G: @ 30GB

  1. Packages on H: @ 134


Array A (2 disks) Raid 1

            1. OS on C: @ 16GB

            1. SMS,SQL on D: @ remainder of space

Array B (4 or 6 disks) Raid 5

            1. Backup OS on E:

            1. Utilities on F:

SQL database on G: (if SQL is on same server as SMS)

External Array 9 disks or more

Array C (2 disks) Raid 1 containing SQL transaction logs

Array D (5 disks or more) Raid 5 containing OS images and SMS packages

Memory Configuration

          • 4GB using the /3gb switch in boot.ini on the pvalentino-SMSII SQL server

Network Connections

          • Dual 100MB network link is acceptable for SQL and SMS running on same box although GB is preferred

Install SQL 2000 until SP3a

NOTE: SMS 2003 supports only the SQL Server default instance. SQL Server named instances are not supported in SMS 2003. This applies only to SQL Server 2000 or later. For more information, see the SQL Server Help.

          • Install DB Components

          • Local Computer

          • Default

          • Accept Licence

          • Server and Client Tools

          • Choose Default

          • change Program files path to E:MSSQL

          • change Data Files path to G:MSSQL

          • Keep default collations

          • Keep default Network Libraries settings

          • per seat 800 devices

          • Install SP3a from D:x86setupsetupsql.exe

          • Choose Windows Authentication Mode

          • Upgrade MS Search and Apply SQL Server SP3a

          • Don't send reports to MS

          • Added pvalentino-SMSII$ Computer Account with Full Control to the System Management Container and all child objects in adsiedit.

    • Create Query in Domain Container: root of search DC=admin,DC=state,DC=mn,DC=us and query string of cn=System*

    • Run the Query and locate CN=System Management

    • Right-click CN=System Management and select Properties

    • Select the Security tab and click Add, then click Object Types and check off the Computers Option

    • Click Add and enter pvalentino-SMSII$ to add the SMS computer account, then select Full Control

    • Click Advanced, highlight pvalentino-SMSII$ and then click Edit

    • Under Apply onto: select This object and all child objects

Installation of Primary Site Server

  1. Run autorun.exe from the SMS installation CD and select SMS 2003 from the setup screen to begin installation.

  2. Enter Name: of pvalentino and other fields are pre-populated.

  3. Don't select option to extend schema

  4. Choose Advanced Security

  5. Select Remote Tools and Change Path to E:SMS by clicking Browse and entering the correct path.

  6. Enter pvalentino-SMSII which is running SQL locally and leave default option of Yes for Windows Authentication mode

  7. Select Yes to automatically create the database.

  8. Accept default database name of SMS_SC1

  9. Change Number of SMS Administrator consoles: to 10 and leave default of 100 for SQL Server connections.

  10. Finish

To run the SMS 2003 SP1 Deployment Readiness Wizard on a Primary Site

  1. Start DRW.exe on pvalentino-SMSII.

  2. On the Welcome page, click Next.

  3. On the Tests page, select the tests that you want to run and then click Next.

  4. On the Completing the Systems Management Server 2003 Deployment Readiness Wizard page, click Finish.

Test the Database Upgrade Process

With the /testdbupgrade setup switch, you should test the SMS site database upgrade on a backup copy of the SMS site database, as in the following example:

Setup.exe /testdbupgrade SMS_SC1

After successfully running the database upgrade test, you are assured that the database portion of the upgrade process will be successful. You can review the results of the test in SMSsetup.log, which is in the root of the system drive.

To start the upgrade process:

1. Run Setup.exe from the SMS 2003 SP1 Upgrade product media.

2. If you have not already run DRW, setup prompts you to run DRW. If DRW completes with no errors, the upgrade continues. If DRW records any error, you must first correct the error before you can complete the upgrade.

3. All SMS services are uninstalled and then reinstalled on all SMS site systems.

Wait 30 Minutes then Install SMS SP2

  1. Execute autorun.exe in the SMS SP2 folder

  2. Select Do not accept unsigned data option

  3. Continue with all default options to the finish

Admin Console

Site Boundaries

  1. Drill down to Site Hierarchy and right-click SC1 – Pvalentino

  2. Click the site boundaries tab and click the yellow * to add the subnpvalentino and Active Directory Sites shown below

Adding Site Systems

Open SMS Admin console and drill down to the Site Settings branch for the primary site. Choose \pvalentino-SMSII in the site system roles in the right pane. Double-click it to open the properties box. Click the tab for the role you want to add.

Reporting Point:

To select the RP role for server, click the Reporting Point tab and place a check box in the Use This System As a Reporting Point check box. IIS must already be installed on the server before enabling this role.

Server Locator Point:

Click the Server Locator Point tab and select Use this site system as a server locator point. Again, IIS must be installed on server before this option can be enabled successfully.

Management Point:

Only one server per site can have the Management Point role. place a check box in the Use This System As a Management Point. The MP component takes significantly longer than the others to install. IIS, ASP.NET, BITS, and WebDAV components are required before this can be installed on the server. Troubleshoot installation problems with MPSetup.log.

Client Access Point:

There must be at least one CAP configured per site, even if there are no legacy clients assigned to the site. Enable in same manner as other Points.

Distribution Point:

DPs require adequate disk space for all the SMS packages required and need to be protected from slow WAN access.

To install the DP on a specific drive on a server, create a SMSPKG folder on that drive and share it, being sure to allow appropriate permissions. Specify New Server Share Site System and configure the DP for that location. The DP will create a share below the specified location and share it out to clients as the SSPKGx$ share that will contain the software packages.

Be sure to enable BITS.

DPs are typically grouped by physical (North American DPs) or logical (low-bandwidth DPs) groupings.

Enable as a Protected Distribution point to protect the DP from clients over slow WAN or wireless links.

Turned on the following on pvalentino-SMSII according to steps above:

  • Management Point

  • Client Access Point

  • Distribution Point just local, enabled BITS

  • Server Locator Point

  • Reporting Point

Upgrade SQL to 2005

  1. Insert SQL 2005 Standard CD Disk 1 and select Install > Server Components, tools, Books online, and samples link

  2. Enter pvalentino for Name: and Company: under Registration Information screen

  3. Choose Advanced, keeping all defaults except add Management Tools under Client Options

  4. Change Service Account setting to Use the built-in System account Local system

  5. Do not check to enable error and usage reporting.

  6. Reboot Computer

Install SQL Server 2005 SP1

  1. Insert SQL 2005 SP1 CD and select all default options to the end

  2. Finish

  3. Reboot Computer

Assigning Advanced Clients to the new primary site from the Command Prompt

You can assign Advanced Clients to SMS sites by running a script at the command prompt. The Advanced Client has a scripting object (Microsoft.SMS.Client) that you can use to do this. This object is installed with the Advanced Client software.

Set smsclient = CreateObject("Microsoft.SMS.Client") oldsite = smsclient.GetAssignedSite wscript.echo oldsite smsclient.SetAssignedSite("SC1")

and to return to auto assignment replace last line of code above with


Removing the Advanced Client if there are problems

Only a user with administrative credentials on the computer can remove the Advanced Client software.

Remove the Advanced Client software by using the Ccmclean.exe tool. This tool is available for download on the Microsoft Web site at


If the client is installed on a management point, use the following syntax to prevent

Ccmclean.exe from removing the management point:

Ccmclean.exe client

Use Client Push Installation to Install SMS Advanced Client

The minimum requirement for SMS 2003 SP2 is:

  1. Windows 2000 SP4

  2. Default shares ADMIN$, IPC$

  3. Server service must be started

  4. Remote Registry Service must be enabled

  5. WMI and BITS must be enabled and running

In the Administrator console drill down through the Site Database and Site Hierarchy nodes to the site that you wish to configure, expand the Site Settings node, and expand Client Installation Methods. Right-click Client Push Installation and select Properties to open the Client Push Installation dialog box.

Place a checkmark in the Enable Client Push Installation to Assigned Resources check box to automatically push the Advanced Client out to clients.

If there are machines that fail to install via the Client Push method then a Client Installation Script used as a Machine Startup Script like the following could be customized to the environment to install the advanced client.



Option Explicit

Dim FSO, WSHShell, SysFolder, ClientInst, objNetwork

Dim colSystemEnvVars, computerName

Set up object env

Set WSHShell = WScript.CreateObject(“WScript.Shell”)

Set FSO = CreateObject(“Scripting.FileSystemObject”)

Set objNetwork = WScript.CreateObject(“WScript.Network”)

Set colSystemEnvVars = WSHShell.Environment(“System”)

Get Computer Name for Logging

computerName = objNetwork.ComputerName

Read System32 Folder location into variable

Set SysFolder = fso.GpvalentinopecialFolder(1)

Check to see if SMS2003 Client exists

If FSO.FileExists(SysFolder & “ccmccmexec.exe”) Then

Msgbox “Client Already Installed”



end if

Msgbox “Installing Client”

Launch the SMS2003 client install, client access PointINST.exe, don’t wait for exit

WSHShell.Run \SITESERVERNAMESMSClienti386capinst.exe, 1, false





Imaging Computers with Advanced Client Preinstalled

Can be done automatically with MS Business Desktop Deployment (BDD) Solution Accelerator or:

  1. Chose system to use as a Base or Gold Image and install the Advanced Client using CCMSetup.exe but with the CCMSTARTSERVICES=FALSE option

  1. Verify that SMS Agent Host is not running and if it is run Net Stop CCMEXEC

  1. Execute the Ccmdelcert.exe tool from the SMS 2003 toolkit 2

  1. Shut down the base gold system

  1. Use preferred imaging software to create the image of the system

  1. Test the image by restoring to a test destination PC

Use the following VB Script in SMS Advertisement to increase the TotalSize value for the Client Cache to allow for system images. Adjust size according to needs in MB.

Set ui = CreateObject(“UIResource.UIResourceMgr”)

Set cacheInfo = ui.GetCacheInfo

cacheInfo.TotalSize = 2000 ‘ Changes max to approx 2GB

Client Installation Troubleshooting Paths:

On Server



On Client



To remove a site first uninstall SMS legacy and Advanced Clients.


  1. Manually with SMSMAN.exe

  1. Automatically by removing site from the Site Boundaries Tab of Site Database > Site Hierarchy > Right-click site name and choose Properties


  1. Msiexec.exe client.msi /x /qb-

  1. CCMClean.exe /client /q /retry:5,60

No comments: