To prohibit Outlook 2007 from sending the Winmail.dat file, follow these steps:

1. Install hotfix 957692.

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

   957692  (/Feedback.aspx?kbNumber=957692/ ) Description of the Outlook 2007 hotfix package (Outlook.msp): October 28, 2008
2. Add the DisableTNEF registry entry. To do this, follow these steps:
   1. Exit Outlook 2007.
   2. Start Registry Editor.
      • In Windows Vista, click Start
        Collapse this imageExpand this image

        

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

        Collapse this imageExpand this image

        

        If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

      • In Windows XP, click Start, click Run, type regedit, and then click OK.
   3. Locate and then select the following registry subkeys:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook Preferences

   4. On the Edit menu, point to New, and then click DWORD Value.
   5. Type DisableTNEF, and then press ENTER.
   6. Right-click DisableTNEF, and then click Modify.
   7. In the Value data box, type 1, and then click OK.
   8. On the File menu, click Exit to exit Registry Editor.

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

Update information

The update for Microsoft Office Outlook 2007 Help is available for download from the Microsoft Download Center. To download this update, visit the following Microsoft Web site:

Prerequisites

There are no prerequisites for installing this update.

Restart information

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

Removal information

To remove this update, use the Add or Remove Programs item in Control Panel.

System administrators can use the Spunist.exe tool to remove this update. The Spuninst.exe tool is located in the following folder:

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

File information

The English version of this update uses a Microsoft Windows Installer package to install the update. 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

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

Windows Vista helps business users significantly increase productivity by helping them find and use information, empower mobility and collaboration, improve security, and increase overall efficiency while keeping IT costs low.

This session will discuss and demonstrate how 2007 Microsoft Office System users can leverage Windows Vista features to achieve an even greater competitive advantage. Features in Word, Excel, PowerPoint, and the other Office programs can use the search, mobility, security, and efficiency of Windows Vista to get a lot more done, much faster, and more easily.

For example, we will see how the new Ribbon in the main Office programs can quickly harness the search capability of Windows Vista online. This helps bring vital data into Word and Excel documents. We will see how this information can then be easily shared with others on mobile devices or though online collaboration tools.

This is a Level 200 (http://support.microsoft.com/default.aspx?scid=gp;en-us;webcastlevels&sd=gn) session presented by Tom Bunzel.

Tom Bunzel specializes in knowing what presenters need and how to make technology work. He has appeared on Tech TV’s Call for Help, formerly as “Professor PowerPoint” and has been a featured speaker at InfoComm and PowerPoint LIVE. Tom also works as a “technology coach” for corporations, including the Neuroscience Education Institute. He teaches regularly at West LA College Extension and privately around Southern California.

Tom has written several books, the latest being Solving the PowerPoint Predicament: Using Digital Media for Effective Communication, Sams Teach Yourself PowerPoint 2003 in 24 Hours, and Easy Digital Music for QUE Publishing. Tom Bunzel’s other books are Easy Creating CDs and DVDs, How to Use Ulead DVD Workshop, Digital Video on the PC: Video Production on Your Multimedia PC, and the update to Peachpit Press’s PowerPoint 2002/2001 for Windows & Macintosh (Visual QuickStart Guide). He is Contributing Editor to “Presentations” magazine, and also writes a weekly column as the Office Reference Guide for InformIT.com.

He can be reached through his Web site http://www.professorppt.com/ (http://www.professorppt.com/).

Viewing the Presentation

To view, click this link: View this On-demand Recording (https://www118.livemeeting.com/cc/msevents/view?id=WV113006) (Length: 1 hour 9 minutes)

Provide Feedback on this Broadcast (http://support.microsoft.com/common/survey.aspx?scid=sw;en;1326&p0=WV&p1=en-us&p2=113006)

Support WebCasts Home (http://support.microsoft.com/webcasts)

When you use a rule to move messages from someone to a folder in Microsoft Office Outlook 2007, the rule does not work. Additionally, you receive the following error message:

Note This issue does not occur in Microsoft Office Outlook 2003.

Notes

• This issue can occur if Outlook 2003 does not use Microsoft Office Word as the e-mail editor.
• If the Outlook 2003 user opens the e-mail message by using Outlook Web Access, the hyperlink appears. However, it points to an invalid address. Additionally, in the Outlook Web Access Sent Items folder of the Outlook 2007 user, the hyperlink also points to an invalid address.

To resolve this issue, follow these steps:

1. Apply hotfix 957697. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   957697  (/Feedback.aspx?kbNumber=957697/ ) Description of the Word 2007 hotfix package (Word.msp): October 28, 2008
2. Set the WordRTFOutPathPref registry entry. To do this, follow these steps:
   1. Click Start, and then click Run.
   2. Type regedit, and then click OK.
   3. Locate and then click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Word Options
   4. On the Edit menu, point to New, and then click DWORD Value.
   5. Type WordRTFOutPathPref, and then press ENTER.
   6. Right-click WordRTFOutPathPref, and then click Modify.
   7. In the Value data box, type 1, and then click OK.
   8. Exit Registry Editor.

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

Note After you install this hotfix package, the Choose a digital certificate dialog box appears in front of all windows as expected. Additionally, this hotfix package does not affect any other dialog box prompt that might occur as the result of other configurations.

Back to the top

This guidance contains recommendations that are based on the types 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 March 11, 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 March 11, 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.

Note Not 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 Office 2000 components.
•	Microsoft Update does not support any Apple Macintosh products.

Specific exceptionsMicrosoft Update does not support the part of security update 933103 that involves the following products:

•	Microsoft Visual Studio 2002
•	Microsoft Visual Studio 2003
•	Microsoft BizTalk Server 2000
•	Microsoft BizTalk Server 2002
•	Microsoft Commerce Server 2000
•	Microsoft Internet Security and Acceleration (ISA) Server 2000

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

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.0.1

You can detect security updates that were released on March 11, 2008 if you use MBSA version 2.0.1.

General Exceptions

•	MBSA version 2.0.1 does not support any Office 2000 components.
•	MBSA version 2.0.1 does not support any Macintosh products.
•	MBSA version 2.0.1 is not supported on Windows Vista. However, MBSA version 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: 931943 (/Feedback.aspx?kbNumber=931943/)Microsoft Baseline Security Analyzer (MBSA) support for Windows Vista
•	MBSA version 1.2.1 is no longer supported. It will not detect security updates that were released after October 2007.

Specific exceptionsMBSA version 2.0.1 does not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

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 March 11, 2008 if you use any of the following items:

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

General Exceptions

•	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Office 2000 components.
•	WSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support any Macintosh products.
•	SUS 1.0 Service Pack 1 (SP1) is no longer supported. It will not receive security updates.

Specific exceptionsWSUS 2.0 SP1, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

Environments that detect and deploy security updates by using SMS 2.0, SMS 2003, or System Center Configuration Manager 2007

You can detect and deploy all security updates that were released on March 11, 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 2007

General Exceptions

•	SMS ITMU and System Center Configuration Manager do not support any Office 2000 components.
•	SMS together with the SUS Feature Pack does not support the following products: • The 2007 Office system • Windows Internet Explorer 7 • Windows Vista • Windows Server 2008 • Any x64-based versions of Windows • Any Itanium-based versions of Windows
•	The SMS SUS Feature Pack, SMS ITMU, and System Center Configuration Manager do not support any Macintosh products.

Specific exceptionsWSUS 2.0, WSUS 3.0, and WSUS 3.0 SP1 do not support the part of security update 933103 that involves the following products:

•	Visual Studio 2002
•	Visual Studio 2003
•	BizTalk Server 2000
•	BizTalk Server 2002
•	Commerce Server 2000
•	ISA Server 2000

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

Note The 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.

Note To simplify this table, items that were listed under the General Exceptions heading for each detection and deployment technology are not included.

For example, the Microsoft Update column in this table may include a Yes. However, the security bulletin lists an Office 2000 component as affected. Previously, we would have stated in the table that Microsoft Update partially supported deployment of the security update. However, no Office 2000 components are supported by Microsoft Update. Therefore, we no longer account for that product in the table because it is always listed as a general exception.

Security update	Bulletin	Component	Office Update	Windows Update	Microsoft Update	MBSA 2.0.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
949029	MS08-014	Microsoft Excel	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949031	MS08-015	Microsoft Outlook	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
949030	MS08-016	Office	Yes	Not applicable	Yes	Yes	Yes	Yes	Yes	Yes
933103	MS08-017	Microsoft Office Web Components	Partially. See Office Update section.	Not applicable	Partially. See Microsoft Update section.	Partially. See MBSA section.	Partially. See WSUS section.	Yes	Partially. See SMS section.	Partially. See System Center Configuration Manager section.

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 Thursday, March 13, 2008 12: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 does not detect, click the following article number to view the article in the Microsoft Knowledge Base:

If you installed a program that is listed in the Affected software section of a security bulletin, 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:

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 informationabout 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 to 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

Issue that this hotfix package fixes

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.

How to apply this hotfix

1. Download the hotfix package.
2. Extract the following file from the hotfix package:

   Office2007-kb960404-fullfile-x86-glb.exe

3. Double-click the file that you extracted in step 2 to add or replace the following files in the root of the Office installation source:
   • . Admin Oct.dll
   • . Admin Patchca.dll
   • . Admin fr-fr Octres.dll
4. Use these new files to save the Office Customization Tool updates.

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

Hotfix information

Back to the top

In this scenario, the shared folder goes offline. After the shared folder goes offline, you cannot make the shared folder go online from Windows Explorer.

Back to the top

Back to the top

Method 1

Wait awhile. The shared folder will come online again by itself.

Back to the top

Method 2

Do not open the file by using the Open File dialog box in an Office application or in WordPad. Instead, double-click the file to open it.

Back to the top

Back to the top

Back to the top

In some instances, a credential dialog box may appear in the Outlook user interface when you encounter this issue.

Back to the top

Note Windows Server 2003 and earlier versions of Microsoft Windows operating systems do not exhibit this behavior. The change of behavior in Windows Server 2008 is intended to protect domain controllers against clients that open too many NSPI connections without then closing the connections. Too many connections such as these can result in resource depletion.

Back to the top

Note The Outlook NSPI MAPI provider that is installed with Microsoft Outlook is only intended for use with Microsoft Outlook. External scripts and applications that rely on the Outlook NSPI MAPI provider are not supported.

How to modify the registry to allow for additional NSPI connections

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.

If more concurrent NSPI connections per user are legitimately required, you can change the default limit. To do this, follow these steps:

1.	Click Start, click Run, type regedit, and then click OK.
2.	Locate and then click the following registry key: HKEY_LOCAL_MACHINE System CurrentControlSet Services NTDS
3.	On the Edit menu, point to New, and then click Key.
4.	Type Parameters, and then press ENTER.
5.	Click the Parameters key.
6.	On the Edit menu, point to New, and then click DWORD Value.
7.	Type NSPI max sessions per user, and then press ENTER.
8.	Double-click NSPI max sessions per user, type the maximum number of the NSPI connections that you want to have, and then click OK.
9.	Exit Registry Editor.

Back to the top

To confirm that you encountered the issue that is described in the Symptoms section, follow these steps:

1.

Enable event logging for NSPI connections. To do this, follow these steps: a. On the domain controller that is targeted for the NspiBind connection, click Start, click Run, type regedit, and then click OK. b. Locate and then double-click the following registry entry: HKEY_LOCAL_MACHINE System CurrentControlSet Services NTDS Diagnostics 4 MAPI Interface Events c. In the Value data box, type 5, and then click OK. Note The default value of this registry entry is 0. d. On the File menu, click Exit. Note This is a verbose level of event logging and may generate many events. This verbose level of event logging includes events that are unrelated to the diagnosis of this issue. We recommend that you restore this setting to the default value after you finish troubleshooting.

2.

After you enable event logging, an event that resembles the following is logged in the Directory Services event log when this issue occurs: Event ID: 2820NSPI max connection limit for the user has reached.You need to do NSPI unbind on old connections before making new connections.Additional DataMax NSPI connections per user: %1User: %2

A network capture of the failure may contain packets that resemble the following:

Source	Destination	Protocol	Information
ClientIP	ServerIP	NSPI	NspiBind request
ServerIP	ClientIP	NSPI	NspiBind response, Status: MAPI_E_LOGON_FAILED

Back to the top

Back to the top

Back to the top

Issues that the hotfix package fixes

This hotfix package fixes the following issues:

•	949877 (/Feedback.aspx?kbNumber=949877/) You cannot see private items in the calendar even though the Delegate can see my private items option is enabled in Outlook 2007
•	949878 (/Feedback.aspx?kbNumber=949878/) Error message when you use a rule to move messages to a folder in Outlook 2007 after you set the value of the PreferANSI registry entry: Cannot move to the <folder_name> folder

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-kb949751-fullfile-x86-glb.exe	12.0.6300.5000	13,270,152	27-Feb-2008	11:50	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Outlook.msp	Not applicable	14,236,160	27-Feb-2008	18:22	Not applicable

Contents of the Outlook.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

• The attachment is saved in the Document Workspace site that is specified by the sender.
• The recipient of the e-mail message receives a copy of the attachment in the e-mail message.
• The e-mail message also contains a link to the shared attachment in the Document Workspace site.

Because the attachment is attached to the e-mail message as a shared attachment, the sender expects that the e-mail message contains only a link to the attachment in the Document Workspace site.

To resolve this issue, follow these steps:

1. Apply hotfix 959642. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   959642  (/Feedback.aspx?kbNumber=959642/ ) Description of the Outlook 2007 hotfix package (Mso.msp,Outlook.msp): December 16, 2008
2. Set the SharedAttachmentsNotAttached registry entry. To do this, follow these steps:
   1. Click Start, and then click Run.
   2. Type regedit, and then click OK.
   3. Locate and then click the following registry subkey:
      HKEY_CURRENT_USER Software Microsoft Office 12.0 Outlook Preferences
   4. On the Edit menu, point to New, and then click DWORD Value.
   5. Type SharedAttachmentsNotAttached, and then press ENTER.
   6. Right-click SharedAttachmentsNotAttached, and then click Modify.
   7. In the Value data box, type 1, and then click OK.
   8. Exit Registry Editor.

• 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 packages.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

Back to the top

• A Cannot open this item error message occurs when you try to open a message from the search results in a shared mailbox.
• When you send a multipart MIME message by using the Japanese version of Outlook 2007, the message includes an 8-bit Shift JIS (SJIS) character without any encoding.
• If you read an e-mail message in Outlook Web Access without sending a read receipt, and then later you delete the message in Outlook cached mode, a non-read notification is sent to the sender of the message.
• You receive a One or more rules cannot be saved because of invalid actions or conditions error message when you try to save the rules collection by using the Outlook object model.
• When you move exceptions to a recurring meeting, the exceptions may be reported as deleted if you access these exceptions by using the Outlook object model.
• After you upgrade Outlook 2003 to Outlook 2007, you receive a Cannot delete this folder or The Operation Cannot be performed because the object has been deleted error message when you try to delete SharePoint folders or a single item in a SharePoint folder.
• You receive a You cannot make changes to contents of this read-only folder error message when you try to use Outlook to add items to a Windows SharePoint Services (WSS) discussion list.
• The BeforeItemPaste event in the Outlook 2007 object model does not work when the Search box is used to filter or restrict items in a folder that is not enabled for instant search.
• When you use m as a unit in the Duration field in the Japanese version of Outlook 2007, it is recognized as hours instead of minutes.
• When the sender of an e-mail message has Send As permissions to another mailbox, the From field of the printed e-mail message incorrectly contains on behalf of text.
• The information bar of a meeting invitation displays a Please respond message that conflicts with the No Response Required message that is displayed in the same Information Bar of Outlook 2007.
• The same profile is listed two times in the Choose Profile dialog box of Outlook 2007 when you create a new profile that contains some extended characters in the name. This issue occurs if the Outlook Mobile Service Add-in is enabled.
• Outlook 2007 may crash if an application on the Microsoft Exchange server responds to port 80 requests for availability information from Outlook.

• This hotfix fixes the following issue:
  959629  (/Feedback.aspx?kbNumber=959629/ ) If you send an e-mail message that contains a shared attachment in Outlook 2007, the attachment is also sent to the recipients
• This hotfix fixes the following issue:
  959878   (/Feedback.aspx?kbNumber=959878/ ) The Recover Deleted Items option in Outlook 2007 is still available after you set the DumpsterAlwaysOn registry entry to 0
• This hotfix fixes the following issue:
  959625  (/Feedback.aspx?kbNumber=959625/ ) On a client computer that is running Office Communicator 2007, you may be unable to make a TAPI call from Office Outlook 2007

Back to the top

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems 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

Mso.msp information

Outlook.msp information

Back to the top

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 June 12, 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, and 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 Server and Exchange Server 2003 • Microsoft Internet Security and Acceleration Server 2004 • Microsoft SQL Server 2005
•	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 June 12, 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 June 12, 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 927051 (security bulletin MS07-030) SUS does not support any part of this security update.
•	Security update 931213 (security bulletin MS07-032) 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 June 12, 2007. Any exceptions are in the following list.

Note SMS together with SUIT does not support Windows Vista, any x64-based versions of Windows, or any Itanium-based versions of Windows.

•	Security update 931213 (security bulletin MS07-032) SMS SUIT does not support any part of this security update.
•	Security update 929123 (security bulletin MS07-034) 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

927051

MS07-030

Microsoft Visio

Yes

Not applicable

Yes

Yes

Yes

Not applicable

Yes

Not applicable

Yes

Yes

935840

MS07-031

Schannel

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

931213

MS07-032

Windows Vista

Not applicable

Yes

Yes

Not applicable

Yes

Not applicable

Yes

Not applicable

Not applicable

Yes

933566

MS07-033

Windows Internet Explorer

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

929123

MS07-034

Microsoft Outlook Express

Not applicable

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes, with ESUIT

Yes

935839

MS07-035

Win32 API

Not applicable

Yes

Yes

Yes

Yes

Yes

Yes

Not applicable

Yes

Yes

Back to the top

Rereleased security updates

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 June 13, 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 June 12, 2007.

Microsoft Knowledge Base article number	Bulletin ID	Component	Detection note
931213	MS07-032	Windows Vista	See the MBSA section
929123	MS07-034	Outlook Express	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
929123	MS07-034	Outlook Express

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, click the following article number to view the article 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. 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 Web site:

Back to the top

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous 2007 Office suites fix release. We recommend that you consider applying the most recent fix release that contains the hotfix that you need.

Back to the top

How to obtain the August 2008 cumulative update packages

A set of supported cumulative update packages are now available from Microsoft. However, each package is intended to correct only the applications that are listed in this article. Apply the packages only to systems that are experiencing these specific problems. If you are not severely affected by any of these problems, we recommend that you wait for the next 2007 Office suites service pack that contains the hotfixes in these cumulative update packages.

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 a specific cumulative update package. To create a separate service request, visit the following Microsoft Web site:

Back to the top

Packages that are included in the August 2008 cumulative update

A link to a Microsoft Knowledge Base article that discusses each hotfix will be released as the article becomes available. To obtain a specific hotfix, please contact support and ask for the hotfix by referencing the Knowledge Base article number.

For more information about the 2007 Office suite bugs, click the following article numbers to view the articles in the Microsoft Knowledge Base.

Hotfix package name	Knowledge Base article number	Product
Access.msp	956054 (/Feedback.aspx?kbNumber=956054/) Description of the Access 2007 hotfix package (Access.msp): August 26, 2008	Access
Ace.msp	956838 (/Feedback.aspx?kbNumber=956838/) Description of the Access 2007 hotfix package (Ace.msp): August 26, 2008	Access
Excel.msp, Oart.msp	956798 (/Feedback.aspx?kbNumber=956798/) Description of the Excel 2007 hotfix package (Excel.msp, Oart.msp): August 26, 2008	Excel
Excel.msp, Xlconv.msp	956836 (/Feedback.aspx?kbNumber=956836/) Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp): August 26, 2008	Excel Converter
Excel.msp, Xlconv.msp, Graph.msp	956511 (/Feedback.aspx?kbNumber=956511/) Description of the Excel 2007 hotfix package (Excel.msp, Xlconv.msp, Graph.msp): August 26, 2008	Excel Converter
Excel-xx-xx.msp (Localized – All Languages) Not Global	956510 (/Feedback.aspx?kbNumber=956510/) Description of the Excel 2007 hotfix package (Excel-xx-xx.msp): August 26, 2008	Excel Localized
Ifswfe.msp	956315 (/Feedback.aspx?kbNumber=956315/) Description of the Forms Server 2007 hotfix package (Ifswfe.msp): August 26, 2008	Forms Server
Ipeditor.msp;infopath.msp	956314 (/Feedback.aspx?kbNumber=956314/) Description of the InfoPath 2007 hotfix package (Ipeditor.msp, Infopath.msp): August 26, 2008	InfoPath
Coreserver.msp	956056	SharePoint Server
Gfonts.msp	956514 (/Feedback.aspx?kbNumber=956514/) Description of the 2007 Office hotfix package (Gfonts.msp): August 26, 2008	Fonts
Ime32.msp	956793 (/Feedback.aspx?kbNumber=956793/) Description of the Input Method Editor (Japanese) 2007 hotfix package (Ime32.msp): August 26, 2008	English Assist
Msdaipp.msp	956790 (/Feedback.aspx?kbNumber=956790/) Description of the 2007 Office system hotfix package (Msdaipp.msp): August 26, 2008	Internet Publishing Provider
Mso.msp	956506 (/Feedback.aspx?kbNumber=956506/) Description of the 2007 Office system hotfix package (Mso.msp): August 26, 2008	Office Core
Graph.msp, Excel.msp, Xlconv.msp, Xlview.msp	956796 (/Feedback.aspx?kbNumber=956796/) Description of the 2007 Office system hotfix package (Graph.msp, Excel.msp, Xlconv.msp, Xlview,msp): August 26, 2008	Excel Converter, Excel Viewer
Oart.msp; OartConv.msp	956058 (/Feedback.aspx?kbNumber=956058/) Description of the 2007 Office hotfix package (Oart.msp, OartConv.msp): August 26, 2008	Office Art
Outlook.msp	956059	Outlook
PowerPoint.msp	956316 (/Feedback.aspx?kbNumber=956316/) Description of the PowerPoint 2007 hotfix package (PowerPoint.msp): August 26, 2008	PowerPoint
RichEd20.msp	956801 (/Feedback.aspx?kbNumber=956801/) Description of the PowerPoint 2007 hotfix package (RichEd20.msp): August 26, 2008	Rich Edit
Project.msp	956060 (/Feedback.aspx?kbNumber=956060/) Description of the Project 2007 hotfix package (Project.msp): August 26, 2008	Project
Pjsrvapp.msp, Pjsrvwfe.msp	956061	Project Server
Visio.msp	956063 (/Feedback.aspx?kbNumber=956063/) Description of the Visio 2007 hotfix package (Visio.msp): August 26, 2008	Visio
Visio.msp (ru-ru) Localized	956837	Visio Localized (Russian)
Visio.msp, Vviewer.msp	956791 (/Feedback.aspx?kbNumber=956791/) Description of the Office Visio 2007 hotfix package (Visio.msp, Vviewer.msp): August 26, 2008	Visio Viewer
Word.msp	956064	Word
Word.msp, Wordconv.msp	956795 (/Feedback.aspx?kbNumber=956795/) Description of the Word 2007 hotfix package (Word.msp, Wordconv.msp): August 26, 2008	Word Converter
Sts.msp	956057	Windows SharePoint Services
Wssmui.msp {All languages}	957109 (/Feedback.aspx?kbNumber=957109/) Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008	Windows SharePoint Services

Back to the top

Prerequisites

Prerequisites are listed in the KB articles for the individual packages.

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

Back to the top

This update also improves the compatibility between Outlook 2007 and some IMAP e-mail servers.

Back to the top

Update information

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:

Previously released security updates and hotfixes that are contained in this update

Back to the top

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	File version	File size	Date	Time
Contab32.dll	12.0.6300.5000	136,232	13-Dec-2007	06:56
Dlgsetp.dll	12.0.6308.5000	90,656	23-Mar-2008	02:14
Emsmdb32.dll	12.0.6307.5000	1,477,224	16-Mar-2008	08:29
Exsec32.dll	12.0.6300.5000	394,752	13-Dec-2007	06:56
Mimedir.dll	12.0.6309.5000	343,568	28-Mar-2008	03:24
Mspst32.dll	12.0.6308.5000	1,107,040	23-Mar-2008	02:14
Olmapi32.dll	12.0.6309.5000	2,953,776	28-Mar-2008	03:24
Omsmain.dll	12.0.6300.5000	663,088	13-Dec-2007	08:40
Omsxp32.dll	12.0.6300.5000	195,136	13-Dec-2007	08:40
Outlmime.dll	12.0.6309.5000	601,160	28-Mar-2008	03:24
Outlook.exe	12.0.6309.5000	12,840,480	28-Mar-2008	03:25
Outlph.dll	12.0.6300.5000	180,800	13-Dec-2007	06:56
Outlrpc.dll	12.0.6302.5000	47,624	07-Feb-2008	03:57
Outlvbs.dll	12.0.6300.5000	60,448	07-Dec-2007	07:05
Pstprx32.dll	12.0.6309.5000	416,280	28-Mar-2008	03:25
Scanpst.exe	12.0.6300.5000	40,520	07-Dec-2007	07:05
Scnpst32.dll	12.0.6308.5000	265,816	23-Mar-2008	02:14
Scnpst64.dll	12.0.6308.5000	275,552	23-Mar-2008	02:14

For information about how to distribute product updates for the 2007 Microsoft Office system, 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

Back to the top

Issue that the hotfix package fixes

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

Consider the following scenario. On a computer that has the East Asian languages enabled, you have a Microsoft Office Word 2003 document. The document contains numbers that are enclosed in parentheses. Some numbers are used to number a list. You open the document in Microsoft Office Word 2007. In this scenario, you may experience a delay of 1 second to 5 seconds after you type a character in the last line of the numbered list.

Note You do not experience a delay when you type successive characters.

Back to the top

Hotfix package 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 package.

Restart information

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

Hotfix package replacement information

This hotfix package does not replace a previously released hotfix package.

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 package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package 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-kb953139-fullfile-x86-glb.exe	12.0.6300.5000	11,972,416	21-May-2008	16:27	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,243,392	21-May-2008	23:05	Not Applicable

Contents of Word.msp

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

Back to the top

1.	Exit Outlook 2007.
2.	Click Start, and then click Control Panel.
3.	Click User Accounts and Family Safety or User Accounts. Note If you do not see User Accounts and Family Safety or User Accounts, go to the next step.
4.	Click Mail.
5.	Click Data Files, click Personal Folders, and then click Settings.
6.	Note the text in the Filename box. Note If you cannot view all the text, click in the Filename box, and then press the RIGHT ARROW key repeatedly.
7.	Click OK, and then click Close two times.
8.	Click Start, type %ProgramFiles% Microsoft Office Office12 in the Start Search box, and then press ENTER.
9.	Double-click Scanpst.
10.	In the Enter the name of the file you want to scan box, type the path and file name of the Outlook .pst file that you noted in step 6.
11.	Click Start.
12.	When the Inbox Repair Tool finishes, click OK.

Back to the top

Back to the top

Back to the top

In this scenario, the workflow displays the following message:

Back to the top

Note This metadata page problem is not exclusive to a picture library. This problem may also occur if you allow for management of content types on any other library, regardless of what content types are enabled. Additionally, adding certain columns to other library types, such as a document library, can cause this problem to occur.

When you click OK on the metadata entry page, the workflow sees this action as a change to the item. This unintended change to the item causes the workflow rule to cancel the workflow when the Cancel this workflow when the: Document is changed rule is enabled.

Back to the top

After you change these settings, a CheckIn button appears instead of an OK button on the metadata entry page when a picture item is uploaded. The CheckIn button does not cause the workflow to be canceled upon upload. This button still allows for successive change to the picture item to cancel the workflow as intended.

You can also work around this problem by clicking Cancel on the metadata page. By clicking Cancel, you receive the effect that you want on the workflow. However, this is not intuitive to the upload process and does not let the user add metadata during upload.

Another way to work around this problem is to click Upload or Upload Multiple Pictures. When you click one of these buttons, the metadata does not appear during the upload process.

Back to the top

Back to the top