KB Articles

Page 1 of 73412345...102030...Last »

Missing export option for Proofpoint users in Office 365 dedicated

When you click the Export icon in the Proofpoint UI in Microsoft Office 365 dedicated, the option to export is not visible.
This issue occurs because you are not in the Export Users group. To perform the Export function, you must be a member of the Export Users group. This is a new behavior for the latest Proofpoint build.
To resolve this issue, make sure that you are a member of the Export Users group.

Users in the “Export Users” group are assigned user rights to create and view export jobs. Users who are not in the Export Users group cannot create or view export jobs. For these users, the Export option is not available.

The following is a screen shot of a user profile in the Export Users group.

Collapse this imageExpand this image

Article ID: 2995537 – Last Review: August 30, 2014 – Revision: 3.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
vkbportal226 kbgraphic kbgraphxlink KB2995537

Read the article:
Missing export option for Proofpoint users in Office 365 dedicated

"Subtask NeedsConfiguration execution failed" error in the Hybrid Configuration wizard in Exchange Server 2013

ERROR : Subtask NeedsConfiguration execution failed: Configure MRS Proxy Settings Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. An IIS directory entry couldn’t be created. The error message is Access is denied. . HResult = -2147024891 at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors)

See more here:
"Subtask NeedsConfiguration execution failed" error in the Hybrid Configuration wizard in Exchange Server 2013

Error when you run Hybrid Configuration wizard: "Execution of the Set-FederatedOrganizationIdentifier cmdlet has thrown an exception"

When you run the Hybrid Configuration wizard in Exchange Server 2013 to set up a hybrid deployment between your on-premises Exchange organization and Exchange Online, you receive an error message that resembles the following: 

ERROR : Subtask Configure execution failed: Configure Organization Relationship 
Execution of the Set-FederatedOrganizationIdentifier cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. Federation trust “contoso.com/Configuration/Deleted Objects/Microsoft Federation Gateway
DEL: ” wasn’t found. Make sure you have typed it correctly.

Note The object that’s specified in the error message above will be different from the object in the error message that you receive.

This issue may occur if stale or obsolete registry entries are present in Active Directory and these registry entries point to deleted instances.  

For example, this issue can occur if you run the Hybrid Configuration wizard in Exchange 2013 after an earlier Exchange 2010-based federation trust was not completely removed or incorrectly removed. 

Warning This procedure requires Active Directory Service Interfaces Editor (ADSI Edit). Using ADSI Edit incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems that result from the incorrect use of ADSI Edit can be resolved. Use ADSI Edit at your own risk. 

To resolve this issue, follow these steps:

  1. Start ADSI Edit, locate CN=OrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DomainName, and then delete the following containers in it:
    • CN=Federation
    • CN=Federation Trusts
    • CN=Hybrid Configuration
  2. From the Exchange Server 2013 installation media, run setup.exe /adprep to configure the containers.

After you complete these steps, rerun the Hybrid Configuration Wizard.

Still need help? Go to the Office 365 Community

(http://community.office365.com/)

 website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 2995731 – Last Review: August 29, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365022013 o365 o365a hybrid KB2995731

Read the original:
Error when you run Hybrid Configuration wizard: "Execution of the Set-FederatedOrganizationIdentifier cmdlet has thrown an exception"

Responses from external meeting attendees do not appear in Outlook tracking

Consider the following scenario. You create an Outlook meeting, and you invite one or more attendees who are external to your Exchange organization. Later, you notice that the Tracking page in the Outlook meeting does not show the meeting responses from the external attendees. Additionally, if you view the meeting in Exchange Server 2007 Outlook Web Access (OWA) or in Exchange Server 2010 and Exchange Server 2013 Outlook Web App (OWA), the tracking information does not show attendee responses from external attendees.
By default, Exchange Server are not configured to process external meeting requests or meeting responses. 
Your mailbox can be configured to process external meeting requests and meeting responses. You can enable this feature by using OWA, or an Exchange administrator can enable it for you by using the Exchange Management Shell.

Use OWA to enable the processing of external meeting responses

Outlook Web Access

  1. Log on to OWA, and then click Options.
  2. Click Calendar Options, and then click to select the Automatically process requests and responses from external senders check box under Automatic Calendar Processing.
  3. Click Save to apply the changes.

Outlook Web App

  1. Log on to OWA, click Options, and then click See All Options.
  2. Click Settings, and then click Calendar.
  3. Under Automatic Processing, click to enable the Automatically process requests and responses from external senders check box.
  4. Click Save to apply the changes.

Use the Exchange Management Shell to enable the processing of external meeting responses

The Exchange Server administrator must start the Exchange Management Shell on the Exchange mailbox server and then run the following command in the Exchange Management Shell:

Set-mailboxcalendarsettings username -ProcessExternalMeetingMessages $true

where username is the affected user’s alias.

Article ID: 2331322 – Last Review: August 28, 2014 – Revision: 4.0


Applies to
  • Microsoft Exchange Server 2013 Enterprise
  • Microsoft Exchange Server 2013 Standard
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition

See original article:
Responses from external meeting attendees do not appear in Outlook tracking

Incorrect taskbar preview for minimized Excel 2010 workbooks

Consider the following scenario:
  • You open multiple workbooks in Excel 2010.
  • You move Excel 2010 to a second monitor that is positioned either to the right or below the main monitor.
  • You minimize Excel 2010 from the maximized state.
  • You move pointer over each workbook on the taskbar.

In this scenario, an incorrect or same taskbar preview is displayed for each workbook.

To work around this issue, use one of the following methods:
Excel 2010 is a multiple document instance (MDI). Starting from Windows 7, bitmap live previews are enabled as per the top level window. Office has to work around as MDI applications such as Excel 2010 only have 1 top level window. The workaround code mistakenly does not consider this particular multi-monitor scenario.

Article ID: 2992464 – Last Review: August 27, 2014 – Revision: 1.0

kbsurveynew kbtshoot kbexpertiseinter kbbug KB2992464

Read More:
Incorrect taskbar preview for minimized Excel 2010 workbooks

Update Rollup 14 for Exchange Server 2007 Service Pack 3

Update Rollup 14 for Microsoft Exchange Server 2007 Service Pack 3 (SP3) was released on August 26, 2014. Before you install this update rollup, see the Installation instructions in this article.

Method 1: Windows Update

This update rollup is available on Windows Update

(http://update.microsoft.com/)

.

Note Microsoft Update does not detect update rollups for Exchange Server 2007 on clustered Exchange Server 2007 systems.

Method 2: Microsoft Download Center

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

This update includes new daylight saving time (DST) updates for Exchange Server 2007 SP3. For more information about DST, go to the following Microsoft website:

Installation instructions

Restart requirement

Services that must be restarted after you apply this update rollup are restarted automatically.

Removal information

To remove Update Rollup 14 for Exchange Server 2007 SP3, go to Add or Remove Programs in Control Panel. Then, remove update 2936861.

For more information about terminology that Microsoft uses to describe software updates, 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

Article ID: 2936861 – Last Review: August 26, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Server 2007 Service Pack 3, when used with:
    • Microsoft Exchange Server 2007 Enterprise Edition
    • Microsoft Exchange Server 2007 Standard Edition
kbfix atdownload kbsurveynew kbexpertiseadvanced KB2936861

Link:
Update Rollup 14 for Exchange Server 2007 Service Pack 3

Outlook Web App logon times out in an Exchange Server 2010 environment

After a user enters his or her account name and password in Outlook Web App, the logon process fails, and the user receives a time-out error message. When this issue occurs, no Outlook Web App users in your Exchange Server organization can log on. This issue may last for several hours until you restart the Client Access server.
This issue occurs because of an infinite wait (or freeze) in the ADNotificationListener method.
To resolve this issue, install the following update:
2961522

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

Update Rollup 7 for Exchange Server 2010 Service Pack 3

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

Article ID: 2982873 – Last Review: August 26, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2010 Service Pack 3, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbqfe kbfix kbexpertiseinter kbsurveynew KB2982873

Read More:
Outlook Web App logon times out in an Exchange Server 2010 environment

S/MIME option disappears when you use Outlook Web App in Internet Explorer 11 in an Exchange Server 2010 environment

After you apply Update Rollup 5 for Microsoft Exchange Server 2010 Service Pack 3 (SP3) in your environment, you cannot install S/MIME controls in Outlook Web App through Internet Explorer 11. Additionally, the S/MIME option is not displayed on the Options page in Outlook Web App.
This issue occurs because Outlook Web App does not recognize Internet Explorer 11 as a browser that supports S/MIME controls.
To resolve this issue, install the following update: 
2961522

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

Update Rollup 7 for Exchange Server 2010 Service Pack 3

To work around this issue, use Internet Explorer 11 in compatibility mode to access Outlook Web App. To do this, press F10 to display the menu bar, and then on the Tools menu in Internet Explorer 11, click Compatibility View settings. Then, add the Outlook Web App site to the list of sites to be viewed in compatibility view.

Notes

  • When you use this workaround to access Outlook Web App, you receive the following error message the first time that you do this:

    To use S/MIME you must have Internet Explorer 7 or a later version. For more information, contact your Help desk.

    To work around this issue, close Internet Explorer 11, reopen the page in compatibility mode, and then the S/MIME option will work as expected.

  • When you use this workaround, Internet Explorer 11 saves your Compatibility View settings for the website. Every time that you access the Outlook Web App site, Compatibility View will be used. To turn off Compatibility View for a website, click the Compatibility View icon for that website. You can also add or remove specific websites from Compatibility View without accessing each website.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about loading Outlook Web App Premium in Internet Explorer 11, go to the following website:For more information about Outlook Web App and S/MIME, go to the following Microsoft website:

Article ID: 2978645 – Last Review: August 26, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2010 Service Pack 3, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbsurveynew kbqfe kbfix kbexpertiseadvanced KB2978645

Read the original post:
S/MIME option disappears when you use Outlook Web App in Internet Explorer 11 in an Exchange Server 2010 environment

Update Rollup 7 for Exchange Server 2010 Service Pack 3


Update Rollup 7 for Exchange Server 2010 SP3 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
  • 2983261

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

    “HTTP 400 – Bad Request” error when you open a shared mailbox in Outlook Web App in an Exchange Server 2010 environment

  • 2982873

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

    Outlook Web App logon times out in an Exchange Server 2010 environment

  • 2980300

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

    Event 4999 is logged when the World Wide Web publishing service crashes after you install Exchange Server 2010 SP3

  • 2979253

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

    Email messages that contain invalid control characters cannot be retrieved by an EWS-based application

  • 2978645

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

    S/MIME option disappears when you use Outlook Web App in Internet Explorer 11 in an Exchange Server 2010 environment

  • 2977410

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

    Email attachments are not visible in Outlook or other MAPI clients in an Exchange Server 2010 environment

  • 2976887

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

    eDiscovery search fails if an on-premises Exchange Server 2010 mailbox has an Exchange Online archive mailbox

  • 2976322

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

    Assistant stops processing new requests when Events in Queue value exceeds 500 in Exchange Server 2010

  • 2975988

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

    S/MIME certificates with EKU Any Purpose (2.5.29.37.0) are not included in OAB in Exchange Server 2010

  • 2966923

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

    Domain controller is overloaded after you change Active Directory configurations in Exchange Server 2010

This update also includes new daylight saving time (DST) updates for Exchange Server 2010 SP3. For more information about DST, go to the following Microsoft website:

Installation instructions

Learn more about how to install the latest update rollup for Exchange Server 2010

(http://technet.microsoft.com/en-us/library/ff637981.aspx)

.

Also learn about the following update installation scenarios.

Install the update on computers that aren’t connected to the Internet

Collapse this imageExpand this image

When you install this update rollup on a computer that’s not connected to the Internet, you may experience long installation times. Additionally, you may receive the following message:

Creating Native images for .Net assemblies.

This behavior is caused by network requests to connect to the following website:

http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl

(http://crl.microsoft.com/pki/crl/products/CodeSigPCA.crl)

These network requests represent attempts to access the certificate revocation list for each assembly that native image generation (NGen) compiles to native code. However, because the Exchange server is not connected to the Internet, each request must wait to time out before the process continues.

To resolve this issue, follow these steps:

  1. On the Tools menu in Internet Explorer, click Internet Options, and then click the Advanced tab.
  2. In the Security section, clear the Check for publisher’s certificate revocation check box, and then click OK.

Clear this security option in Internet Explorer only if the computer is in a tightly controlled environment. When setup is complete, select the Check for publisher’s certificate revocation check box again.

Collapse this imageExpand this image

Install the update on computers that have customized Outlook Web App files

Collapse this imageExpand this image

Important Before you apply this update rollup, make a backup copy of any customized Outlook Web App

(http://technet.microsoft.com/en-us/library/ee633483(EXCHG.140).aspx )

files.

When you apply an update rollup package, the update process updates the Outlook Web App files if that is required. Therefore, any customizations to the Logon.aspx file or to other Outlook Web App files are overwritten, and you must re-create the Outlook Web App customizations in Logon.aspx.

Collapse this imageExpand this image

Install the update for CAS Proxy Deployment Guidance customers who deploy CAS-CAS proxying

Collapse this imageExpand this image

If you meet both of the following conditions, apply the update rollup on the Internet-facing Client Access servers before you apply the update rollup on the non-Internet-facing Client Access servers:
Note For other Exchange Server 2010 configurations, you do not have to apply the update rollup on your servers in any particular order.

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

Collapse this imageExpand this image

Restart requirement

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

Removal information

To remove Update Rollup 7 for Exchange Server 2010 SP3, use the Add or Remove Programs item in Control Panel to remove update 2961522.

Installing this update on a DBCS version of Windows Server 2012

You cannot install or uninstall Update Rollup 7 for Exchange Server 2010 SP3 on a double-byte character set (DBCS) version of Windows Server 2012 if the language preference for non-Unicode programs is set to the default language. To work around this issue, you must first change this setting. To do this, follow these steps:

  1. In Control Panel, open the Clock, Region and Language item, and then click Region.
  2. Click the Administrative tab.
  3. In the Language for non-Unicode programs area, click Change system locale.
  4. On the Current system locale list, click English (United States), and then click OK.

After you successfully install or uninstall Update Rollup 7, revert this language setting as appropriate.

For more information about terminology that Microsoft uses to describe software updates, click the following article number to go to 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

Article ID: 2961522 – Last Review: August 26, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Server 2010 Service Pack 3, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbfix kbexpertiseinter kbsurveynew atdownload KB2961522

See the original post:
Update Rollup 7 for Exchange Server 2010 Service Pack 3

"HTTP 400 – Bad Request" error when you open a shared mailbox in Outlook Web App in an Exchange Server 2010 environment

Consider the following scenario:
  • In a Microsoft Exchange Server 2010 environment, you create a shared mailbox whose SMTP address starts with “oma” (as in the name “omar,” for example).
  • You log on to Outlook Web App, and then you try to open the shared mailbox.

In this scenario, the shared mailbox does not open, and you receive the following error message:
 

This issue occurs because Exchange considers a URL that contains the ”/owa/oma” string a request for a service.
To resolve this issue, install the following update:
2961522

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

Update Rollup 7 for Exchange Server 2010 Service Pack 3

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

Article ID: 2983261 – Last Review: August 26, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Server 2010 Service Pack 3, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbqfe kbfix kbsurveynew kbexpertiseinter KB2983261

See the article here:
"HTTP 400 – Bad Request" error when you open a shared mailbox in Outlook Web App in an Exchange Server 2010 environment

Page 1 of 73412345...102030...Last »

Recent Comments

    Archives

    Categories