• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 778
  • Last Modified:

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

Hi,

I've got the following setup:

parentdomain.com
 - childdomain.parentdomain.com

There is an exchange server called parentserver in parentdomain.com and a childserver in childdomain.parentdomain.com

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.
0
D_Hartup
Asked:
D_Hartup
3 Solutions
 
garyraffertyCommented:
Need to no more about your setup are you using Front End servers?
0
 
D_HartupAuthor Commented:
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.
0
 
ATIGCommented:
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


0
 
LeeDerbyshireCommented:
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.
0
 
iacinfotechCommented:
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.
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now