In Windows Server 2008, the Volume Shadow Copy Service (VSS) logs warning events in the inquiry Virtual Printer Device (VPD) page 0×83 data for any descriptors that are not logical unit number (LUN) identifiers. These events only provide information and do not represent errors.

The event that is logged in the Application log resembles the following:

The following are the suggested operations for this VSS warning.

Operation:

•	Check whether the volume is supported by a provider.
•	Add a volume to a shadow copy set.

Context:

Execution Context: Provider   Provider Name: <provider name>   Provider Version: 1.0   Provider ID: {b57190af-454a-4dd0-8afd-e57facd5d9af}   Volume Name:   ? Volume{5b1ced58-7dd1-11dc-b4df-00065ba14874}    Snapshot Context: 25   Execution Context: Coordinator   Provider ID: {00000000-0000-0000-0000-000000000000}   Volume Name:   ? Volume{5b1ced58-7dd1-11dc-b4df-00065ba14874}    Execution Context: Coordinator

Friendly view of the event data:

- System  - Provider   [ Name]  VSS  - EventID 12333   [ Qualifiers]  0   Level 3   Task 0   Keywords 0x80000000000000  - TimeCreated   [ SystemTime]  <time>   EventRecordID 279   Channel Application   Computer <computer name>   Security- EventData   1   1   60   0   1

Binary data:

In Words0000: 6F43202D 203A6564 48524F43 435455570008: 30303030 38303331 6143202D 203A6C6C0010: 48524F43 43545557 30303030 353332310018: 4950202D 20203A44 30303030 303230310020: 4954202D 20203A44 30303030 323931320028: 4D43202D 20203A44 575C3A43 6F646E690030: 735C7377 65747379 5C32336D 767373760038: 78652E63 20202065 7355202D 203A72650040: 4120544E 4F485455 59544952 5359535C0048: 204D4554 20202020 6953202D 20203A640050: 2D312D53 38312D35In Bytes0000: 2D 20 43 6F 64 65 3A 20   - Code:0008: 43 4F 52 48 57 55 54 43   CORHWUTC0010: 30 30 30 30 31 33 30 38   000013080018: 2D 20 43 61 6C 6C 3A 20   - Call:0020: 43 4F 52 48 57 55 54 43   CORHWUTC0028: 30 30 30 30 31 32 33 35   000012350030: 2D 20 50 49 44 3A 20 20   - PID:0038: 30 30 30 30 31 30 32 30   000010200040: 2D 20 54 49 44 3A 20 20   - TID:0048: 30 30 30 30 32 31 39 32   000021920050: 2D 20 43 4D 44 3A 20 20   - CMD:0058: 43 3A 5C 57 69 6E 64 6F   C: Windo0060: 77 73 5C 73 79 73 74 65   ws syste0068: 6D 33 32 5C 76 73 73 76   m32 vssv0070: 63 2E 65 78 65 20 20 20   c.exe0078: 2D 20 55 73 65 72 3A 20   - User:0080: 4E 54 20 41 55 54 48 4F   NT AUTHO0088: 52 49 54 59 5C 53 59 53   RITY SYS0090: 54 45 4D 20 20 20 20 20   TEM0098: 2D 20 53 69 64 3A 20 20   - Sid:00a0: 53 2D 31 2D 35 2D 31 38   S-1-5-18

On a Windows Vista-based computer, when you try to copy files from a server on a network, the copy process may stop responding (hang), and you may receive a message that resembles the following:

This problem may occur only occasionally.

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:

File information

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

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Smb.sys	6.0.6000.20521	66,048	24-Jan-2007	03:02	x86
Update.mum	Not Applicable	1,986	24-Jan-2007	16:57	Not Applicable
X86_microsoft-windows-nbsmb.d_31bf3856ad364e35_6.0.6000.20521_none_454313304b30a4e0.manifest	Not Applicable	687	24-Jan-2007	16:57	Not Applicable
X86_microsoft-windows-nbsmb_31bf3856ad364e35_6.0.6000.20521_none_5df94bff13fca6fc.manifest	Not Applicable	6,230	24-Jan-2007	16:58	Not Applicable

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_microsoft-windows-nbsmb.d_31bf3856ad364e35_6.0.6000.20521_none_a161aeb4038e1616.manifest	Not Applicable	691	24-Jan-2007	16:57	Not Applicable
Amd64_microsoft-windows-nbsmb_31bf3856ad364e35_6.0.6000.20521_none_ba17e782cc5a1832.manifest	Not Applicable	6,498	24-Jan-2007	23:59	Not Applicable
Smb.sys	6.0.6000.20521	87,552	24-Jan-2007	03:23	x64
Update.mum	Not Applicable	1,986	24-Jan-2007	16:57	Not Applicable

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about how hotfix packages are named, 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:

Back to the top

You try to use the following repadmin /syncall command to propagate all the changes of a specified naming context to all the domain controllers in a domain and to all the global catalogs in the forest:

Note In this command, dsa represents the host name of a domain controller. Also, NamingContext represents the distinguished name of the directory partition.

However, a Windows Server 2008-based read-only domain controller (RODC) will not try to pull the changes for the specified naming context.

Note The Windows Server 2008-based RODC holds the changes for the specified naming context in its read-only global catalog partition.

To confirm this behavior, you can run the repadmin /showreps command on an RODC. You may notice that the time stamp of the last successful replication of the specified partition was left unchanged. If you run the same command on a full domain controller that is running either Windows Server 2003 or Windows Server 2008, you see that the time stamp of last successful replication for the specified partition is up to date.

Back to the top

This issue occurs because the syncall parameter in the first command that is mentioned in the Symptoms section, uses the hasPartialReplicaNCs attribute on the NTDS settings object to collect a list of domain controllers that host the naming context. Then, the command triggers a replication event. This command will enable domain controllers to do a pull replication of the naming context from its replication partners.

RODCs store the hasPartialReplicaNCs attribute locally. When the repadmin /syncall command is executed from a full domain controller, the full domain controller does not have information about the RODC. Therefore, no replication to the RODC is triggered.

Back to the top

To resolve this issue, you must explicitly specify the read-only global catalog name in the dsa parameter together with the naming context to obtain the updates to the read-only global catalog name. To do this, run a command that resembles the following at a command prompt:

Note The /P parameter is not a repadmin option on a read-only global catalog. This is the case because, by definition, the read-only global catalogs cannot have originating updates to replicate to other domain controllers.

Note To access advanced help for the Repadmin.exe tool, use the /experthelp parameter.

Back to the top

This behavior is by design.

Back to the top

For more information about the Repadmin.exe syntax, visit the following Web site:

The following is the output of the Repadmin /showattr command when the command is run against all the domain controllers. You will notice that the hasPartialReplicaNCs attribute is only returned when Repadmin /showattr is queried against the RODC.

Domain Information:Parent Domain:  DC1-2003 Domain Controller                            2008-01 2008 Domain ControllerSub-Domain:  2008-02 - Windows server 2008 Domain Controller 2008-03 - Windows Server 2008 Domain Controller.C: Users Administrator.SUB>repadmin /showattr * CN=NTDS Settings,CN=2008-03,CN=Servers,CN=Asia,CN=Sites,CN=Configuration,DC=contoso,DC=com /atts:hasPartialReplicaNCsRepadmin: running command /showattr against full DC dc1.contoso.comDN: CN=NTDS Settings,CN=2008-03,CN=Servers,CN=Asia,CN=Sites,CN=Configuration,DC=contoso,DC=comRepadmin: running command /showattr against full DC 2008-02.sub.contoso.comDN: CN=NTDS Settings,CN=2008-03,CN=Servers,CN=Asia,CN=Sites,CN=Configuration,DC=contoso,DC=comRepadmin: running command /showattr against full DC 2008-01.contoso.comDN: CN=NTDS Settings,CN=2008-03,CN=Servers,CN=Asia,CN=Sites,CN=Configuration,DC=contoso,DC=comRepadmin: running command /showattr against read-only DC 2008-03.sub.contoso.comDN: CN=NTDS Settings,CN=2008-03,CN=Servers,CN=Asia,CN=Sites,CN=Configuration,DC=contoso,DC=com    1> hasPartialReplicaNCs: DC=contoso,DC=com

Back to the top

This article describes the Microsoft IPsec Diagnostic Tool that is available for use in the following Windows operating systems:

•	Windows Server 2008
•	Windows Vista
•	Windows Server 2003
•	Windows XP

You can use the Microsoft IPsec Diagnostic Tool to check for common network problems on the host computer. When problems are found, the tool suggests appropriate repair commands. The tool also collects IPsec policy information on the computer, and it parses the IPsec logs to determine the reasons for network failures. Additionally, you can use this tool for collecting traces of VPN connections and for collecting information about NAT clients, about Windows Firewall configuration, about Group Policy updates, about Wireless events, and about System events.

This diagnostic report that is generated by this tool is derived from the system logs that are collected by the tool during its analysis phase. Therefore, this report is conclusive. The information in these logs is sufficient to diagnose any network-related issues. For assisted support, you may have to share the logs with network administrators or with Microsoft Support. For more assistance, see the Help feature that is included with the tool.

To download the Microsoft IPsec Diagnostic Tool, visit the following Microsoft Download Center Web site:
The following file is available for download from the Microsoft Download Center:
Download the Microsoft IPSec Diagnostic Tool – 1.0.msi package now. (http://www.microsoft.com/downloads/details.aspx?FamilyID=1d4c292c-7998-42e4-8786-789c7b457881&DisplayLang=en)Release Date: January 30, 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.

According to RFC 2045, MIME e-mail clients that do not have S/MIME capability can read clear signed messages. However, for Microsoft Exchange Server 2007 users, MIME e-mail clients cannot read the body of clear signed messages in Microsoft Office Outlook Web Access if the S/MIME control is not installed. The body of the e-mail message is blank.

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

To work around this problem, use Microsoft Outlook or another e-mail client that supports S/MIME.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

When messages are sent in Microsoft Transport Neutral Encapsulation Format (MS-TNEF) format from Exchange 2000 Server or from Exchange Server 2003 to Exchange Server 2007, certain properties are not converted. The Outlook Web Access client has to have these properties to display the body of the e-mail message.

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

This article describes how to back up Hyper-V virtual machines from the parent partition on a Windows Server 2008-based computer by using Windows Server Backup.

To back up Hyper-V virtual machines from the parent partition on Windows Server 2008 by using Windows Server Backup, you must register the Microsoft Hyper-V VSS writer with Windows Server Backup.

To register the Hyper-V VSS writer with Windows Server Backup, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry key:
   HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion
3. Right-click CurrentVersion, point to New, and then click Key.
4. Type WindowsServerBackup, and then press ENTER.
5. Right-click WindowsServerBackup, point to New, and then click Key.
6. Type Application Support, and then press ENTER.
7. Right-click Application Support, point to New, and then click Key.
8. Type {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, and then press ENTER.
9. Right-click {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}, point to New, and then click String Value.
10. Type Application Identifier, and then press ENTER.
11. Right-click Application Identifier, and then click Modify.
12. In the Value data box, type Hyper-V, and then click OK.
13. On the File menu, click Exit.

More information about Hyper-V virtual machine backups

Back up the virtual machines by using Windows Server Backup

• When you perform a backup of the virtual machines, you must back up all volumes that host files for the virtual machine.For example, if the virtual machine configuration files are stored on the D: volume, and the virtual machine virtual hard disk (VHD) files are stored on the E: volume, you must back up both the D: and E: volumes.
• Virtual machines that do not have Integration Services installed will be put in a saved state while the VSS snapshot is created.
• Virtual machines that are running operating systems that do not support VSS, such as Microsoft Windows 2000 or Windows XP, will be put in a saved state while the VSS snapshot is created.
• Virtual machines that contain dynamic disks must be backed up offline.

Restore virtual machines by using Windows Server Backup

To restore the virtual machines, follow these steps:

1. Start Windows Server Backup in Administrative Tools.
2. On the Actions menu, click Recover.
3. Select the server that you want to recover data from, and then click Next.
4. Select the date and time that you want to restore from, and then click Next.
5. Select the Applications recovery type, and then click Next.
6. Select Hyper-V, and then click Next.
7. Select the restore location, and then click Next.
8. Click Recover to start the restore process.

Note All volumes that host files for the virtual machine will be restored. Individual virtual machines cannot be restored by using Windows Server Backup.

Virtual machines that contain two or more snapshots will not be restored. To work around this issue, follow these steps:

1. Start Hyper-V Manager in Administrative Tools.
2. Delete the virtual machine that was not restored.
3. Start Windows Server Backup in Administrative Tools.
4. On the Actions menu, click Recover.
5. Select the server that you want to recover data from, and then click Next.
6. Select the date and time that you want to restore from, and then click Next.
7. Select the Files and folders recovery type, and then click Next.
8. Select the directory where the snapshots are stored, and then click Next.

   Note By default, the snapshots are located in the following directory:

   C: ProgramData Microsoft Windows Hyper-V Snapshots
9. Select the location where the snapshots should be restored, and then click Next.
10. Click Recover to start the restore process.
11. After the restore has finished, perform another restore. However, use the Applications recovery type, and select Hyper-V to correctly restore the virtual machines.

Consider the following scenario:

• You are running a Windows Server 2008-based computer that is connected to a storage device over some Microsoft Multipath I/O (MPIO) paths.
• A Microsoft MPIO Device Specific Module is enabled for these MPIO paths.
• The storage device is configured as an iSCSI boot device or a Storage Area Network (SAN) boot device.
• You have installed hotfix 957316 on the Windows Server 2008-based computer.

In this scenario, the computer restarts repeatedly, or you may receive a Stop error message, depending on the actual failure recovery options.

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

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008.
• The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

For all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

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

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008

In a C++ Microsoft Jet DAO MFC (CDao) application, insertions and updates may not work on a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008. Additionally, you may receive the following error message:

Note If the application does not capture the exception that is returned by CDao on the insertion or the update, the database will not have the updates that you intended to make.

Back to the top

This problem occurs when all the following conditions are true:

•	The application is written in Microsoft Visual C++ and uses the CDao classes to access a Microsoft Jet database data source.
•	The Use Multi-Byte Character Set value is set for the Character Set project option.
•	The data that the application is inserting or updating was retrieved from a fixed-length defined Text column.
•	The source Text column contains data that is the maximum length that the column allows. For example, a Text(10) column contains a value of 1234567890.
•	Successive insertions or updates occur from the original variable that is returned from the CDaoRecordset object.
•	The target table column is one of the following columns: • The same column from which the original data was retrieved • Another fixed-length column that is defined as a Text column of the same size

Back to the top

To resolve this problem, apply the hotfix that is described in Microsoft Knowledge Base article 943509.

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

Back to the top

If you cannot apply the hotfix that is described Microsoft Knowledge Base article 943509, use one of the following methods to work around this problem:

•	Update the application. To do this, copy the retrieved data from the original Visual C++ variable to a new variable. Then, insert or update the data from the new variable.
•	Update the database design. To do this, use one of the following methods: • Modify the column widths to one character larger than any expected data. • Redefine the width as a non-fixed length.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

This article describes the Microsoft Office SharePoint Server 2007 issues that are fixed in the Office SharePoint Server 2007 hotfix package that is dated December 16, 2008.

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

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:
  • You publish a SharePoint Portal Server 2007 publishing portal site through Microsoft Internet Security and Acceleration (ISA) Server 2006.
  • The Web application that hosts the publishing portal site is configured to use Allow Anonymous Access and Windows Authentication (NTLM).
  • Output caching is enabled on the publishing portal site through ISA Server 2006, but output caching fails.

  If you press F5 in Internet Explorer to refresh the Web page, the date on the output page is updated. The date should remain constant for the period of time in which the cache is not invalidated. To see the date on the output page in Internet Explorer, right-click the Web page, click View Source, and search for the code that resembles the following:

  Rendered using cache profile:Public Internet (Purely Anonymous) at: 2008-10-10T12:00:57
• You add the Scheduling Start Date field and the Scheduling End Date field to a Web page. You try to publish a page with Immediately option, you may receive the following error message:
  You must specify a valid date within the range of xxx and xxx.
• When you review a document library through Site Content and Structure, filtering does not work when the column value contains a semicolon (;).
• If you configure the Max. Cache Size setting of the Site collection object cache to more than 2000, an integer overflow exception may occur. You may receive an error message that resembles the following:
  Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
• Non-core search Web part queries are not recorded into usage logs.
• You add the Scheduling Start Date field and the Scheduling End Date field to a Web page. You set the values for the Scheduling Start Date field and the Scheduling End Date field, and then you wait until the Web page expires. When you try to publish the Web page, you may receive the following error message:
  The end date of a page must be in the future. Please edit the end date and try again.
• Incremental crawls fail to be scheduled when you have multiple Shared Services Providers (SSPs), and one SSP contains many sources.
• You use the Team Site template as the template for the Top-level site in Office SharePoint Server 2007. A subsite owner of the top-level site does not have access permissions to the top-level site. When the subsite owner tries to create his own subsite, the owner may receive an Access Denied error message.
• You may receive an ELEMENT NOT FOUND (COM-INTEROP): exception when you are running crawls that overlap. This issue causes the crawls to fail, and SharePoint server does not index any further documents.
• When you click the Local Office SharePoint Server Sites link in Content Sources, you may receive the following error message:
  Unexpected Error has occurred
• Search returns zero results during an index merge process.

This hotfix fixes the following issues:

• 959122  (/Feedback.aspx?kbNumber=959122/ ) Users cannot create a new variation of a page that they created in a Microsoft Office SharePoint Server 2007 site
• 960254  (/Feedback.aspx?kbNumber=960254/ ) Error message when you click Checked out to me in the Manage Content and Structure page after you filter the picture library by a custom column: Cannot find column [repro]

Known issue

Symptoms

After you apply this Cumulative Update, scheduled incremental crawls or full crawls never run.

Workaround

Create a new daily, weekly, or monthly schedule. Or, edit an existing daily, weekly, or monthly schedule.

• If the Repeat within the day check box is checked, and you already have a repetition interval, you do not have to do anything
• If the Repeat within the day check box is not checked, enter 5 minutes in the Run Every text box. Additionally, enter 6 minutes in the For text box.

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 issues that are 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.

32-bit hotfix package

Download information

Microsoft Windows Installer .msp file information

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:

64-bit hotfix package

Download information

Microsoft Windows Installer .msp file information

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:

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

This article describes the support for Suite B cryptographic algorithms that was added in Windows Vista Service Pack 1 (SP1) and in Windows Server 2008. Suite B is a group of cryptographic algorithms that are approved by the United States National Security Agency (NSA).

Suite B is used as an interoperable cryptographic framework for protecting sensitive data. Support has been extended to the Suite B algorithms for the following areas:

•	Main mode
•	Quick mode
•	Authentication settings

This article also describes the Internet Protocol security (IPsec) policy configuration syntax that uses Suite B algorithms.

Back to the top

Support limitations

Support limitations for Suite B include the following:

•	The authoring of policies that contain Suite B algorithms is not supported in the Windows Firewall with Advanced Security Microsoft Management Console (MMC) snap-in.
•	The Netsh advfirewall help command does not display configuration options for Suite B algorithms.
•	The creation and enforcement of IPsec policy by using Suite B algorithms is supported only in Windows Vista Service Pack 1 (SP1), in Windows Server 2008, or in later versions of Windows.

Back to the top

Definitions

•	Suite B Suite B is a set of standards that are specified by the National Security Agency (NSA). Suite B provides the industry with a common set of cryptographic algorithms that can be used to create products that meet the widest range of U.S. government needs. Suite B includes specification of the following types of algorithms: • Integrity • Encryption • Key exchange • Digital signature
•	Federal Information Processing Standards (FIPS) FIPS is a set of guidelines and standards that govern federal computing resources. All Suite B algorithms are FIPS-approved. For more information, visit the following Web site: http://www.itl.nist.gov/fipspubs/geninfo.htm (http://www.itl.nist.gov/fipspubs/geninfo.htm)
•	NIST This is an acronym for the National Institute of Standards and Technology.
•	Data integrity algorithms Data integrity algorithms use message hashes to make sure that information is not being changed while it is in transit.
•	Data encryption algorithms Data encryption algorithms are used to hide information that is being transmitted. The encryption algorithms are used to convert plain text to a secret code. For example, the encryption algorithms can convert plain text to ciphertext. The ciphertext can then be decoded to the original plain text. Each algorithm uses a key to perform the conversion. The type of key and the length of the key depend on the algorithm that is being used.
•	IPsec This is an abbreviation for the term Internet Protocol security. For more information about IPsec, visit the following Microsoft Web site: http://technet.microsoft.com/en-us/network/bb531150.aspx (http://technet.microsoft.com/en-us/network/bb531150.aspx)
•	Advanced Encryption Standard Galois Message Authentication Code (AES-GMAC) This algorithm is described in NIST Special Publication 800-38D. To view this document, visit the following Web site: http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf (http://csrc.nist.gov/publications/nistpubs/800-38d/sp-800-38d.pdf)
•	Advanced Encryption Standard in Galois/Counter Mode (AES-GCM) This algorithm is described in NIST Special Publication 800-38D. To view this document, visit the following Web site: http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf (http://csrc.nist.gov/publications/nistpubs/800-38d/sp-800-38d.pdf)
•	Elliptic Curve Digital Signature Algorithm (ECDSA) Elliptic curve (EC) is a variant of the digital signature algorithm that operates on EC groups. The EC variant provides smaller key sizes for the same security level. This algorithm is described in FIPS publication 186-2. To view this publication, visit the following Web site: http://csrc.nist.gov/publications/fips/fips186-2/fips186-2-change1.pdf (http://csrc.nist.gov/publications/fips/fips186-2/fips186-2-change1.pdf)
•	Certification authority (CA) A certification authority is an entity that issues digital certificates. IPsec can use these certificates as an authentication method.
•	Authentication Header (AH) Authentication Header is an IPsec protocol that provides authentication, integrity, and anti-replay functionality for the whole packet. This includes the IP header and the data payload. AH does not provide confidentiality. This means that AH does not encrypt the data. The data is readable, but it is unwriteable.
•	Encapsulating Security Payload (ESP) ESP is an IPsec protocol that provides confidentiality, authentication, integrity, and anti-replay functionality. ESP can be used alone, or it can be used together with AH.

Back to the top

Main-mode algorithms

In Windows Vista SP1 and in Windows Server 2008, the following integrity algorithms are supported in addition to those algorithms that are already supported in the release version of Windows Vista:

•	SHA-256
•	SHA-384

Note The key exchange algorithm and the encryption algorithm are not changed.

Back to the top

Quick-mode algorithms

In Windows Vista SP1 and in Windows Server 2008, the following algorithms are supported in addition to those algorithms that are already supported in the release version of Windows Vista.

Integrity (AH or ESP)

•	SHA-256
•	AES-GMAC-128
•	AES-GMAC-192
•	AES-GMAC-256

Integrity and encryption (ESP only)

•	AES-GCM-128
•	AES-GCM-192
•	AES-GCM-256

For more information about AH and ESP combinations that are supported and not supported, see the Quick-mode cryptographic algorithm combinations that are supported and not supported section.

Restrictions for Quick mode

•	The same integrity algorithm should be used for both AH and ESP.
•	The AES-GMAC algorithms are available for an integrity algorithm that has null encryption. Therefore, if any of these algorithms are specified for ESP integrity, the encryption algorithm cannot be specified.
•	If you use an AES-GCM algorithm, the same algorithm should be specified for both ESP integrity and encryption.

Back to the top

Authentication

In Windows Vista SP1 and in Windows Server 2008, the following authentication methods are supported in addition to those authentication methods that are already supported in the release version of Windows Vista.

•	Computer certificate with ECDSA-P256 signing
•	Computer certificate with ECDSA-P384 signing

Note The default authentication method for Windows Vista is RSA SecurId authentication.

Back to the top

Syntax and examples

This section describes the syntax for using the Netsh advfirewall command to add and to modify connection security rules. This section also provides examples of Netsh advfirewall commands.

Add a connection security rule

Netsh advfirewallUsage: add rule name=<string>      endpoint1=any|localsubnet|dns|dhcp|wins|defaultgateway|         <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list>      endpoint2=any|localsubnet|dns|dhcp|wins|defaultgateway|         <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list>      action=requireinrequestout|requestinrequestout|         requireinrequireout|noauthentication      [description=<string>]      [mode=transport|tunnel (default=transport)]      [enable=yes|no (default=yes)]      [profile=public|private|domain|any[,...] (default=any)]      [type=dynamic|static (default=static)]      [localtunnelendpoint=<IPv4 address>|<IPv6 address>]      [remotetunnelendpoint=<IPv4 address>|<IPv6 address>]      [port1=0-65535|any (default=any)]      [port2=0-65535|any (default=any)]      [protocol=0-255|tcp|udp|icmpv4|icmpv6|any (default=any)]      [interfacetype=wiresless|lan|ras|any (default=any)]      [auth1=computerkerb|computercert|computercertecdsap256|computercertecdsap384|computerpsk|         computerntlm|anonymous[,...]]      [auth1psk=<string>]      [auth1ca=<CA Name> [certmapping:yes|no] [excludecaname:yes|no] ...]      [auth1healthcert=yes|no (default=no)]      [auth1ecdsap256ca=<CA Name> [certmapping:yes|no] [excludecaname:yes|no] ...]      [auth1ecdsap256healthcert=yes|no (default=no)]      [auth1ecdsap384ca=<CA Name> [certmapping:yes|no] [excludecaname:yes|no] ...]      [auth1ecdsap384healthcert=yes|no (default=no)]      [auth2=computercert| computercertecdsap256|computercertecdsap384|userkerb|usercert| usercertecdsap256|usercertecdsap384|userntlm|anonymous[,...]]      [auth2ca=<CA Name> [certmapping:yes|no] ...]      [auth2ecdsap256ca=<CA Name> [certmapping:yes|no] ...]      [auth2ecdsap384ca=<CA Name> [certmapping:yes|no] ...]      [qmpfs=dhgroup1|dhgroup2|dhgroup14|ecdhp256|ecdhp384|mainmode|         none (default=none)]      [qmsecmethods=         ah:<integrity>+esp:<integrity>-<encryption>+[valuemin]+[valuekb]         |default]        Remarks:      - The rule name should be unique, and it cannot be all.      - When mode=tunnel, both tunnel endpoints must be specified and must be        the same IP version. Also, the action must be requireinrequireout.      - At least one authentication must be specified.      - Auth1 and auth2 can be comma-separated lists of options.      - The computerpsk and computerntlm methods cannot be specified together        for auth1.      - Computercert cannot be specified with user credentials for auth2.     - Certsigning options ecdsap256 and ecdsap384 are supported only on Windows Vista SP1 and on later versions of Windows Vista.      - Qmsecmethods can be a list of proposals separated by a comma (,).      - For qmsecmethods, integrity=md5|sha1|sha256| aesgmac128|aesgmac192|aesgmac256|aesgcm128|aesgcm192|aesgcm256 and        encryption=3des|des|aes128|aes192|aes256|aesgcm128|aesgcm192|aesgcm256.      - If aesgcm128, aesgcm192, or aesgcm256 is specified, it must be used for both ESP integrity and encryption.       -  sha-256, aesgmac128, aesgmac192, aesgmac256, aesgcm128, aesgcm192, aesgcm256 are supported only on Windows Vista SP1 and on later versions of Windows Vista.       - Qmpfs=mainmode uses the main mode key exchange setting for PFS.      - We recommend that you do not use DES, MD5, or DHGroup1. These        cryptographic algorithms are provided for backward compatibility        only.      - The default value for certmapping and for excludecaname is no.      - The quotation mark () characters in the CA name must be replaced with a backslash character followed by a single quotation mark ( ').

Example 1

Consider the following example of a Netsh advfirewall command:

This command creates a connection security rule that has the following authentication methods in the authentication set:

•	The first authentication method is a certificate that uses RSA certificate signing.
•	The second authentication method is a health certificate that uses ECDSA256 for certificate signing.

The connection security rule protects traffic by using AH and ESP integrity with the new AES-GMAC 256 algorithm. The rule does not include encryption.

Example 2

Consider the following example of a Netsh advfirewall command:

This command creates a connection security rule that has one authentication method in the authentication set. The authentication method is a certificate that uses RSA certificate signing.

The connection security rule protects traffic by using AH and ESP integrity with SHA256 for integrity and with AES192 for encryption.

Modify an existing connection security rule

Netsh advfirewallUsage: set rule      group=<string> | name=<string>      [type=dynamic|static]      [profile=public|private|domain|any[,...] (default=any)]      [endpoint1=any|localsubnet|dns|dhcp|wins|defaultgateway|         <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list>]      [endpoint2=any|localsubnet|dns|dhcp|wins|defaultgateway|         <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list>]      [port1=0-65535|any]      [port2=0-65535|any]      [protocol=0-255|tcp|udp|icmpv4|icmpv6|any]      new      [name=<string>]      [profile=public|private|domain|any[,...]]      [description=<string>]      [mode=transport|tunnel]      [endpoint1=any|localsubnet|dns|dhcp|wins|defaultgateway|         <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list>]      [endpoint2=any|localsubnet|dns|dhcp|wins|defaultgateway|         <IPv4 address>|<IPv6 address>|<subnet>|<range>|<list>]      [action=requireinrequestout|requestinrequestout|         requireinrequireout|noauthentication]      [enable=yes|no]      [type=dynamic|static]      [localtunnelendpoint=<IPv4 address>|<IPv6 address>]      [remotetunnelendpoint=<IPv4 address>|<IPv6 address>]      [port1=0-65535|any]      [port2=0-65535|any]      [protocol=0-255|tcp|udp|icmpv4|icmpv6|any]      [interfacetype=wiresless|lan|ras|any]     [auth1=computerkerb|computercert|computercertecdsap256|computercertecdsap384|computerpsk|         computerntlm|anonymous[,...]]      [auth1psk=<string>]      [auth1ca=<CA Name> [certmapping:yes|no] [excludecaname:yes|no] ...]      [auth1healthcert=yes|no (default=no)]      [auth1ecdsap256ca=<CA Name> [certmapping:yes|no] [excludecaname:yes|no] ...]      [auth1ecdsap256healthcert=yes|no (default=no)]      [auth1ecdsap384ca=<CA Name> [certmapping:yes|no] [excludecaname:yes|no] ...]      [auth1ecdsap384healthcert=yes|no (default=no)]      [auth2=computercert| computercertecdsap256|computercertecdsap384|userkerb|usercert| usercertecdsap256|usercertecdsap384|userntlm|anonymous[,...]]      [auth2ca=<CA Name> [certmapping:yes|no] ...]      [auth2ecdsap256ca=<CA Name> [certmapping:yes|no] ...]      [auth2ecdsap384ca=<CA Name> [certmapping:yes|no] ...]      [qmsecmethods=         ah:<integrity>+esp:<integrity>-<encryption>+[valuemin]+[valuekb]|         default]Remarks:      - This sets a new parameter value on an identified rule. The command fails        if the rule does not exist. To create a rule, use the add command.      - Values after the new keyword are updated in the rule.  If there are        no values, or if the new keyword is missing, no changes are made.      - Only a group of rules can be enabled or disabled.      - If multiple rules match the criteria, all matching rules are         updated.      - The rule name should be unique, and it cannot be all.      - Auth1 and auth2 can be comma-separated lists of options.      - The computerpsk and computerntlm methods cannot be specified together        for auth1.      - Computercert cannot be specified by using user credentials for auth2.     - Certsigning options ecdsap256 and ecdsap384 are supported only on Windows Vista SP1 and on later versions of Windows Vista.        - Qmsecmethods can be a list of proposals that are separated by a comma (,).      - For qmsecmethods, integrity=md5|sha1|sha256| aesgmac128|aesgmac192|aesgmac256|aesgcm128|aesgcm192|aesgcm256 and        encryption=3des|des|aes128|aes192|aes256|aesgcm128| aesgcm192|aesgcm256      - If aesgcm128 or aesgcm256 is specified, it must be used for both ESP integrity and for encryption.       -  Sha-256, aesgmac128, aesgmac192, aesgmac256, aesgcm128, aesgcm192, and aesgcm256 are supported only on Windows Vista SP1 and on later versions of Windows Vista.      - If qmsemethods are set to default, qmpfs will be set to default also.      - Qmpfs=mainmode uses the main mode key exchange setting for PFS.      - We recommend that you do not use DES, MD5, or DHGroup1. These        cryptographic algorithms are provided for backward compatibility        only.      - The default value for certmapping and excludecaname is no.      - The quotation mark () characters in the CA name must be replaced with a backslash character followed by a single quotation mark ( ').

The following is an example of a command that updates the rule that was created in Example 1 in the previous section:

This command updates the rule to use AES-GCM 256 for ESP integrity and encryption and to use AES-GMAC 256 for AH integrity.

Set global Main-mode settings

The following Help text is for the Netsh advfirewall set global command.

netsh advfirewall>set globalUsage: set global statefulftp|statefulpptp  enable|disable|notconfigured      set global IPsec (parameter) (value)      set global mainmode (parameter) (value) | notconfiguredIPsec Parameters:      strongcrlcheck    - Configures how CRL checking is enforced.                          0: Disable CRL checking                          1: Fail if cert is revoked (default)                          2: Fail on any error                          notconfigured: Returns the value to its unconfigured state.      saidletimemin     - Configures the security association idle time in                          minutes.                        - Usage: 5-60|notconfigured (default=5)      defaultexemptions - Configures the default IPsec exemptions. The default is                          to exempt IPv6 neighbordiscovery protocol from                          IPsec.                        - Usage: none|neighbordiscovery|notconfiguredMain Mode Parameters:      mmkeylifetime     - Sets the main mode key lifetime in minutes, in sessions, or in both.                        - Usage: <num>min,<num>sess      mmsecmethods      - Configures the main mode list of proposals                        - Usage:                          keyexch:enc-integrity,enc-integrity[,...]|default                        - keyexch=dhgroup1|dhgroup2|dhgroup14|                          ecdhp256|ecdhp384                        - enc=3des|des|aes128|aes192|aes256                        - integrity=md5|sha1|sha256|sha384Remarks:      - This configures global settings, such as advanced IPsec options.      - We recommend that you do not use DES, MD5, or DHGroup1. These        cryptographic algorithms are provided for backward compatibility        only.      - The mmsecmethods keyword default sets the policy to the following:        dhgroup2-aes128-sha1,dhgroup2-3des-sha1      - Sha256 and sha384 are supported only on Windows Vista SP1 and on later versions of Windows Vista.

The following is an example of a command that uses the new SHA algorithms in the Main-mode cryptographic set:

Back to the top

Troubleshooting, configuration, and verification commands

The Netsh advfirewall consec show rule all command

The Netsh advfirewall consec show rule all command displays configuration for all connection security rules.

The following is a sample of output for this command.

Rule Name:				testEnabled:					YesProfiles:					Domain,Private,PublicType:					StaticMode:					TransportEndpoint1:				AnyEndpoint2:				AnyProtocol:					AnyAction:					RequestInRequestOutAuth1:					ComputerPSKAuth1PSK:				         12345MainModeSecMethods			         ECDHP384-3DES-SHA256,ECDHP384-3DES-SHA384QuickModeSecMethods			AH:AESGMAC256+ESP:AESGCM256-AESGCM256+60 min+100000kb

The Netsh advfirewall monitor show mmsa command

The Netsh advfirewall monitor show mmsa command displays the Main mode security association.

The following is a sample of output for this command.

Main Mode SA at 01/04/2008 13:10:09Local IP Address:				157.59.24.101Remote IP Address:			         157.59.24.119My ID:Peer ID:First Auth:				ComputerPSKSecond Auth:				NoneMM Offer:				         ECDHAP384-3DES-SHA256Cookie Pair:				203d57505:5d088705Health Pair:				NoOk.

The Netsh advfirewall monitor show qmsa command

The Netsh advfirewall monitor show qmsa command displays the Quick mode security association.

The following is a sample of output for this command.

Main Mode SA at 01/04/2008 13:10:09Local IP Address:				157.59.24.101Remote IP Address:			         157.59.24.119Local Port:				AnyRemote Port:				AnyProtocol:					AnyDirection:				BothQM Offer:				         AH:AESGMAC256+ESP:AESGCM256-AESGCM256+60min +100000kb	Ok.

The Netsh advfirewall show global command

The Netsh advfirewall show global command displays global settings.

The following is a sample of output for this command.

Global Settings:IPsec:					StrongCRLCheck				0:DisabledSAIdleTimeMin				5minDefaultExemptions			         NeighborDiscoveryIPsecThroughNAT			         Server and client behind NATStatefulFTP				EnableStatefulPPTP				EnableMain Mode:KeyLifetime				2min,0sessSecMethods				DHGroup1-3DES-SHA256,DHGroup1-3DES-SHA384

Back to the top

Interoperability

Creation, enforcement, and management of the IPsec policy that uses Suite B algorithms was introduced in Windows Vista SP1 and in Windows Server 2008. You can manage a Group Policy that contains Suite B algorithms only by using tools that were released with Windows Vista SP1 or with Windows Server 2008.

Sample scenarios and expected results are as follows.

Scenario 1

You use the new cryptographic algorithms to apply a policy that is created on a computer that is running Windows Server 2008 or Windows Vista SP1 to a computer that is running the release version of Windows Vista.

Expected result

If a rule contains cryptographic suites that use the new cryptographic algorithms, these cryptographic suites are dropped and other cryptographic suites in the cryptographic set are used instead.

If none of the cryptographic suites in the rule are recognized, the whole rule is dropped. An event is logged that indicates that the rule cannot be processed. Therefore, if all cryptographic suites in the key exchange cryptographic set are dropped, none of the connection security rules in the policy are applied. However, all firewall rules are still applied.

The authentication set process resembles the cryptographic set process. If a policy that contains the new certificate flags (ECDSA-P256 or ECDSA-P384) is applied to a computer that is running the release version of Windows Vista, the authentication methods are dropped.

If all authentication methods in the first authentication set are dropped for this reason, the whole rule is not processed. If all authentication methods in the second authentication set are dropped, the rule is processed by using only the first authentication set.

Scenario 2

On a computer that is running the release version of Windows Vista, you use the new cryptographic algorithms to view a policy that was created on a computer that is running Windows Server 2008 or Windows Vista SP1.

Expected result

The new algorithms are displayed as “unknown” in both the monitoring and authoring parts of the Windows Firewall Advanced Security MMC snap-in. The Netsh advfirewall command also displays the algorithms as “unknown” in Windows Vista.

Restrictions on interoperability

Restrictions on interoperability are as follows:

•	We do not support remote management of policies that use Suite B algorithms on computers that are running Windows Vista SP1 or Windows Server 2008 from a computer that is running the release version of Windows Vista.
•	When a policy that is created on a computer that is running Windows Vista SP1 or Windows Server 2008 is imported to a computer that is running the release version of Windows Vista, some parts of the policy are dropped. This occurs because the release version of Windows Vista cannot recognize the new algorithms.

Back to the top

Quick-mode cryptographic algorithm combinations that are supported and not supported

The following table shows supported Quick-mode cryptographic algorithm combinations.

Protocol	AH Integrity	ESP Integrity	Encryption
AH	AES-GMAC 128	None	None
AH	AES-GMAC 192	None	None
AH	AES-GMAC 256	None	None
AH	SHA256	None	None
AH	SHA1	None	None
AH	MD5	None	None
ESP	None	AES-GMAC 128	None
ESP	None	AES-GMAC 192	None
ESP	None	AES-GMAC 256	None
ESP	None	SHA256	None
ESP	None	SHA1	None
ESP	None	MD5	None
ESP	None	SHA256	Any supported encryption algorithm except AES-GCM algorithms
ESP	None	SHA1	Any supported encryption algorithm except AES-GCM algorithms
ESP	None	MD5	Any supported encryption algorithm except AES-GCM algorithms
ESP	None	AES-GCM 128	AES-GCM 128
ESP	None	AES-GCM 192	AES-GCM 192
ESP	None	AES-GCM 256	AES-GCM 256
AH+ESP	AES-GMAC 128	AES-GMAC 128	None
AH+ESP	AES-GMAC 128	AES-GMAC 128	None
AH+ESP	AES-GMAC 128	AES-GMAC 128	None
AH+ESP	SHA-256	SHA-256	None
AH+ESP	SHA1	SHA1	None
AH+ESP	MD5	MD5	None
AH+ESP	SHA256	SHA256	Any supported encryption algorithm except AES-GCM algorithms
AH+ESP	SHA1	SHA1	Any supported encryption algorithm except AES-GCM algorithms
AH+ESP	MD5	MD5	Any supported encryption algorithm except AES-GCM algorithms
AH+ESP	AES-GMAC 128	AES-GCM 128	AES-GCM 128
AH+ESP	AES-GMAC 192	AES-GCM 192	AES-GCM 192
AH+ESP	AES-GMAC 256	AES-GCM 256	AES-GCM 256

Note AES-GMAC is the same as AES-GCM with null encryption. For example, you can specify AH integrity to use AES-GMAC 128, and you can specify ESP Integrity to use AES-GCM 128. This is the only exception to the rule that AH and ESP integrity algorithms must be identical.

The combinations that are described in the following table are not supported.

Protocol	AH Integrity	ESP Integrity	Encryption
ESP	None	AES-GMAC 128	Any supported encryption algorithm
ESP	None	AES-GMAC 192	Any supported encryption algorithm
ESP	None	AES-GMAC 256	Any supported encryption algorithm
ESP	None	AES-GCM 128	1. None 2. Any encryption algorithm except AES-GCM 128
ESP	None	AES-GCM 192	1. None 2. Any encryption algorithm except AES-GCM 192
ESP	None	AES-GCM 256	1. None 2. Any encryption algorithm except AES-GCM 256
AH+ESP	AES-GMAC 128	AES-GMAC 128	Any supported encryption algorithm
AH+ESP	AES-GMAC 192	AES-GMAC 192	Any supported encryption algorithm
AH+ESP	AES-GMAC 256	AES-GMAC 256	Any supported encryption algorithm

For more information about Suite B, visit the following Web site:

For more information about IPsec and connection security rules, visit the following Microsoft Web site:

For more information about Cryptography Next Generation in Windows Server 2008, visit the following Microsoft Web site:

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

Back to the top

Consider the following scenario:

•	You are running the Czech (CS-CZ) version of Windows Server 2008.
•	You start the TS Gateway Manager component, and then you click the Server Farm tab.

However, when you try to locate the Add and Remove buttons on the Server Farm tab, they appear to be missing.

Back to the top

In the Czech version of Windows Server 2008, the UI for the Server Farm tab in the TS Gateway Manager component is poorly laid out for certain display resolutions. Therefore, the Add and Remove buttons may be partly obscured. However, the functionality of these buttons remains unaffected.

The Add button is located in the upper-right corner of the window, and the Remove button is located in the lower-right corner.

Back to the top

To work around this behavior, use one of the following methods.

Method 1

Enter information in the appropriate text boxes, and then click the corresponding buttons even if the buttons are partly obscured.

Method 2

Use the following keyboard shortcuts to access the Add and Remove buttons:

•	Press ALT+P to access the Add button.
•	Press ALT+B to access the Remove button.

Back to the top

The TS Gateway Manager has known display problems when you use a display resolution of 120 dots per inch (DPI). If you experience additional display problems in the TS Gateway Manager, you can set the display resolution to 96 DPI. To do this, follow these steps:

1.	Right-click the desktop, and then click Personalize.
2.	Click Adjust font Size (DPI), and then click Default scale (96 DPI) – fit more information.
3.	When you are prompted to restart the computer, click OK.

Back to the top

This article describes the Microsoft Office Word 2007 issues that are fixed in the hotfix package that is dated February 15, 2008.

•	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

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

File name	File version	File size	Date	Time	Platform
Winword.exe	12.0.6300.5000	349,720	12-Dec-2007	15:54	x86
Wwlib.dll	12.0.6300.5000	17,485,848	12-Dec-2007	15:54	x86

Contents of the Wordconv.msp file

File name	File version	File size	Date	Time	Platform
Wrd12cnv.dll	12.0.6300.5000	4,272,664	12-Dec-2007	17:08	x86
Wrd12exe.exe	12.0.6300.5000	24,584	12-Dec-2007	17:08	x86

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

Back to the top

Consider the following scenario.

•	You have a Windows Server 2008-based computer that has Hyper-V installed.
•	You create a virtual machine on the Windows Server 2008-based computer.
•	You create the virtual machine from a virtual hard disk image (.vhd file) that was created by using Microsoft Virtual Server 2005 or Microsoft Virtual PC 2007.

In this scenario, the VMBus Integration Services device does not load. When you open Device Manager on the virtual machine, a yellow triangle that has an exclamation point on it appears next to VMBus. When you double-click VMBus, the VMBus Properties dialog box displays one of the following messages:

Back to the top

This issue occurs because the hardware abstraction layer (HAL) is not automatically updated in Windows Server 2008. (This is also true in Windows Vista.)

When a virtual machine is created by using Virtual Server or Virtual PC, the Advanced Configuration and Power Interface (ACPI) HAL is used. The Integration Services require an Advanced Configuration and Power Interface (ACPI) HAL to load the VMBus device correctly.

Back to the top

To resolve this issue, follow these steps:

1.	Start the virtual machine.
2.	Click Start, click Run, type Msconfig.exe, and then click OK.
3.	In the System Configuration dialog box, click the Boot tab, and then click Advanced Options.
4.	In the BOOT Advanced Options dialog box, click to select the Detect HAL check box, and then click OK.
5.	Click Yes to restart the virtual machine.
6.	After the virtual machine is restarted, open Device Manager, and then verify that all Integration Services devices are installed.
7.	In Device Manager, expand Computer, and then verify that ACPI x86-based PC is listed as the HAL.

Note You can clear the Detect HAL check box that you selected in step 4. If the Detect HAL check box is selected, the virtual machine takes a slightly longer time to start.

Back to the top

For more information about Hyper-V technology, visit the following Microsoft Web site:

Back to the top

If a PS/2 keyboard or a PS/2 mouse is not connected to a Windows Server 2008-based computer when the computer starts, the following event is logged in the System log:

Event ID: 7026
The following boot-start or system-start driver(s) failed to load: i8042prt

Additionally, the remote console keyboard and mouse appear to the server as USB devices. In Device Manager, a black exclamation point (!) on a yellow field appears next to these devices.

Back to the top

This behavior occurs because Windows Server 2008 does not initialize the remote administration key to 1 if the emergency management console is enabled.

Back to the top

You can safely ignore the event.

Back to the top

On a Windows Vista-based or Windows Server 2008-based computer, you have a printer on which some device fonts are installed. On the computer, you change some fonts in the font substitution table of the printer from TrueType fonts to the printer’s device fonts. However, you cannot change the settings back to the original TrueType fonts. Therefore, if you have a character that does not print correctly by using the device fonts, the correct output for that character cannot be obtained.

This problem occurs because in the printer’s Properties dialog box, a font can be removed from the font substitution table by using a null device font name. However, when the printer calls the IPrintCoreHelper::SetFontSubstitution method, the null device font name is identified as invalid. Therefore, you cannot change the settings back to the original TrueType fonts.

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

To apply this hotfix on Windows Vista-based computers, you must have Windows Vista SP1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately . MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported 32-bit versions of Windows Server 2008 and of Windows Vista

For all supported 64-bit versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

To configure the font substitution table of the printer, follow these steps:

1. Click Start, type Printers in the Start Search box, and then click Printers.
2. Right-click the printer, and then click Properties.
3. Click the Device Settings tab.
4. Expand Font Substitution Table, and then configure the fonts.

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

For more information about the IPrintCoreHelper::SetFontSubstitution method, visit the following Microsoft Web site:

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

Microsoft has released Update Rollup 5 for Microsoft Exchange Server 2007 Service Pack 1 (SP1). This article describes the following information about the update rollup:

• The issues that the update rollup fixes
• How to obtain the update rollup
• The prerequisites to install the update rollup

Issues that the update rollup fixes

Update Rollup 5 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

• 925371  (/Feedback.aspx?kbNumber=925371/ ) Domino users cannot find meeting request attachments that are sent from Exchange 2007 users
• 939037  (/Feedback.aspx?kbNumber=939037/ ) By default, managed content settings apply to the root folder and all subfolders in an Exchange 2007 environment
• 949722  (/Feedback.aspx?kbNumber=949722/ ) Event ID 800 does not include the user name of users who ran the Get-MessageTrackingLog command in an Exchange 2007 environment
• 949895  (/Feedback.aspx?kbNumber=949895/ ) Exchange Management Shell crashes (stops responding), and Event ID 1000 is logged when you perform a cross-forest migration from Exchange Server 2003 to Exchange Server 2007 S949895
• 949901  (/Feedback.aspx?kbNumber=949901/ ) Exchange 2007 users cannot send e-mail messages to a mail-enabled public folder in a mixed Exchange 2003 and Exchange 2007 environment
• 949968  (/Feedback.aspx?kbNumber=949968/ ) Unified Messaging does not handle the diversion header correctly in Exchange Server 2007 Service Pack 1
• 950272  (/Feedback.aspx?kbNumber=950272/ ) The formatting of a plain text message is incorrect when you print the plain text message by using Outlook Web Access in an Exchange Server 2007 environment
• 951267  (/Feedback.aspx?kbNumber=951267/ ) An exception occurs in Exchange Management Console when you preview AddressList in an Exchange Server 2007 environment
• 951273  (/Feedback.aspx?kbNumber=951273/ ) The received date and the received time of IMAP messages are changed to the time of migration after you migrate mailboxes to an Exchange 2007 Service Pack 1-based server
• 951505  (/Feedback.aspx?kbNumber=951505/ ) You may receive an error message when you run the Update-SafeList cmdlet in an Exchange 2003 and Exchange 2007 mixed environment
• 951564  (/Feedback.aspx?kbNumber=951564/ ) Exchange 2007 Service Pack 1 Update Rollup 5 supports the addition of new items to context menus in Outlook Web Access 2007
• 951710  (/Feedback.aspx?kbNumber=951710/ ) You receive error messages or warnings when you change an Active Directory schema so that the Company property supports more than 64 characters
• 952097  (/Feedback.aspx?kbNumber=952097/ ) Event ID 12800 is logged on an Exchange 2007-based server: Message processing failed because there is not enough available memory (8007000E-82000387)
• 952583  (/Feedback.aspx?kbNumber=952583/ ) Japanese DBCS characters are corrupt when you reply to a message or forward a message in an Exchange Server 2007 Service Pack 1 environment
• 953619  (/Feedback.aspx?kbNumber=953619/ ) A public folder conflict message cannot be delivered, and event error 1016 is logged, when the public folder name contains DBCS characters in an Exchange Server 2007 Service Pack 1 environment
• 953787  (/Feedback.aspx?kbNumber=953787/ ) You receive an error message when you try to move Exchange 2000 mailboxes or Exchange 2003 mailboxes from one forest to an Exchange 2007 server that is located in another forest by using the Move-Mailbox command
• 953840  (/Feedback.aspx?kbNumber=953840/ ) Event ID 5000 occurs, and the IMAP4 service may crash, on a server that is running Exchange Server 2007 with Service Pack 1 when you use a third-party application to migrate POP3 and IMAP4 users
• 954036  (/Feedback.aspx?kbNumber=954036/ ) Hidden folders or files are listed when you view a UNC file server by using OWA in an Exchange 2007 environment
• 954195  (/Feedback.aspx?kbNumber=954195/ ) The task originator is not notified of task changes and task progress in an Exchange Server 2007 environment
• 954197  (/Feedback.aspx?kbNumber=954197/ ) Exchange 2007 CAS cannot copy the OAB from the OAB share on Windows Server 2008-based Exchange 2007 CCR clusters
• 954270  (/Feedback.aspx?kbNumber=954270/ ) Message class changes during conversion when a digitally signed Message Disposition Notification is received by a server that is running Exchange Server 2007 Service Pack 1
• 954451  (/Feedback.aspx?kbNumber=954451/ ) An appointment item cannot be opened by a CDOEX-based application if the item is saved by Exchange Web Service together with the Culture property in Exchange Server 2007
• 954684  (/Feedback.aspx?kbNumber=954684/ ) You cannot use an Outlook 2007 client to display or download an attachment when you access a message that includes an inline attachment from Exchange Server 2007
• 954810  (/Feedback.aspx?kbNumber=954810/ ) An Exchange 2007 room mailbox stops processing requests after the resource booking assistant receives a delegated meeting request from an Exchange 2003 user
• 954887  (/Feedback.aspx?kbNumber=954887/ ) You cannot add a Mail User or a Mail Contact to the Safe Senders list in Exchange 2007 by using OWA Client
• 955001  (/Feedback.aspx?kbNumber=955001/ ) Error message when you use the IMAP protocol to send a SEARCH command that has the CHARSET argument on an Exchange 2007 server: BAD Command Argument Error
• 955196  (/Feedback.aspx?kbNumber=955196/ ) Log files are not copied to the target server in a standby continuous replication environment in Exchange Server 2007
• 955429  (/Feedback.aspx?kbNumber=955429/ ) A VSS backup application causes the Information Store service to crash repeatedly on an Exchange 2007 Service Pack 1-based server
• 955460  (/Feedback.aspx?kbNumber=955460/ ) The start time and the end time of a meeting request are incorrect when a delegate uses Exchange Web Service to send the request in an Exchange 2007 environment
• 955480  (/Feedback.aspx?kbNumber=955480/ ) Meeting requests from external senders are displayed as Busy instead of Tentative in an Exchange 2007 environment
• 955599  (/Feedback.aspx?kbNumber=955599/ ) Event ID 10 messages fill up the Application log on an Exchange 2007 CAS server if an Exchange Server 2003 mailbox owner makes an Exchange Web Service call
• 955619  (/Feedback.aspx?kbNumber=955619/ ) A user cannot access the mailbox by using a POP client or an IMAP client through Client Access Server in an Exchange 2007 environment
• 955741  (/Feedback.aspx?kbNumber=955741/ ) A message stays in the Outbox, and the message is resent until it is deleted manually on Windows Mobile 6.1-based devices in an Exchange 2007 Service Pack 1 CAS proxying scenario
• 955946  (/Feedback.aspx?kbNumber=955946/ ) A sender receives an NDR from the Exchange 2007 server when the sender submits a private message by using an SMTP server
• 955989  (/Feedback.aspx?kbNumber=955989/ ) The SPN registration of a cluster fails, and Error event IDs 1119 and 1034 are logged in an Exchange Server 2007 Service Pack 1 environment
• 956199  (/Feedback.aspx?kbNumber=956199/ ) The last character of a user’s Chinese display name is truncated in the Offline Address Book on an Exchange 2007 server
• 956319  (/Feedback.aspx?kbNumber=956319/ ) The W3wp.exe process may crash on an Exchange 2007 CAS server after you use Entourage to send a message that is larger than 48 KB
• 956573  (/Feedback.aspx?kbNumber=956573/ ) Event ID 1032 is not logged in the Application log when users send e-mail messages while they are logged on to Outlook Web Access as another user in Exchange 2007
• 956582  (/Feedback.aspx?kbNumber=956582/ ) Exchange Server 2007 Update Rollup 3 does not update the Outlook Web Access Logon.aspx file after you modify the file
• 956613  (/Feedback.aspx?kbNumber=956613/ ) The W3wp.exe process intermittently stops responding and Event ID 1000 is logged in Exchange Server 2007 Service Pack 1
• 956709  (/Feedback.aspx?kbNumber=956709/ ) Some recurring meetings may be missing when you view the meetings using Outlook Web Access in Exchange Server 2007
• 957002  (/Feedback.aspx?kbNumber=957002/ ) The Edgetransport.exe process may crash intermittently on a server that is running Exchange Server 2007 Service Pack 1
• 957813  (/Feedback.aspx?kbNumber=957813/ ) A Non-Delivery Report is generated when you try to send a high priority message that is larger than 250 KB in an Exchange Server 2007 Service Pack 1 environment
• 957978  (/Feedback.aspx?kbNumber=957978/ ) The OAB generation is unsuccessful and Event IDs 9328 and 9373 are logged in the Application log in a Windows Server 2008-based Exchange 2007 Single-Copy cluster environment
• 958855  (/Feedback.aspx?kbNumber=958855/ ) The Edge Transport service crashes repeatedly, and an event error 1000 is logged repeatedly on a server that is running Exchange Server 2007 Service Pack 1
• 958856  (/Feedback.aspx?kbNumber=958856/ ) Event ID: 7012 occurs when you search message tracking logs on an Exchange Server 2007-based server

Update rollup information

This update rollup does not apply to the Exchange Server 2007 release to manufacturing (RTM) version. The series of update rollup packages for Exchange Server 2007 SP1 is independent of the corresponding series of update rollups for Exchange Server 2007 RTM. For a list of update rollups that apply to the Exchange Server 2007 RTM, see the Update rollups for Exchange Server 2007 RTM section in the following Microsoft Knowledge Base article:

Download information

To download and install Update Rollup 5 for Exchange Server 2007 SP1, visit the following Microsoft Update Web site:

Note Microsoft Update does not detect update rollups for Exchange Server 2007 on clustered servers that are running Exchange Server 2007.

You may want to deploy Update Rollup 5 for Exchange Server 2007 SP1 to multiple computers that are running Exchange Server 2007. Or, you may want to deploy Update Rollup 5 for Exchange Server 2007 SP1 to clustered servers that are running Exchange 2007. The update rollup is also available from the Microsoft Download Center.

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

Download the Update Rollup 5 for Exchange Server 2007 Service Pack 1 package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=652ED33A-11A1-459C-8FFE-90B9CBFE7903&displaylang=en)

Release Date: November 20, 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.

Note Certain Exchange 2007-managed code services may not start after you install this update rollup. This is true if the services cannot access the following Microsoft Web site:

For more information about how to resolve or work around this issue, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the Exchange Server 2007 servicing model, click the following article number to view the article in the Microsoft Knowledge Base:

Update replacement information

Update Rollup 5 for Exchange Server 2007 SP1 is a cumulative update. This update replaces the updates that are mentioned in the following Microsoft Knowledge Base articles:

• 945684  (/Feedback.aspx?kbNumber=945684/ ) Description of Update Rollup 1 for Exchange Server 2007 Service Pack 1
• 948016  (/Feedback.aspx?kbNumber=948016/ ) Description of Update Rollup 2 for Exchange Server 2007 Service Pack 1
• 949870  (/Feedback.aspx?kbNumber=949870/ ) Description of Update Rollup 3 for Exchange Server 2007 Service Pack 1
• 952580  (/Feedback.aspx?kbNumber=952580/ ) Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1

Prerequisites

The following list contains prerequisites for the Update Rollup 5 for Exchange Server 2007 Service Pack 1:

• Install Exchange Server 2007 SP1 on the computer before you apply this update rollup.
• Remove all interim updates for Exchange Server 2007 before you apply this update rollup.

Restart requirement

The required services are automatically stopped and then restarted when you apply this update rollup.

Removal information

To remove Update Rollup 5 for Exchange Server 2007 SP1, use Add or Remove Programs in Control Panel to remove update 953467.

Important information for Outlook Web Access users about Outlook Web Access customization

When you apply an update rollup package, the update process will copy over the Outlook web access files if needed. If you have modified the logon.aspx file or other Outlook Web Access files, the customizations will be overwritten in order to ensure that Outlook Web Access is updated correctly. After you apply the update rollup package, you must re-create Outlook Web Access customization in logon.aspx.

We recommend that you always make a backup copy of any customized Outlook Web Access files before you apply the update rollup. For more information about Outlook Web Access customization details, visit the following Microsoft Web site:

If you are a CAS Proxy Deployment Guidance customer, and if you have deployed CAS-CAS proxying, apply the update rollup to the Internet-facing Client Access servers before you apply the update rollup to the non-Internet-facing Client Access servers. For other Exchange Server 2007 configurations, the order in which you apply the update rollup to the servers is not important.

For more information about CAS-CAS proxying, visit the following Microsoft Web site:

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

Microsoft has released security bulletin MS07-017. The security bulletin contains all the relevant information about the security update. This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

•	Home users: http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx (http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx)
•	IT professionals: http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx (http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx)

Back to the top

Known issues

•

Microsoft is aware of an issue that affects a limited number of printer drivers. When you try to print by using one of these drivers, you may experience the following symptoms: • Your computer automatically restarts. • After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error.A log of this error has been created. Please tell Microsoft about this problem.We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you click the link at the bottom of the message box, you see error signature information that resembles the following: BCCode : 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) OSVer : 5_1_2600 SP : 0_0 Product : 256_1 • You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer… Technical information: *** Stop 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) UNEXPECTED_KERNEL_MODE_TRAP For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 935843 (/Feedback.aspx?kbNumber=935843/) Stop 0×0000007F error when you print from Windows XP or Windows 2000 with GDI security update 925902 installed

•

After you install this security update on a computer that is running Windows XP with Service Pack 2, certain third-party applications may not start. Additionally, you receive an error message that resembles the following: application_executable_name – Illegal System DLL Relocation The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C: Windows System32 Hhctrl.ocx occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL. For more information about this issue, and to see a list of third-party programs that Microsoft has confirmed are affected by this problem, click the following article number to view the article in the Microsoft Knowledge Base: 935448 (/Feedback.aspx?kbNumber=935448/) Certain programs may not start, and you receive an error message on a computer that is running Windows XP Service Pack 2: Illegal System DLL Relocation If you receive a similar message when you use other programs, install update 935448. If we confirm that other programs are affected by this problem, we will update Microsoft Knowledge Base article 935448 with more information.

Back to the top

The revision number and the review dates for this article may reflect minor editorial revisions or structural revisions to this content. The major technical revisions to this content are listed in this table.

Date	Revisions
April 17, 2007	Updated the Known issues section to include information about a Stop error that you may receive after you install this security update. Added this table.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Back to the top

You are running a Microsoft Exchange Server environment that includes Exchange Server 2007. You are using Microsoft Office Outlook 2007 or Microsoft Office Outlook 2003 in cached mode on a client computer. You send an e-mail message from Outlook on the client computer to a non-Simple Mail Transfer Protocol (SMTP) address. For example, you address the e-mail message to an address, such as FAX. In this scenario, you receive a non-deliverable report (NDR) message that resembles the following message:

This problem can occur in several circumstances. Outlook generates an NDR message when one of the following conditions is true:

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

To resolve this problem, follow these steps:

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.

Outlook 2007 and Outlook 2003 maintain a list of allowed address types in the registry. Outlook hands over messages that are addressed to an allowed address type to Exchange Server for further processing. When messages are addressed to an address type that is not included in the allowed list, Outlook does not reference Exchange Server but immediately returns an NDR message.

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:

For more information about address spaces and connector scope, visit the following Microsoft Web site, and see the Address Spaces and Connector Scope section:

Consider the following scenario. You mount a Virtual Machine hard disk file (.vhd file) as a loopback device in Windows Server 2008. The .vhd file is now available as a virtual hard disk. In this scenario, users may access the virtual machine, and they can read from or write to the virtual hard disk.

Back to the top

This issue occurs if you mount a .vhd file as loopback device by using the Hyper-V Windows Management Instrumentation (WMI) APIs.

Back to the top

To enforce the security of the contents of a .vhd file that is mounted as a loopback device, use one of the following methods:

•	Configure NTFS file system permissions on files and folders in the mounted .vhd file.
•	Use a separate server to which virtual machine users do not have access.

Back to the top

For more information about Hyper-V, visit the following Microsoft Web site:

Back to the top

On a Windows Vista-based computer or on a Windows Server 2008-based client computer, you create a shortcut to a DFS link in the Favorite Links folder (%Userprofile% Links). However, when you try to click the shortcut in Windows Explorer, the contents of the DFS share do not appear.

Note This problem does not occur if the shortcut points to a DFS root folder or if the shortcut uses the UNC path for the target share.

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

To apply this hotfix, the computer must run one of the following:

•	Windows Vista
•	Windows Vista Service Pack 1
•	Windows Server 2008

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

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

Windows Vista and Windows Server 2008 file information notes

•	The files that apply to a specific product milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table: Version Product Milestone Service branch 6.0.6000 .20xxx Windows RTM LDR 6.0.6001.22xxx Windows Vista SP1 and Windows Server 2008 SP1 SP1 LDR
•	Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
•	The MANIFEST files (.manifest) and MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintaining the state of the updated component. The security catalog files, for which attributes not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

File name	File version	File size	Date	Time	Platform
Shell32-ppdlic.xrm-ms	Not Applicable	3,150	25-Jul-2008	02:48	Not Applicable
Shell32.dll	6.0.6000.20882	11,320,320	25-Jul-2008	03:13	x86
Shell32.dll	6.0.6001.22229	11,581,952	25-Jul-2008	03:22	x86

For all supported x64-based versions of Windows Server 2008 and Windows Vista

File name	File version	File size	Date	Time	Platform
Shell32-ppdlic.xrm-ms	Not Applicable	3,150	25-Jul-2008	03:01	Not Applicable
Shell32.dll	6.0.6000.20882	12,788,736	25-Jul-2008	03:24	x64
Shell32.dll	6.0.6001.22229	12,899,328	25-Jul-2008	03:53	x64
Shell32.dll	6.0.6000.20882	11,320,320	25-Jul-2008	03:13	x86
Shell32.dll	6.0.6001.22229	11,581,952	25-Jul-2008	03:22	x86

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and Windows Vista

File name	Package_for_kb953537_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	19,139
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,367
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_client~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,715
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,421
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_sc~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,424
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,425
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_server~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,432
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,422
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,431
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	19,020
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	Package_for_kb953537_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum
File version	Not Applicable
File size	1,425
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_0c8d50707aa16033b3a64bd0220e5bf9_31bf3856ad364e35_6.0.6000.20882_none_cb304f2db0940c2d.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_11f01c3c0091e5d8d47f19e365b71f2a_31bf3856ad364e35_6.0.6000.20882_none_aa6561f3261feaa4.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_195c7f5f144e141af4e2293ffacd3b69_31bf3856ad364e35_6.0.6000.20882_none_fedd5434fd72c0c7.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_1a39b2269eec529c646151b3a4e874ec_31bf3856ad364e35_6.0.6000.20882_none_30709238f68c823d.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_24b6c295fbf637309c77e5b993c8df99_31bf3856ad364e35_6.0.6000.20882_none_d87b7d6122dbe2eb.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_280b405f3c1666dd258d69fbda8670d0_31bf3856ad364e35_6.0.6000.20882_none_518fd1521a3c627b.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_36c049e76ff263209fb3052ba4b9e7e8_31bf3856ad364e35_6.0.6000.20882_none_58bacf2d641e2ba1.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_38bbd75ee49d829d79ad5c4be14b0c23_31bf3856ad364e35_6.0.6000.20882_none_3928ba639cbd9a23.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_3f0f1d20e1db0484fce01e9a7a575e1c_31bf3856ad364e35_6.0.6000.20882_none_41e882f2ae8151c9.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_4505df0c3b76b17302b4bb0713e092b0_31bf3856ad364e35_6.0.6000.20882_none_43ce13c59f05fe8a.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_458acf96413aab1ad51d38337fbe6895_31bf3856ad364e35_6.0.6000.20882_none_e0a9a825a94e72fa.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_465bd0635faebe77e75c24978b267a59_31bf3856ad364e35_6.0.6000.20882_none_29c2c8087d493461.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_46853169a8455c91c71ffa0ee118e9e7_31bf3856ad364e35_6.0.6000.20882_none_c07b87a202cd1c7b.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_46f8c85ec82ceb603ffd886951f82a26_31bf3856ad364e35_6.0.6000.20882_none_1c0a54a24a97780a.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_489e1c68b765054efa21f22c3866dfd2_31bf3856ad364e35_6.0.6000.20882_none_c6713d7146e491fd.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_4cb8c73d564be7256f299ed37e66bee1_31bf3856ad364e35_6.0.6000.20882_none_14459f61c8704864.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_5aa9fe1ea5a40010e1571af571dd363c_31bf3856ad364e35_6.0.6000.20882_none_a247bf4310cda742.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_5acb3f49c956fb58b8ded84508425f48_31bf3856ad364e35_6.0.6000.20882_none_51de1d5d7ae6614b.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_6d71edc617d70dcb8747abb83be7e8cb_31bf3856ad364e35_6.0.6000.20882_none_25d3b9b7d3407deb.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_7682c3d1a0f2612e4dee3b44ec336a1b_31bf3856ad364e35_6.0.6001.22229_none_7ce88f51f54a97d1.manifest
File version	Not Applicable
File size	695
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_80e2335f26e51c085b99e5c2bc094a8a_31bf3856ad364e35_6.0.6000.20882_none_c731e3a7227bfc49.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_841f12beeeedf3823a682b313bed31ce_31bf3856ad364e35_6.0.6000.20882_none_c095bcd79dd0ac6c.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_8bbbeaca73e36a2418fadd0aa4475efe_31bf3856ad364e35_6.0.6000.20882_none_1ef756416ffc4254.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_8f8f6126ffadf3d771cad901eadf6ed2_31bf3856ad364e35_6.0.6000.20882_none_2c4988dc479089be.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_9458692ec5e23304c8d7bf1b179abace_31bf3856ad364e35_6.0.6000.20882_none_015507f62b7122ce.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_984f22c59a2e66f9d66ffbd9e02fba50_31bf3856ad364e35_6.0.6000.20882_none_3eaacec034d259dc.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_9e7ac22538a08fc505eee8c6dda2c160_31bf3856ad364e35_6.0.6000.20882_none_e9b5f1c9d8377d99.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_ba27e2bfe24d68beaf30898686e0204c_31bf3856ad364e35_6.0.6000.20882_none_938aa1490a163cdf.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_c7e8a8b6bd4afe992ba65f286c6fdb9b_31bf3856ad364e35_6.0.6000.20882_none_a82d31f25829f819.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_db8698b0da6fab8f0e2fc21744ee68a2_31bf3856ad364e35_6.0.6000.20882_none_cc05d2cf587dfd23.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_df5fee1cbb6a1f34f60333eb286815ee_31bf3856ad364e35_6.0.6000.20882_none_f4e53123a96c99e9.manifest
File version	Not Applicable
File size	708
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_e5abc8d436d5cb289344e9abdf4218d5_31bf3856ad364e35_6.0.6000.20882_none_bb999b5a6ffa7741.manifest
File version	Not Applicable
File size	695
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_eabcba71355f842bd4fe29642f7d7f1f_31bf3856ad364e35_6.0.6000.20882_none_740b0ed446aef107.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_eb9c61ba7edf25ac10f70187dc7647b6_31bf3856ad364e35_6.0.6000.20882_none_6d67eabe44d48fe2.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_ecf63702ff1aeb6776ad71a4e3b31325_31bf3856ad364e35_6.0.6000.20882_none_4bc5d32a58aa87a8.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_f61a979035e70cd23b362e4a92232f34_31bf3856ad364e35_6.0.6000.20882_none_ce8ffe572fe63934.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_f8f2f452a4c6078c9fc2f4136047d660_31bf3856ad364e35_6.0.6000.20882_none_d31d6d13b1c2d2ed.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08
File name	X86_fd33c635b678d128c4a7e94e877066cf_31bf3856ad364e35_6.0.6000.20882_none_4937468c2f3823c7.manifest
File version	Not Applicable
File size	703
Date (UTC)	25-Jul-2008
Time (UTC)	13:08

Additional files for all supported x64-based versions of Windows Server 2008 and Windows Vista

File name	Amd64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20882_none_c696a7a0e68f7d2b.manifest
File version	Not Applicable
File size	905,287
Date (UTC)	25-Jul-2008
Time (UTC)	03:38
File name	Amd64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6001.22229_none_c8c4c7d4e37f17d7.manifest
File version	Not Applicable
File size	906,231
Date (UTC)	25-Jul-2008
Time (UTC)	04:41
File name	Package_for_kb953537_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	19,570
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,375
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_client~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,725
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,429
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,432
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,433
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_server~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,440
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,430
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,439
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	19,453
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Package_for_kb953537_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum
File version	Not Applicable
File size	1,433
Date (UTC)	25-Jul-2008
Time (UTC)	13:09
File name	Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20882_none_d0eb51f31af03f26.manifest
File version	Not Applicable
File size	896,876
Date (UTC)	25-Jul-2008
Time (UTC)	03:22
File name	Wow64_microsoft-windows-shell32_31bf3856ad364e35_6.0.6001.22229_none_d319722717dfd9d2.manifest
File version	Not Applicable
File size	899,202
Date (UTC)	25-Jul-2008
Time (UTC)	03:34

Back to the top