How to make Exchange 2010 work in a local network throughout Russia, without Internet access?

C

civdef2015-07-16 08:55:30

Microsoft Exchange

civdef, 2015-07-16 08:55:30

Preamble. Given: a large organization with offices throughout Russia will have a distributed star-type structure. I specify we are in the same AD forest, we have a second-level domain in the regions of the third. That's actually the question:
1. In the main office of a DAG of several servers, through which settings (where to poke), to make sure that the servers of the head office are the main ones, and the regions are secondary (where is it in the settings)?
2. And what about the address book? How to transfer the rights to the book so that there is one global list of addresses (of all offices in Russia), but we did our part, and the regions in their OU changed theirs, according to the staffing structure

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

S

Sergey Kovalev, 2015-07-16
@civdef

You are coming from the wrong side. Unnatural and counterproductive.
You need to start with MCITP : Enterprise Messaging Administrator 2010
Designing Exchange integration within the current infrastructure
Planning & deploying mailbox servers
Deploying Client Access Services
Planning & deploying Message Transport in Exchange 2010
Backup, Recovery and maintaining high availability
regarding critical and necessary services on the Toaster is not entirely logical.
You need specialists who will solve this problem on the spot and in accordance with all the nuances.
Demand training from the management, otherwise it will be bad.

C

civdef, 2015-07-16
@civdef

Moving away from general words, to the point. I went to lunch and got enlightenment =)
1. Create a connector rule to work with another exchange server. Each server has its own connector. In the same forest, for a third-level domain.
2. And for the delegation of authority, everything is also simple. In the ADSI Configuration - Services - Microsoft Exchange - Organization Name - CN=Address Lists Containers branch, assign handles responsible for creating child objects, in parallel create the desired ou.
I went to drive in a test environment and read books. Thanks for participating.