How to edit your contact info in OWA

I’ve had a couple of users, in the environment I host for friends & family, ask me how to change their contact info in the GAL. After doing some searching I was unable to find a good article on this topic, which surprised me. I’m sure after posting this I will get comments to ones I didn’t find, but in searching on “edit contact info in owa exchange” and several other variants of this I didn’t find a blog post or article on this, at least on the first two pages of hits.

By default in Exchange 2010 and higher users have the ability to edit their contact. This can be disabled, I did find a good article by Michel de Rooij on this topic:

The easiest solution is to tell users to goto and once they login to OWA they will be taken to the edit contact info page in Exchange 2010 or 2013.

To get to this page from OWA and its menus is pretty easy, if you don’t know where to look. Of course if you know the URL, which I didn’t since I rarely use OWA, or don’t do end user support, you could setup a URL to redirect to the correct URL.

For Exchange 2010

1)      Login into OWA
2)      In the upper right, under your name, choose Options\See All Options…EX12-See-All

3)      Then click Edit to the lower right of the “Account Information…” area, which will show your name, e-mail, contact numbers
4)      Click Contact Location to change your address
5)      Then click Save

For Exchange 2013

1)      In OWA, in the upper right hand corner click the little gear and choose Options
2)      On the options\account page in the middle at the bottom click Edit information

Posted in Exchange, Technical | Tagged | Leave a comment

Exchange 2010 SP3 UR6 and 2013 CU5 released

Few days late on this, been really busy with projects and personal life this year!

Here’s a quick summary and I’ll start tracking know issues at some point here too.

Exchange 2010 SP3 UR6 – Download | KB2936871 Info
Exchange 2013 CU5 – EHLO Blog Post | Download | KB2936880 (CU5 includes SP1 updates)

Blog post about 2013 CU5 I recommend reading:

Exchange 2010 SP3 UR6 fixes (from

  • 2960652 Organizer name and meeting status field can be changed by EAS clients in an Exchange Server 2010 environment
  • 2957762 “A folder with same name already exists” error when you rename an Outlook folder in an Exchange Server 2010 environment
  • 2952799 Event ID 2084 occurs and Exchange server loses connection to the domain controllers in an Exchange Server 2010 environment
  • 2934091 Event ID 1000 and 7031 when users cannot connect to mailboxes in an Exchange Server 2010 environment
  • 2932402 Cannot move a mailbox after you install Exchange Server 2010 SP3 RU3 (KB2891587)
  • 2931842 EWS cannot identify the attachment in an Exchange Server 2010 environment
  • 2928703 Retention policy is applied unexpectedly to a folder when Outlook rule moves a copy in Exchange Server 2010
  • 2927265 Get-Message cmdlet does not respect the defined write scope in Exchange Server 2010
  • 2925273 Folder views are not updated when you arrange by categories in Outlook after you apply Exchange Server 2010 Service Pack 3 Update Rollup 3 or Update Rollup 4
  • 2924592 Exchange RPC Client Access service freezes when you open an attached file in Outlook Online mode in Exchange Server 2010
  • 2923865 Cannot connect to Exchange Server 2010 when the RPC Client Access service crashes

Exchange 2013 CU5 fixes (from

  • 2963590 Message routing latency if IPv6 is enabled in Exchange Server 2013
  • 2963566 Outlook Web App accessibility improvement for UI appearance in Exchange Server 2013
  • 2962439 You cannot sync contacts or tasks in Microsoft CRM client for Outlook in an Exchange Server 2013 environment
  • 2962435 CRM synchronization fails if the time zone name of a meeting is not set in an Exchange Server 2013 environment
  • 2962434 Slow performance in Outlook Web App when Lync is integrated with Exchange Server 2013
  • 2958430 “Some or all Identity references could not be translated” error when you manage DAG in Exchange Server 2013 SP1 in a disjoint namespace domain
  • 2957592 MIME is disabled in Outlook Web App when you press Tab to move the focus in an email message in Exchange Server 2013
  • 2942609 Exchange ActiveSync proxy does not work from Exchange Server 2013 to Exchange Server 2007
  • 2941221 EWS integration for Lync works incorrectly in an Exchange Server 2013 and 2007 coexistence environment
  • 2926742 Plain-text message body is cleared when writing in Outlook Web App by using Internet Explorer 8 in Exchange Server 2013
  • 2926308 Sender’s email address is broken after importing a PST file into an Exchange Server 2013 mailbox
  • 2925559 Users always get the FBA page when they access OWA or ECP in Exchange Server 2013
  • 2924519 “SyncHealth\Hub” folder is created unexpectedly after installing Cumulative Update 2 for Exchange Server 2013
  • 2916113 Cannot open .tif files from email messages by using Windows-based applications in an Exchange Server 2013 environment
  • 2592398 Email messages in the Sent Items folder have the same PR_INTERNET_MESSAGE_ID property in an Exchange Server 2010 environment
Posted in Exchange, Microsoft, Technical | Tagged , | Leave a comment

DMARC! broke your mailing lists!

4/25 Update: Renamed post to “DMARC” instead of Yahoo now that Aol has their DMARC policy set to reject:

After spending sometime the last couple of days checking and rechecking my SPF settings I figured out today it was a change Yahoo made that broke message delivery to external recipients. Yahoo made this change “over the weekend” per some news articles, I first noticed NDRs dues to this on Monday 4/7/2014

The issue is that Yahoo changed their DMARC, which is made up for SPF and/or DKIM settings/policies, to “p=reject” which tells receiving email servers to reject emails from addresses that don’t originate from its servers. So if a Yahoo users sends an e-mail to and it contains recipients at @yahoo, @gmail, @msn, @hotmail,, @comcast, and many other email providers that check the original sending severs (Yahoo in the case) policy they will reject the mail. This is because the sending server of the e-mail is and not

Yahoo did this to help reduce spam that is being sent from accounts on their servers to mailing list that contains external recipients. But they basically “broke every mailing list in the world” to quote some of the many news articles I found today about this issue.

At this time there is no work around for Exchange that I know of. The suggestion is to tell users to stop using yahoo to send e-mail to mailing list. So this won’t work since as email admins we have no control over what users do externally.

I’m hoping Yahoo fixes this policy setting ASAP! I will update this post as I learn more!

Errors users\DL owners will see: gave this error:
Message not accepted for policy reasons. See # #SMTP# gave this error:
oFxW1n00k0D7utr0DFxXU1 Message rejected due to DMARC. Please see gave this error:
(BAY0-MC3-F11) Unfortunately, messages from ( on behalf of ( could not be delivered due to domain owner policy restrictions.

The only workarounds that I’m aware of at this time is to use an EDGE address rewrite rule to have any messages sent to a DL to have their From address to be the DLs, instead of the sending users. The other is to enable moderation on your DLs that have external recipients and for any coming from or (currently, but more will be added in the future I’m sure) resent them manually from the DL or a mailbox.

I’m hoping to hear back from some of my peers soon on better workarounds.

Good blog post on DMARC and why the rejection is happening and why this is a good thing, in general:

News articles about this issue:

Posted in Exchange, Microsoft, Technical, Uncategorized | 4 Comments

Known Issues with Exchange 2013 SP1

This is an early draft of issues I’ve heard of so far.

Last updated: 4/14/14

  1. Important: 3/4 Transport server doesn’t start after upgrade and some products that use Transport Agents don’t work
  2. Important: When building a DAG cmdlet will fail if NetBIOS and AD short domain name don’t match – 4/14/2014
    • From this FB post:
      • In Exchange 2013 SP1, when building a DAG, you will see issues with Set-DAG and Add/Remove-DatabaseAvailabilityGroupServer cmdlets if your Domain NETBIOS name is not equal your AD short name, eg NETBIOS name is “FOO”, and your domain name is “bar.contoso.local”. Both cmdlets will terminate with a Dr Watson. The DAG will still build fine, except for the FSW resource – there will be no FSW assigned to the DAG. We already have a FIU you can request through PSS, or create the FSW manually as a temporary workaround.
    • Work around: Manually create the FSW, contact PSS for fix, wait for public fix
  3. Minor: “Ceres” Search Foundation install error
    • From Paul Robichaux’s blog post
      • “When deploying the RTM build of Exchange 2013 SP1, I found that one of my servers was throwing an error I hadn’t seen before during installation”
  4. Minor: Default apps in Outlook Web App do not work if Exchangeis installed in Window Server 2012R2
    • From KB2938292 posted on 3/19/2014
      • “When you install Microsoft Exchange Server 2013 on a Window Server 2012 R2-based computer, default”
      • This issue will be fixed in Exchange Server 2013 Cumulative Update 5
    • Work around: Edit the web.config and add the following line to the “<appSettings> section:
      UseLegacyRequestUrlGeneration” value=”true”/>

      • 3/25: A peer of mine is working on a blog post with more details and I will post a link to it when he post it.

Related items

  1. 3/4 Outlook2013SP1 Issue: Fails to connect to Exchange in a multi-forest environment

Related Posts

Posted in Exchange, Microsoft, Technical | Tagged , , | 6 Comments

Quick post: Exchange 2013 SP1, Exchange 2010 SP3 RU5, & 2007 SP3 RU13 was just released

It’s been awhile since I’ve posted, been busy on projects, but wanted to at least let everyone know that Exchange 2013 SP1 (aka CU4), 2010 SP3 RU5, 2007 SP3 RU13, & Office 2013 Sp1 was just released.

EHLO Post on the Exchange 2013 SP1 update 

See Tony Redmond’s blog post here for more details for now:

Downloads: Exchange 2013 SP1 | Exchange 2010 SP3 RU5 | Exchange 2007 SP3 RU13 | Office 2013 SP1

I will also create a blog post for 2013 & 2010 to talk about what’s in each of these updates and to track ‘known’ issues with them.

Big new feature in Exchange 2013 SP1, which requires Outlook 2013 SP1, is MAPI/HTTP. More to come in a later post, but for now you can view a video of Joe Warren, Exchange developer, on it here:

Posted in Exchange, Technical | Tagged , | Leave a comment

Got an idea for something you would like to see in Exchange?

If so go here: and you can post your idea or vote on it if someone else already has one similar.

Tony Redmond blogged about this site also here: He is planning on having a Q&A session with Perry Clarke, Microsoft CVP for Exchange, on 12/13. For more on that see Tony’s post here:

So we, the Exchange MVPs & others, have started to populate this idea list and could use your help on voting (up or down) and posting new ideas. We hope this site will be come a great place for sharing and voting on ideas and that the Microsoft Exchange team will start to look at it for ideas on what to do or fix in future releases.

Posted in Uncategorized | Tagged , | Leave a comment

New Exchange security updates (MS13-105) released as RUs for 2007, 2010, and SUs for 2013

Today Microsoft is releasing security updates for Exchange 2007 SP3, 2010 SP2, 2010 SP3, 21013 CU2, & 2013 CU3 for MS13-105. For Exchange 2007 SP3 & 2010 SP2 these are included in the latest Rollup Updates. For Exchange 2013 Microsoft is following the updates plan they documented in the EHLO blog post “Servicing Exchange 2013” and will provide a Security Update (SU) package to be installed on top of CU2 or CU3.

So the new RUs for 2007 will be 2007 SP3 RU12 (KB2903911 | Download), for 2010 SP2 RU8 (KB2903903 | Download), and 2010 SP3 RU4 (KB2905616 | Download). For Exchange 2013 this update will be installed on top of CU2 or CU3, 2013 CU2 (KB2880833 | Download) and 2013 CU3 (KB2880833 | Download). An update for Exchange 2013 CU1 is NOT being provided, per the Microsoft policy of only support the current version (CU3) and one version back (CU2).

  • To summarize it another way:
      1. 2007 SP3 RU12 = 2007 SP3 RU11 + new security fixes
      2. 2010 SP2 RU8 = 2010 SP2 RU7 + new security fixes
      3. 2010 SP3 RU4 = 2010 SP3 RU3 + new security fixes
      4. Exchange 2013 CU2 will get a SU package containing the new required security fixes and the previously released security fix so you only need to apply one SU if you never applied the original one
      5. Exchange 2013 CU3 will get a SU package containing only the new required security fixes since CU3 was released
  • Issues addressed
    1. Updates Oracle OutsideIn libraries (previously known as Stellant) to a non-vulnerable version
    2. Removes a XSS attack vector in OWA logon
    3. Removes a deserialization attack vector by setting EnableViewStateMac in OWA

Mostly from the EHLO Blog post: Released: Microsoft Security Bulletin MS13-105 for Exchange

For Exchange Server 2007 & 2010, the update is being delivered via an NEW Update Rollup. UR3 will ONLY contain this security fix for MS13-105 and the other changes that were in UR2.

For Exchange Server 2013, this security updates is being delivered as discrete update and contains no other changes.  Security updates for 2013 are cumulative in nature based upon a given Cumulative Update.  This means customers who are running CU2 who have not deployed MS13-061 can move straight to the Cu3 update because it will contain both updates.  Customers who are already running MS13-061 on CU2 may install MS13-105 on top of MS13-061 without removing the previous release.  If MS13-061 was previously deployed, Add/Remove Programs will indicate that both updates are installed.  If MS13-061 was not previously deployed, only MS13-105 will appear in Add/Remove Programs.

All of these fixes will be available immediately on the download center and through Windows Update per our standard security release practice.  Note that we will not be releasing Exchange Server 2010 Service Pack 3 Update Rollup 3 to Windows Update due to the closeness of these releases and to avoid the supersedence confusion created with Update Rollups that are labeled as security releases vs. those that are not.  Windows Update will indicate that Update Rollup 4 supersedes Update Rollup 2 avoiding the problem of Windows Update offering Update Rollup 3 to customers who have Update Rollup 4 installed already.

Posted in Exchange, Technical | Tagged , , | Leave a comment