Microsoft KB Archive/909914

= Detection and deployment guidance for the November 8, 2005 security release =

Article ID: 909914

Article Last Modified on 10/27/2006

-

APPLIES TO

 Microsoft Windows Server 2003 Service Pack 1, when used with:  Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

 Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

 Microsoft Windows Server 2003, Standard Edition (32-bit x86)

 Microsoft Windows Server 2003, Web Edition</li></ul> </li> Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)</li> Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)</li> Microsoft Windows Server 2003, Standard Edition (32-bit x86)</li> Microsoft Windows Server 2003, Web Edition</li> Microsoft Windows XP Service Pack 2, when used with:  Microsoft Windows XP Professional</li></ul>

 Microsoft Windows XP Home Edition</li></ul> </li> Microsoft Windows XP Service Pack 1, when used with:  Microsoft Windows XP Professional</li></ul>

 Microsoft Windows XP Home Edition</li></ul> </li> Microsoft Windows 2000 Service Pack 4, when used with:  <li>Microsoft Windows 2000 Advanced Server</li></ul>

<ul> <li>Microsoft Windows 2000 Datacenter Server</li></ul>

<ul> <li>Microsoft Windows 2000 Professional Edition</li></ul>

<ul> <li>Microsoft Windows 2000 Server</li></ul> </li> <li>Microsoft Windows Small Business Server 2003 Premium Edition</li> <li>Microsoft Windows Small Business Server 2003 Standard Edition</li> <li>Microsoft Small Business Server 2000 Standard Edition</li></ul>

-

<div class="notice_section">

<div class="summary_section">

INTRODUCTION
As part of an ongoing commitment to provide detection tools and deployment recommendations for security updates, Microsoft is delivering this detection and deployment guidance for all updates that are released during a Microsoft Security Response Center (MSRC) release cycle. This guidance contains recommendations that are based on the types of scenarios that may exist in various Microsoft operating system environments. This guidance includes the use of tools such as Microsoft Windows Update, Microsoft Office Update, Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), the Extended Security Update Inventory Tool, and the Enterprise Update Scan Tool. Currently, the guidance in this document does not apply to 64-bit systems. Microsoft intends to add this information in future releases of this guide.

This article describes the detection and deployment guidance for the security release that is dated November 8, 2005.

<div class="moreinformation_section">

Environments that detect and that deploy security updates by using Windows Update, Microsoft Update, and Office Update
The update that was released on November 8, 2005, is available on the following Microsoft Web sites:
 * Microsoft Windows Update
 * Microsoft Update

Environments that detect security updates by using MBSA version 1.2.1 or MBSA version 2.0
If you use MBSA version 1.2.1 or MBSA version 2.0 to detect security updates, you can detect the security update that was released on November 8, 2005.

Environments that detect and that deploy security updates by using Software Update Services or Windows Server Update Services
If you use Software Update Services (SUS) or Windows Server Update Services (WSUS) to detect and to deploy security updates, you can detect the security update that was released on November 8, 2005.

Environments that detect and that deploy security updates by using SMS with the Software Update Services Feature Pack and with the Extended Security Update Inventory Tool
If you use SMS to detect and to deploy security updates, you can detect the security update that was released on November 8, 2005.

Some of the security updates may be fully detected only if you use the latest cumulative Extended Security Update Inventory Tool. To obtain this tool, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=2C93DA1D-48A0-4E5C-991F-87E08954F61B&displaylang=en

Summary of detection and deployment guidance
The following table summarizes the detection and deployment guidance for each new security update.

Re-released security updates
There are no security updates that are being re-released this month.

Frequently asked questions
Q1: What is Microsoft doing to provide guidance about how to deploy these updates?

A1: Microsoft encourages system administrators to join the monthly technical webcast to learn more about security updates. The webcast for this security update airs on November 8, 2005, at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032263907&EventCategory=3&culture=en-US&CountryCode=US

Q2: Is the Enterprise Update Scan Tool cumulative as the Extended Security Update Inventory Tool is for SMS?

A2: No, the Enterprise Update Scan tool is not cumulative. There are no plans to make the Enterprise Update Scan tool cumulative.

Q3: Can I use MBSA to determine whether these updates are required?

A3: Yes, you can use MBSA version 1.2.1 and MBSA version 2.0 to detect whether the security update that was released in November 2005 is required, except where noted.

For more information about the programs that MBSA does not currently detect, click the following article numbers to view the articles in the Microsoft Knowledge Base:

306460 Microsoft Baseline Security Analyzer 1.2.1 (MBSA) returns note messages for some updates

895660 Microsoft Baseline Security Analyzer 2.0 is available

If you installed a program that is listed in the &quot;Affected software&quot; section of a security bulletin that is mentioned in the related article, you may have to manually determine whether you must install the required security update. For more information about MBSA, visit the following Microsoft Web site:

http://www.microsoft.com/technet/security/tools/mbsahome.mspx

Q4: Which security updates require that I use the Enterprise Update Scan Tool together with MBSA to identify vulnerable systems on my network?

A4: No security updates require the Enterprise Update Scan Tool this month. The single security update is fully detected by MBSA.

Q5: Can I use SMS to determine whether the updates are required?

A5: Yes. SMS helps detect and deploy this security update. SMS uses MBSA for detection. Therefore, SMS does not detect the same programs that MBSA does not detect. For more information about SMS, visit the following Microsoft Web site:

http://www.microsoft.com/smserver/default.mspx

The Security Update Inventory Tool together with the Extended Security Update Inventory Tool are required for detection of all the security updates for Microsoft Windows and for other affected Microsoft products. For more information about the limitations of the Security Update Inventory Tool, click the following article number to view the article in the Microsoft Knowledge Base:

306460 Microsoft Baseline Security Analyzer (MBSA) returns note messages for some updates

SMS also uses the Office Inventory Tool to detect the required security updates for Office programs such as Microsoft Word.

Keywords: kbhowto kbinfo KB909914

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.