KB Articles

Page 1 of 74912345...102030...Last »

Issue reporting during migration to ANSI-D in Office 365 Dedicated/ITAR

During a migration to High Availability (ANSI-D) in Office 365 Dedicated/ITAR, you will work with the ANSI-D deployment team. This team will help coordinate the required changes for migrating mailboxes to the new Microsoft Exchange environment. However, this team’s resources should not be directly engaged for support incidents about slow or reduced service. Any service issues that may arise during the migration should be escalated to Microsoft Online Services Support (MOSSUP), as outlined in section 2 of the Office 365 Customer Operations Handbook. 

Because of the many networking and DNS changes that are required before a successful migration, you are expected to be involved throughout the course of the investigation. If you want additional help or require traction because of urgency, you can follow the incident escalation chart that is defined in section 2.1.11 of the Office 365 Customer Operations Handbook

As a reminder, you can submit a support incident online

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

 to MOSSUP, or you can contact Microsoft Online Services Support by telephone

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

. For all escalations, be ready to provide the following information:

  • List of affected users
  • Description of the issue
  • Error information or screen shots
  • Exact builds of applications involved (that is, operating system, Outlook Client, Lync Client, Internet Explorer)
  • Troubleshooting steps and results completed

Note When it is possible, make sure that client-side and networking troubleshooting are completed before escalation. Also make sure that you provide all available diagnostic information to help in the escalation.

Before you move all mailboxes to the ANSI-D topology, you are asked to designate a pilot group of users to move. These pilot users should consist of the different kinds of mailboxes, user types, and clients that make up your general user population. Tests should be completed for line-of-business applications, core business scenarios, and user profiles.

Also, make sure that you are familiar with the relevant service changes and known issues

(https://sharepoint.partners.extranet.microsoft.com/sites/MMS%20Knowledge%20Base/Release%20Docs/Exchange/Exchange%20Upgrades/EXO-D%20Platform%20Upgrades.htm)

Additionally, you can review known issues on the Microsoft Support

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

 site. On the site, enter the Exchange Online Dedicated ANSI-D search string.

Article ID: 3011547 – Last Review: October 24, 2014 – Revision: 2.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Continue Reading:
Issue reporting during migration to ANSI-D in Office 365 Dedicated/ITAR

Error when you try to connect to Exchange Online by using an SMTP client

When you try to connect to Microsoft Exchange Online by using a Simple Mail Transfer Protocol (SMTP) client, you receive an error message that states that the Exchange Online server is unknown, cannot be located, or is configured incorrectly. 

The text of the error message varies, depending on the kind of client or connection that’s used. Here’s one example of an error message that you may receive:

Sending of message failed.
An error occurred sending mail: .outlook.com is unknown. The server may be incorrectly configured. Please verify that your SMTP server settings are correct and try again.

This issue may occur if the SMTP client tries to connect to one of the following regional Exchange Online SMTP servers:
  • smtp-apacnorth.outlook.com
  • smtp-apacsouth.outlook.com
  • smtp-emea.outlook.com
  • smtp-emeacenter.outlook.com
  • smtp-emeacentral.outlook.com
  • smtp-emeaeast.outlook.com
  • smtp-emeasouth.outlook.com
  • smtp-emeawest.outlook.com
  • smtp-latam.outlook.com
  • smtp-nameast.outlook.com
  • smtp-namnorth.outlook.com
  • smtp-namsouth.outlook.com
  • smtp-namwest.outlook.com
  • smtp-unisa.outlook.com
Make sure that SMTP clients connect to smtp.outlook.com instead of one of the regional SMTP addresses. For more information, see the following webpages:
The regional SMTP endpoints were used in earlier versions of Exchange Online. They are replaced by the smtp.outlook.com endpoint in the current version of Exchange Online.

Article ID: 3009995 – Last Review: October 24, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365p o365022013 o365 o365a KB3009995

Read More:
Error when you try to connect to Exchange Online by using an SMTP client

High memory usage by W3wp process of default application pool in an Exchange Server 2010 environment

Consider the following scenario:
  • You have more than 64 Microsoft Exchange Server 2010 Client Access servers in one Active Directory site in an Exchange Server 2010 environment.
  • Outlook Anywhere is enabled in the environment.

In this scenario, the W3wp.exe process that belongs to the default application pool on all Client Access servers consumes lots of event handles and memory. Then, the W3wp.exe process eventually runs out of handles and freezes, and you have to restart the default application pool to recover from this issue.

This issue occurs because the number of Client Access servers in one Active Directory site is limited to 64 servers.
To work around this issue, reduce the number of servers. Or, segregate the servers onto different Active Directory sites.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 3007848 – Last Review: October 24, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
kbsurveynew kbfix kbbug kbexpertiseadvanced KB3007848

Read the article:
High memory usage by W3wp process of default application pool in an Exchange Server 2010 environment

Messages with an SCL rating of 5 or greater are delivered to the Inbox instead of the Junk Email folder in Outlook in Exchange Online

Email messages that have a spam confidence level (SCL) rating of 5 or greater that you expect to delivered to the Junk Email folder in Outlook are delivered to the Inbox folder instead in Exchange Online. 
This occurs if the affected mailbox is also used as the delivery location for undeliverable journal reports. 
This behavior is by design. Mail that’s sent to an address that’s used for undeliverable journal reports won’t be journaled. Transport rules settings and mailbox rule settings don’t apply to these messages. We recommended that you create a dedicated mailbox for undeliverable journal reports.

For more information about examining the SCL and other properties of an email message in Office 365, see the Introducing Message Analyzer, an SMTP header analysis tool in Microsoft Remote Connectivity Analyzer

(http://blogs.technet.com/b/exchange/archive/2013/05/01/introducing-message-analyzer-an-smtp-header-analysis-tool-in-microsoft-remote-connectivity-analzyer.aspx)

blog post.

Article ID: 3009297 – Last Review: October 23, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365022013 o365 o365a KB3009297

Read More:
Messages with an SCL rating of 5 or greater are delivered to the Inbox instead of the Junk Email folder in Outlook in Exchange Online

Can’t manage the list of users who can submit in-policy meeting requests for resource mailboxes in an Exchange 2010-based hybrid deployment

Assume that you have a hybrid deployment of on-premises Exchange Server 2010 and Exchange Online in Office 365. You discover that you can’t use the Exchange Management Console in Exchange 2010 to manage the list of users who can submit in-policy meeting requests to resource mailboxes in Exchange Online. 

For example, when you try to add users to the list of users who can book meeting requests (the BookInPolicy parameter) for a room mailbox, you receive the following error message:

The property has an incorrect type: System String. It should be type: Microsoft.Exchange.Data.Directory.ADObjectId.

This behavior is by design. 

Method 1: Use Exchange Online PowerShell

To use Exchange Online PowerShell to add users to the list of users who can automatically book a room mailbox, follow these steps: 

  1. Connect to Exchange Online by using remote PowerShell. For more info about how to do this, see Connect to Exchange Online using remote PowerShell

    (http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx)

    .

  2. Run the following commands:
    $room = Get-CalendarProcessing "Room Name" $room.BookInPolicy += "UserB", "UserC"

    Set-CalendarProcessing room -BookInPolicy $room.BookInPolicy

    Note In this example, UserB and UserC are added to the list.

Method 2: Use the Exchange admin center in Exchange Online

To use the Exchange admin center to add users to the list of users who can automatically book a room mailbox, follow these steps:

  1. Sign in Office 365, and then go to the Exchange admin center.
  2. Give the admin account full access to the resource mailbox.
  3. Sign in to Outlook Web App by using the admin account, and then follow these steps:
    1. In the upper-right are of the Outlook Web App screen, click your name, and then in the drop-down list, click Open another mailbox.
    2. Type the email address of the resource mailbox, and then click Open
    3. In the upper-right corner of the page, click Settings (

      Collapse this imageExpand this image

      ), and then click Options.

    4. In the left navigation pane, click settings, click resource, and then under These users can schedule automatically if the resource is available and can submit a request for owner approval if the resource is unavailable, click Select users and groups. Then, add the users who you want.
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: 3010295 – Last Review: October 22, 2014 – Revision: 3.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Service Pack 3
  • Microsoft Exchange Server 2010 Enterprise
o365022013 o365 o365a o365e o365m hybrid kbgraphxlink kbgraphic kbbug kbnofix KB3010295

Read more here:
Can’t manage the list of users who can submit in-policy meeting requests for resource mailboxes in an Exchange 2010-based hybrid deployment

Emergency message purge and transport rule processing in Office 365 dedicated

In Microsoft Office 365 dedicated, a user may experience one of the following issues:
  • Many problems occur with mail queuing or performance. 
  • An email message that includes incorrect or sensitive content is sent to multiple mailboxes.
The first issue may occur if many email messages or very large email messages are sent to multiple users. This may be related to a denial of service attack.

The second issue may occur if an employee or outside sender sends an email message that is considered inappropriate or that contains sensitive or confidential information.

To resolve these issues, Microsoft can take the following actions:
  • Emergency transport rule
    • Removes instances of an email message from transport queues. 
    • Keeps new instances of an email message from being delivered to users.
  • Emergency message purge
    • Removes instances of an email message from mailboxes.

In some scenarios, it may be appropriate to request both an emergency transport rule and an emergency message purge. The following are three  common scenarios.

Scenario 1

A user reports that an email message that includes an attachment was incorrectly sent to a distribution group that has thousands of members. The attachment contains salary information for several hundred users. This issue occurred 30 minutes earlier, and the sender of the email message engaged his or her service desk to request that the email message be removed from the recipients’ mailboxes.

Scenario 1: Resolution

To resolve the issue in this scenario, a MOSSUP-recognized authorized requester from your organization must contact Microsoft to request an emergency message purge. To do this, please use the Exchange Online topic and the Message Purge subtopic when you submit a support incident online

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

to Microsoft Online Services Support, or contact Microsoft Online Services Support by telephone

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

. In addition, please provide as much information about the email message as possible. The information should include the sender, the recipients, the subject, the day or time that the email message was sent, and the fact that the email message contains an attachment.

Scenario 2

Users report that they are receiving many copies of an email message from an external sender. Some users reply all and forward the email message. There are some reports of internal messages taking a long time to be received.

Scenario 2: Resolution

To resolve the issue in this scenario, a MOSSUP-recognized authorized requester from your organization must contact Microsoft to request an emergency message purge and an emergency transport rule. To do this, please use the Exchange Online topic and the Message Purge subtopic when you submit a support incident online

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

 to Microsoft Online Services Support, or contact Microsoft Online Services Support by telephone

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

. In addition, please provide as much information about the email message as possible. The information should include the sender, the recipients, the subject, the day or time that the email message was sent, and the evidence that is available to indicate that other email messages are delayed. This lets us determine whether an emergency transport rule is necessary.

Scenario 3

An internal process generated many email messages, and all mail delivery is delayed.

Scenario 3: Resolution

To resolve the issue in this scenario, a MOSSUP-recognized authorized requester from your organization must contact Microsoft to request an emergency transport rule to delete these email messages. To do this, please use the Exchange Online topic and the Message Purge subtopic when you submit a support incident online

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

 to Microsoft Online Services Support, or contact Microsoft Online Services Support by telephone

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

. In addition, please provide as much information about the email message as possible. The information should include the sender, the recipients, the subject, the day or time that the email message that was sent, and the evidence that is available to indicate that other email messages are delayed.

Emergency transport rule

If it is necessary, an emergency transport rule will be created based on the characteristics that are provided, and corresponding email messages will be deleted.

Emergency message purge

The emergency message purge process removes email messages from a user’s mailbox based on specific characteristics. These characteristics can include sender, day or time that the message was sent, subject line, and whether there is an attachment. The emergency message purge searches for email messages that match the criteria and then removes these email messages from the mailbox. The email messages in the Recoverable Items folder of the mailbox are also removed. However, the email message is not removed from the Purges folder. This means that the purged item can be recovered individually by an administrator. However, the purged item is not recoverable from Microsoft Outlook and cannot be recovered in a bulk process.

For more information about deleted-item retention and recovery, go to the following Microsoft TechNet website:

An emergency message purge can be completed by Microsoft O365 Dedicated Support. The process involves multiple steps to make sure that the correct content is removed from users’ mailboxes. This process is optimized to make sure that the correct information is removed in as timely a manner as possible. 

Limitations and risks

  • Only messages that exist in the customer’s managed email environment can be purged.

    Notes 

    • Email messages that are sent outside the environment cannot be removed by Microsoft in this process. This includes public email services such as Hotmail and other private email servers.
    • If you are using a language that contains double-byte characters (for example, Korean is a language that uses double-byte characters), MOSSUP cannot complete the purge request. However, the customer can perform the message purge by using Windows PowerShell cmdlets in self-service tools. 

  • Email messages that are saved to .pst files or to a local drive cannot be purged by Microsoft in this process.
  • Depending on the number of mailboxes that must be searched, the time to complete this request can vary.
  • Email messages are deleted based on their subject, and this process searches for a complete string of words in the subject line. For example, a purge run against the subject “Welcome to the company” will also delete email messages such as “Welcome to the company Bob” or “I felt welcome to the company.” Preparation work has to be done before the actual purge to make sure that the correct email messages and recipients are targeted.
  • Forward and reply messages in an email thread cannot be specifically targeted. The message purge must be run against the subject that does not have the “FW:” or “RE:” prefixes. If a valid message is to be excluded from the purge, the Sent time stamp must be used to omit the valid message.

    For example, a valid message that has the subject “Company Wide Announcement for January” is sent at 3:00 p.m. Eastern Standard Time (EST). One recipient replies to all the recipients of this message at 3:15 EST and creates a message that has the subject “RE: Company Wide Announcement for January.” This reply contains sensitive information that should be purged. However, the initial email message should not be targeted. To perform this purge, the subject “Company Wide Announcement for January” is used with a Sent time stamp of 3:14 PM EST. All the messages in the thread that are sent after 3:14 PM EST will be purged.

  • Any email message that is deleted from a mailbox that has Single Item Retention (SIR) disabled cannot be recovered by Microsoft. Because there is a risk that messages will be unintentionally deleted from mailboxes that have SIR disabled, Microsoft will enable SIR on any mailboxes that are found. If mailboxes that have SIR disabled are found, the purge process will be delayed for these mailboxes until SIR is enabled. It will take 60 minutes to make sure that these mailboxes are enabled.
  • By design, messages from Proofpoint archives cannot be deleted. Therefore, requests for the deletion of these messages will not be processed.

General process narrative

Customers should be aware that they have to work closely with O365 Dedicated Support throughout the following process:

  1. A MOSSUP-recognized authorized requester must submit a support incident. 

    Note If you are unsure whether the requester is a member of the list of MOSSUP-recognized authorized requesters, contact your service delivery manager (SDM). 

    The support incident provides O365 Dedicated Support with the characteristics that are needed to identify the target email message. These include the sender, the subject line, and the date or time that the email message that was sent. If a customer other than the MOSSUP-recognized authorized requester should work with O365 Dedicated Support, this should be specified in the support incident. If the customer knows from which recipients’ mailboxes they want the email message purged, they should include a list of recipients in the support incident.

  2. If the case is a Severity A escalation, customers must call O365 Dedicated Support after they submit the support incident.
  3. The O365 Dedicated Support agent will work to obtain a complete list of the recipients if the customer did not provide this or if the customer is not sure of who should be included in the list of recipients. The agent will do this by searching the message-tracking logs for the message in question and exporting all recipients. This lets the purge process be run against as few mailboxes as possible. Message tracking expedites the process and avoids unexpected consequences. However, message-tracking logs are maintained for only ten days. If the email message was sent more than ten days earlier, the requester must provide a list of recipients.

    Note An environment-wide purge can be run against all mailboxes. Depending on the number of mailboxes in the environment and the size of the mailboxes, this process can take up to 48 hours. Such a purge should be done only in situations in which O365 Dedicated Support and the customer requester agree that this is the method of choice. 

  4. The O365 Dedicated Support agent will engage the MOSSUP-recognized authorized requester (or the customer contact who is specified by the MOSSUP-recognized authorized requester) to confirm the recipient list before the agent goes to the next step.
  5. A pre-purge process is run against the recipient list or all mailboxes. During this process, a search is run against the mailboxes to identify the email message that fits the criteria of the target email message. O365 Dedicated Support will provide the requester with a spreadsheet that includes a list of the users and the number of messages that were found that meet the criteria of the target email message. However, there may be a strong business reason to skip this part of the process. If this is the case, skipping the pre-purge search process should be approved by the MOSSUP-recognized authorized requester. Even if the pre-purge search process is skipped, a check should nevertheless be made to make sure that the SIR feature is enabled for all recipients and all mailboxes. If the SIR feature is not enabled, the support agent will enable the SIR feature. This feature makes sure that messages can be recovered for a specific mailbox from the mailbox Purges folder. 

    For more information about the SIR feature, go to the following Microsoft TechNet website: 

    It will take an hour to confirm that the SIR feature is set on the mailbox. The process can continue for the mailboxes that are found to have the SIR feature enabled. The purge can then be run against the remaining mailboxes. If there is a strong business reason to continue the purge process on all mailboxes immediately, the customer contact should communicate this to the O365 Dedicated Support agent.

    After the pre-purge process is complete and the customer reviews the spreadsheet, the MOSSUP-recognized authorized requester must provide approval to O365 Dedicated Support through an email message. Then, the purge will continue.

  6. When O365 Dedicated Support receives the approval, the purge will be run, and a spreadsheet that contains the recipients and the number of email messages that were found will be sent to the customer. 

Note For more information about self-service options to control data spillage, click the following article number to view the article in the Microsoft Knowledge Base:

2811786

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

How to control data spillage in Office 365 dedicated and ITAR

Article ID: 2736413 – Last Review: October 22, 2014 – Revision: 11.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Taken from:
Emergency message purge and transport rule processing in Office 365 dedicated

Unable to manage the list of users who can submit in-policy meeting requests for resource mailboxes in an Exchange 2010-based hybrid deployment

Assume that you have a hybrid deployment of on-premises Exchange Server 2010 and Exchange Online in Office 365. You find that you’re unable to use the Exchange Management Console in Exchange 2010 to manage the list of users who can submit in-policy meeting requests to resource mailboxes in Exchange Online. 

For example, when you try to add users to the list of users who can book meeting requests (the BookInPolicy parameter) for a room mailbox, you get the following error message:

The property has an incorrect type: System String. It should be type: Microsoft.Exchange.Data.Directory.ADObjectId.

This behavior is by design. 

Method 1: Use Exchange Online PowerShell

To use Exchange Online PowerShell to add users to the list of users who can automatically book a room mailbox, follow these steps: 

  1. Connect to Exchange Online by using remote PowerShell. For more info about how to do this, see Connect to Exchange Online using remote PowerShell

    (http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx)

    .

  2. Run the following commands:
    $room = Get-CalendarProcessing "Room Name" $room.BookInPolicy += "UserB", "UserC"

    Set-CalendarProcessing room -BookInPolicy $room.BookInPolicy

    Note In this example, UserB and UserC are added to the list.

Method 2: Use the Exchange admin center in Exchange Online

To use the Exchange admin center to add users to the list of users who can automatically book a room mailbox, follow these steps:

  1. Sign in Office 365, and then go to the Exchange admin center.
  2. Give the admin account full access to the resource mailbox.
  3. Sign in to Outlook Web App by using the admin account, and then follow these steps:
    1. In the upper-right are of the Outlook Web App screen, click your name, and then in the drop-down list, click Open another mailbox.
    2. Type the email address of the resource mailbox, and then click Open
    3. In the upper-right corner of the page, click Settings (

      Collapse this imageExpand this image

      ), and then click Options.

    4. In the left navigation pane, click settings, click resource, and then under These users can schedule automatically if the resource is available and can submit a request for owner approval if the resource is unavailable, click Select users and groups, and then add the users who you want.
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: 3010295 – Last Review: October 22, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Service Pack 3
  • Microsoft Exchange Server 2010 Enterprise
o365022013 o365 o365a o365e o365m hybrid kbgraphxlink kbgraphic kbbug kbnofix KB3010295

View the original here:
Unable to manage the list of users who can submit in-policy meeting requests for resource mailboxes in an Exchange 2010-based hybrid deployment

Office 365 DNS Diagnostics and DNS configuration

This article is listed on Office 365 DNS diagnostic tool.

To use your own domain name with Office 365 will need up to 10 DNS records manually configured third-party Domain Registrar Web site.
Misconfiguration of the DNS is one of the top queries received from customers of the Office 365 days a year. May cause problems if DNS record is missing or incorrectly configured in Outlook and mail flow connectivity, Lync sign-in, or external Instant Messaging (IM) provider Federation.

Office 365 DNS Diagnostics detects all the DNS records required for Office 365 services, identifies the known configuration mistakes.

When you use the Office 365 DNS diagnostic

DNS configuration errors is a primary cause of the problem that is described in this section. Strongly recommended to run Office 365 DNS diagnostic to identify these problems.

Exchange Online problems

  • Mail delivery problems
    • Cannot receive mail on the Internet
    • To receive a non-delivery report (NDR)
  • Outlook client connectivity problems
    • Outlook and Exchange Online connection issues
    • Autodiscover does not work

Lync Online of the problem

  • Lync client sign-in problems
  • IM does not work between the contacts are federated or public IM connectivity partners (PIC)
  • IM from Outlook Web App or presence issues
SharePoint Online the issue
  • Access to the published Web site to use the domain name

How to use the Office 365 DNS diagnostic

Office 365 DNS Diagnostic can be run on Internet-accessible computers. Office 365 DNS diagnostic tool using Nslookup.exe queries and DNS records of Office 365 days a year from the computer’s default DNS servers, detects a DNS misconfiguration. However, does not collect data specific to the computer that is running the tool.

  1. Office 365 DNS diagnostic O365 Customer Domain Name page, type the domain name. Office 365 DNS diagnostic tool verify DNS records for the domain.

    Collapse this imageExpand this image

    Note domain Office 365 portal (http://portal.microsoftonline.com

    (http://portal.microsoftonline.com/)

    ) To verify that have been approved and added. If you have not yet approved the domain will access to the following Microsoft Web site.

  2. Select the scenario that applies in the Exchange Deployment Scenario page. Cloud Only or Co-exist/Hybrid is optional.

    Scenario if there is more than one domain, select the domain you entered in step 1 applies.

    • If you have moved to Office 365 [Cloud Onlychoose all the mailboxes to the appropriate domain.
    • Select the Cloud Only If you don’t use the domain to the appropriate Exchange Online mailbox.
    • Select the Co-exist/Hybrid If divided into on-premises Exchange Server environment and Exchange Online mailboxes are hosted.
For more information, visit to the following Microsoft Web site.
If you need additional information Office 365 community

(http://community.office365.com/ja-jp/default.aspx)

Please see the Web site.

Article ID: 2776497 – Last Review: October 21, 2014 – Revision: 17.0


Applies to
  • Microsoft Lync Online
  • Microsoft Exchange Online
  • Microsoft SharePoint Online
o365 o365a o365p o365e o365022013 o365m kbgraphic kbmt KB2776497 KbMten

View the original here:
Office 365 DNS Diagnostics and DNS configuration

Shared mailboxes moved from on-premises environments to Office 365 are converted to user mailboxes after directory synchronization

Assume that you have a hybrid deployment of Microsoft Exchange Online in Microsoft Office 365 and in your on-premises Microsoft Exchange Server environment. After directory synchronization runs, shared mailboxes that were moved from the on-premises environment to Office 365 are unexpectedly converted to regular mailboxes. When this occurs, you may be unable to convert the mailboxes to shared mailboxes. If you can make this conversion, the mailboxes revert to shared mailboxes the next time that directory synchronization runs.

Also, when you view the properties of the shared mailboxes in the Office 365 portal, you may receive the following error message:

Exchange: Couldn’t convert the mailbox because the mailbox is already of the type ‘Regular’

This issue occurs if the value of the msExchRemoteRecipientType attribute isn’t set correctly by the on-premises hybrid server that’s running Microsoft Exchange Server 2010. The value of the msExchRemoteRecipientType attribute is incorrectly set to 0×4. A value of 0×4 indicates that the mailbox was migrated. In this situation, directory synchronization replicates the attribute to the cloud, and then Office 365 converts the shared mailbox to a MailUser object.

The value of the msExchRemoteRecipientType attribute should be set to 0×64. The hexadecimal value of 0×64 is equal to a decimal value of 100. In this situation, the shared mailbox isn’t converted to a regular mailbox when directory synchronization runs. Instead, it remains as a shared mailbox. 

To work around this issue, use the Exchange Management Shell to change the value of the msExchRemoteRecipientType attribute. 

Change the value of the msExchRemoteRecipientType attribute for one user

To change the value for one user, follow these steps:

  1. Run the Exchange Management Shell as an admin.
  2. At the command prompt, type the following command, and then press Enter:
    Set-Mailbox –identity user@contoso.com –RemoteRecipientType “ProvisionMailbox, ProvisionArchive”

Note The ProvisionMailbox and ProvisionArchive flags set the msExchRemoteRecipientType attribute to the correct decimal value for the version of Exchange on which the Exchange Management Shell commands are running.

Change the value of the msExchRemoteRecipientType attribute for all users

To change the value this for all users, follow these steps:

  1. Run the Exchange Management Shell as an admin.
  2. At the command prompt, type the following commands, and then press Enter:
    $mbx = Get-Mailbox -ResultSize Unlimited -Filter (RecipientTypeDetails -eq "UserMailbox") -and (RemoteRecipientType -eq "Migrated")
    $mbx | Set-Mailbox -RemoteRecipientType "ProvisionMailbox, ProvisionArchive"

Note The ProvisionMailbox and ProvisionArchive flags set the msExchRemoteRecipientType attribute to the correct decimal value for the version of Exchange on which the Exchange Management Shell commands are running.

This is a known issue. Microsoft is currently investigating the issue and will post more information in this article when it becomes available.
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: 2710029 – Last Review: October 17, 2014 – Revision: 13.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
o365 o365022013 o365e o365m o365a hybrid kbbug KB2710029

View article:
Shared mailboxes moved from on-premises environments to Office 365 are converted to user mailboxes after directory synchronization

Internet accessible URLs required for connectivity to Microsoft Dynamics CRM Online

You cannot access Microsoft Dynamics CRM 2011, Microsoft Dynamics CRM 2013, or specific URLs fail to load when you use Microsoft Dynamics CRM. When you try to configure Microsoft Dynamics CRM for Outlook, you receive the following error: 

The server address (URL) is not valid

In addition, a network error message is seen if you monitor network traffic or web request and will be logged as an HTTP 502 error. 

Proxy and/or Firewall configuration may be configured to prevent Microsoft Dynamics CRM URLs from accessing server resources.
For a list of Required Accessible IP Address Ranges see this article 2728473

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

To view the Required URLs for Microsoft Dynamics CRM with Office 365, see the link below:

Office 365 URLs and IP address ranges

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

Article ID: 2655102 – Last Review: October 17, 2014 – Revision: 17.0


Applies to
  • CRM Online via Office 365 E Plans
  • Microsoft Dynamics CRM Online Professional Edition
  • Microsoft Dynamics CRM Online Professional Plus
kbmbsmigrate kbsurveynew KB2655102

Read More:
Internet accessible URLs required for connectivity to Microsoft Dynamics CRM Online

Page 1 of 74912345...102030...Last »

Recent Comments

    Archives

    Categories