SBS2011

SBS2011 – Changing default accepted domain breaking OWA


After recently installing an SBS2011 server for a customer I started setting up Exchange ActiveSync and IMAP on their iPad’s, Phones etc.
It soon became apparent that there was a problem. Although the devices would connect to the server they would come up with errors relating to not being able to download 0kb of a message, not being able to update folder lists and OWA would give you the following error if you tried to forward anything.

User host address: (Public IP Address)

User: (Username)

EX
Address: /o=First Organization/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Recipients/cn=(Username)

SMTP
Address: mailto:Username@Domain.Com
Username@Domain.Com

OWA
version: 14.1.218.13

Mailbox
server: server.domain.local

Exception

Exception
type: System.ArgumentException

Exception
message: imceaDomain must be a valid domain name.

Call
stack

Microsoft.Exchange.Data.Storage.InboundConversionOptions.CheckImceaDomain(String
imceaDomain)

Microsoft.Exchange.Data.Storage.InboundConversionOptions..ctor(String
imceaDomain)

Microsoft.Exchange.Clients.Owa.Core.Utilities.CreateInboundConversionOptions(UserContext
userContext)

Microsoft.Exchange.Clients.Owa.Core.ReplyForwardUtilities.CreateForwardItem(BodyFormat
bodyFormat, Item item, ReplyForwardFlags flags, UserContext userContext,
StoreObjectId parentFolderId)

Microsoft.Exchange.Clients.Owa.Premium.Controls.ItemForwardPreFormAction.Execute(OwaContext
owaContext, ApplicationElement& applicationElement, String& type,
String& state, String& action)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DoFinalDispatch(OwaContext
owaContext)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext
owaContext)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext
owaContext)

Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object
sender, EventArgs e)

System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously

The problem is that if you change the Default domain in Exchange the external accepted domain has spaces in the name, it is “Windows SBS External Domain. You can get around this by either changing the Default domain back to *domain*.local or if that isn’t an option do the following:

Open Exchange PowerShell and run the following cmdlet: Get-AcceptedDomain

We now wanted to ammend it to a name without spaces or special characters. Run the following commend let inserting your external domain name in at the end: Set-AcceptedDomain -Identity “Windows SBS External Domain” -Name “Domain.co.uk”

Then run the get cmdlet again: Get-AcceptedDomain

You should now see that it has updated. Close the PowerShell

Final thing you will need to is Restart IIS.

About these ads

11 comments

  1. Cris Hanna · July 12, 2011

    It appears you are trying to setup your ActiveSync and OWA connections using an IP address rather than a URL. If that’s the case it’s not supported…you must have a valid URL and it must match what you entered when you ran the “Setup Your Internet Address” Wizard.

  2. Cris Hanna · July 12, 2011

    My SBS 2011 as are most folks, setup using the default out of the box settings and it works just fine, once you run the wizard

    So you run the wizard, choose I have a domain name, choose I want to manage it myself, then comes the place to enter the domain name and you would enter domain.co.uk Now the wizard assumes that you are using the host name “remote” in your public dns to point to your public IP. If you are using mail or anything besides remote, you must click on the advanced link and change remote to whatever before completing the wizard

    so my question is: are you trying to reply from a different domain name other than the one you used in the original wizard?

  3. Cris Hanna · July 12, 2011

    Actually I think you mis-read the blog…”This is not an issue, since this accepted domain is not made default. However, we have been seeing an increasing number of cases coming in where customers are making this accepted domain default, and therefore run into the issue. In fact, you do not need to assign a default accepted domain unless you are interoperating with a non-Exchange email server within the same organization, and the vast majority of SBS customers run a pure Exchange environment (third-party spam filtering hosts are not considered to be in the same Exchange organization, think Lotus Notes instead).”

    So…out of the box, it’s just fine…if you changed it to make it the default accepted domain, it can be an issue.

  4. IT Support Guy in Brisbane · July 12, 2011

    Interesting Post.
    Looking forward to experimenting with it.

  5. jackalacka · July 12, 2011

    from one IT guy to another, thanks. This was my exact issue and your solution worked perfect.

  6. shemsargent · July 12, 2011

    Thanks a million! I had the same problem on SBS 2011. It looks like POP3 connector compares the client account address domain to the Accepted Domain’s Name field instead of its DomainName field. However, when you create an Accepted Domain in Exchange 2010, it populates the Name field with the same string as the Identity field.

    After reading your post, I couldn’t find a way to change this using EMC, so I tried your method using EPS. It worked! I can get my email via POP. Additionally, EMC now shows our domain name in the Name and Accepted Domain fields on the table.

    I really think that this is a problem with the POP3 connector using the wrong field. It should be using the Accepted Domain’s DomainName field, not the Name field. This would match the convention as displayed in EMC.

  7. Salim Lohiya · July 12, 2011

    Thanks, this saved me hours of headache

  8. Pingback: Owa | TagHall
  9. compare autoresponders · 23 Days Ago

    Thanks for the good writeup. It in fact was once a enjoyment account it.
    Look complicated to far introduced agreeable from you!
    By the way, how can we keep up a correspondence?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s