Article ID: 926030 - View products that this article applies to.
You can use Microsoft Systems Management Server (SMS) 2.0 or Microsoft SMS 2003 to deploy Microsoft Windows Server 2003 Service Pack 2 (SP2) from a shared distribution folder on a network. This article assumes that you have an understanding of SMS and that you have a working knowledge of software distribution. Additionally, this article assumes that the SMS infrastructure is established or that you will establish an SMS infrastructure before you deploy Windows Server 2003 SP2.
Important To use SMS 2.0 to deploy Windows Server 2003 SP2, you must have SMS 2.0 Service Pack 4 (SP4) installed.
To download Windows Server 2003 SP2, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/windowsserver/bb229701.aspxTo use SMS to deploy Windows Server 2003 SP2, follow these steps:
Create the SMS packageTo use SMS to distribute software, you must first create an SMS package that contains the files and the instructions that direct the software distribution process. When you create the SMS package, you define the location of the package source files. This location is where SMS obtains the source files. You also create the package definition file (.sms file) to distribute Windows Server 2003 SP2.
A package definition file is a specially formatted file. This file contains the information that you must have to create the SMS package. If you import this file, SMS immediately creates the package for you. After you use a package definition file to create a package, you can modify the package exactly as you modify any other SMS package.
Each predefined SMS package also contains SMS programs. These programs are commands that run on each targeted computer to control the package installation. Each program uses a different combination of options that you can use to install the package. For example, the package definition file for Windows Server 2003 SP2 includes programs to install the service pack with user input and programs to install the service pack without user input. These SMS programs must be compatible with the installation files for the package.
To create the SMS package, follow these steps:
After you create the package source folder, create the SMS package. To have SMS create the package for you, import the Windows Server 2003 SP2 product definition file. To download the Windows Server 2003 SP2 product definition file, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=59BEDA75-753A-4E14-A62A-2BFAD20FD1DEAfter you download the Windows Server 2003 SP2 definition file, follow these steps:
Distribute and advertise the SMS packageAfter you create the SMS package for the service pack, you must distribute the package to your distribution points. Distribution points are shared folders where SMS client computers can access the package source files.
Note Make sure that all distribution points have sufficient disk space for the SMS package.
To distribute the SMS package to the distribution points, follow these steps:
(http://support.microsoft.com/kb/302430/ )How to assign software to a specific group by using Group Policy
For more information about SMS 2.0, see the SMS 2.0 Administrator's Guide. For specific information about SMS 2.0 software distribution, see Chapter 12, "Distributing Software," in the SMS 2.0 Administrator's Guide.
For more information about SMS 2003, see the Systems Management Server 2003 Concepts, Planning, and Deployment Guide. For information about how to distribute software by using SMS 2003, see Chapter 3, "Software Distribution," in this guide. To download the most recent version of this guide, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=784838B3-34E0-4122-B3E2-17C5B4EEF8F4&displaylang=enFor information about the security features in SMS, visit the following Microsoft Web site:
http://www.microsoft.com/smserver/security/default.mspxTo obtain the SMS Security Essentials white paper, visit the following Microsoft Web site:
Article ID: 926030 - Last Review: November 16, 2007 - Revision: 3.1
Contact us for more help