privacy-statement

Page 1 of 11812345...102030...Last »

Cannot add an additional mailbox to a MAPI profile in Exchange 2000 Server

Article ID: 833399 – Last Review: September 6, 2011 – Revision: 3.0

When you try to add an additional Exchange mailbox to an existing MAPI profile, you receive one of the following error messages:
The name could not be resolved. The action could not be completed.

The name cannot be resolved. The action cannot be completed.

For example, this issue occurs after you follow these steps
to add an additional mailbox to a MAPI profile:

  1. In Control Panel, double-click Mail, and
    then click Show Profiles.
  2. Click the profile that you want to modify, click
    Properties, click E-mail Accounts, and then
    click Next.
  3. In the Name list, click Microsoft
    Exchange Server
    , click Change, and then click
    More Settings.
  4. Click the Advanced tab, and then click
    Add.
This issue may occur if another object that has the same LegacyExchangeDN attribute as the Exchange Server exists in the Active Directory
directory service. This object may exist in the
LostAndFoundConfig container container. In this scenario, the
101e6613 registry key is
absent from the following registry subkey on the client computer where you
cannot add an additional Exchange mailbox to the profile:

HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles13dbb0c8aa05101a9bb000aa002fc45a

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other
LDAP version 3 client, and you incorrectly modify the attributes of Active
Directory objects, you can cause serious problems. These problems may require
you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003,
Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows
and Exchange. Microsoft cannot guarantee that problems that occur if you
incorrectly modify Active Directory object attributes can be solved. Modify
these attributes at your own risk.

To
search for this LegacyExchangeDN attribute in the directory, use the LDP utility against
a Global Catalog.

Note The default port is 3268.

To do this, follow these
steps:

  1. Open the ldp.exe tool.
  2. On the Browse menu,
    click Search.
  3. In
    the Filter
    field, paste the LegacyExchangeDN string
    of the impacted server:

    legacyExchangeDN=/o=OrganizationName/ou=AdministrativeGroupName/cn=Configuration/cn=Servers/cn=ServerName

  4. Set the Scope to the
    Subtree option,
    and then
    click Run.
  5. If the search returns two entries, you must investigate in
    the output, and determine which object has the same
    LegacyExchangeDN attribute as the Exchange server computer.

If an object that has the same name as the Exchange computer
appears in the LostAndFoundConfig container, remove it. To do
this, follow these steps:

  1. Start the ADSI Edit snap-in. To do this, click
    Start, click Run, type
    adsiedit.msc in the Open box, and then
    click OK.

    Note ADSI Edit is included with the Microsoft Windows 2000 Support
    Tools.
    For
    additional information about how to install the Windows 2000 Support Tools,
    click the following article number to view the article in the Microsoft
    Knowledge Base:

    301423 

    (http://support.microsoft.com/kb/301423/
    )

    How to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer

  2. Connect to a domain controller if you are not already
    connected to a domain controller.
  3. Expand Configuration Container
    servername.example.com
    , expand
    CN=Configuration,DC=example,DC=com,
    and then click CN=LostAndFoundConfig.
  4. View the contents of the right pane. If an object that has
    the same name as the Exchange computer appears in the right pane, right-click
    that object, and then click Delete. Click Yes
    to confirm the removal of the object.
  5. Quit ADSI Edit.
  6. On the Exchange computer, restart all the Exchange-related services.


To work around this issue, copy the missing
101e6613 registry entry
from a correctly functioning profile.

Note This workaround resolves the issue for the current user. However,
you must perform this workaround every time that you create a new user.

To copy this registry value, follow these steps:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 

(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows
  1. On the computer where you cannot add an additional Exchange
    mailbox to the profile, start Registry Editor. To do this, click
    Start, click Run, type
    regedit in the Open box, and then click
    OK.
  2. Locate and then click the following registry subkey:

    HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles13dbb0c8aa05101a9bb000aa002fc45a

    Note Replace with the name of the user where you
    cannot successfully add a mailbox to the MAPI profile.

  3. If the 101e6613 registry entry does not appear
    in the right pane, create it. To do this, follow these steps:

    1. On the Edit menu, point to
      New, and then click Binary Value.
    2. In the New Value #1 box, type
      101e6613, and then press ENTER.
  4. Copy the contents from the
    101e6613 registry entry
    of a user where you can successfully add an additional mailbox to the user’s
    MAPI profile to the new registry value that you created in step 3. To do this,
    follow these steps:

    1. Locate and then click the following registry subkey,
      where is the name of a user where you can successfully add a
      mailbox to the MAPI profile:

      HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles13dbb0c8aa05101a9bb000aa002fc45a

    2. In the right pane, right-click
      101e6613, and then click Modify.
    3. In the Value data box, select all the
      text, press CTRL+C to copy the text to the clipboard, and then click
      Cancel.
    4. Locate and then click the following registry subkey,
      where is the name of a user where you cannot successfully add
      a mailbox to the MAPI profile:

      HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles13dbb0c8aa05101a9bb000aa002fc45a

    5. In the right pane, right-click
      101e6613, and then click Modify.
    6. Press CTRL+V to paste the clipboard contents to the
      Value data box, and then click OK.
  5. Quit Registry Editor.

Other Resources

Other Support Sites

Community

Get Help Now

Article Translations

Follow this link:
Cannot add an additional mailbox to a MAPI profile in Exchange 2000 Server

Email received from a sender using Outlook includes a Winmail.dat attachment

You receive an email message that contains a winmail.dat attachment. This issue may occur if all of the following conditions are true:
  • The email message is sent to you by someone using Microsoft Outlook.
  • The format of the message is Rich Text format (RTF).


This issue is more common when the email message is sent to you over the Internet.

The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
The data in a winmail.dat file is not usable. To resolve this issue, ask the sender to re-send the message in plain text format. The sender can change the format of the email messages that they send by using the following steps:  
  1. On the Tools menu, click Options, and then click Mail Format.
  2. In Compose in this message format, click
    to select Plain Text, and then click OK.

NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient’s contact record.

The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:  

  1. On the Tools menu, click Address Book.
  2. In Show Names From, click the Personal Address Book.
  3. Select the addressee that you want to set as plain text,
    and then click Properties on the File menu.
  4. In the SMTP-General tab, click to clear the Always send to this recipient in
    Microsoft Exchange rich text format
    check box, and then click OK.

 The sender can use the following steps to set plain text in the recipient’s contact record:  

  1. Open the recipient’s record in the Contacts folder.
  2. Double-click the recipient’s e-mail address.
  3. In the E-Mail Properties dialog box, click Send Plain Text only under Internet Format.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

For more information about Winmail.dat
attachments, click the following article numbers to view the articles in the Microsoft Knowledge Base:

149203 

(http://support.microsoft.com/kb/149203/
)

Preventing Winmail.dat from
being sent over IMC

138053 

(http://support.microsoft.com/kb/138053/
)
How to prevent the Winmail.dat file from being sent to Internet users

See the article here:
Email received from a sender using Outlook includes a Winmail.dat attachment

Windows 7 may not calculate the size of writable area on BD-R, BD-R DL and BD-R XL correctly.

When attempting to burn 46GB of data to a BD-R Dual Layer disc, or 23GB to a BD-R Single Layer disc in master mode, the process fails and the following error message will be displayed:

“The disc wasn’t burned successfully. Make sure that you have the latest firmware for your CD or DVD burner installed, and then try again.”

Collapse this imageExpand this image

This problem occurs because Windows 7 does not calculate the write capacity of BD-R correctly.

Note: This problem may occur also when you use BD-R XL (Triple or Quadruple Layer) media.

To work around this issue, do not attempt to write more than 22GB of data onto a BD-R Single Layer disc or 45GB for a BD-R Dual Layer disc.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Read More:
Windows 7 may not calculate the size of writable area on BD-R, BD-R DL and BD-R XL correctly.

Error message when you try to verify your domain in Office 365 during a cutover from Business Productivity Online Standard Suite: "Can’t verify domain"

Article ID: 2601510 – Last Review: September 6, 2011 – Revision: 2.0

You try to self-migrate or cut over your service from Microsoft Business Productivity Online Standard Suite to Microsoft Office 365. However, when you try to verify the domain in Office 365, you receive the following error message:

Can’t verify domain
We can’t verify because the domain is associated with a Microsoft Online Services Business Productivity Online Suite (BPOS) account. If you want to use this domain with Microsoft Online Services, you must first remove the domain from BPOS. If you are the owner of the domain and are not using it with BPOS, contact Microsoft Online Services Technical Support to resolve the issue.

This behavior occurs if the domain name was not completely removed from all aspects of the Business Productivity Online Standard Suite service before you cut over to Office 365. A mechanism is used to service the Business Productivity Online Standard Suite to Office 365 transition process. Because of this mechanism, residual proxy addresses may be present for user accounts, groups, contacts, and conference rooms. Therefore, these items may cause a domain name conflict when you try to verify a domain name in Office 365. This behavior may occur even if the domain object itself was already removed from Business Productivity Online Standard Suite.  
We recommend that you follow the Office 365 transition process to migrate your Business Productivity Online Standard Suite subscription to Office 365 instead of performing a self-driven cutover. For more information about the Office 365 transition process, visit the following Office 365 website:
To work around this issue, follow these steps.

Warning When you perform a self-driven cutover from Business Productivity Online Standard Suite to Office 365, a service interruption occurs. This workaround requires you to remove Business Productivity Online Standard Suite settings. This means that service for the Business Productivity Online Standard Suite account is made permanently unusable.

  1. Sign to the Microsoft Online Services Administration Center.
  2. Disable directory synchronization in the Business Productivity Online Standard Suite account. To do this, follow these steps:
    1. Click the Migration tab, and then click the Directory Synchronization subtab.
    2. Under I have enabled directory synchronization, click Disable.

      Collapse this imageExpand this image

  3. Delete all users from the Business Productivity Online Standard Suite account.
    1. Click the Users tab, and then click the Users List subtab.
    2. Select all users. To do this, click to select the check box that is to the left of the Display name column.
    3. In the Actions pane, click Delete user.
  4. Delete all distribution lists from the Business Productivity Online Standard Suite account.
    1. Click the Service Settings tab, click the Exchange Online subtab, and then click Distribution Lists.
    2. Select all distribution lists. To do this, click to select the check box that is next to each distribution list.
    3. In the Actions pane, click Delete distribution list.
  5. Delete all contacts from the Business Productivity Online Standard Suite account.
    1. Click the Service Settings tab, click the Exchange Online subtab, and then click Contacts.
    2. Select all contacts. To do this, click to select the check box that is next to each contact in the list.
    3. In the Actions pane, click Delete contact.
  6. Delete all conference rooms from the Business Productivity Online Standard Suite account.
    1. Click the Service Settings tab, click the Exchange Online subtab, and then click Conference rooms.
    2. Select all conference rooms. To do this, click to select the check box that is next to each conference room in the list.
    3. In the Actions pane, click Delete conference room.
  7. Remove the domain object from Business Productivity Online Standard Suite account.
    1. Click the Users tab, and then click the Domains subtab.
    2. Click to select the check box that is next to the domain that you want to delete.
    3. Click Delete.
  8. Wait six hours for the changes to synchronize from the Business Productivity Online Standard Suite data center to the Office 365 data center before you try to verify the domain again in Office 365.
  9. Contact Forefront Online Protection for Exchange Online (FOPE) technical support to have the domain name manually removed from Business Productivity Online Standard Suite and FOPE data center. This will make the Exchange Online service cutover from Business Productivity Online Standard Suite to Office 365 easier.


Other Resources

Other Support Sites

Community

Get Help Now

See the original article here:
Error message when you try to verify your domain in Office 365 during a cutover from Business Productivity Online Standard Suite: "Can’t verify domain"

Microsoft Security Advisory: Fraudulent digital certificates could allow spoofing

Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, visit the following Microsoft website:

Download information

The following files are available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the Update for Windows 7 (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=9ff2c9b5-3237-4d69-ae3b-0b4c470d2c64)

Collapse this imageExpand this image

Download the Update for Windows 7 for x64-based Systems (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=bb5531f8-5767-4211-8432-a0d9aae0c8cb)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 R2 for Itanium-based Systems (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=a3119596-d7a3-48ba-bedf-b02768922164)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 R2 x64 Edition (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=9e7c9c25-0fcd-4c6b-b006-3829a575aa30)

Collapse this imageExpand this image

Download the Update for Windows Vista (KB2607712) package now.
(

http://www.microsoft.com/downloads/details.aspx?FamilyId=2a75d9b2-7e04-49d2-8a29-36fae83a7b2f

)

Collapse this imageExpand this image

Download the Update for Windows Vista for x64-based Systems (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=a0a40dd4-3dec-473b-b1f5-10cbf1819c73)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=d17cfc4a-2336-4f22-a5dd-b19fa08e4352)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 for Itanium-based Systems (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=caf94eff-9750-4209-bb78-641ef67aae59)

Collapse this imageExpand this image

Download the Update for Windows Server 2008 x64 Edition (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=7a2485a4-b628-4f34-b01f-74e22b8cbd70)

Collapse this imageExpand this image

Download the Update for Windows XP (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=d399eb4b-8570-4cdb-a9d5-e5e8fd466caf)

Collapse this imageExpand this image

Download the Update for Windows XP x64 Edition (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=e5cfb043-6c35-42bf-83b8-513bbfa3bfbf)

Collapse this imageExpand this image

Download the Update for Windows Server 2003 (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=65f89181-2a50-4c5a-8f4a-e11d722ef207)

Collapse this imageExpand this image

Download the Update for Windows Server 2003 for Itanium-based Systems (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=b8f188e0-9021-48ca-8e19-8747045573d0)

Collapse this imageExpand this image

Download the Update for Windows Server 2003 x64 Edition (KB2607712) package now.
(http://www.microsoft.com/downloads/details.aspx?FamilyId=b277e12b-6572-4d76-bcaa-71d5a3ec54c0)

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

119591 

(http://support.microsoft.com/kb/119591/
)
How to obtain Microsoft support files from online services

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

Known issues

  • A restart is required for all editions of Windows XP and of Windows Server 2003.
  • A restart is not required for all editions of Windows Vista, of Windows 7, of Windows Server 2008, and of Windows Server 2008 R2. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, you receive a message that advises you to restart. 
  • At the explicit request of the Dutch government, the release of this update on Windows Update will be delayed for the Netherlands.

    This update will become available to the Netherlands on Windows Update and on all Automatic Update channels at a later date. Customers who want to manually install this update should click the appropriate platform download in the “Download information” section. On the next page, users will be able to select the language to install and can continue with the download and the installation.

Continue reading here:
Microsoft Security Advisory: Fraudulent digital certificates could allow spoofing

The Junk E-mail Reporting Tool does not appear in Outlook

The Junk E-mail Reporting Tool is installed on the computer. However, it does not appear in Microsoft Outlook.
This issue may occur if a plug-in conflict disables the Junk E-mail Reporting Tool.
To resolve this issue, use one of the following procedures, depending on your version of Outlook. 

Microsoft Outlook 2010

  1. Click File.
  2. Click Options.
  3. Click Add-Ins.
  4. Under the Manage list, make sure that COM Add-ins is selected, and then click Go.
  5. Click to select the Microsoft Junk E-mail Reporting Add-in check box.
  6. Click OK.
  7. Restart Outlook 2010.

Microsoft Office Outlook 2007

  1. On the Help menu, click Disabled Items.
  2. Select Junk E-mail Reporting Tool.
  3. Click Enable.
  4. Restart Outlook 2007.

Microsoft Office Outlook 2003

  1. On the Help menu, click About Microsoft Office Outlook.
  2. Click Disabled Items.
  3. Select Junk E-mail Reporting Tool.
  4. Click Enable.
  5. Restart Office Outlook 2003.


View original post here:
The Junk E-mail Reporting Tool does not appear in Outlook

SharePoint 2010: New discussion board list view runs into exception: Attempted to use an object that has ceased to exist

Consider the following scenario:

You have a discussion board list and you create a new view based on the Flat template. In the Folders section of the view settings, you select either the “In all folders” or the “In the top-level folder” options. The following error occurs:

Attempted to use an object that has ceased to exist. (Exception from HRESULT: 0×80030102 (STG_E_REVERTED))

This is expected behavior. The “In all folders” and “In the top-level folder” options are not valid for a Flat view in a Disscusion Board list at this time.
Use the default “In folders of content type” setting in the Folders section when you create a view based on the Flat template.

Collapse this imageExpand this image

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

View article:
SharePoint 2010: New discussion board list view runs into exception: Attempted to use an object that has ceased to exist

Support for programming with Business Contact Manager for Outlook

This article describes how Microsoft supports integrating Microsoft Business Contact Manager (BCM) with custom solutions.

The level of programmability support for BCM varies, depending on the version of BCM being used. The following sections explain the kind of support that is provided, depending on the version.

BCM 2003

BCM 2003 was not designed to be customizable. Although BCM 2003 uses Outlook custom forms itself to implement user interface, Microsoft does not support customizing those forms further by editing the forms in form design mode. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

828242 

(http://support.microsoft.com/kb/828242/
)
You cannot customize Business Contact Manager forms in the Outlook forms designer

BCM 2007

Microsoft has created a guide for the Outlook 2007 version of BCM. To read this guide, visit the following MSDN website:


This guide shows how to use the Outlook object model to automate various tasks in BCM. Microsoft supports integrating with BCM only if it is done within the scope of what is documented in the BCM Developer Guide.

BCM 2010

Although BCM 2010 provides general usability improvements compared to BCM 2007, the overall architecture of the data that is stored in Outlook is mostly unchanged. The BCM 2007 Developer Guide has not been updated for BCM 2010, however, information in the Developer Guide can be used as a basis for integrating with BCM 2010 and Microsoft will support this scenarios.

Many of the code samples in the Developer Guide contain code samples that reference a particular folder path in BCM 2007. Because the BCM 2010 folders are one level deeper in the folder path, these paths will have to be updated. For example, consider a VBA code sample that has the following line of code:

Set bcmContactsFldr = bcmRootFolder.Folders("Business Contacts")

This code would have to be updated to the following:

Set bcmContactsFldr = bcmRootFolder.Folders("Business Records").Folders("Business Contacts")

View article:
Support for programming with Business Contact Manager for Outlook

Performance issue when you enable the AuthNoEncap policy to handle large payloads in a network environment in Windows 7 or in Windows Server 2008 R2

Consider the following scenario. You enable the AuthNoEncap policy to handle large payloads in a network environment. Then, you perform a network operation on a computer that is running Windows 7 or Windows Server 2008 R2 in the network environment. In this scenario, you may experience a significant decrease in network performance.
This issue occurs because the TCP stack uses the IPsec slow path instead of the IPsec fast path when the TCP stack processes AuthNoEncap traffic.

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, you must be running one of the following operating systems:

  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 

(http://support.microsoft.com/kb/976932/
)

Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows 7/Windows Server 2008 R2″ on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.

  • 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.1.760
    0.21xxx
    Windows 7 and Windows Server 2008 R2 RTM LDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2 SP1 LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the “Additional file information for Windows 7 and for Windows Server 2008 R2″ section. 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, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7

Collapse this tableExpand this table

File name File version File size Date Time Platform
Fwpkclnt.sys 6.1.7600.21006 187,264 12-Jul-2011 04:34 x86
Tcpip.sys 6.1.7600.21006 1,301,376 12-Jul-2011 04:35 x86
Fwpkclnt.sys 6.1.7601.21768 187,776 12-Jul-2011 05:56 x86
Tcpip.sys 6.1.7601.21768 1,303,424 12-Jul-2011 05:56 x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Collapse this tableExpand this table

File name File version File size Date Time Platform
Fwpkclnt.sys 6.1.7600.21006 288,128 12-Jul-2011 05:33 x64
Tcpip.sys 6.1.7600.21006 1,888,128 12-Jul-2011 05:33 x64
Fwpkclnt.sys 6.1.7601.21768 288,640 12-Jul-2011 05:29 x64
Tcpip.sys 6.1.7601.21768 1,914,240 12-Jul-2011 05:29 x64
For all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name File version File size Date Time Platform
Fwpkclnt.sys 6.1.7600.21006 482,688 12-Jul-2011 04:15 IA-64
Tcpip.sys 6.1.7600.21006 3,800,448 12-Jul-2011 04:15 IA-64
Fwpkclnt.sys 6.1.7601.21768 483,200 12-Jul-2011 04:19 IA-64
Tcpip.sys 6.1.7601.21768 3,803,520 12-Jul-2011 04:19 IA-64
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 

(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows

To work around this problem, disable Large Send Offload (LSO) in the TCP/IP protocol. To do this, follow these steps:

  1. Click Start

    Collapse this imageExpand this image

    , type regedit in the Search programs and files box, and then press Enter.

    Collapse this imageExpand this image

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

  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters

  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type DisableLargeSendOffload, and then press Enter.
  5. Right-click DisableLargeSendOffload, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor.
  8. Restart the computer.
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:

824684 

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

Additional file information


Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Collapse this tableExpand this table

File name X86_63b2417eb9dd62e0eb1139be82c86eca_31bf3856ad364e35_6.1.7600.21006_none_5fee7b79ebde9cca.manifest
File version Not applicable
File size 702
Date (UTC) 12-Jul-2011
Time (UTC) 09:21
Platform Not applicable
File name X86_a24ff779972a7e2a89a2bd8ffa8d1fe4_31bf3856ad364e35_6.1.7601.21768_none_4630e7eeeb8d371b.manifest
File version Not applicable
File size 702
Date (UTC) 12-Jul-2011
Time (UTC) 09:21
Platform Not applicable
File name X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21006_none_b3d5668ae095d505.manifest
File version Not applicable
File size 3,834
Date (UTC) 12-Jul-2011
Time (UTC) 04:57
Platform Not applicable
File name X86_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21768_none_b57d0c7addeae803.manifest
File version Not applicable
File size 3,834
Date (UTC) 12-Jul-2011
Time (UTC) 06:20
Platform Not applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

Collapse this tableExpand this table

File name Amd64_64de594551836357dfd1d976aeb0e347_31bf3856ad364e35_6.1.7601.21768_none_478f19f3354ca5a0.manifest
File version Not applicable
File size 706
Date (UTC) 12-Jul-2011
Time (UTC) 09:21
Platform Not applicable
File name Amd64_e2ddea40f744287622ae42f8e4b38fc3_31bf3856ad364e35_6.1.7600.21006_none_131570faab66a0a9.manifest
File version Not applicable
File size 706
Date (UTC) 12-Jul-2011
Time (UTC) 09:21
Platform Not applicable
File name Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21006_none_0ff4020e98f3463b.manifest
File version Not applicable
File size 3,838
Date (UTC) 12-Jul-2011
Time (UTC) 05:59
Platform Not applicable
File name Amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21768_none_119ba7fe96485939.manifest
File version Not applicable
File size 3,838
Date (UTC) 12-Jul-2011
Time (UTC) 07:11
Platform Not applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name Ia64_0289f3c0cf5086b1b5f86369e0ba37f7_31bf3856ad364e35_6.1.7600.21006_none_4e515909ccd19c1a.manifest
File version Not applicable
File size 704
Date (UTC) 12-Jul-2011
Time (UTC) 09:21
Platform Not applicable
File name Ia64_7558328428d6e0808c0f4aa357866d35_31bf3856ad364e35_6.1.7601.21768_none_c15e4cc30c7da21f.manifest
File version Not applicable
File size 704
Date (UTC) 12-Jul-2011
Time (UTC) 09:21
Platform Not applicable
File name Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.21006_none_b3d70a80e093de01.manifest
File version Not applicable
File size 3,836
Date (UTC) 12-Jul-2011
Time (UTC) 05:55
Platform Not applicable
File name Ia64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7601.21768_none_b57eb070dde8f0ff.manifest
File version Not applicable
File size 3,836
Date (UTC) 12-Jul-2011
Time (UTC) 07:02
Platform Not applicable

View article:
Performance issue when you enable the AuthNoEncap policy to handle large payloads in a network environment in Windows 7 or in Windows Server 2008 R2

A conversation window opens unexpectedly when you press ENTER in the Search box in Office Communicator 2007 or in Office Communicator 2007 R2

You search for a contact in Microsoft Office Communicator 2007 or in Microsoft Office Communicator 2007 R2. After you type the name of the contact in the Search box
and press ENTER, a conversation window opens unexpectedly.
This problem occurs because Office Communicator 2007 or Office Communicator 2007 R2 does not recognize the status of Input Method Editor (IME). When you input characters by using IME, these characters are used when you press ENTER. However, Office Communicator 2007 or Office Communicator 2007 R2 handles the action in the same manner as when you are not using IME.
To fix this problem, apply the following update for Office
Communicator 2007:
2028885 

(http://support.microsoft.com/kb/2028885/
)
Description of the Office Communicator 2007 update package: July 2010

To fix this problem, apply the following update for Office
Communicator 2007 R2:

2028888 

(http://support.microsoft.com/kb/2028888/
)
Description of the Office Communicator 2007 update package: July 2010

Visit link:
A conversation window opens unexpectedly when you press ENTER in the Search box in Office Communicator 2007 or in Office Communicator 2007 R2

Page 1 of 11812345...102030...Last »

Recent Comments

    Archives

    Categories