The Quick and Cheap Steps to Perform a Lab Installation of SMS 2003 Using Evaluation Code


The below instructions assumes that you have two machines (virtual or physical).  One of the machines will act as the domain controller and SMS client.  HW requirements for the domain controller should meet or exceed the following criteria:

-          P-III @ 1Ghz or better

-          256 MB RAM or better

-          Adequate free disk space (SMS client will take around 10-25MB when installed and collecting inventory information.  You also may want additional free space if you plan to  test out security patch or software deployment to this server)

The other machines will act as the SMS site server.  HW requirements for this server should meet or exceed the following criteria:

-           P-III @ 1 Ghz or better

-          1 GB RAM or better

-          10GB of contiguous free disk space

It is assumed that both machines are on a standard routed IP network with no filters or firewalls separating the two machines.  The network itself can be ‘real’ or ‘virtual’ as long as the servers themselves recognize it.  Internet access for at least the machine that is to be the SMS site server is highly recommended as the ITMU installation instructions below assume this for catalog synchronization.

Before getting started with the below instructions, both of these machines should be running Windows Server 2003 w/SP1 either Standard or Enterprise with the latest patches installed. 

Finally, all steps below assume that you utilize the default Administrator account within the domain who has complete administrative access to the entire forest.

Pre-Install Tasks:

-          Run DCPROMO on one of the servers to create an AD Forest.  You can name the domain anything you like but we will refer to the domain name as ‘SMSDOM.LOCAL’ and the domain controller as ‘SMSDC’.

-          Join the other Windows Server to the newly created Domain.  This server will be your SMS Primary Site Server.  We will refer to this server in this document as ‘SMSServer’.

-          Create the following user accounts in the SMSDOM.LOCAL domain using ADU&C:

o   zSMSClientInstall

§  Add this user to the Domain Admins Group

o   zSMSSoftInstall

§  Add this user to the Domains Admins Group

-          In the SMSDOM.LOCAL domain, modify the permissions on the ‘System’ Container using ADU&C:

o   Open the ADU&C on SMSDC.

o   You may need to Select View => Advanced Features in order to make the ‘System’ container visible within ADU&C

o   Right-Click the System Container and choose Properties

o   Click the Security tab

o   Click Add… to add a new object

o   Click Object Types… and check ‘Computers’ and click OK

o   Type ‘SMSServer$’ and click Check Names and click OK

o   With the SMSServer account highlighted, check the ‘Allow’ checkbox for ‘Full Control’

o   Click the Advanced button

o   Select the SMSServer account and click the ‘Edit…’ button

o   Select ‘This object and all child objects’ in the ‘Apply onto:’ dialog box and click OK

o   Click OK two more times to confirm the changes

-          On SMSServer, add the following Windows components by going to Control Panel => Add/Remove Programs => Add/Remove Windows Components:

o   Add ASP.NET under the Application Server Component – this will automatically add some dependent components which are also needed

o   Add ‘Background Intelligent Transfer Service (BITS) Server Extensions’ under the Application Server => Internet Information Services (IIS) sub-component

o   Click OK and Next to Install the components that have been added – note that you may need to tell the wizard where to find your W03 i386 bits.

-          On SMSServer, set the WebDAV extensions to ‘Allow’:

o   Open the IIS Manager MMC

o   In the Web Services Extension folder, highlight WebDav and click the Allow button

o   Close the IIS Manager MMC

-           Download all of the evaluation code from

o   SMS 2003 w/SP2 Eval:

o   SQL 2005 Eval:

o   Inventory Tool for Microsoft Updates:

o   OSD Feature Pack:

Installation Tasks:

-           Install SQL 2005 Evaluation Edition (~10 – 20 minutes)

o   Run Setup.exe from the Servers folder on the SQL 2005 Evaluation DVD that you downloaded

o   Check to Accept the EULA and click Next

o   Click Install to install the .NET Framework, SQL Client, and Support Files

o   Click Next when complete

o   Click Next Again

o   Confirm that the Configuration Checks have all Passed and click Next

o   Enter Name and Company Information and click Next

o   On the Components screen check only ‘SQL Server Database Services’

o   Optional:  Add Management Tools:

§  Click The Advanced button

§  Under the Client Components feature Select Install for the Management Tools component and click Next

o   Leave the default of ‘Default Instance’ and click Next

o   On the Service Account page, select ‘Use the built-in System account’ and choose ‘Local system in the dialog and click Next

o   Choose Windows Authentication Mode and click Next

o   Accept the default SQL collation and click Next

o   Optionally select to send error reports or feature usage to MSFT (this is NOT required) and click Next

o   Review your choices and click Install

o   SQL 2005 will now install.  Click Next then Finish when prompted


-          Install SMS 2003 w/SP2 Evaluation Edition (~10-15 minutes)

o   After expanding SMS2003_SP2_EVAL.EXE, run autorun.exe from the SMS 2003 w/SP2 source.

o   Select ‘SMS 2003 Service Pack 2’ from the splash screen to install SMS 2003 w/SP2

o   Click Next twice.

o   Choose ‘Install an SMS primary site’ and click Next

o   Choose ‘Custom Setup’ and click Next

o   Click ‘I Agree’ to accept the EULA and click Next

o   Fill in the Name and Organization fields accordingly and click Next (the eval bits should pre-populate the Product Key fields)

o   Enter a three-character site code such as ‘SMS’, and Site Name and click Next

o   Check the ‘Extend the Active Directory schema’ box and click Next

o   Select ‘Advanced security’ and click Next.

o   Select ‘Do not accept unsigned data’ and click Next

o   Leave the default of ‘100’ for number of SMS clients and click Next

o   Check ‘Remote Tools’ and click Next

o   The ‘Computer running SQL Server’ should already be populated with the name of the server (SMSServer) – leave this default.  Ensure ‘Yes’ is selected to use ‘integrated security’ and click Next.

o   Click Yes to create the SMS site database automatically.

o   Leave the default database name and click Next

o   Leave the default DB path and click Next

o   Leave all of the default settings for ‘Concurrent SMS Administrator Consoles’ and click Next.

o   Review your configuration and click Finish to start the install.

o   Click OK when prompted.

o   Do NOT Continue until you see the ‘System Management’ container within the ‘System’ container in ADU&C – this may take a few minutes after the installation completes.


-          Configure SMS 2003 for Testing (~30 minutes)

o   Set the AD Site as an SMS boundary:

§  On SMSServer, open the SMS Administrator console

§  Navigate to Systems Management Server => Site Hierarchy => [Site code] – [Site Name]

§  Right-click [Site code] – [Site Name] and click Properties

§  Click the Site Boundaries tab

§  Click the yellow ‘*’ to add a new boundary.

§  Choose ‘Active Directory site’ as the Boundary Type.

§  Type the following EXACTLY in the Site Name:  Default-First-Site-Name

§  Click OK to add the new boundary

§  Click OK to close the Property Page

o   Configure the ‘Push’ Client Install Account

§  Navigate to SMS => [Site Code] => Site Settings => Client Installation Methods

§  Double-click Client Push Installation

§  Click the Accounts tab

§  Click the yellow ‘*’ to add an account

§  Type ‘SMSDOM\zSMSClientInstall’ in the ‘User name:’ dialog

§  Type and confirm the password for the account

o   Configure the Software Installation Account

§  Navigate to SMS => [Site Code] => Site Settings => Component Configuration

§  Double-click Software Distribution

§  Click the ‘Set…’ button in the Advanced Client Network Access Account section (NOT the Legacy… section)

§  Enter ‘SMSDOM\zSMSSoftInstall’ for the User name

§  Enter and confirm the password for this account

§  Click OK twice to add the account and close the property page

o   Define and install the appropriate Site Systems

§  Navigate to SMS => [Site Code] => Site Settings => Site Systems

§  Double click \\SMSServer

§  Click the Reporting Point tab and check ‘Use this site system as a reporting point’

§  Click the Server Locator Point and check ‘Use this site system as a server locator point’

§  Click the Distribution Point tab and check ‘Enable Background Intelligent Transfer Service (BITS)

§  Click the Management Point tab and check ‘Use this site system as a management point’

§  Click OK

§  Click Yes when asked if it is OK to make this site system the default management point

o   Confirm that the Management Point is installed and running before continuing:

§  Navigate to SMS => System Status => Site Status => [Site code – Site Name] => Component Status

§  Right-click SMS_MP_CONTROL_MANAGER and select Show Messages => All

§  Confirm that a message with ID of 500 and a Description of ‘This component started.’ appears

§  Click OK and close the status message dialog

o   Configure SMS Client Agents

§  Navigate to SMS => [Site Code] => Site Settings => Client Agents

§  Double-click ‘Hardware Inventory Client Agent’

·         Check ‘Enable hardware inventory on clients’

·         Select ‘Simple schedule’ and ‘1 Hours’

·         Click OK

§  Double-click ‘Software Inventory Client Agent’

·         Check ‘Enable hardware inventory on clients’

·         Select ‘Simple schedule’ and ‘1 Hours’

·         Click OK

§  Double-click ‘Remote Tools Client Agent’

·         Check ‘Enable Remote Tools on clients’

·         Check ‘Manage RA settings’ and ‘Override RA user settings’ in the Remote Assistance section

·         Click the Policy tab

·         In the Remote Assistance section select ‘Full control’ for ‘Level of access allowed’

·         Click the Notification tab

·         Select ‘When a session begins and ends’ for the ‘Play a sound’ section

·         Click OK

§  Double-click ‘Advertised Programs Client Agent’

·         Check ‘Enable software distribution to clients’

·         Check ‘New program notification icon opens Add or Remove Programs’

·         Click the Notification tab

·         Check ‘Display a notification message’

·         Click OK

§  Double-click ‘Software Metering Client Agent’

·         Check ‘Enable software metering on clients

·         Click OK

o   Configure Discovery Methods

§  Navigate to SMS => [Site Code] => Site Settings => Discovery Methods

·         Double-click Active Directory System Discovery

·         Check ‘Enable Active Directory System Discovery’

·         Click the yellow ‘*’ to add a container

·         Choose ‘local domain’

·         Click OK

·         Highlight the SMSDOM domain and click OK

·         Click the Polling Schedule tab

·         Check ‘Run discovery as soon as possible’

·         Click OK

o   Confirm that SMSServer and SMSDC are discovered:

§  Navigate to SMS => Collections

§  Right-click ‘All Systems’ and select All Tasks => Update Collection Membership

§  Click OK

§  Double-Click All Systems

§  With All Systems highlighted, hit F5 to refresh the view.  Hit F5 again if the hour glass icon on All Systems still persists

§  You should now see SMSServer and SMSDOM appear within the All Systems Collection.  If not, repeat the process of updating the collection membership in this section

o   Push the SMS Client to SMSServer and SMSDC

§  Navigate to SMS => Collections

§  Right-click ‘All Systems’ and select ‘All Tasks’ => ‘Install Client…’

§  Click Next

§  Select ‘Advanced Client’ and click Next

§  Check ‘Include domain controllers’ and click Next

§  Click Finish

In 5-10 minutes, both machines should show in the ‘All Systems’ collection as having the client installed.  To confirm this, repeat the task of updating the collection membership above.  Several minutes after this, both machines’ HW and SW inventories should appear in the SMS database.  At this point, the basic SMS installation is complete.  You can add any test machines to your test domain and either manually install the SMS client or push the SMS client to these machines once they are discovered during the AD System discovery polling schedule (which you can also force to ‘as soon as possible).

-           Install the ITMU (~30 minutes)

o    Expand the SMS2003ITMU_ENU.EXE

o   Navigate to the folder you expanded to and run SMSITMU.MSI

o   Click Next

o   Select ‘I accept the license agreement’ and click Next

o   Click Next to accept the default installation location

o   Enter SMSServer (or the name of your SMS site server) as the Synchronization host computer and click Next

o   Accept the defaults and click Next twice

o   Click Next to begin the installation.  After installation, SMS will immediately start synchronizing the Update catalog – this can take 10 – 30 minutes. 


-           Install the OSD FP (~5 minutes)

o    NOTE:  the ITMU must be done synchronizing before the OSD FP can be installed (only one MSI can run at any given time)

o   Expand the SMS2003OSDFPUpdate.exe

o   Navigate to the folder you expanded to and run OSDeployment_Setup.EXE

o   Click Next

o   Select ‘I accept the license agreement’ and click Next

o   Read the security warning and click Next

You are done and ready to go!!!

Comments (3)

  1. Anonymous says:

    Wow – just noticed that it has been a while since my last post – sorry about that as I know so many of

  2. Anonymous says:

    Worked perfectly.  I had a test environment up and running in less than a hour!

  3. your to says:

    This is a wonderful opinion. The things mentioned are unanimous and

    needs to be appreciated by everyone.


    <a href=" " rel="dofollow">your to</a>

Skip to main content