Back to the top

Issues that this hotfix package fixes

This hotfix package fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	In Microsoft Office PowerPoint 2007, you save a presentation (.pptx) file that contains a radial or path gradient-filled shape as a PDF file. Then, when you open the PDF file, you find that the shape is not gradient filled. Note This problem may occur when a shadow is applied to the shape.
•	Consider the following scenario: • In a PowerPoint 2007 presentation, you insert two same-line Callout shapes. • You change the arrow settings of the line style for a Line Callout shape to the nondefault arrow settings. • You do not make any changes to the arrow settings for another line callout shape. • You save the presentation in the PowerPoint 97-2003 Presentation (.ppt) format. In this case, when you open the .ppt file in PowerPoint 2007 or in PowerPoint 2003, only the Callout shape that has the default arrow settings is displayed. The Callout shape that has nondefault arrow settings is not displayed.
•	Consider the following scenario: 1. In an instance of PowerPoint 2007, you create a new presentation (.pptx), and you add a drawing object in a slide. 2. In another instance of PowerPoint 2007, you open a PowerPoint 2003 presentation (.ppt) in which you have set the default formatting for drawing objects. 3. You copy and paste the slide that you created in step 1 to the PowerPoint 2003 presentation that you opened in step 2. In this scenario, you find that the drawing object that you add to the slide in step 1 uses the default formatting that was set in the PowerPoint 2003 presentation.
•	You create a chart in a Microsoft Office Excel 2007 workbook. Then, you copy and paste the chart to a slide in PowerPoint 2007. In this case, a new Excel 2007 instance starts unexpectedly.
•	In an Excel 2007 workbook, you insert a chart and then change the font color for legend entries. Then, you save the changes to the workbook. When you reopen the workbook in Excel 2007, the font color for the legend entries is reverted unexpectedly to the original color.
•	In an Excel 2007 workbook, you insert a chart, and you make the trendline and the equation that is displayed on the chart. When you copy and paste the chart into a Word document or into a PowerPoint presentation, the equation may be displayed incorrectly on the chart. Additionally, when you save and reopen the Excel 2007 workbook that contains the chart, you may find that the equation is also displayed incorrectly.

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry information

You do not have to make any changes to the registry to apply this hotfix.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix has the file attributes (or later 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 item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb956058-fullfile-x86-glb.exe	12.0.6327.5000	17,307,968	21-Aug-2008	05:10	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Oart.msp	Not Applicable	16,296,448	20-Aug-2008	15:03	Not Applicable
Oartconv.msp	Not Applicable	8,827,904	20-Aug-2008	15:03	Not Applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Contents of the Oart.msp file

Contents of the Oartconv.msp file

Additional notes

•	For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.
•	For more information, click the following article number to view the article in the Microsoft Knowledge Base: 824684 (/Feedback.aspx?kbNumber=824684/) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Back to the top

Issue that this hotfix package fixes

This hotfix package fixes the following issue that was not previously documented in a Microsoft Knowledge Base article:

After you upgrade from Microsoft Office 2003 to the 2007 Microsoft Office system, you may receive the following error message when you double-click an .xml file:

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issue that is listed in this article.The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

Microsoft Windows Installer .msp file information

Xmleditverb.msp information

Back to the top

This guidance contains recommendations that are based on the kinds of scenarios that may exist in various Microsoft operating system environments. This guidance includes how to use tools such as the following tools:

•	Windows Update
•	Microsoft Update
•	Office Update
•	The Microsoft Baseline Security Analyzer (MBSA)
•	Windows Server Update Services (WSUS)
•	Microsoft System Center Configuration Manager
•	Microsoft Systems Management Server (SMS)
•	The Extended Security Update Inventory Tool

This article describes the detection and deployment guidance for the security release that is dated August 12, 2008.

Back to the top

Detection and deployment

Environments that detect and deploy security updates by using Windows Update, Microsoft Update, Office Update, and Mactopia

Security updates that were released on August 12, 2008 are available through the following Web sites. Any exceptions are described in each Web site section. The products that are supported by each Web site are also listed.

NoteNot every update is available on every Web site that is listed here.

Windows Update

The products that are supported by this Web site are as follows:

•	Microsoft Windows 2000
•	Windows XP
•	Windows Server 2003
•	Windows Vista
•	Windows Server 2008

Microsoft Update

The products that are supported by this Web site are as follows:

•	Microsoft Internet Security and Acceleration Server 2004
•	Microsoft Internet Security and Acceleration Server 2006
•	Microsoft Exchange 2000 Server
•	Microsoft Exchange Server 2003
•	Microsoft Exchange Server 2007
•	Microsoft Office 2002
•	Microsoft Office 2003
•	The 2007 Microsoft Office system
•	Windows 2000
•	Windows XP
•	Windows Server 2003
•	Windows Vista
•	Windows Server 2008
•	Microsoft SQL Server 2005
•	Microsoft Forefront Client Security
•	Microsoft Visual Studio 2005

General exceptions

•	Microsoft Update does not support SQL 7.0 or Microsoft Date Engine (MSDE) 1.0.
•	Microsoft Update does not support Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.
•	Microsoft Update does not support MSN Messenger or Windows Live Messenger.

Specific exceptions

•

955702 (MS08-050) – Microsoft Update only supports Windows Messenger 4.7 on Windows XP Service Pack 2 (SP2) and on Windows XP Service Pack 3 (SP3). No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

Office Update

The products that are supported by this Web site are as follows:

•	Office 2000
•	Office 2002
•	Office 2003
•	The 2007 Office system

General exceptions

•	Office Update does not support 2007 Office components when they are installed on computers that are running Windows Vista or Windows Server 2008. You must use Microsoft Update instead.
•	Office Update does not support any Macintosh products.

Mactopia

The products that are supported by this Web site are as follows:

•	Microsoft Office 2001 for Mac
•	Microsoft Office 2004 for Mac
•	Microsoft Office X for Mac
•	Microsoft Office 2008 for Mac

Environments that detect security updates by using Microsoft Baseline Security Analyzer (MBSA) version 2.1

You can detect security updates that were released on August 12, 2008 if you use MBSA version 2.1.

NoteMBSA version 2.1 is now released and fully supports security and vulnerability assessment scans on Windows Vista and on Windows Server 2008.

General exceptions

•	MBSA version 2.1 does not support SQL 7.0 or MSDE 1.0.
•	MBSA version 2.1 does not support any Office 2000 components.
•	MBSA version 2.1 does not support any Macintosh products.
•	MBSA version 2.1 does not support Microsoft Works 8 when using an offline scan. For more information, see the Offline and Online scans section, later in this section.
•	MBSA version 2.1 does not support MSN Messenger or Windows Live Messenger.
•	MBSA version 1.2.1 and 2.0.1 are no longer supported.

Specific exceptions

•	955702 (MS08-050) – MBSA only supports Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.
•	924090 (MS08-044) – MBSA only supports detection of Microsoft Works when doing an online scan. For more information, see the Offline and Online scans section, later in this section.

Offline and Online scans

•	Online scan This is when the system that is scanned by MBSA 2.1 has connectivity to Microsoft Update. This is shown in the completed scan report.
•	Offline scan This is when the system that is scanned by MBSA 2.1 is managed by WSUS or in an offline secure environment that forces the system to use the WSUSSCN2.CAB offline catalog.

Environments that detect and deploy security updates by using Windows Server Update Services (WSUS)

You can detect and deploy security updates that were released on August 12, 2008 if you use any of the following items:

•	WSUS 2.0 Service Pack 1 (SP1)
•	WSUS 3.0
•	WSUS 3.0 SP1

General exceptions

•	WSUS does not support SQL 7.0 or MSDE 1.0.
•	WSUS does not support Microsoft Works 8.
•	SUS 1.0 SP1 is no longer supported. It will not receive security updates.

Specific exceptions

•

955702 (MS08-050) – WSUS only supports Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or SCCM 2007

You can detect and deploy all security updates that were released on August 12, 2008 if you use any of the following items:

•	Systems Management Server (SMS) 2.0 together with the SUS Feature Pack
•	Systems Management Server (SMS) 2003 together with the SUS Feature Pack
•	Systems Management Server (SMS) 2003 together with Inventory Tool for Microsoft Updates (ITMU)
•	System Center Configuration Manager (SCCM) 2007

General exceptions

•	Microsoft Systems Management Server 2003 SP3 includes support for, and is required for, Windows Vista and Windows Server 2008 manageability.
•	SMS 2003 together with ITMU and SCCM 2007 do not support the following products: • SQL 7.0 • MSDE 1.0 • Microsoft Works 8
•	SMS together with the SUS Feature Pack do not support the following products: • MSDE 1.0 • SQL 2005 • SQL 2008 • Exchange 2007 • Microsoft Works 8 • The 2007 Office system • Windows Internet Explorer 7 • Windows Vista • Windows Server 2008 • Any x64-based versions of Windows or of SQL • Any Itanium-based versions of Windows or of SQL
•	The SMS SUS Feature Pack, SMS ITMU, and SCCM do not support any Macintosh products.

Specific exceptions

•

955702 (MS08-050) – SMS SUSFP, SMS ITMU, and SCCM 2007 only support Windows Messenger 4.7 on Windows XP SP2 and on Windows XP SP3. No other versions of Windows are supported. Windows Messenger 5.1 is not supported.

NoteThe SMS SUS Feature Pack requires the Extended Security Update Inventory Tool to detect all the security updates.

To obtain the Extended Security Update Inventory Tool, visit the following Microsoft Web site:

Summary of detection and deployment guidance

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

NoteTo simplify this table, items that were listed under the general exceptions heading for each detection and deployment technology are not included.

For example, the SMS SUS Feature Pack column in this table may include a Yes. However, the security bulletin lists a Windows Vista component as affected. Previously, we would have stated in the table that the SMS SUS Feature Pack partly supported the deployment of the security update because the SMS SUS Feature Pack does not support Windows Vista components. Currently, we no longer account for that specific exception in the table because the exception is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.1	WSUS 2.0 and WSUS 3.0	SMS SUS Feature Pack	SMS Inventory Tool for Microsoft Updates	System Center Configuration Manager 2007
			Detect and deploy	Detect and deploy	Detect and deploy	Detect only	Detect and deploy	Detect and deploy	Detect and deploy	Detect and deploy
955617	MS08-041	Access	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
955048	MS08-042	Word	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
954066	MS08-043	Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
924090	MS08-044	Office Filters	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
953838	MS08-045	Internet Explorer	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
952954	MS08-046	Windows ICM	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
953733	MS08-047	IPsec	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
951066	MS08-048	Outlook Express/Windows Mail	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
950974	MS08-049	Event System	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes	Yes
955702	MS08-050	Windows Messenger	Not applicable	Partly, see the Windows Update section	Partly, see the Microsoft Update section	Partly, see the MBSA section	Partly, see the WSUS section	Partly, see the SMS section	Partly, see the SMS Update section	Partly, see the SCCM section
949785	MS08-051	PowerPoint	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes

Rereleased security updates

There are no rereleases this month.

Back to the top

Frequently asked questions

What is Microsoft doing to provide guidance about how to deploy these updates?

We encourage system administrators to join the monthly technical Webcast to learn more about security updates. The Webcast for this security update airs on August 13, 2008 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

What other information should I know about MBSA?

For more information about the programs that MBSA currently supports, visit the following Microsoft TechNet Web site:

Can I use SMS or System Center Configuration Manager to determine whether the updates are required?

Yes. SMS helps detect and deploy these security updates. SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with SUSFP use MBSA version 1.2.1 technology for detection. Therefore, SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack have limitations that resemble the limitations of MBSA version 1.2.1.

For more information about SMS, visit the following Microsoft Web site:

The SUS Feature Pack together with the Extended Security Update Inventory Tool is required to detect all the security updates on Microsoft Windows and on other affected Microsoft products.

For more information about the limitations of the SUS Feature Pack, click the following article number to view the article in the Microsoft Knowledge Base:

SMS 2.0 together with the SUS Feature Pack and SMS 2003 together with the SUS Feature Pack also use the Microsoft Office Inventory Tool to detect the required security updates for Microsoft Office programs such as Microsoft Word.

SMS 2003 customers can also use ITMU to detect and deploy security updates. ITMU uses technology from Microsoft Updates. For more information about ITMU, visit the following Microsoft Web site:

System Center Configuration Manager 2007 uses WSUS 3.0 for detection and deployment of these security updates. Therefore, anything that is supported by WSUS 3.0 is also supported by System Center Configuration Manager 2007.

Back to the top

This problem affects both Microsoft Office Outlook Web Access Premium and Microsoft Office Outlook Web Access Light. Windows Internet Explorer 7 and later versions of Internet Explorer are the only versions of Internet Explorer that support the S/MIME control.

Note This problem occurs only if the following conditions are true:

•	The e-mail messages are sent within a Microsoft Exchange Server organization.
•	The e-mail messages are sent from Microsoft Exchange 2000 Server or from Microsoft Exchange Server 2003 to Exchange Server 2007.
•	The e-mail messages are in an Exchange Server 2007 mailbox.

Back to the top

Back to the top

Back to the top

If you forward the e-mail message in Outlook or if you perform any other operation that promotes the clear signed content to the relevant MAPI properties of the clear signed message, the body of the e-mail message is visible in Outlook Web Access.

For more information about clear signed messages, visit the following Web sites:

For more information about S/MIME, visit the following Web site:

Back to the top

Back to the top

Issues that this hotfix package fixes

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	Consider the following scenario: • On an Office SharePoint site, you set a document library’s document template type to Microsoft Office Word 97-2003 document (.doc). • On a client computer that is running Office Word 2007, you create a new document from the document library. In this case, when you try to save the document in Office Word 2007, the default document type that appears in the Save as type box of the Save As dialog box is Word Document (*.docx). Additionally, if you do not notice that Word Document (*.docx) is wrong document type for the document library on the SharePoint site, and then click Save in the Save As dialog box, a dialog box states that states that you are saving the document in the wrong document type . If you click Cancel in this dialog box, you notice that the Save As dialog box reappears. However, the file name is changes to some random numbers together with .tmp file name extension. For example, the file name may appear as 6AF9E345.tmp.docx.
•	In Office Word 2007, you add a XML schema to the schema library. Then, when you open or close a document that has the XML schema applied, you may notice that a memory leak occurs in Performance Monitor.
•	In Office Word 2007, you insert an object that is from an Internet address. After that, when you try to change the source of the linked object to another Internet address, you receive the following error message: You cannot use an Internet address here. Enter a path that points to a location on your computer or on the network.
•	Office Word 2007 stops responding when you try to open WordPerfect 5.1 files.
•	You embed a Word document object in a 2007 Microsoft Office file. However, you cannot save a copy of the Word document object to a network location in the Word 2007 format (.docx).

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix package, you must have Word 2007 installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.The global version of this hotfix has the file attributes (or later 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 item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb941468-fullfile-x86-glb.exe	12.0.6300.5000	15,670,968	28-Jan-2008	17:55	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,064,704	28-Jan-2008	18:15	Not Applicable
Wordconv.msp	Not Applicable	6,239,232	28-Jan-2008	18:15	Not Applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Contents of the Word.msp file

Contents of the Wordconv.msp file

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

• If you do not have an SMTP connector that includes the required address space type.
• If you have an address space that is scoped to the whole Exchange organization in a custom connector, and the custom connector is configured on a computer that is running Exchange 2000 Server or an Exchange Server 2003.

Back to the top

1. Create a new Send connector on the Exchange Server 2007 computer. Make sure that this connector includes the required custom address space type and that the connector points to a smart host. For more information about how to create a Send connector in Exchange Server 2007, visit the following Microsoft Web site:
   http://technet.microsoft.com/en-us/library/aa998814.aspx (http://technet.microsoft.com/en-us/library/aa998814.aspx)
2. Restart the Microsoft Exchange Information Store service in the Services snap-in. This updates the registry entry on the client.
3. Restart Outlook.
4. Send e-mail to the custom address.

Back to the top

This list in the registry is refreshed every time that Outlook starts a MAPI session in cached mode. This list is stored in the 01026687 registry entry under the following registry subkey:

Back to the top

For example, you modify the following Setting Id element in the Config.xml file.

<Setting Id=Reboot Value=Never />

However, the computer still prompts you to restart when you use this Config.xml file to deploy the 2007 Office system.

Note The default setting for the Setting Id element in the Config.xml file is as follows.

<Setting Id=Reboot Value=IfNeeded />

Back to the top

Back to the top

<Setting Id=SETUP_REBOOT Value=Never />

The Never value makes sure that you are not prompted to restart and that the restart process does not occur automatically.

The values that you can configure for the SETUP_REBOOT property are as follows:

•	AutoAlways: Always initiate a restart. Do not prompt the user.
•	Always: Always prompt for a restart at the end of setup.
•	IfNeeded: Prompt for a restart at the end of setup if setup requires a restart. Note This is the default setting.
•	AutoIfNeeded: Initiate a restart if setup requires a restart. Do not prompt the user.
•	Never: Never initiate or prompt for a restart.

Back to the top

For more information about the 2007 Office Resource Kit, visit the following Microsoft Web site:

For more information about how to use the Config.xml file, visit the following Microsoft Web site:

For more information about the Setup properties and about how they can be controlled in the Config.xml file, visit the following Microsoft Web site:

Back to the top

To resolve this issue, you must remove Business Contact Manager manually.

Important We recommend that you use the Add or Remove Programs feature or Programs and Features to uninstall Business Contact Manager. If Add or Remove Programs or Programs and Features does not completely uninstall Business Contact Manager, you will be continuously prompted to install Business Contact Manager. You can follow the steps in this article to manually uninstall it. To install or uninstall Business Contact Manager, you must be an administrator on the computer.

Before you remove Business Contact Manager, follow these steps:

1. Use an account that has the appropriate permissions. Log on to the computer by using an account that is a member of the local Administrators group.
2. Back up your data if you want save your Business Contact Manager databases in their present state. Typically, Business Contact Manager databases (.mdf files) are stored in a folder that belongs to the user who created the database.
   • In Windows XP:
     C: Documents and Settings <user> Local Settings Application Data Microsoft Business Contact Manager
   • In Windows Vista:
     C: Users <user> AppData Local Microsoft Business Contact Manager
3. Stop all SQL Server services. We recommend that you stop all SQL Server services before you uninstall SQL Server components. Active connections can prevent successful uninstallation. To stop SQL Server services, follow these steps:
   1. • In Windows XP:
        Click Start, click Control Panel, click Administrative Tools, and then double-click Services.
      • In Windows Vista:
        Click Start
        Collapse this imageExpand this image

        

        , type Services.msc in the Start Search box, and then press ENTER.

   2. In the Name list, right-click each service that is related to SQL Server, and then click Stop.
4. Uninstall SQL Server. For more information about how to uninstall SQL Server, visit the following Microsoft Web site:

Note You should follow these steps to remove Business Contact Manager in the order in which they are listed.

To manually uninstall Business Contact Manager, follow these steps.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

1. Uninstall Business Contact Manager install packages by using the Msiexec.exe command-line tool.

   For more information about how to use the Msiexec.exe command-line tool, visit the following Microsoft Web site:

   http://technet.microsoft.com/en-us/library/cc759262.aspx (http://technet.microsoft.com/en-us/library/cc759262.aspx)
2. In Windows XP:
   • Click Start, click Run, type Regedit in the Open box, and then click OK.

   In Windows Vista:

   • Click Start, type Regedit in the Start Search box, and then click Regedit.exe in the Programs list.
3. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Uninstall
4. Locate the Business Contact Manager entry under this subkey, and then double-click the UninstallString entry in the right pane.
5. Copy the contents that are displayed in the Value data box.
6. Click Start, click Run, type cmd in the Open box, and then click OK.
7. Paste or type the content that you copied in step 5 at the command prompt, and then press ENTER.
8. Click Yes when you are prompted to confirm removal of Business Contact Manager.
9. Repeat steps 4 through 8 for all Business Contact Manager entries that you find under the HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Uninstall subkey.
10. If you experience the symptoms after you perform steps 1 through 9, delete the Business Contact Manager registry subkey.
11. Locate the following subkey in Registry Editor:
    HKEY_LOCAL_MACHINE SOFTWARE Microsoft Business Solution eCRM
12. Right-click the Business Solution eCRM subkey, and then click Delete.
13. Locate the following subkey in Registry Editor:
    HKEY_CURRENT_USER SOFTWARE Microsoft Business Solution eCRM
14. Right-click the Business Solution eCRM subkey, and then click Delete.
15. Locate the following subkey in Registry Editor:
    HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion SharedDLLs
16. Locate the following entry under the Names column in the right pane:
    DriveLetter: Program Files Microsoft Small Business Business Contact Manager lpshared

    Note In this step, DriveLetter is the name of the drive where Business contact Manager is installed.

17. Right-click the entry, and then click Delete.

If these steps do not uninstall all the components and files that are related to Business Contact Manager, contact product support. For a complete list of product support telephone numbers, visit the following Microsoft Web site:

Back to the top

Back to the top

Detection and deployment

Environments that detect and that deploy security updates by using Windows Update, Microsoft Update, and Office Update

Security updates that were released on May 8, 2007 are available through the following Web sites. Any exceptions are in the following list. The products that are supported by each Web site are also listed.

•	Microsoft Windows Update http://update.microsoft.com/windowsupdate (http://update.microsoft.com/windowsupdate) • Windows 2000, Windows XP, Windows Server 2003
•	Microsoft Update http://update.microsoft.com/microsoftupdate (http://update.microsoft.com/microsoftupdate) • Windows 2000, Windows XP, and Windows Server 2003 • Microsoft Office XP and Office 2003 • Microsoft Exchange 2000 and Exchange 2003 • Internet Security and Acceleration Server 2004 • Microsoft SQL Server 2005 • Security update 934233 (security bulletin MS07-023) Microsoft Update does not support the Excel 2000 part of this security update. • Security update 934232 (security bulletin MS07-024) Microsoft Update does not support the Word 2000 part of this security update. • Security update 934873 (security bulletin MS07-025) Microsoft Update does not support the Office 2000 part of this security update.
•	Office Update http://officeupdate.microsoft.com (http://officeupdate.microsoft.com) • Office 2000, Office XP, and Office 2003
•	Mactopia http://www.microsoft.com/mac (http://www.microsoft.com/mac) • Office 2001 for Mac • Office X for Mac • Office 2004 for Mac

Note Not every update is available on every Web site that is listed.

Environments that detect security updates by using MBSA version 1.2.1 or MBSA version 2.0.1

Microsoft Baseline Security Analyzer (MBSA) version 1.2.1 contains an integrated version of the Office Detection Tool (ODT). If you use MBSA 1.2.1 or MBSA version 2.0.1 to detect security updates, you can detect all the security updates that were released on May 8, 2007. Any exceptions are in the following list.

Note The ODT part of MBSA 1.2.1 is limited to local scans only.

Note MBSA 1.2.1 does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

Note MBSA 2.0.1 is not supported on Windows Vista. However, MBSA 2.0.1 supports remote scans of computers that are running Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Environments that detect and that deploy security updates by using Software Update Services (SUS) or Windows Server Update Services (WSUS)

If you use SUS, WSUS 2.0, or WSUS 3.0 to detect and to deploy security updates, you can detect most security updates that were released on May 8, 2007. Any exceptions are in the following list.
Note SUS 1.0 SP1 does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

•	Security update 934233 (security bulletin MS07-023) SUS does not support any part of this security update. WSUS does not support the Excel 2000 part of this security update.
•	Security update 934232 (security bulletin MS07-024) SUS does not support any part of this security update. WSUS does not support the Word 2000 part of this security update.
•	Security update 934873 (security bulletin MS07-025) SUS does not support any part of this security update. WSUS does not support the Office 2000 part of this security update.
•	Security update 931906 (security bulletin MS07-028) SUS does not support any part of this security update.

Environments that detect and that deploy security updates by using SMS 2.0 together with the Security Update Inventory Tool (SUIT) or SMS 2003 together with the Inventory Tool for Microsoft Updates (ITMU)

If you use Microsoft Systems Management Server (SMS) 2.0 together with SUIT, SMS 2003 together with SUIT, or SMS 2003 together with ITMU to detect and to deploy security updates, you can detect and deploy all security updates that were released on May 8, 2007. Any exceptions are in the following list.
Note SMS together with SUIT does not support Windows Vista, any Windows x64 editions, or Windows Itanium-based systems.

•	Security update 934233 (security bulletin MS07-023) SMS ITMU does not support the Excel 2000 part of this security update.
•	Security update 934232 (security bulletin MS07-024) SMS ITMU does not support the Word 2000 part of this security update.
•	Security update 934873 (security bulletin MS07-025) SMS ITMU does not support the Office 2000 part of this security update.
•	Security update 931832 (security bulletin MS07-026) SMS SUIT does not support the Exchange 2007 part of this security update.
•	Security update 931906 (security bulletin MS07-028) SMS SUIT supports this update when you use the Extended Security Update Inventory Tool (ESUIT).

To obtain ESUIT, visit the following Microsoft Web site:

Back to the top

Summary of detection and deployment guidance

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

Security update

Bulletin

Component

Office Update

Windows Update

Microsoft Update

MBSA 1.2 and the Office Detection Tool

MBSA 2.0.1

SUS

WSUS 2.0 and WSUS 3.0

Enterprise Scan Tool

SMS Security Update Inventory Tool

SMS Inventory Tool for Microsoft Updates

Detect and deploy

Detect and deploy

Detect and deploy

Detect only

Detect only

Detect and deploy

Detect and deploy

Detect only

Detect and deploy

Detect and deploy

934233

MS07-023

Excel

Yes

Not applicable

Partially, see the MU section

Yes

Partially, see the MBSA section

Not applicable

Partially, see the WSUS section

Not applicable

Yes

Partially, see the SMS section

934232

MS07-024

Word

Yes

Not applicable

Partially, see the MU section

Yes

Partially, see the MBSA section

Not applicable

Partially, see the WSUS section

Not applicable

Yes

Partially, see the SMS section

934873

MS07-025

Office

Yes

Not applicable

Partially, see the MU section

Yes

Partially, see the MBSA section

Not applicable

Partially, see the WSUS section

Not applicable

Yes

Partially, see the SMS section

931832

MS07-026

Exchange

Not applicable

Not applicable

Yes

Partially, see the MBSA section

Yes

Not applicable

Yes

Not applicable

Partially, see the SMS section

Yes

931768

MS07-027

Internet Explorer

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

931906

MS07-028

CAPICOM

Not applicable

Not applicable

Yes

No

Yes

Not applicable

Yes

Yes

Yes, with ESUIT

Yes

935966

MS07-029

DNS

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

Back to the top

Rereleased security updates

There are no rereleases this month.

Back to the top

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 May 9, 2007 at 11:00 A.M. (Pacific Time). To register, visit the following Microsoft Web site:

Q2: Is the Enterprise Scan Tool (EST) cumulative for SMS like ESUIT is cumulative for SMS?

A2: No, the EST is not cumulative. There are no plans to make the EST cumulative.

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

A3: Yes, you can use MBSA 1.2.1 and MBSA 2.0.1 to fully detect the need for the following security updates that were released on May 8, 2007, except where noted.

Microsoft Knowledge Base article number	Bulletin ID	Component	Detection note
934233	MS07-023	Excel	See the MBSA section
934232	MS07-024	Word	See the MBSA section
934873	MS07-025	Office	See the MBSA section
931832	MS07-026	Exchange	See the MBSA section
931906	MS07-028	CAPICOM	See the MBSA section

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

You may have installed a program that is listed in the Affected software section of a security bulletin that is mentioned in the related article. In this case, 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:

Q4: Which security updates require that I use the EST together with MBSA 1.2.1 to determine which systems on my network are vulnerable?

A4: The following security update requires that you use the EST together with MBSA to determine which systems on the network are vulnerable.

Microsoft Knowledge Base article number	Bulletin ID	Component
931906	MS07-028	CAPICOM

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

A5: Yes, SMS helps detect and deploy these security updates. SMS 2.0 and SMS 2003 together with SUIT use MBSA 1.2.1 technology for detection. Therefore, SMS 2.0 and SMS 2003 together with SUIT have limitations that resemble the limitations of MBSA 1.2.1. For more information about SMS, visit the following Microsoft Web site:

SUIT together with ESUIT are required for detection of all the security updates on Microsoft Windows and on other affected Microsoft products. For more information about the limitations of SUIT, click the following article numbers to view the articles in the Microsoft Knowledge Base:

SMS 2.0 and SMS 2003 together with SUIT also use the Microsoft Office Inventory Tool to detect the required security updates for Microsoft Office programs such as Microsoft Word.

Alternatively, SMS 2003 customers can use ITMU to detect and deploy security updates. ITMU uses technology from Microsoft Updates. For more information about ITMU, visit the following Web site:

Back to the top

Back to the top

Issues that this hotfix package fixes

This hotfix package fixes the following issues:

•	940977 (/Feedback.aspx?kbNumber=940977/) The ShapeRange.Shadow.Type property incorrectly returns a value of -2 for all shadow types when you try to programmatically obtain the shadow type of a shape in PowerPoint 2007
•	944970 (/Feedback.aspx?kbNumber=944970/) A text box that has the Resize shape to fit text option enabled does not anchor as expected in Microsoft Office PowerPoint 2007

This hotfix fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

•	In Microsoft Office Excel 2007, when you save an Excel workbook that contains a chart that is created in Excel 2003, Excel 2007 may randomly stop responding (hang). This issue occurs when you save the workbook after you print the workbook. Or, this issue occurs when you save the workbook after you preview the workbook in the Print Preview window.
•	In Microsoft Office Excel 2007, you use the Chart.Axes(xlValue) method or the Chart.Axes(xlCategory) method to return an axis object. However, the position and size information about the axis are incorrect if the chart is a 3D chart. This issue does not occur in Microsoft Excel 2000 or in Microsoft Office Excel 2003.
•	In Microsoft Office PowerPoint 2007, when you try to resize a horizontal line or a vertical line by pressing the SHIFT key, the line incorrectly extends to the maximum allowed size.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.
The Global version of this hotfix has the file attributes (or later 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 item in Control Panel.Download information

File name	File version	File size	Date	Time	Platform
Office-kb941658-fullfile-x86-glb.exe	12.0.6300.5000	29,596,416	28-Jan-2008	17:55	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Mso.msp	Not Applicable	18,862,592	28-Jan-2008	18:18	Not Applicable
Oart.msp	Not Applicable	15,945,216	28-Jan-2008	18:18	Not Applicable
Oartconv.msp	Not Applicable	8,575,488	28-Jan-2008	18:18	Not Applicable

After the hotfix is installed, the Global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Mso.msp

Oart.msp

Oartconv.msp

NoteFor more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Update details

This update replaces the following previously released update:

Back to the top

Installation details

How to obtain and install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

To determine the version of the files that are installed on the computer, follow these steps, as appropriate for the operating system that you are running.

Windows Vista

1. Click Start
   Collapse this imageExpand this image

   

   , and then click Search.

2. Click Advanced Search.
3. In the Location box, click Local Hard Drives.
4. In the Name box, type Outlfltr.dat, and then click Search.
5. In the list of files, right-click Outlfltr.dat, and then click Properties.
6. On the General tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Windows XP

1. Start Search Companion. To do this, click Start, and then click Search.

   Note If Windows Desktop Search starts, click Click here to use Search Companion.

2. In the Search Results window, click All files and folders in the Search Companion pane.
3. In the All or part of the file name box, type Outlfltr.dat, and then click Search.
4. In the list of files, right-click Outlfltr.dat, and then click Properties.
5. On the General tab and on the Version tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting, executable file. The following .msp file is distributed in this update:

Information for administrators about how to reinstall specific components

If you update your administrative installation point and if you then recache and reinstall Outlook 2007 on client computers, you can run a command-line command that includes the REINSTALL=[ list of features ] property. This property specifies whether you want to reinstall specific components of Outlook 2007 from the administrative image.

For this update, the value for REINSTALL=[ list of features ] is as follows:

Or, you can substitute the REINSTALL=ALL parameter to reinstall all Microsoft Office components on the client computer.

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

For more information about the policy for how e-mail is filtered by the junk e-mail filters in Outlook or in Exchange Server, click the following article number to view the article in the Microsoft Knowledge Base:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

Additionally, an error message that resembles the following is logged in the SQL Server Errorlog file:

The following events are also logged in the Application log:

Note This issue may also occur if you install the stand-alone version of SQL Server 2005 Express Edition.

Back to the top

Back to the top

Back to the top

Update details

This update replaces the following previously released update:

Back to the top

Installation details

How to obtain and install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

To determine the version of the files that are installed on the computer, follow these steps, as appropriate for the operating system that you are running.

Windows Vista

1. Click Start
   Collapse this imageExpand this image

   

   , and then click Search.

2. Click Advanced Search.
3. In the Location box, click Local Hard Drives.
4. In the Name box, type Outlfltr.dat, and then click Search.
5. In the list of files, right-click Outlfltr.dat, and then click Properties.
6. On the General tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Windows XP

1. Start Search Companion. To do this, click Start, and then click Search.

   Note If Windows Desktop Search starts, click Click here to use Search Companion.

2. In the Search Results window, click All files and folders in the Search Companion pane.
3. In the All or part of the file name box, type Outlfltr.dat, and then click Search.
4. In the list of files, right-click Outlfltr.dat, and then click Properties.
5. On the General tab and on the Version tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting, executable file. The following .msp file is distributed in this update:

Information for administrators about how to reinstall specific components

If you update your administrative installation point and if you then recache and reinstall Outlook 2007 on client computers, you can run a command-line command that includes the REINSTALL=[ list of features ] property. This property specifies whether you want to reinstall specific components of Outlook 2007 from the administrative image.

For this update, the value for REINSTALL=[ list of features ] is as follows:

Or, you can substitute the REINSTALL=ALL parameter to reinstall all Microsoft Office components on the client computer.

For information about how to distribute product updates for the 2007 Microsoft Office system, visit the following Microsoft Web site:

For more information about the policy for how e-mail is filtered by the junk e-mail filters in Outlook or in Exchange Server, click the following article number to view the article in the Microsoft Knowledge Base:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

You may want to create custom e-mail alert handler in Microsoft Office SharePoint Server 2007 in any of the following scenarios:

•	Fields, such as the ItemName field, are truncated to 70 characters in the e-mail alert. To work around the 70-character limit, use the method that this article describes.
•	You want to embed additional content in the e-mail alert.
•	You want to change the layout or the appearance of the e-mail alert.

These steps include sample code that formats the output to closely resemble the default alert template e-mail messages. You can modify the HTML in this sample code to customize the resulting e-mail alert.

1.	Create a class project that inherits from the IAlertNotificationHandler interface. Include the Microsoft.SharePoint namespace and the Microsoft.SharePoint.Utilities namespace in the project. Use the following code: public class Class1:IAlertNotifyHandler { #region IAlertNotifyHandler Members public bool OnNotification(SPAlertHandlerParams ahp) { try { SPSite site = new SPSite(ahp.siteUrl+ahp.webUrl); SPWeb web = site.OpenWeb(); SPList list=web.Lists[ahp.a.ListID]; SPListItem item = list.GetItemById(ahp.eventData[0].itemId) ; string FullPath=HttpUtility.UrlPathEncode(ahp.siteUrl++ahp.webUrl++list.Title++item.Name); string ListPath = HttpUtility.UrlPathEncode(ahp.siteUrl + + ahp.webUrl + + list.Title); string webPath=HttpUtility.UrlPathEncode(ahp.siteUrl++ahp.webUrl); string build = ; if (ahp.eventData[0].eventType==1) eventType=Added; else if(ahp.eventData[0].eventType==2) eventType=Changed; else if(ahp.eventData[0].eventType==3) eventType=Deleted; build = <style type= text/css >.style1 { font-size: small; border: 1px solid #000000;+ background-color: #DEE7FE;}.style2 { border: 1px solid #000000;}</style></head>+ <p><strong>+ item.Name.ToString() +</strong> has been +eventType +</p>+ <table style= width: 100% class= style2 ><tr><td style= width: 25% class= style1 >+ <a href=+ webPath +/_layouts/mysubs.aspx>Modify my Settings</a></td>+ <td style= width: 25% class= style1 > <a href=+ FullPath +>View +item.Name+</a></td>+ <td style= width: 25% class= style1 ><a href= + ListPath + >View + list.Title + </a></td> + </tr></table>; string subject=list.Title.ToString() ; SPUtility.SendEmail(web,true , false, ahp.headers[to].ToString(), subject,build); return false; } catch (System.Exception ex) { return false; } } #endregion }
2.	Add a strongly-signed .dll file to the Global Assembly Cache (GAC). You can drag the assembly to the assembly folder. Or, you can use the GACUtil tool to register the .dll file. For more information, visit the following MSDN Web sites: • Installing an Assembly into the Global Assembly Cache http://msdn2.microsoft.com/en-us/library/dkkx7f79(vs.71).aspx (http://msdn2.microsoft.com/en-us/library/dkkx7f79(vs.71).aspx) • Global Assembly Cache Tool (Gacutil.exe) http://msdn2.microsoft.com/en-us/library/aa309379(VS.71).aspx (http://msdn2.microsoft.com/en-us/library/aa309379(VS.71).aspx) For more information, click the following article number to view the article in the Microsoft Knowledge Base: 315682 (/Feedback.aspx?kbNumber=315682/) How to install an assembly in the Global Assembly Cache in Visual Basic .NET or in Visual Basic 2005
3.	Make a copy of the alertTemplates.xml file that is in the following folder: C: Program Files Common Files Microsoft Shared Web Server Extensions 12 Template Xml Name this new file CustomAlertTemplates.xml, and then save the file. Note Do not directly modify the alertTemplates.xml file. Directly modifying this file is unsupported.
4.	Edit the file and search for the keyword properties.Add the following lines to the properties block: <NotificationHandlerAssembly>AlertHandler, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d59ecf2a3bd66904</NotificationHandlerAssembly> <NotificationHandlerClassName>AlertHandler.Class1</NotificationHandlerClassName> <NotificationHandlerProperties></NotificationHandlerProperties> The stub should resemble this now: <Properties> <ImmediateNotificationExcludedFields>ID;Author;Editor;Modified_x0020_By;Created_x0020_By;_UIVersionString;ContentType;TaskGroup;IsCurrent;Attachments;NumComments;</ImmediateNotificationExcludedFields> <DigestNotificationExcludedFields>ID;Author;Editor;Modified_x0020_By;Created_x0020_By;_UIVersionString;ContentType;TaskGroup;IsCurrent;Attachments;NumComments;</DigestNotificationExcludedFields> <NotificationHandlerAssembly>AlertHandler, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d59ecf2a3bd66904</NotificationHandlerAssembly> <NotificationHandlerClassName>AlertHandler.Class1</NotificationHandlerClassName> <NotificationHandlerProperties></NotificationHandlerProperties> </Properties> Include this XML stub in each alert template section that you want in the alert template file.
5.	At a command prompt, change to the C: Program Files Common Files Microsoft Shared web server extensions 12 BIN directory. Then, run the following command: stsadm -o updatealerttemplates -filename C: Program Files Common Files Microsoft Shared Web Server Extensions 12 TEMPLATE XML customalerttemplates.xml -url your_sharepoint_site url
6.	Run the following command: stsadm -o setproperty -pn job-immediate-alerts -pv every 1 minutes This command specifies how frequently SharePoint Server checks for alerts that are to be sent immediately. The value specified is in minutes. For this test, the frequency is set to 1 minute. For more information, visit the following Microsoft Web site: http://technet2.microsoft.com/windowsserver/WSS/en/library/0eb072fe-8321-483b-9d1e-3412e3f42a481033.mspx?mfr=true (http://technet2.microsoft.com/windowsserver/WSS/en/library/0eb072fe-8321-483b-9d1e-3412e3f42a481033.mspx?mfr=true)
7.	Make sure that you have SharePoint configured for outgoing e-mail messages.For more information about how to configure outgoing e-mail messages, visit the following Microsoft Web site: http://technet2.microsoft.com/windowsserver/WSS/en/library/91570494-09ba-4537-904b-c61a6268d6bc1033.mspx?mfr=true (http://technet2.microsoft.com/windowsserver/WSS/en/library/91570494-09ba-4537-904b-c61a6268d6bc1033.mspx?mfr=true)
8.	If you are using the document library for the test, make sure that you have alerts for the document library turned on.
9.	Run the following commands: • iisreset • services.msc
10.	In the Services MMC snap-in, restart the Windows SharePoint Services Timer service.

After you complete these steps, the custom e-mail alert handler should be configured. After you create a new alert, you should receive the updated custom e-mail alert.

How to get help and support for this security update

For home users, no-charge support is available by calling 1-866-PCSAFETY in the United States and Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for security update support issues, visit the International Support Web site:

For enterprise customers, support for security updates is available through your usual support contacts.

More information about this security update

For more information about this security update, click the following article numbers to view the articles in the Microsoft Knowledge Base:

For example, you create a customization file to install Microsoft Office OneNote 2007 and to generate a custom OneNote shortcut in the following location:

After you use this customization file, you notice that the OneNote shortcut is not generated in the following location as expected:

Instead, you notice that the shortcut is generated in the following location:

Back to the top

Installations of the 2007 Office system are per-computer. Therefore, the shortcuts are put in the CommonAppDataFolder folder instead of in the AppDataFolder folder.

Back to the top

After all per-user files and all registry entries are added by using the OCT, the shortcuts are copied to a user’s profile the next time that the user runs a 2007 Office application.

If you want the shortcuts to be copied to the profile before the user starts a 2007 Office application, you can add a registry entry that will run a one-time start of a 2007 Office application during the logon process.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To run a one-time start of a 2007 Office application during the logon process, use the Add registry entries section of the OCT to add a registry entry that resembles the following registry entry:

Back to the top

Back to the top

Update details

This update replaces the following previously released update:

Back to the top

Installation details

How to obtain and to install the update

This update is available from the Microsoft Download Center. To download this update and to obtain installation instructions and deployment strategies, visit the following Microsoft Web site:

How to determine whether the update is installed

This update contains files that have the versions that are listed in the following table.

File Name	Version	Size	Date	Time
Outlfltr.dat	12.0.6211.1416	3,613,680	21-Feb-2008	02:46

You do not have to install this update if you have a later version of the files that are listed in the table.

To determine the version of the files that are installed on the computer, follow the steps that are appropriate for your situation.

Windows Vista

1.	Click Start, and then click Search.
2.	Click Advanced Search.
3.	In the Location box, click Local Hard Drives.
4.	In the Name box, type Outlfltr.dat, and then click Search.
5.	In the list of files, right-click Outlfltr.dat, and then click Properties.
6.	On the General tab, examine the properties of the Outlfltr.dat file that is installed on the computer.

Windows XP

Information for administrators about .msp files

This update consists of a full-file Microsoft Windows Installer (.msp) file. The .msp file is packaged in a self-extracting executable file. The following .msp file is distributed in this update:

Information for administrators about how to reinstall specific components

If you update your administrative installation point, and if you then recache and reinstall Outlook 2007 on client computers, you can run a command-line command that includes the REINSTALL=[ list of features ] property. This property specifies whether you want to reinstall specific components of Outlook 2007 from the administrative image.

For this update, the value for [ list of features ] is as follows:

Or, you can substitute the REINSTALL=ALL parameter to reinstall all Microsoft Office components on the client computer.

For detailed procedures that describe how to update an administrative image and how to update client computers, see the Updating clients from a patched administrative image section in the Distributing Office 2003 Product Updates topic. To view this topic, visit the following Microsoft Web site:

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all versions of Office. For more information about the Office System TechCenter, visit the following Microsoft Web site:

Back to the top

In this scenario, the updated information is not present in the resource’s calendar or in its meeting entry.

Back to the top

How to obtain the hotfix

This issue is fixed in the Outlook 2007 Hotfix Package that was released on February 7, 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

Update details

The Office 2004 for Mac 11.4.2 Update contains several changes that improve security and stability. These changes include fixes for vulnerabilities that an attacker can use to overwrite the contents of a computer’s memory by using malicious code.

Back to the top

Prerequisites

Before you install the Office 2004 for Mac 11.4.2 Update, make sure that the computer is running Mac OS X 10.2.8 (Jaguar) or a later version of the Mac OS X operating system.

To verify that the computer meets this prerequisite, click About This Mac on the Apple menu.

Additionally, the Microsoft Office 2004 for Mac 11.4.1 Update must be installed on the computer before you install the Office 2004 for Mac 11.4.2 Update. To verify that the Office 2004 for Mac 11.4.1 Update is installed, follow these steps:

1.	On the Go menu, click Applications.
2.	Open the Microsoft Office 2004 folder, and then open the Office folder.
3.	Click the Microsoft Component Plugin file.
4.	On the File menu, click Get Info.
5.	Click General. The version information is displayed.

Back to the top

How to obtain the update

The following file is available for download from the Microsoft Download Center:

Download the Microsoft Office 2004 for Mac 11.4.2 Update package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=99F54471-CCF9-4D94-A882-A05ECD128ADC)

Release Date: May 13, 2008

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Notes

•

The Office 2004 for Mac 11.4.2 Update is also available from Microsoft AutoUpdate. AutoUpdate is a program that automatically keeps Microsoft software up-to-date. To use AutoUpdate, start a Microsoft Office program. Then, on the Help menu, click Check for Updates. For more information about resources for Office 2004 for Mac, visit the following Microsoft Web site: http://www.microsoft.com/mac (http://www.microsoft.com/mac)

•

The Read Me file that is included with the Office 2004 for Mac 11.4.2 Update includes the following important release information: • The minimum system requirements • Instructions for how to install the update • Information about how to troubleshoot problems that may occur when you install the update • Information about the updated files that this update adds or changes

Back to the top

Back to the top

List of issues that are fixed

This hotfix fixes the following issues:

•	932842 (/Feedback.aspx?kbNumber=932842/) A nested conditional field that contains a DocProperty field or a DocVariable field may not be updated as expected in a header or in a footer in Word 2003
•	943733 (/Feedback.aspx?kbNumber=943733/) After you merge or split table cells in a Word 2007 document while Track Changes is enabled, the row that contains the cells is not marked as a revision

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next 2007 Microsoft Office suites service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

There are no prerequisites for installing this hotfix package.

Restart information

You do not have to restart the computer after you apply this hotfix package.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you must either create a registry key or modify a registry key.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix has the file attributes (or later 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 item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb941273-fullfile-x86-glb.exe	12.0.6300.5000	11,795,000	28-Jan-2008	17:55	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,064,704	28-Jan-2008	18:13	Not Applicable

Contents of the Excel.msp file

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Issues that the hotfix package fixes

This hotfix fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

•	You enable the Confirm file format conversion on open option in Word 2007. When you double-click a newly created .docx file on the desktop, the Convert File dialog box appears. Note This problem occurs because the .docx file is a zero-byte file. The file is not a valid Word .docx file.
•	When you save a .docx file as an .rtf file, some characters in Office Math Markup Language (OMML) equations are changed.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next 2007 Microsoft Office suites service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix has the file attributes (or later 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 item in Control Panel.

Download information

File name	File version	File size	Date	Time	Platform
Office-kb949950-fullfile-x86-glb.exe	12.0.6300.5000	15,850,056	11-Mar-2008	21:22	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,222,912	12-Mar-2008	03:32	Not Applicable
Wordconv.msp	Not Applicable	6,249,984	12-Mar-2008	03:32	Not Applicable

Contents of the Word.msp file

Contents of the Wordconv.msp file

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Note This issue also occurs in Microsoft Office Outlook 2003.

Back to the top

Back to the top

Back to the top