Deploying Windows Server 2003 SP1 with SMS

  • Article

Published : August 1, 2005

This document provides detailed steps on how to prepare Windows Server 2003 SP1 files for deployment, create queries to identify SMS clients ready for the Windows Server 2003 SP1 upgrade, deploy the Windows Server 2003 SP1 upgrade to your SMS clients, and verify that the SMS clients successfully upgraded from Windows Server 2003 to Windows Server 2003 SP1.

Windows Server 2003 Service Pack 1 provides convenient, comprehensive access to the latest updates, enhancements, and new features for Windows Server 2003. Each of these components allows customers to better leverage the enhanced security, reliability, and performance of Windows Server 2003.

Microsoft recommends that a corporate update management solution, such as Systems Management Server 2003 or Windows Server Update Services (WSUS), is used as a best-practice approach for implementing a managed rollout of Windows Server 2003 SP1. This document details the steps necessary to test a deployment of Windows Server 2003 SP1 using SMS. While some procedures in this document focus specifically on SMS 2003 Advanced Clients, most procedures apply to both SMS 2003 Legacy Clients and SMS 2.0.

Note

Windows Server 2003 SP1 is supported by SMS 2.0 SP4 and SMS 2.0 SP5.

This document assumes that you have an understanding of SMS and that you have a working knowledge of software distribution. Additionally, it assumes that your SMS infrastructure is established or that you will establish an SMS infrastructure before you deploy Windows Server 2003 SP1.

Deploying Windows Server 2003 SP1 Using SMS

The following topics in this section provide detailed information about how to deploy Windows Server 2003 SP1 using SMS:

  • How to Prepare Windows Server 2003 SP1 Files

  • How to Identify and Prepare SMS Clients That Are Ready for Windows Server 2003 SP1

  • How to Deploy Windows Server 2003 SP1 to SMS Clients

  • How to Verify Upgrade Success with SMS

The procedures in this section are primarily focused on using SMS 2003 for the Windows Server 2003 SP1 deployment, but SMS 2.0 with SP4 or SP5 can also be used. Steps specific to SMS 2003 or SMS 2.0 are identified within each procedure.

Important

Windows Server 2003 SP1 deployment in SMS 2.0 will not succeed unless the SMS 2.0 SP4 or SP5 version is installed.

How to Prepare Windows Server 2003 SP1 Files

Before you can deploy Windows Server 2003 SP1, you must perform the following procedures on the primary site server.

To obtain and extract the Windows Server 2003 SP1 source files

  1. Create a folder named WS2K3SP1 on the C: Drive.

  2. Copy the Windows Server 2003 SP1 source file (WindowsServer2003-KB889101-SP1-x86-ENU.exe) to the C:\WS2K3SP1 folder by downloading it from the Microsoft Download Center or by using the file from the Windows Server 2003 SP1 CD. This CD is available from Microsoft and can be ordered from the Windows Server 2003 Service Pack 1 on CD Web page.

    Note

    The Windows Server 2003 SP1 file is approximately 329 MB in size.

  3. At a command prompt, type WindowsServer2003-KB889101-SP1-x86-ENU.exe /x from the C:\WS2KSP1 folder and then press ENTER.

  4. Type C:\WS2K3SP1 in the Choose Directory For Extracted Files text box, or browse to this folder by clicking Browse. All Windows Server 2003 SP1 source files are extracted to C:\WS2K3SP1\I386. The \I386 folder is created when the file is extracted.

To obtain the Windows Server 2003 SP1 package definition file

  1. Go to the Windows Server 2003 Service Pack 1 SMS Files Web page on the Microsoft Download Center.

  2. Download the SRSP1sms.exe file to the C:\WS2K3SP1 folder.

  3. Open SRSSP1sms.exe, and extract the SRSSP1.sms file to the C:\WS2K3SP1 folder.

How to Identify and Prepare SMS Clients That Are Ready for Windows Server 2003 SP1

The procedures included in this section enable you to identify and prepare SMS clients that are ready for the Windows Server 2003 SP1 upgrade.

The following procedure creates a Managed Object Format (MOF) file that is used to create an SMS 2003 sample query that identifies SMS Advanced Client computers with sufficient hardware to support an upgrade to Windows Server 2003 SP1. You will use the query in subsequent steps as a membership rule for a collection of computers that receive the Windows Server 2003 SP1 advertisement.

Note

If you do not use this query, you could potentially advertise Windows Server 2003 SP1 to computers that cannot successfully install it, resulting in a failed deployment. However, you can also create your own query using different criteria to identify computers that you can upgrade to Windows Server 2003 SP1.

To create the WS2K3SP1.mof query file

  1. Copy the following code and paste it into Notepad.

    //***********************************************************************

// // Created by SMS Export object wizard // // Wednesday, June 12, 2005 created // // File Name: WS2K3SP1.MOF // // Comments : // // Query to find all SMS client computers running Windows Server // 2003 (no SP) with at least 2 GB of hard drive free space. // //***********************************************************************

// ***** Class : SMS_Query ***** [SecurityVerbs(140551)] instance of SMS_Query { Comments = "SMS 2003 clients running Windows Server 2003 ready " "to upgrade to Windows Server 2003 SP1"; Expression = "select distinct SMS_R_System.NetbiosName, " "SMS_G_System_OPERATING_SYSTEM.Caption, " "SMS_G_System_OPERATING_SYSTEM.CSDVersion, " "SMS_G_System_OPERATING_SYSTEM.OSLanguage, " "SMS_G_System_LOGICAL_DISK.FreeSpace from " "SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM " "on SMS_G_System_OPERATING_SYSTEM.ResourceID = " "SMS_R_System.ResourceId inner join " "SMS_G_System_LOGICAL_DISK on " "SMS_G_System_LOGICAL_DISK.ResourceID = " "SMS_R_System.ResourceId where " "SMS_G_System_OPERATING_SYSTEM.Caption like " ""Microsoft(R) Windows(R) Server 2003%" and " "SMS_G_System_OPERATING_SYSTEM.OSLanguage = 1033 and " "SMS_G_System_OPERATING_SYSTEM.CSDVersion is NULL and " "SMS_G_System_LOGICAL_DISK.FreeSpace > 2048 and " "SMS_G_System_LOGICAL_DISK.DeviceID = "C:""; LimitToCollectionID = ""; Name = "Clients ready for Windows Server 2003 SP1"; QueryID = ""; TargetClassName = "SMS_R_System"; }; // ***** End *****

  1. Save the file in the C:\WS2K3SP1\ folder with the file name WS2K3SP1.mof.

The next procedure creates a MOF file that is used to create an SMS 2003 query to identify SMS Advanced Client computers that do not meet the minimum requirements for the Windows Server 2003 SP1 installation.

The sample query will find all systems that are running Windows Server 2003 but have limited disk space or have a different operating system language than English. You can create your own query using different criteria that identify computers that are not ready to upgrade to Windows Server 2003 SP1.

To create the WS2K3SP1_Fail.mof query file

  1. Copy the following code and paste it into Notepad.

    // *************************************************************************

// // Created by SMS Export object wizard // // Wednesday, June 12, 2005 created // // File Name: WS2K3SP1_FAIL.MOF // // Comments : // // Query to find all SMS client computers running Windows Server // 2003 (no SP) with less than 2 GB of hard drive free space and/or // OS language not English. // *************************************************************************

// ***** Class : SMS_Query ***** [SecurityVerbs(140551)] instance of SMS_Query { Comments = "SMS 2003 clients running Windows Server 2003 NOT " "ready to upgrade to Windows Server 2003 SP1."; Expression = "select distinct SMS_R_System.NetbiosName, " "SMS_R_System.AgentSite, " "SMS_G_System_OPERATING_SYSTEM.Caption, " "SMS_G_System_OPERATING_SYSTEM.CSDVersion, " "SMS_G_System_OPERATING_SYSTEM.OSLanguage, " "SMS_G_System_LOGICAL_DISK.FreeSpace from SMS_R_System " "inner join SMS_G_System_LOGICAL_DISK on " "SMS_G_System_LOGICAL_DISK.ResourceID = " "SMS_R_System.ResourceId inner join " "SMS_G_System_OPERATING_SYSTEM on " "SMS_G_System_OPERATING_SYSTEM.ResourceID = " "SMS_R_System.ResourceId where " "SMS_G_System_OPERATING_SYSTEM.Caption like " ""Microsoft(R) Windows(R) Server 2003" and " "SMS_G_System_OPERATING_SYSTEM.CSDVersion is NULL and " "(SMS_G_System_OPERATING_SYSTEM.OSLanguage != 1033 or " "SMS_G_System_LOGICAL_DISK.FreeSpace < 2048 and " "SMS_G_System_LOGICAL_DISK.DeviceID = "C:")"; LimitToCollectionID = ""; Name = "Clients NOT ready for Windows Server 2003 SP1"; QueryID = ""; TargetClassName = "SMS_R_System"; }; // ***** End *****

  1. Save the file in a folder named C:\WS2K3SP1\ with the file name WS2K3SP1_Fail.mof.

In the following procedure, you import the query from each of the two MOF files that you created previously. One of the queries will be used as the membership rule of the collection for computers that are ready to be upgraded to Windows Server 2003 SP1.

Note

If the queries based on the sample MOF files do not return any results, ensure that hardware inventory is enabled for the site. This sample query determines how much disk free space is available, which is obtained from reported hardware inventory.

To import the query

  1. Start the SMS Administrator Console.

  2. In the console tree, expand Site Database and then click Queries.

  3. Go to the Action menu, click All Tasks, and then click Import Objects to open the Welcome to the Import Object Wizard dialog box.

  4. Click Next to open the Import Object Wizard MOF File dialog box, where you select the MOF file containing the object to import.

  5. Click Browse, and then open WS2K3SP1.MOF from C:\WS2K3SP1\.

  6. Click Next to display the Import Object Wizard Unknown Source dialog box.

Note

You will see a message indicating that the MOF file was created by an unknown source when using the MOF files provided in this document. This message can be ignored as the query will import correctly.

  1. Click Next to open the Completing the Import Objects Wizard dialog box, which indicates the query has been imported. Click Finish to close the wizard.

  2. Repeat steps 3–7, using WS2k3SP1_Fail.MOF in place of WS2K3SP1.MOF.

  3. Click Queries in the console tree, click the Action menu, and click Refresh to refresh the list of queries.

  4. In the console tree, expand Queries and then click Clients ready for Windows Server 2003 SP1.

  5. On the Action menu, clickRun Query. The systems that meet the criteria for upgrading to Windows Server 2003 SP1 are displayed in the details pane. Verify that the expected computers appear in the results pane.

  6. In the console tree, expand Queries and then click Clients NOT ready for Windows Server 2003 SP1.

  7. On the Action menu, clickRun Query. The systems that do not have at least 2 GB of hard drive space or that have a non-English-based operating system are displayed in the details pane.

    Windows Server 2003 SP1 should not be deployed to these systems until they have at least 2 GB of hard drive space. For systems running non-English-based operating systems, the appropriate version of Windows Server 2003 SP1 should be used.

In the following procedure, you create a collection that can be used to target the Windows Server 2003 SP1 installation. For SMS 2003 sites, this collection uses the query that you created previously. For SMS 2.0 sites, you must manually create a similar query to be used in creating the collection or use a predefined collection.

To create the collection

  1. In the console tree, click Collections.

  2. On the Action menu, point to New,and then click Collection to open the Collection Properties dialog box, which displays General settings for the new collection.

  3. In the Name field, type Clients ready for Windows Server 2003 SP1.

    Note

    The name of the query and the name of the corresponding collection do not have to be the same.

  4. In the Comment box, type All SMS 2003 clients with sufficient hardware resources to upgrade to Windows Server 2003 SP1and then click the Membership Rules tab.

  5. Click New Query Rule to open the Query Rule Properties dialog box.

  6. Click Import Query Statement.

  7. Click Clients ready for Windows Server 2003 SP1, and then click OK.

  8. In the Name box, type Clients ready for Windows Server 2003 SP1.

  9. Under the Collection limiting options, click Limit to collection and then click Browse.

  10. Click All Windows Server 2003 Systems, and then click OK to display the Query Rule Properties dialog box, where the All Windows Server 2003 Systems collection is listed as the limiting collection.

    Note

    Ensure that the All Windows Server 2003 Systems collection has been updated and refreshed since adding any new Windows Server 2003 systems to the SMS inventory.

  11. Click OK to open the Collection Properties dialog box, which displays the new membership rule as a query.

  12. Verify that Update this collection on a schedule is selected, and then click OK.

  13. In the console tree, expand Collections.

  14. In the console tree, click Clients ready for Windows Server 2003 SP1, and then on the Action menu, click Refresh. The collection members appear in the details pane. The collection should include the same computers as the Clients ready for Windows Server 2003 SP1 query does. Verify that this collection contains at least one member before proceeding to the next section.

How to Deploy Windows Server 2003 SP1 to SMS Clients

The following sections provide detailed steps on how to prepare for the deployment of Windows Server 2003 SP1 using SMS software distribution, verify the status of each component in the process, manually run the upgrade on an SMS client, and verify a successful deployment.

How to Prepare the Windows Server 2003 SP1 Deployment

The following procedure creates a package and program to advertise to all computers in the target collection. You then assign distribution points for the package and create the advertisement for the package. This is accomplished using the Distribute Software Wizard.

To create the necessary objects and advertise the update program

  1. In the console tree, click the Clients ready for Windows Server 2003 SP1 collection, and then on the Action menu, point to All Tasks.

  2. Click Distribute Software to open the Distribute Software to Collection Wizard dialog box.

  3. Click Next to open the Distribute Software to Collection Wizard Package dialog box, where you choose options for package distribution.

  4. Select Create a new package from a definition, and then click Next to open the Distribute Software to Collection Wizard Package Definition dialog box, where you select the package definition file to use.

  5. Click Browse, and then open C:\WS2K3SP1\SRSP1.sms to display the Distribute Software to Collection Wizard Package Definition dialog box. Notice that Windows Server 2003 SP1 (update.exe) has been added to the list.

  6. Under Package definition, verify that Windows Server 2003 SP1 (update.exe) is selected, and then click Next to open the Distribute Software to Collection Wizard Source Files dialog box, which prompts for source file handling instructions.

  7. Click Always obtain files from a source directory, and then click Next.

  8. In the Distribute Software to Collection Wizard Source Directory dialog box, click Local drive on site server and then click Browse.

  9. In the Browse for Folder dialog box, click C:\WS2K3SP1\I386 and then click OK.

    Important

    Make sure you select C:\WS2K3SP1\I386. If you select another directory, the size of the resulting package might double in size.

  10. In the Distribute Software to Collection Wizard Source Directory dialog box, click Next.

  11. In the Distribute Software to Collection Wizard Distribution Points dialog box, under Distribution points, select the appropriate distribution point(s) and then click Next.

  12. In the Distribute Software to Collection Wizard Select a Program to Advertise dialog box, under Programs, click Automated upgrade from Windows Server 2003 (update and then click Next.

    The next three steps apply to SMS 2.0 only. Skip to step 16 if using SMS 2003.

  13. This step applies to SMS 2.0, only. In the Distribute Software Wizard Advertisement Target dialog box, select Advertise the program to an existing collection and then click Browse.

  14. This step applies to SMS 2.0, only. In the Browse Collection dialog box, select the collection to advertise to and then click OK.

  15. This step applies to SMS 2.0, only. In the Distribute Software Wizard Advertisement Target dialog box, click Next.

  16. In the Distribute Software to Collection Wizard Advertisement Name dialog box, type Windows Server 2003 SP1 Update and click Next to accept the advertisement name.

  17. In the Distribute Software to Collection Wizard Advertise to Subcollections dialog box, select Advertise the program only to members of the specified collection and then click Next.

  18. In the Distribute Software to Collection Wizard Advertisement Schedule dialog box, verify that the current date and time is for the Advertise the program after item.

  19. Verify that No. This advertisement never expires is selected, and then click Next.

  20. In the Distribute Software to Collection Wizard Assign Program dialog box, select Yes. Assign the program, and then in the Assign after box, verify that the current time is listed.

  21. Click Next.

  22. In the Distribute Software to Collection Wizard dialog box, click Finish.

Use the following procedure to verify the configuration of the package, program, and advertisement created by the Distribute Software to Collection Wizard.

To verify package, program, and advertisement configuration

  1. In the console tree, expand Packages.

    Note

    You might need to refresh the display to see the new package.

  2. In the console tree, expand Microsoft Windows Server 2003 SP1 (update.exe) English.

  3. In the console tree, click Programs.

  4. In the details pane, click Automated upgrade from Windows Server 2003 (update, and then on the Action menu, click Properties.

    Note

    The Automated upgrade from Windows Server 2003 (update Program Properties dialog box displays general settings for the program. Notice that the command line is: update\UPDATE.EXE /q /f /forcerestart. This command performs an unattended upgrade and restarts the computer when the upgrade is complete.

  5. Click the Requirements tab.

  6. On the Requirements tab, in Maximum allowed run time, type 60 to indicate the time in minutes required to run the program.

    Note

    In SMS 2.0, the Maximum allowed run time setting is labeled Estimated run time.

  7. In the This program can run only on specified client platforms section, ensure that the All x86 Windows Server 2003 is the only client platform checked.

    Note

    SMS 2.0 might not include the All x86 Windows Server 2003 client platform.

  8. Click the Environment tab to note that the default setting specifies that the program requires administrative permissions to run, and then click OK.

  9. In the console tree, click Distribution Points to note that the distribution points for the package appear in the details pane where the appropriate distribution points are listed.

  10. In the console tree, click Advertisements.

    Note

    You might need to refresh the display to see the new advertisement.

  11. In the details pane, click Windows Server 2003 SP1 (update.exe), and then on the Action menu, click Properties. Note the package, program, and collection listed for the advertisement.

    If using SMS 2.0, skip to step 13 when you have completed this step.

  12. This step applies to SMS 2003 only. In the Windows Server 2003 SP1 update dialog box, click the Advanced Client tab to see how Advanced Clients interact with the advertisement.

    Important

    Using the settings in this step prevents clients in remote boundaries from installing the program and ensures that clients run from the distribution point. If necessary, change settings specified in the Windows Server 2003 SP1 update Advertisement Properties dialog box on the Advanced Client tab to download the program from the distribution point before running it or to use a remote distribution point if a local one is not available.

  13. Click Cancel to close the advertisement properties dialog box.

Use the following procedure to verify that the advertised program is available by viewing the package status in the SMS Administrator console.

To view the package status

  1. In the console tree, expand System Status, and then expand Package Status.

  2. Under Package Status, click Microsoft Windows Server 2003 SP1 (update.exe) English.

  3. In the details pane, click the local site code, and then, on the Action menu, point to Show Messages.

  4. Click All.

  5. In the Status Messages: Set Viewing Period dialog box, click Skip to view all messages.

  6. In the SMS Status Message Viewer for <site code><site name> window, expand the Description column to view more detail on the description.

  7. Note the following message IDs that result and their significance:

    Message ID

    Description

    30000

    User created the package

    30003

    User created the program (two instances of this in our package)

    30004

    User modified the program

    30009

    User targeted the package to a distribution point

    2300

    Distribution Manager begins processing the package

    2311

    Distribution Manager successfully created or updated the package

    2342

    Distribution Manager starts sending the package to the distribution point

    2329

    Distribution Manager copied the package to the distribution point

    2330

    Distribution Manager successfully distributed the package to the distribution point

    2301

    Distribution Manager successfully processed the package

    Note

    A package of this size can take several minutes to be copied to the distribution point. Proceed to the next step only after the package status indicates the package has been copied to the distribution point. You might need to manually refresh the package status to see the most recent status messages.

  8. Close the SMS Status Message Viewer for <site code><site name>.

Use the following procedure to verify that the advertised program is available by viewing the advertisement status in the SMS Administrator console.

To check the advertisement status

  1. In the console tree, expand System Status, and then expand Advertisement Status.

  2. Under Advertisement Status, click Windows Server 2003 SP1 Update.

  3. In the details pane, click the local site code, and then on the Action menu, point to Show Messages.

  4. Click All.

  5. In SMS Status Message Viewer for <site code><site name>, expand the Description column to view more detail on the description.

  6. Note the following message IDs that result and their significance:

    Message ID

    Description

    30006

    User created the advertisement

    3900

    Offer Manager successfully processed the new advertisement

  7. Close the SMS Status Message Viewer for <site code><site name>.

How to Run the Upgrade Advertisement

In the following procedures, you ensure that the advertised program for the Microsoft Windows 2003 SP1 upgrade runs on the Advanced Client computer. By doing so, you verify that the processes that you have already completed on the site server have been successful. You also verify that your client computer has been upgraded to Windows Server 2003 SP1.

In a production environment, you would not normally need to visit individual client computers to initiate discovery data collection or hardware inventory because these functions are normally scheduled to run on a recurring basis.

Complete the following procedure on an SMS 2003 Advanced Client running Windows Server 2003.

Note

For SMS 2.0, you can use the Advertised Program Monitor to view the state of the advertised program. SMS 2.0 clients check for and run the advertised program according to the schedule of the Advertised Programs Client Agent. When a program is scheduled to run on an SMS 2.0 client, the Advertised Program Countdown dialog box appears, indicating that a program is scheduled to run.

To manually run the upgrade program from the Advanced Client

  1. Log on to the client computer.

  2. In Control Panel, start Systems Management and then click the Actions tab.

  3. Click Machine Policy Retrieval & Evaluation Cycle, and then click Initiate Action.

    Note

    This process may take several minutes to complete.

  4. Click OK to close the Machine Policy Retrieval & Evaluation Cycle message box.

  5. Click OK to close System Management. Note the following:

    • It takes a few minutes for the policy to be evaluated and the Assigned Program About to Run notification to be displayed. Remain at this point until the notification appears.

    • When the Assigned Program About to Run countdown reaches zero, the automated installation of Microsoft Windows Server 2003 SP1 occurs. Whether you logged on with administrative credentials or not, SMS runs the upgrade with administrative credentials.

    • Depending on the hardware used, the upgrade process might take as long as 60 minutes. You can monitor the Update.exe process in Task Manager to confirm that the upgrade is still in progress. The computer restarts automatically after the upgrade completes.

Use the following procedure to verify that the upgrade to Windows Server 2003 SP1 has successfully completed and that the computer subsequently sends updated client data. Complete this procedure from the client running Windows Server 2003 SP1 after the system has automatically restarted.

To verify a successful upgrade on the SMS client and to send new inventory

  1. Log on to the client computer with administrative credentials.

  2. Right-click My Computer, and then click Properties to view the System Properties dialog box where the service pack version is displayed. Verify that Service Pack 1 is displayed.

  3. Click OK.

  4. In Control Panel, start Systems Management. For SMS 2003:

    1. Click the Actions tab.

    2. Click Discovery Data Collection Cycle, and then click Initiate Action, which causes the Advanced Client to generate a new discovery data record (DDR).

    3. In the Discovery Data Collection Cycle message box, click OK.

    4. Click Hardware Inventory Cycle, and then click Initiate Action, which causes the Advanced Client to generate a new hardware inventory report.

    5. In the Hardware Inventory Cycle message box, click OK.

    6. Click OK to close Systems Management.

    For SMS 2.0:

    1. Click the Components tab to open the Systems Management Properties dialog box.

    2. Click Hardware Inventory Agent, and then click Start Component.

    3. Click OK to close the System Management Properties dialog box.

    4. Click OK to close Systems Management.

How to Verify Upgrade Success with SMS

You can use the procedures in this section to view the status of the advertised program that was run on the client computers using the SMS Administrator Console. You can then verify that the reporting client is running Windows Server 2003 SP1 through discovery and inventory data.

Use the following procedure to view the status of the advertised program that was run on the client computers from the SMS Administrator Console on the primary site server.

To determine the advertisement status

  1. Start the SMS Administrator Console.

  2. In the console tree, expand System Status and then expand Advertisement Status.

  3. Under Advertisement Status, click Windows Server 2003 SP1 Update, and then on the Action menu, click Refresh to view the number of clients that received, started, and successfully completed the Windows Server 2003 SP1 upgrade.

  4. In the details pane, click the local site code, and then, on the Action menu, point to Show Messages.

  5. Click All to open SMS Status Message Viewer for <site code><site name>, which displays all messages for the selected advertisement at the local site.

    Notice the messages with a System entry of SMSClientName. These came from the client computer during the program execution.

  6. Expand the Description column to view more details. The messages described in the following table indicate the status of the upgrade program.

    Message ID

    Description

    10002

    The client received the advertisement.

    10035

    The program for the advertisement has not started because the content for the package has not been acquired. This is due to the time required to distribute the source files to the distribution point before installation could begin.

    This message applies to SMS 2003 only.

    10005

    The operating system at the client was able to start the program successfully.

    10022

    The program ran successfully, but a reboot was required to complete the installation. This message should occur before status message 10008.

    This message applies to SMS 2003, only.

    10008

    The client successfully processed the advertised program (it returned an exit code indicating success).

  7. Close SMS Status Message Viewer for <site code><site name>.

Use the following procedure to view the current client configuration in the SMS site database by viewing discovery and inventory data.

To view the current client data

  1. In the console tree, expand Collections.

  2. Under the Collections node, click All Windows Server 2003 Systems.

  3. In the details pane, click SMSClientName, and then on the Action menu, point to All Tasks.

  4. Click Start Resource Explorer.

  5. In the console tree, expand Hardware and then click Operating System.

  6. In the details pane, click the only record, and then on the Actionmenu, click Properties to open the Operating System Properties dialog box.

    Note

    The data for the Caption attribute is listed as Microsoft Windows Server 2003, <version>, where the version is Standard Edition, Enterprise Edition, and so on. The value for CSD Version should now be Service Pack 1.

  7. Click Close, and then close Resource Explorer. You have successfully upgraded your Windows Server 2003 client computers to Windows Server 2003 SP1 using SMS.

You have now successfully created queries to identify SMS clients ready for the Windows Server 2003 SP1 upgrade, deployed the Windows Server 2003 SP1 upgrade to your SMS Clients, and verified that the SMS clients successfully upgraded from Windows Server 2003 to Windows Server 2003 SP1.