pramod1
asked on
exhange 2007, exchange 2013
We have a resource forest set up.
We have resource domain, where all resource, such as mailboxes, file/print servers are kept and there is user domain, where only user accounts are kept.
User account in resource domain is disabled. Mailbox is linked to user account in the user domain. This is done by LinkedMasterAccount attribute in the user account.
we have 1 hub and client access server ( which is also DC) and 1 mailbox server sitting on xxx. lan domain which is in resource domain.
We have another DC which is xxx.com which have all enabled accounts.
We have 2300 users and divded into 16 storage groups
We are planning to upgrade to exchange 2013
Our Action Plan
A) We want to keep the same resource setup.
B) Build separate windows server 2012 and make it DC in same resource forest set up
C) Replicate DC from exchange 2007 ( CAS and Hub Server) to new windows server 2012 DC as disabled AD accounts.
D) Install exchange 2013 on windows server 2012 and build DAG involving 3 mailbox servers
E) Move mailbox from exchange 2007 to 2013
Please add to my plan if I am missing something
We have resource domain, where all resource, such as mailboxes, file/print servers are kept and there is user domain, where only user accounts are kept.
User account in resource domain is disabled. Mailbox is linked to user account in the user domain. This is done by LinkedMasterAccount attribute in the user account.
we have 1 hub and client access server ( which is also DC) and 1 mailbox server sitting on xxx. lan domain which is in resource domain.
We have another DC which is xxx.com which have all enabled accounts.
We have 2300 users and divded into 16 storage groups
We are planning to upgrade to exchange 2013
Our Action Plan
A) We want to keep the same resource setup.
B) Build separate windows server 2012 and make it DC in same resource forest set up
C) Replicate DC from exchange 2007 ( CAS and Hub Server) to new windows server 2012 DC as disabled AD accounts.
D) Install exchange 2013 on windows server 2012 and build DAG involving 3 mailbox servers
E) Move mailbox from exchange 2007 to 2013
Please add to my plan if I am missing something
Looks about right. Just wondering if there is a reason not to go to Exchange 2016? It does have better security features and controls.
ASKER
my company decided, any how 2 questions
1) what methods should I use to replicate DC which has disabled ad accounts to new DC.
2) any articles in creating legacy namespaces, or with EWS, OWA to work in middle of transition
1) what methods should I use to replicate DC which has disabled ad accounts to new DC.
2) any articles in creating legacy namespaces, or with EWS, OWA to work in middle of transition
Hello pramod1,
Your design will work, but if possible (resources available) consider:
- Do not co-locate your DC with Exchange. This separation can be easily justified as far as you have +2000 mailboxes. Additionally, if you are implementing the DAG that you specified in 'E', it will be mandatory.
- If possible, use Windows Server 2012 R2 (Maybe you already mean R2 explicitly, but just in case).
- You can also go with Exchange 2016 as Joshua says, it will be better from multiple perspectives. However, in this scenario as far as you cannot transition directly from 2007 to 2016, you will need to stop at 2013 (or 2010) and then upgrade to 2016. The latter means that you will complete two transitions (AKA migrations).
In general terms your plan sounds good, of course... as you know there are many small details involved in the process.
Note: On step C, be aware that if your accounts are disabled, and you replicate them to a different DC, you will continue exactly with the same [disabled] accounts. It does not require any additional task.
Your design will work, but if possible (resources available) consider:
- Do not co-locate your DC with Exchange. This separation can be easily justified as far as you have +2000 mailboxes. Additionally, if you are implementing the DAG that you specified in 'E', it will be mandatory.
- If possible, use Windows Server 2012 R2 (Maybe you already mean R2 explicitly, but just in case).
- You can also go with Exchange 2016 as Joshua says, it will be better from multiple perspectives. However, in this scenario as far as you cannot transition directly from 2007 to 2016, you will need to stop at 2013 (or 2010) and then upgrade to 2016. The latter means that you will complete two transitions (AKA migrations).
In general terms your plan sounds good, of course... as you know there are many small details involved in the process.
Note: On step C, be aware that if your accounts are disabled, and you replicate them to a different DC, you will continue exactly with the same [disabled] accounts. It does not require any additional task.
ASKER
thanks, but any methods I should use to replicate from disabled DC to new DC,
ASKER
what do you mean by do not co-locate? I didn't get it very clear
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I mean do not install together your ADDS Role (Domain Controller) with your Exchange roles.
If you want a DAG, you cannot combine a Mailbox with a DC.
Independently of using a DAG or not, if possible... consider to use a separate server as a DC.
If you want a DAG, you cannot combine a Mailbox with a DC.
Independently of using a DAG or not, if possible... consider to use a separate server as a DC.
ASKER
If I set up nee DC how will it replicate from old dc
When the DCPROMO process completes it ensures that all the critical data is replicated. After that, automatic replication objects are created in Active Directory to maintain the replication in two ways between the new and old servers.