This is the first time we have deployed a multi site Exchange organization. Here is the scenario and I am wondering if it is the correct one or if I should have done it a different way.
We have a VPN setup between our corporate location and a satellite campus. The satellite campus has it's own namespace and is a tree in our forest. We have Exchange 2013 SP1 setup at the corp location. We installed two Exchange 2013 SP1 servers at the satellite location in that domain in the same Exchange organization. I was able to create a few linked users mailboxes (newly acquired and in process of user migration into our forest) and mail delivers between the two without issue. But lately every new user will not receive email and they will be in the queue. Does not matter if the email is from a corp user or a local user on the same mailbox server.
We decided to do this because we want them to have all of their Exchange resources, email, CAS services and UM local to them, but they are still part of our system. I am having a hard time finding why this is happening. I also noticed that the emails sent from one satellite user to another is actually going through the corp hub transport server and not their local. Sites and Services is setup with the correct subnets for each site. I have verified the send and receive connectors.
Is this scenario the best way to configure our organization or should we simply have created a second organization of their own and tried to share calendars, etc between the two? All of our other services are centrally located so it only made sense that this should also work but before going live I wanted to see if this was the optimal way. This is not a high availability or site resiliency plan. No DAGs are used. We are just one company with two separate very remote disjoint locations and even though we have a small VPN for services we would like to keep as much as possible local to that site.
I have not been able to find information on this scenario. Everything seems to point to SR/HA scenarios. Any advice would be greatly appreciated.
We have a VPN setup between our corporate location and a satellite campus. The satellite campus has it's own namespace and is a tree in our forest. We have Exchange 2013 SP1 setup at the corp location. We installed two Exchange 2013 SP1 servers at the satellite location in that domain in the same Exchange organization. I was able to create a few linked users mailboxes (newly acquired and in process of user migration into our forest) and mail delivers between the two without issue. But lately every new user will not receive email and they will be in the queue. Does not matter if the email is from a corp user or a local user on the same mailbox server.
We decided to do this because we want them to have all of their Exchange resources, email, CAS services and UM local to them, but they are still part of our system. I am having a hard time finding why this is happening. I also noticed that the emails sent from one satellite user to another is actually going through the corp hub transport server and not their local. Sites and Services is setup with the correct subnets for each site. I have verified the send and receive connectors.
Is this scenario the best way to configure our organization or should we simply have created a second organization of their own and tried to share calendars, etc between the two? All of our other services are centrally located so it only made sense that this should also work but before going live I wanted to see if this was the optimal way. This is not a high availability or site resiliency plan. No DAGs are used. We are just one company with two separate very remote disjoint locations and even though we have a small VPN for services we would like to keep as much as possible local to that site.
I have not been able to find information on this scenario. Everything seems to point to SR/HA scenarios. Any advice would be greatly appreciated.