16.1 © 2004 pearson education, inc. exam 70-290 managing and maintaining a microsoft® windows®...

16.1 © 2004 Pearson Education, Inc.

Exam 70-290 Managing and Maintaining a Microsoft® Windows® Server 2003 Environment

Lesson 16: Examining Software Update Services and License Management

Goals Install and configure Software Update Services on a

client

Install, configure, and manage a Software Update Services (SUS) Server

Use a Group Policy Object to configure updates

Administer software site licensing




Software Update Services Provides the ability to download, control, and deploy updates,

service packs and patches to the operating system and its components

Gives the administrator unparalleled control over the bandwidth used by Windows Update and the service packs and updates applied by client computers using the Automatic Updates service

Software Updates components The client-side service retrieves your updates from your

Software Update Services (SUS) server or the Internet and installs them

The server-side service can be the central point for distributing updates to clients

(Skill 1)

Installing and Configuring Software Update Services on a Client




Software Updates A Software Update Services (SUS) server is not requiredDedicating a server can significantly reduce your update

bandwidth requirements In order for Software Updates to work at all, the client-side

service must be properly installed and configuredThe client-side service is known as the Automatic Updates

service

Installing and Configuring Software Update Services on a Client (2)

(Skill 1)




Automatic Updates service Included with Windows Server 2003 Is available as a free download for the following

operating systemsWindows 2000 Professional (SP2)Windows 2000 Server (SP2)Windows 2000 Advanced Server (SP2)Windows XP HomeWindows XP Professional


(Skill 1)




After installation of Automatic UpdatesThe service tries to contact the default SUS server (normally

the Microsoft Windows Update server on the Internet)The Automatic Updates service displays a Wizard to the

Local Administrator 24 hours after establishing contact with the server in order to configure the service

If this period is unacceptable, a Local Administrator can configure the computer manuallyIn Windows XP or Windows Server 2003, you can access

Automatic Updates in the System Properties dialog boxIn Windows 2000, you can access the Automatic Updates applet

in the Control Panel


(Skill 1)




From the client side, there are only a few manual configuration optionsKeep my computer up to dateNotify me before downloading any updatesDownload the updates automatically and notify me when

they are ready to be installedAutomatically download the updates and install them on

the schedule that I specify


(Skill 1)




Figure 16-1 Automatic Updates Settings in System Properties (Windows Server 2003)

(Skill 1)




Figure 16-2 The Automatic Updates applet in Control Panel (Windows 2000 Professional)

(Skill 1)




Figure 16-3 Configuring Automatic Updates

(Skill 1)




Some options included with Automatic Updates are not configurable using the Control Panel applet or through System PropertiesReschedule Wait TimeNo Automatic Restart with logged-on usersSpecify intranet Microsoft update service location

To configure these options, you must use Group Policy or manually edit the Registry on each computer


(Skill 1)




SUS is the server-side service responsible for providing updates to client computers in order to reduce the bandwidth requirements for your network and increase manageability

To install SUS on a server, Microsoft recommends that the server meets specific requirements Windows 2000 (SP3)or Windows Server 2003 Pentium III at 700 MHz, or equivalent 512 MB of RAM 6 or more GB of free disk space on an NTFS partition The system partition should be an NTFS partition IIS 4.0 or higher installed

Installing, Configuring, and Managing aSoftware Update Services (SUS) Server

(Skill 2)




To install SUS, download SUS 1.1 from Microsoft at http://go.microsoft.com/fwlink/?LinkId=6930

After you download SUS, double-click the executable (currently SUS10SP1.exe) to install SUS

After the installation is complete, you will be presented with the Software Update Services Web page

Installing, Configuring, and Managing aSoftware Update Services (SUS) Server (2)

(Skill 2)




Typically, the default settings for each of these options will be adequateSelect a Proxy Server configurationSpecify the name your clients will use to locate this update

serverSelect which server to synchronize content fromSelect how you want to handle new versions of previously

approved updatesSelect where you want to store updatesSynchronize installation packages only for these locales

Installing, Configuring, and Managing aSoftware Update Services (SUS) Server (3)

(Skill 2)




Figure 16-4 The Software Update Services Web page

(Skill 2)




Figure 16-5 The Set options page

Allows you to configure how the SUS server connects to the Microsoft Windows Update servers on the Internet

(Skill 2)

This setting is set, by default, to the NetBIOS name of your server; if you use DNS naming exclusively, you will need to change the name to follow DNS naming conventions

This section allows you to choose between direct synchronization of updates from the Microsoft Windows Update servers on the Internet, or local SUS servers on our intranet

This setting determines whether or not you will be required to manually approve new releases of previously approved updates

This option lets you choose whether or not to store all updates locally or leave the updates on the Microsoft Servers

This section allows you to specify the locales supported by the SUS server




Figure 16-6 The Synchronize server page

(Skill 2)




Figure 16-7 The Schedule Synchronization dialog box

(Skill 2)




Figure 16-8 The synchronization status is shown during the synchronization process

(Skill 2)




Figure 16-9 The Approve updates page

(Skill 2)




Figure 16-10 Selecting updates to approve

(Skill 2)




Figure 16-11 The approve updates warning dialog box

Figure 16-12 The license agreement dialog box for the

approved updates

(Skill 2)




Figure 16-13 The approval confirmation dialog box

(Skill 2)

Figure 16-14 The Approve updates page, showing

the status of the approved updates as “Approved”




After SUS is installed, the new Group Policy administrative template wuau.adm is installed by default

This template adds the Windows Update node to the Windows Components node under Administrative Templates in the Computer Configuration node in the Group Policy Object Editor

Using a Group Policy Object to Configure Updates

(Skill 3)




The Windows Update node includes four new configuration options for your Windows Update clientsConfigure Automatic UpdatesSpecify intranet Microsoft update service locationReschedule Automatic Updates scheduled installationsNo auto-restart for scheduled Automatic Updates

installations

Using a Group Policy Object to Configure Updates (2)

(Skill 3)




Figure 16-15 The Windows Update section in the Default Domain Policy

(Skill 3)




Figure 16-16 The Configure Automatic Updates Properties dialog box

(Skill 3)




Figure 16-17 The Specify intranet Microsoft update service location Properties dialog box

(Skill 3)




Figure 16-18 The Reschedule Automatic Updates scheduled installations Properties dialog box

(Skill 3)




Figure 16-19 Opening the Group Policy Object Editor for the default domain policy from the GPMC

(Skill 3)




Windows Server 2003 requires Client Access Licenses (CALs)CALs are licenses to access the serverCALs can be utilized in one of two modes

Per ServerPer Device or User

Administrating Software Site Licensing

(Skill 4)




Per Server licensing modeA single CAL is necessary for each concurrent connection

to the specific server In this mode, you apply CALs to the servers themselves,

and when the maximum number of concurrent connections to that server has been reached, no additional users can access the server

Per Device or User modeA CAL is required for each client connection It doesn't matter to which server the clients connect

Administrating Software Site Licensing (2)

(Skill 4)




Microsoft has changed its licensing requirements in Windows Server 2003Multiple users logged on to a single machine now require

multiple licensesA single user using more than one machine also requires

multiple licenses


(Skill 4)




Licensing toolHelps keep track of your licensingView the maximum number of concurrent licenses being

usedView the servers that are or are not in complianceReview your license purchase history

License Logging service must be enable in the Services console in order for the Licensing tool to function

After this service is enabled, you can access the Licensing service to add licenses and monitor license usage


(Skill 4)




Figure 16-20 The Licensing Tool

(Skill 4)




Figure 16-21 The License Logging service in the Services console

(Skill 4)




Figure 16-22 The Products View tab in the Licensing tool

(Skill 4)




Figure 16-23 The Properties of Windows Server dialog box

(Skill 4)




Figure 16-24 The Clients tab

(Skill 4)




Figure 16-25 The Properties dialog box for a user account

(Skill 4)




Figure 16-26 The Server Browser tab

(Skill 4)




Figure 16-27 The Choose Licensing Mode dialog box

(Skill 4)

16.1 © 2004 pearson education, inc. exam 70-290 managing and maintaining a microsoft® windows®...

Documents