Microsoft Security Bulletin MS07-003 - Critical

  • Article

Vulnerabilities in Microsoft Outlook Could Allow Remote Code Execution (925938)

Published: January 09, 2007 | Updated: January 24, 2007

Version: 1.1

Summary

Who Should Read this Document: Customers who use Microsoft Outlook

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately

Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.

Caveats: Microsoft Knowledge Base Article 925938 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 925938.

Tested Software and Security Update Download Locations:

Affected Software:

Non-Affected Software:

  • Microsoft Office 2007
    • Microsoft Office Outlook 2007

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

Executive Summary

Executive Summary:

This update addresses several newly discovered, privately and publicly reported vulnerabilities. The vulnerabilities are documented in the “Vulnerability Details” section of this bulletin.

When using vulnerable versions of Office, if a user is logged on with administrative user rights, an attacker who successfully exploited these vulnerabilities could take complete control of the system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability Identifiers Impact of Vulnerability Microsoft Outlook 2000 Microsoft Outlook 2002 Microsoft Outlook 2003
Microsoft Outlook VEVENT Vulnerability - CVE-2007-0033 Remote Code Execution None Important Important
Microsoft Outlook Denial of Service Vulnerability - CVE-2006-1305 Denial of Service Moderate Moderate Moderate
Microsoft Outlook Advanced Find Vulnerability - CVE-2007-0034 Remote Code Execution Critical Important Important
Aggregate Severity of All Vulnerabilities Critical Important Important

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

What are the known issues that customers may experience when they install this security update?
Microsoft Knowledge Base Article 925938 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues. For more information, see Microsoft Knowledge Base Article 925938.

  • Microsoft Knowledge Base Article 925542 : Cannot open or save "Office Saved Searches (.oss)" files in Outlook after installing a security update that is dated January 9, 2007 (925542).
  • Microsoft Knowledge Base Article 931270 : You receive an error message "Microsoft Office Outlook has encountered a problem and needs to close. We are sorry for the inconvenience." when you use Microsoft CRM client for Microsoft Outlook (931270).

What updates does this release replace?
This security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.

Bulletin ID Microsoft Outlook 2000 Microsoft Outlook 2002 Microsoft Outlook 2003
MS06-003 Not Applicable Not Applicable Replaced

Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.

Software MBSA 1.2.1 MBSA 2.0
Microsoft Outlook 2000 Yes No
Microsoft Outlook 2002 Yes Yes
Microsoft Outlook 2003 Yes Yes

Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.

For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

For more detailed information, see Microsoft Knowledge Base Article 910723.

Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS detection summary for this security update.

Software SMS 2.0 SMS 2003
Microsoft Outlook 2000 Yes Yes
Microsoft Outlook 2002 Yes Yes
Microsoft Outlook 2003 Yes Yes

SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

For more information about SMS, visit the SMS Web site.

For more detailed information, see Microsoft Knowledge Base Article 910723.

Vulnerability Details

Microsoft Outlook VEVENT Vulnerability - CVE-2007-0033

A remote code execution vulnerability exists in Microsoft Outlook. An attacker could exploit this vulnerability when Outlook parses a file and processes a malformed VEVENT record.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

Mitigating Factors for Microsoft Outlook VEVENT Vulnerability - CVE-2007-0033:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • MAPI is not a valid attack vector for this issue due to Exchange's handling of iCal calendar data embedded in messages or in .ICS attachments.

Workarounds for Microsoft Outlook VEVENT Vulnerability - CVE-2007-0033:

Microsoft has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.

  • Modify the Access Control List on the “MapiCvt Class”registry key. Modifying the Access Control List on the MapiCvt Class registry key helps protect the affected system from attempts to exploit this vulnerability. To modify the MapiCvt Class registry key, follow these steps.

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry before you edit it.

    For Windows 2000

    1. Click Start, click Run, type "regedt32" (without the quotation marks), and then click OK.
    2. Expand HKEY_CLASSES_ROOT, expand CLSID, and then click {0006F085-0000-0000-C000-000000000046}.
    3. Click Security, and then click Permissions.

    Note Make a note of the permissions that are listed in this dialog box so that you can restore them to their original values at a later time.

    1. Click to clear the Allow Inheritable Permissions from the parent to propagate to this object check box. You are prompted to click Copy, Remove, or Cancel. Click Remove, and then click OK.
    2. You receive a message that states that no one will be able to access this registry key. Click Yes when you are prompted to do so.

    For Windows XP Service Pack 2

    1. Click Start, click Run, type "regedit" (without the quotation marks), and then click OK.
    2. Expand HKEY_CLASSES_ROOT, expand CLSID, and then click {0006F085-0000-0000-C000-000000000046}.
    3. Click Edit, and then click Permissions.

    Note Make a note of the permissions that are listed in this dialog box so that you can restore them to their original values at a later time

    1. Click Advanced.
    2. Click to clear the Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here check box. You are prompted to click Copy, Remove, or Cancel. Click Remove, and then check OK.
    3. You receive a message that states that no one will be able to access this registry key. Click Yes, and then click OK to close the Permissions for {0006F085-0000-0000-C000-000000000046} dialog box.

  • Back up and remove the MIMEDIR.DLL {0006F085-0000-0000-C000-000000000046} “MapiCvt Class” registry key. Removing the MIMEDIR.DLL {0006F085-0000-0000-C000-000000000046} “MapiCvt Class” registry key helps protect the affected system from attempts to exploit this vulnerability. To backup and remove the MIMEDIR.DLL {0006F085-0000-0000-C000-000000000046} “MapiCvt Class” registry key, follow these steps:

    Note Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    Note We recommend backing up the registry before you edit it.

    1. Click Start, click Run, type “regedit" (without the quotation marks), and then click OK.
    2. Expand HKEY_CLASSES_ROOT, expand CLSID, and then click {0006F085-0000-0000-C000-000000000046}.
    3. Click File, and then click Export.
    4. In the Export Registry File dialog box, type a file name in the File Name box, and then click Save.
    5. Click Edit, and then click Delete to remove the registry key.
    6. In the Confirm Key Delete dialog box, you receive a “Are you sure you want to delete this key and all of its subkeys” message. Click Yes.

    Command Line Instructions To back up and delete this registry key by using a command-line command, follow these steps:

    1. reg.exe export "HKEY_CLASSES_ROOT\CLSID**\{0006F085-0000-0000-C000-000000000046}**" c:\MapiCvt_Class.reg
    2. reg.exe delete "HKEY_CLASSES_ROOT\CLSID**\{0006F085-0000-0000-C000-000000000046}**" c:\MapiCvt_Class.reg

Impact of Workaround: Users will be unable to use the 'Send Update' feature to send updates to existing meetings from their calendar. Users will be able to create new meetings in their calendar but will be unable to use the 'Send' feature from the meeting invite to automatically send the meeting invite to other recipients. The meeting will be saved to the calendar but the invite will stay in the 'Outbox' folder. Users will be unable to forward meetings from the calendar as iCalendar requests.

FAQ for Microsoft Outlook VEVENT Vulnerability - CVE-2007-0033:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Outlook. An attacker could exploit this vulnerability when Outlook parses a file and processes a malformed VEVENT record.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability?
Outlook does not perform sufficient data validation when processing the contents of an .iCal meeting request. When Outlook opens a specially crafted .iCal meeting request and parses a malformed VEVENT request, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What is an .iCal meeting request?
An iCal is used to create a meeting request to a recipient over the Internet, or outside the organization.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted .ICS (iCal) file or embed the contents of an iCal calendar request in the body of a specially crafted e-mail and send it to a user of Outlook who connects to a POP, IMAP or HTTP server to retrieve their e-mail.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.

What does the update do?
The update removes the vulnerability by modifying the way that Outlook validates the length of an .iCal meeting request before it passes the message to the allocated buffer.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Microsoft Outlook Denial of Service Vulnerability - CVE-2006-1305

A denial of service vulnerability exists in Outlook in its processing of e-mail header information. An attacker who successfully exploited the vulnerability could send a malformed e-mail to a user of Outlook that would cause the Outlook client to fail under certain circumstances. The Outlook client would continue to fail so long as the malformed e-mail message remained on the e-mail server. The e-mail message could be deleted by an e-mail administrator, or by the user via another e-mail client such as Outlook Web Access or Outlook Express, after which point the Outlook client would again function normally.

Mitigating Factors for Microsoft Outlook Denial of Service Vulnerability - CVE-2006-1305:

  • The vulnerability is a denial of service vulnerability only. The attacker would not be able to access the user's e-mail or system in any way. The vulnerability could not be used to read, delete, create, or alter the user's e-mail.
  • If an attacker was able to send a malformed e-mail that successfully exploited this vulnerability, the malformed e-mail could be deleted either by an e-mail administrator, or by the user via another e-mail client such as Outlook Web Access or Outlook Express. Once the specially malformed e-mail has been removed, normal operation would resume.

Workarounds for Microsoft Outlook Denial of Service Vulnerability - CVE-2006-1305:

We have not identified any workarounds for this vulnerability.

FAQ for Microsoft Outlook Denial of Service Vulnerability - CVE-2006-1305:

What is the scope of the vulnerability?
This is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected system to stop responding. During that time, the server cannot respond to requests.

What causes the vulnerability?
The vulnerability results because of the way Outlook processes e-mail header information.

What might an attacker use the vulnerability to do?
Any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.

Who could exploit the vulnerability?
On Outlook, any anonymous user who could deliver a specially crafted message to the affected system could try to exploit this vulnerability.

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted message and sending the message to an affected system. The message could then cause Outlook to fail.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
The update removes the vulnerability by modifying the way that Outlook validates the length of the header in the message.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2006-1305.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Microsoft Outlook Advanced Find Vulnerability - CVE-2007-0034

A remote code execution vulnerability exists in Microsoft Outlook. An attacker could exploit this vulnerability when Outlook parses an .oss file.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

Mitigating Factors for Microsoft Outlook Advanced Find Vulnerability - CVE-2007-0034:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker would have to host a Web site that contains an Office Saved Searches (.oss) file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
  • The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.

Workarounds for Microsoft Outlook Advanced Find Vulnerability - CVE-2007-0034:

  • Do not open or save Office Saved Searches (.oss) files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for Microsoft Outlook Advanced Find Vulnerability - CVE-2007-0034:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Outlook. An attacker could exploit this vulnerability when Outlook parses an Office Saved Searches (.oss) file.

If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

What causes the vulnerability?
Outlook does not perform sufficient data validation when processing the contents of .oss file. When Outlook opens a specially crafted .oss and parses the request, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What is an Office Saved Searches (.oss) File?
Saved Searches are virtual folders that contain views of e-mail items that satisfy specific search criteria. The specific search criteria are stored in .oss file.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take complete control of the affected system.

How could an attacker exploit the vulnerability?
An attacker could try to exploit the vulnerability by creating a specially crafted .oss file in a specially crafted e-mail and send it to a user of Outlook who connects to a POP, IMAP or HTTP server to retrieve their e-mail.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

Could the vulnerability be exploited over the Internet?
Yes. An attacker could try to exploit this vulnerability over the Internet. Firewall best practices and standard default firewall configurations can help protect against attacks that originate from the Internet. Microsoft has provided information about how you can help protect your PC. End users can visit the Protect Your PC Web site. IT professionals can visit the Security Guidance Center Web site.

What does the update do?
The update removes the ability to save these searches as well as removing the ability to open these searches.

Does this update contain any changes to functionality?
Yes. After the update for Outlook 2000, Outlook 2002, or Outlook 2003 is installed, users will not be able to save these searches as well as the ability to open these Searches. For more information, see Cannot open or save Office Saved Searches files in Outlook (KB925542).

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.

Security Update Information

Affected Software:

For information about the specific security update for your affected software, click the appropriate link:

Outlook 2000

Prerequisites and Additional Update Details

Important Before you install this update, make sure that the following requirements have been met:

  • Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites:

Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition

Windows Installer 2.0 for Windows 2000 and Windows NT 4.0

For more information about how to determine the version of Office 2000 that is installed on your computer, see Microsoft Knowledge Base Article 255275.

Inclusion in Future Service Packs

None. Service Pack 3 is the last service pack for Office 2000.

Restart Requirement

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

Removal Information

After you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original CD-ROM.

Automated Client Installation Information

Office Update Web Site

We recommend that you install the Microsoft Office 2000 client updates by using the Office Update Web site. The Office Update Web site detects which installation you have and prompts you to install exactly what you must have to make sure that your installation is completely up to date.

To have the Office Update Web site detect the updates that you must install on your computer, visit the Office Update Web site, and then click Check for Updates. After detection is complete, you will receive a list of recommended updates for your approval. Click Agree and Install to complete the process.

Manual Client Installation Information

For detailed information about how to manually install this update, review the following section.

Installation Information

The security update supports the following setup switches.

Switch Description
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the computer after installation.
/r:I Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a Always restarts the computer after installation.
/r:s Restarts the computer after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Note The full file office update is intended for both client and administrative deployment scenarios.

Client Deployment Information

  1. Download this security update for Outlook 2000.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
  5. If you are prompted to install the update, click Yes.
  6. Click Yes to accept the License Agreement.
  7. Insert your original source CD-ROM when you are prompted to do so, and then click OK.
  8. When you receive a message that states the installation was successful, click OK.

Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.

Client Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook 2000:

File Name Version Date Time Size
Dlgsetp.dll 9.0.0.8954 10-Nov-2006 02:27 77,873
Dumpster.dll 9.0.0.8954 10-Nov-2006 02:32 32,818
Mimedir.dll 9.0.0.8954 10-Nov-2006 01:10 192,561
Outllib.dll 9.0.0.8954 12-Nov-2006 04:40 5,341,234
Outlmime.dll 9.0.3202.0 16-Aug-2006 19:02 106,768
Recall.dll 9.0.0.8954 10-Nov-2006 02:25 45,104

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this issue. For more information about MBSA, visit the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A; Web site.

  • File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results pane, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
    Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Administrative Installation Information

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

Installation Information

The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.

Switch Description
/? Displays the command-line options.
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.

For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Administrative Deployment Information

To update your administrative installation, follow these steps:

  1. Download this security update for Outlook 2000.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate
    Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
  5. Click Yes to accept the License Agreement.
  6. Click Yes if you are prompted to create the folder.
  7. If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: msiexec /a Admin Path**\**MSI File **/p C:\AdminUpdate\**MSP File SHORTFILENAMES=TRUE
    Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2000), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
    Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
  8. Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box.
  9. Click I accept the terms in the License Agreement, and then click Install.

At this point, your administrative installation point is updated. Next, you must update the workstations configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.

Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation.

Workstation Deployment Information

To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:

msiexec /I Admin Path**\**MSI File **/qb REINSTALL=**Feature List REINSTALLMODE=vomu

Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2000), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.

To install all features, you can use REINSTALL=ALL or you can install the following features.

Product Feature
O9OLK, O9PRM, O9PRO, O9SBE, O9PIPC1, O9STD OUTLOOKFiles, OutlookMAPIEMS, OUTLOOKNonBootFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

Administrative Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook 2000:

File Name Version Date Time Size
Dlgsetp.dll 9.0.0.8954 10-Nov-2006 02:27 77,873
Dumpster.dll 9.0.0.8954 10-Nov-2006 02:32 32,818
Mimedir.dll 9.0.0.8954 10-Nov-2006 01:10 192,561
Outllib.dll 9.0.0.8954 12-Nov-2006 04:40 5,341,234
Outlmime.dll 9.0.3202.0 16-Aug-2006 19:02 106,768
Recall.dll 9.0.0.8954 10-Nov-2006 02:25 45,104

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.

  • File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results pane, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
    Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Outlook 2002

Prerequisites and Additional Update Details

Important: Before you install this update, make sure that the following requirements have been met:

  • Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites:

Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition

Windows Installer 2.0 for Windows 2000 and Windows NT 4.0

For more information about how to determine the version of Office XP that is installed on your computer, see Microsoft Knowledge Base Article 291331. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294.

Inclusion in Future Service Packs

None. Service Pack 3 is the last service pack for Office XP.

Restart Requirement

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

Removal Information

To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

Note For Project 2002 Service Pack 1 and Visio 2002 Service Pack 2, after you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original CD-ROM.

Automated Client Installation Information

Microsoft Update Web Site

This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date.

To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process.

Manual Client Installation Information

For detailed information about how to manually install this update, review the following section.

Installation Information

The security update supports the following setup switches.

Switch Description
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the computer after installation.
/r:I Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a Always restarts the computer after installation.
/r:s Restarts the computer after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Note The full file office update is intended for both client and administrative deployment scenarios.

Client Deployment Information

  1. Download the security update for Outlook 2002.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
  5. If you are prompted to install the update, click Yes.
  6. Click Yes to accept the License Agreement.
  7. Insert your original source CD-ROM when you are prompted to do so, and then click OK.
  8. When you receive a message that states the installation was successful, click OK.

Note If the security update is already installed on your computer, you see the following error message: This update has already been applied or is included in an update that has already been applied.

Client Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook 2002:

File Name Version Date Time Size
Cdooff.dll 10.0.6777.0 19-Sep-2005 20:36 236,232
Dlgsetp.dll 10.0.6711.0 08-Apr-2004 02:24 80,584
Dumpster.dll 10.0.6711.0 08-Apr-2004 02:24 39,624
Envelope.dll 10.0.6753.0 24-Feb-2005 01:30 105,160
Exsec32.dll 10.0.6780.0 01-Nov-2005 02:07 346,824
Impmail.dll 10.0.6740.0 11-Nov-2004 12:48 137,928
Mimedir.dll 10.0.6821.0 03-Nov-2006 03:32 172,032
Msoutl.olb 10.0.6732.0 17-Sep-2004 22:27 207,552
Oladd.fae 10.0.6751.0 15-Feb-2005 07:43 187,072
Olappt.fae 10.0.6751.0 15-Feb-2005 07:43 170,696
Oljrnl.fae 10.0.6713.0 05-May-2004 03:47 137,920
Olmail.fae 10.0.6711.0 08-Apr-2004 02:24 133,824
Oltask.fae 10.0.6751.0 15-Feb-2005 07:43 166,600
Outlcm.dll 10.0.6711.0 08-Apr-2004 02:24 543,424
Outllib.dll 10.0.6822.0 11-Nov-2006 00:13 6,359,824
Outlmime.dll 10.0.6816.0 17-Aug-2006 22:20 92,944
Outlook.exe 10.0.6822.0 11-Nov-2006 00:13 47,888
Outlph.dll 10.0.6737.0 22-Oct-2004 22:52 125,632
Outlvbs.dll 10.0.6711.0 08-Apr-2004 02:24 47,816

Administrative Installation Information

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

Installation Information

The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.

Switch Description
/? Displays the command-line options.
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Override installation command defined by author. Specifies the path and name of the Setup.inf or .exe file.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Administrative Deployment Information

To update your administrative installation, perform the following procedure:

  1. Download the security update for Outlook 2002.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate
    Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
  5. Click Yes to accept the License Agreement.
  6. Click Yes if you are prompted to create the folder.
  7. If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: msiexec /a Admin Path**\**MSI File **/p C:\adminUpdate\**MSP File SHORTFILENAMES=TRUE
    Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeXp), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
    Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
  8. Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box.
  9. Click I accept the terms in the License Agreement, and then click Install.

At this point, your administrative installation point is updated. Next, you must update the workstation configurations that were originally installed from this administrative installation. To do this, see the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.

Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation.

Workstation Deployment Information

To deploy the update to the client workstations, click Start, click Run, and then type the following command:

msiexec /iAdmin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu

NoteAdmin Path is the path of your administrative installation point for your application (for example, C:\OfficeXP), MSI File is the MSI database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that have to be reinstalled for the update. To install all features, you can use REINSTALL=ALL.

To install all features, you can use REINSTALL=ALL or you can install the following features.

Product Feature
OUTLOOK, PIPC1, PROPLUS, PRO, SBE, STD, STDEDU OUTLOOKNonBootFiles, OUTLOOKFiles, OutlookMAPIEMS2, OutlookDVExtensionsFiles, OutlookVBScript

Note Additional instructions are provided in Microsoft Knowledge Base Article 832332. Information about this update can also be found on the Microsoft Office XP Resource Kit Web site. General information about the Microsoft Office XP Resource Kit can also be found on TechNet. The Windows Installer Documentation also provides additional information about the parameters supported by the Windows Installer.

Administrative Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook 2002:

File Name Version Date Time Size
Cdooff.dll 10.0.6777.0 19-Sep-2005 20:36 236,232
Dlgsetp.dll 10.0.6711.0 08-Apr-2004 02:24 80,584
Dumpster.dll 10.0.6711.0 08-Apr-2004 02:24 39,624
Envelope.dll 10.0.6753.0 24-Feb-2005 01:30 105,160
Exsec32.dll 10.0.6780.0 01-Nov-2005 02:07 346,824
Impmail.dll 10.0.6740.0 11-Nov-2004 12:48 137,928
Mimedir.dll 10.0.6821.0 03-Nov-2006 03:32 172,032
Msoutl.olb 10.0.6732.0 17-Sep-2004 22:27 207,552
Oladd.fae 10.0.6751.0 15-Feb-2005 07:43 187,072
Olappt.fae 10.0.6751.0 15-Feb-2005 07:43 170,696
Oljrnl.fae 10.0.6713.0 05-May-2004 03:47 137,920
Olmail.fae 10.0.6711.0 08-Apr-2004 02:24 133,824
Oltask.fae 10.0.6751.0 15-Feb-2005 07:43 166,600
Outlcm.dll 10.0.6711.0 08-Apr-2004 02:24 543,424
Outllib.dll 10.0.6822.0 11-Nov-2006 00:13 6,359,824
Outlmime.dll 10.0.6816.0 17-Aug-2006 22:20 92,944
Outlook.exe 10.0.6822.0 11-Nov-2006 00:13 47,888
Outlph.dll 10.0.6737.0 22-Oct-2004 22:52 125,632
Outlvbs.dll 10.0.6711.0 08-Apr-2004 02:24 47,816

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for commonly misconfigured security parameters. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results pane, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
    Note Depending on the version of the operating system, language, or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Outlook 2003

Prerequisites and Additional Update Details

Important: Before you install this update, make sure that the following requirements have been met:

  • To update Office 2003, Office 2003 Service Pack 2 must be installed. Before you install this update, install Office 2003 SP2.

For more information about how to determine the version of Office 2003 that is installed on your computer, see Microsoft Knowledge Base Article 821549. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294.

Inclusion in Future Service Packs:

The fix for this issue will be included in a future service pack.

Restart Requirement

To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.

Removal Information

To remove this security update, use Add or Remove Programs in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from Add or Remove Programs in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

Automated Client Installation Information

Microsoft Update Web Site

This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update by using the Microsoft Update Web site. The Microsoft Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date.

To have the Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates to complete the process.

Manual Client Installation Information

For detailed information about how to manually install this update, review the following section.

Installation Information

The security update supports the following setup switches.

Switch Description
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the computer after installation.
/r:I Prompts the user to restart the computer if a restart is required, except when used with /q:a.
/r:a Always restarts the computer after installation.
/r:s Restarts the computer after installation without prompting the user.
/n:v No version checking - Install the program over any earlier version.

Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Note The full file office update is intended for both client and administrative deployment scenarios.

Client Deployment Information

  1. Download the security update for Office 2003.
  2. Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
  5. If you are prompted to install the update, click Yes.
  6. Click Yes to accept the License Agreement.
  7. Insert your original source CD-ROM when you are prompted to do so, and then click OK.
  8. When you receive a message that states the installation was successful, click OK.

Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.

Client Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook 2003:

File Name Version Date Time Size
Dlgsetp.dll 11.0.8009.0 17-Jan-2006 01:09 77,000
Envelope.dll 11.0.8004.0 06-Dec-2005 23:44 132,808
Exsec32.dll 11.0.8027.0 23-May-2006 00:39 346,896
Mimedir.dll 11.0.8115.0 03-Nov-2006 01:50 177,424
Oladd.fae 11.0.8029.0 02-Jun-2006 23:10 158,992
Olappt.fae 11.0.8109.0 23-Sep-2006 07:15 152,848
Oljrnl.fae 11.0.8109.0 23-Sep-2006 07:15 118,032
Olmail.fae 11.0.8109.0 23-Sep-2006 07:15 113,424
Olnote.fae 11.0.8109.0 23-Sep-2006 07:15 104,720
Oltask.fae 11.0.8029.0 02-Jun-2006 23:10 147,216
Outllib.dll 11.0.8118.0 24-Nov-2006 04:54 7,619,856
Outlmime.dll 11.0.8104.0 17-Aug-2006 23:04 93,456
Outlook.exe 11.0.8118.0 24-Nov-2006 04:56 196,368
Recall.dll 11.0.8001.0 01-Nov-2005 22:57 39,112
Transmgr.dll 11.0.8000.0 22-Oct-2005 23:56 100,552

Administrative Installation Information

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

Installation Information

The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.

Switch Description
/? Displays the command-line options.
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.

For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Administrative Deployment Information

To update your administrative installation, follow these steps:

  1. Download the security update for Office 2003.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file: [path\name of EXE file] /c /t:C:\AdminUpdate
    Note Double-clicking the .exe file does not extract the .msp file; it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.
  5. Click Yes to accept the License Agreement.
  6. Click Yes if you are prompted to create the folder.
  7. If you are familiar with the procedure for updating your administrative installation,click Start, click Run, type the following command, and then click OK: msiexec /a Admin Path**\**MSI File **/p C:\adminUpdate\**MSP File SHORTFILENAMES=TRUE
    Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2003), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
    Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
  8. Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box.
  9. Click I accept the terms in the License Agreement, and then click Install.

At this point, your administrative installation point is updated. Next, you must update the workstations configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.

Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions such as repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section.

Workstation Deployment Information

To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:

Msiexec /I Admin Path**\**MSI File **/qb REINSTALL=**Feature List REINSTALLMODE=vomu

Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2003), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.

To install all features, you can use REINSTALL=ALL or you can install the following features:

Product Feature
BASIC11, OUTLS11, OUTL11, PERS11, PRO11SB, PROI11, PRO11, STDP11, STD11 OUTLOOKFiles, OUTLOOKNonBootFiles, OutlookDVExtensionsFiles, OutlookImportExportFiles
OUTLSM11 OUTLOOKFiles, OUTLOOKNonBootFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization on the Office Admin Update Center. On the home page of that site, look under the Update Strategies section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by the Windows Installer.

Administrative Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Outlook 2003:

File Name Version Date Time Size
Dlgsetp.dll 11.0.8009.0 17-Jan-2006 01:09 77,000
Envelope.dll 11.0.8004.0 06-Dec-2005 23:44 132,808
Exsec32.dll 11.0.8027.0 23-May-2006 00:39 346,896
Mimedir.dll 11.0.8115.0 03-Nov-2006 01:50 177,424
Oladd.fae 11.0.8029.0 02-Jun-2006 23:10 158,992
Olappt.fae 11.0.8109.0 23-Sep-2006 07:15 152,848
Oljrnl.fae 11.0.8109.0 23-Sep-2006 07:15 118,032
Olmail.fae 11.0.8109.0 23-Sep-2006 07:15 113,424
Olnote.fae 11.0.8109.0 23-Sep-2006 07:15 104,720
Oltask.fae 11.0.8029.0 02-Jun-2006 23:10 147,216
Outllib.dll 11.0.8118.0 24-Nov-2006 04:54 7,619,856
Outlmime.dll 11.0.8104.0 17-Aug-2006 23:04 93,456
Outlook.exe 11.0.8118.0 24-Nov-2006 04:56 196,368
Recall.dll 11.0.8001.0 01-Nov-2005 22:57 39,112
Transmgr.dll 11.0.8000.0 22-Oct-2005 23:56 100,552

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for commonly misconfigured security parameters. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results pane, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
    Note Depending on the version of the operating system, language, or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.
    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customers:

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

Support:

  • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Security Resources:

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.

For more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server:

Microsoft Systems Management Server (SMS) delivers a highly configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.

Note SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scan Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Disclaimer:

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions:

V1.0 (January 9, 2007): Bulletin published.

V1.1 (January 24, 2007): Bulletin updated to add “You receive an error message "Microsoft Office Outlook has encountered a problem and needs to close. We are sorry for the inconvenience." when you use Microsoft CRM client for Microsoft Outlook (931270)” under “What are the known issues that customers may experience when they install this security update?” in the “Frequently Asked Questions (FAQ) Related to This Security Update” section.

Built at 2014-04-18T13:49:36Z-07:00