OWA doesn't work for mailboxes moved to child domain exchange member server and other issues

Posted on 2007-08-01
Last Modified: 2012-08-13

I've got the following setup:

There is an exchange server called parentserver in and a childserver in

I can move mailboxes from the parentserver to the childserver fine

However I have three outstanding issues:

1. OWA (which is on the parentserver) doesn't work for mailboxes moved to childserver. Should it?
2. POP3 (the service on the parentserver) doesn't work for mailboxes moved to childserver. Again, should it?
3. Moving mailboxes from childserver to parentserver gives an error in teh event log, and I then have to manuall reconfigure the users outlook to connect to parentserver (it doesn't automatically change it's settings). The error in the event log is "Failed to create the mailbox" error 0x50c, event id 1205

Any help or thoughts would be greatly appreciated.
Question by:D_Hartup
    LVL 8

    Accepted Solution

    Need to no more about your setup are you using Front End servers?
    LVL 6

    Author Comment

    No, just the servers as above. I've been looking up other solutions, and I can see that OWA requires front end server to connect to 2 back end servers. So please ignore the OWA part of this problem.

    The bit I'm most worried about is the pop3 access... I really want to get the mailboxes moved without having to reconfigure the pop3 users workstations.
    LVL 22

    Assisted Solution

    Yes, a users hitting a FE server in the parent domain should be able to access thier mbx in the child domain

    the FE server will communicate via http from the FE -> BE server (can use ipsec to secure)

    the user will need to logon domain\user or user@upnsuffix

    LVL 31

    Assisted Solution

    Did the moved users also get new email addresses in the new domain?  Each OWA VDir can only access one SMTP domain.  If you look at the properties of the existing VDir in ESM, you will see a property named Exchange Path.  Only those users with an SMTP address (it doesn't have to be their Primary SMTP address) in that domain can access OWA through that VDir.  So, you will need to make sure that all your users have an SMTP address (like I say, I doesn't have to be the Primary SMTP address) in that domain.  Or, create a second VDir to cover the new SMTP domain.

    Expert Comment

    This resolved an issue for me with connecting Entourage users to Exchange 2007.  Users in a child domain with a different SMTP domain were able to connect to the server and authenticate, but the folders never showed up.  I added a secondary SMTP address for these users and it started working.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
    "Migrate" an SMTP relay receive connector to a new server using info from an old server.
    In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
    how to add IIS SMTP to handle application/Scanner relays into office 365.

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    11 Experts available now in Live!

    Get 1:1 Help Now