Deploying Windows Server 2003 R2 with Systems Management Server
Microsoft Windows Server 2003 R2 extends the Windows Server 2003 operating system, providing a more efficient way to manage and control access to local and remote resources while easily integrating into your existing Windows Server 2003 environment. Windows Server 2003 R2 provides a scalable, security-enhanced Web platform and enables new scenarios, including simplified branch server management, improved identity and access management, and more efficient storage management. For more details about this product, see the Windows Server 2003 R2 Web site (http://go.microsoft.com/fwlink/?LinkId=64826).
This technical paper describes the processes, using Microsoft Systems Management Server (SMS) 2003, needed to upgrade computers using Windows Server 2003 Service Pack 1 to Windows Server 2003 R2. Details are also provided on how to create SMS collections that list only computers running R2.
This white paper assumes that you have an understanding of SMS and a working knowledge of software distribution. Additionally, this article assumes that your SMS infrastructure is established or that you will establish an SMS infrastructure before you deploy Windows Server 2003 R2.
This paper does not discuss detailed planning information that you need to consider for software distribution. Instead, you should refer to Chapter 5, “Distributing Software,” in the SMS 2003 Operations Guide (http://go.microsoft.com/fwlink/?LinkId=19628) for more information about software distribution. You should also review Appendix F, “Capacity Planning for SMS Component Servers,” and associated worksheets in Scenarios and Procedures for SMS 2003: Planning and Deployment (http://go.microsoft.com/fwlink/?LinkId=27190). This appendix helps you determine the level of performance you might expect from your site and will help you plan for capacity—in this case, the implications of a large software deployment.
The objectives of this technical paper include the following:
Preparing the Windows Server 2003 R2 source files
Creating collections for Windows Server 2003 R2 computers
Using software distribution to deploy the service pack
Running the R2 Setup advertisement
Preparing the Windows Server 2003 R2 Source Files
Before you can begin using this paper to deploy Windows Server 2003 R2, you must put all the required R2 source files into a single folder on the site server, d:\windist, for example. After creating the folder on the site server, copy the cmpnents folder from Windows Server 2003 R2 Disc 2 to the folder you created on the site server.
Creating Collections for Windows Server 2003 R2 Computers
In the following procedure, you create the collection used to target the upgrade of computers running Windows Server 2003 Service Pack 1 to Windows Server 2003 R2. You can also create another collection that groups all the computers that have Windows Server 2003 R2.
Extending SMS Hardware Inventory Configuration
There are a few ways to detect whether a computer has Windows Server 2003 R2 installed or not. One of them is by looking at the OtherTypeDescription attribute of the Win32_OperatingSystem WMI class. By default, this attribute has a blank value. It is set to “R2” after Windows Server 2003 R2 is installed on the computer. Unfortunately, this attribute is not collected by the SMS Hardware Inventory Agent. To change that, you will need to edit the master sms_def.mof file and enable the OtherTypeDescription property. To do that, follow the steps below:
Back up your current MOF file before making changes to it.
To extend SMS hardware inventory configuration
Using a text editor, open sms_def.mof. This file is located in the SMS\Inboxes\Clifiles.src\Hinv folder on the site server.
Search for the string OtherTypeDescription.
By default, the line above OtherTypeDescription reads [SMS_Report (FALSE)]. Edit the line so that it reads [SMS_Report (TRUE)].
Save and close the file.
For more information about editing the sms_def.mof, see Chapter 2, “Collecting Hardware and Software Inventory,” in the SMS 2003 Operations Guide (http://go.microsoft.com/fwlink/?LinkId=19628).
After you make the changes to SMS_def.mof, SMS loads its contents into the SMS database so that Advanced Clients can request them as policy from the management point. The SMS_def.mof is also downloaded to CAPs so that Legacy Clients can acquire it.
Collection of Windows Server 2003 Service Pack 1 Computers
You can create a new collection to find all the Windows Server 2003 Service Pack 1 computers based on the OtherTypeDescription information collected in hardware inventory.
To create a new collection containing all computers running Windows Server 2003 Service Pack 1 but not running R2
Start the SMS Administrator console.
Navigate to the Collections folder.
Right-click the Collections folder, click New, and then click Collection.
In the General tab, enter the name for the new collection (for example, Servers running R2) along with a descriptive comment (optional).
In the Membership Rules tab, click the Query Rules button (the database with the yellow star) to display the Query Rule Properties dialog box.
In the General tab, enter a name for your query (for example, Query for servers running R2).
Click Edit Query Statement to display the Query Statement Properties dialog box.
Click Show Query Language to display the Query Language view of this dialog box.
Paste the following query in the Query statement text box:
SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where (SMS_G_System_OPERATING_SYSTEM.OtherTypeDescription != "R2" or SMS_G_System_OPERATING_SYSTEM.OtherTypeDescription is NULL) AND (sms_r_system.OperatingSystemNameandVersion like '%Server 5.2%')
- Click OK to create the collection and add it to the Collections folder.
The newly created query should return a list of all computers running Windows Server 2003 R2.
For more information about creating collections, see Chapter 4, “Managing Collections and Queries,” in the SMS 2003 Operations Guide (http://go.microsoft.com/fwlink/?LinkId=19628).
Collection of Windows Server 2003 R2 Computers
If a computer has Windows Server 2003 R2 installed, the value of OtherTypeDescription on that computer will be equal to “R2.” You can create a collection to manage all R2 computers in your site. Follow the same steps described in the procedure “To create a new collection containing all computers running Windows Server 2003 Service Pack 1 but not running R2,” but instead use the following query:
select SMS_R_System.ResourceID,SMS_R_System.ResourceType,SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier,SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where (SMS_G_System_OPERATING_SYSTEM.OtherTypeDescription = "R2") AND (sms_r_system.OperatingSystemNameandVersion like '%Server 5.2%')
Using Software Distribution to Deploy Windows Server 2003 R2
In this procedure, you create the necessary SMS objects, such as the package and program, and advertise the program to the Windows Server 2003 Service Pack 1 computers.
To create the package
In the SMS Administrator console, expand Systems Management Server and then expand Site Database.
Right-click Packages, click New, and then click Package. The Package Properties page appears.
In the General tab, type R2 Setup Package in the name field.
In the Data Source tab, select This package contains source files.
Click Set, and enter either a network path or a local drive for the location of the Windows Server 2003 source files. Click OK.
Select other package properties according to your organization requirements.
To select distribution points for the new package
In the SMS Administrator console, expand the package you created in the previous procedure.
Right-click Distribution Points, click New, and then click Distribution Points. The New Distribution Points Wizard appears.
On the Welcome page, click Next and then select the distribution points for the package.
To close the wizard, click Finish.
To create the program for unattended installation
In the SMS Administrator console, expand the R2 package you created.
Right-click Programs, click New, and then click Program. The Program Properties page appears.
In the Name box, enter a name for the program (for example, R2 unattended installation).
In the Command line box, click Browse.
Browse to the location of the Windows Server 2003 source files, select setup2.exe, and then click Open.
In the Command line box, add the following command line arguments after setup2.exe: /q /a /sr /p:< R2 ProductKey >.
If you have a volume licensing agreement with Microsoft, you can encrypt your Windows Server 2003 R2 Volume License Product Key and use the encrypted product key with the command line argument. For more information, see Windows Server 2003 R2 Volume License Product Key Encryption (http://go.microsoft.com/fwlink/?LinkId=64827). For more information about R2 command line arguments, refer to the R2 documentation.
Click the After running arrow, and select SMS restarts computer.
On the Environment tab, click the Program can run arrow, and select Whether or not a user is logged on.
In the Run Mode section, verify that Allow users to interact with this program is not selected.
To create a new advertisement
In the SMS Administrator console, navigate to the Advertisements folder.
Right-click the Advertisements folder, click New, and then click Advertisement.
In the Name box, enter R2 Setup Advertisement.
Click the Package arrow, and select the R2 Setup Package you created.
Click the Program arrow, and select the R2 unattended installation program you created.
Click Browse, select the collection you created to receive Windows Server 2003 R2, and then click OK.
Select other advertisement properties according to your organization requirements. For example, you could configure a mandatory assignment to make the program run at a scheduled time.
In the Advertisement Properties dialog box, click OK.
Running the R2 Setup Advertisement
Advertisements are sent to SMS client computers based on the schedule defined on the site server for the Advertised Programs Client agent. After the advertisement arrives at the client computer, you can run it by clicking the notification, if you have notifications configured, or by starting Run Advertised Programs in the Control Panel. If you configured a mandatory assignment, the program runs at the scheduled time.
After the computer has restarted, Windows Server 2003 R2 will be completely installed on the computer.