QuazzieM
asked on
AD DS Redesign Project
Hey everyone,
Need a bit of help regarding this project thats been thrown on me today :S
Basically our company was bought out by another, I setup a 2way forest trust between the companies ADDS but they now want me to look at redesigning the whole ADDS and migrate both forest to the new one.
Reasons being:-
Company A's AD OU/GPO structure is all types of messed up.. Really haven't seen anything like in my life and I die a little on the inside when I have do anything in it.
Also the DNS Namespace is a split-DNS config, which the powers the be want rectified (based off a security audit they had) and it also doesn't represent the business name anymore,
Company B is configured with an '.internal' DNS Namespace and based on the fact that the whole company will be migrating to the Office 365 project I'm also working on and the fact that my ADDS is full of dead DC metadata that wasn't cleanup up.
Also, with the changes in SSL certificates in regards to the TLD I think I'm going to have a hard time in replacing the SAN SSL certificate in 12mths time when it expires and I'm not sure what it will involve to fix.
Therefore based on all that it's been decided that its time for a fresh design for the our ADDS.
Based on the business requirements, I can't really think of any reason that we need to use a single forest/multi domain design. We are expanding globally, however everything will be administer by me and all the infrastructure is located at one place.
Hence, I believe that going a single forest / single domain will be the best course of the redesign. I will then look to create separate AD sites for each of global offices and set them up with a DC/GC at each branch office.
And the security/configuration requirements will be constructed using OU's in a 'Mixed Hybrid' design
I have a fairly good understanding of the OU and GPO design that I plan to use, but I still have a few question regarding the DNS namespace design and requirements for the Office 365 and other DNS design.
I've purchased the 'bfm.com.au' which we have registered and the DNS delegation is controlled by the company that we use for all the other domains we administer (which I can edit/administer)
Now to to avoid the TLD issues again and taking in consideration the Office 365 project, should I therefore create the new root forest/domain name as 'internal.bfm.com.au' or can I use 'bfm.com.au'. Please note that we don't have any dns entries configured for this domain.
Thanks for all you help..
Need a bit of help regarding this project thats been thrown on me today :S
Basically our company was bought out by another, I setup a 2way forest trust between the companies ADDS but they now want me to look at redesigning the whole ADDS and migrate both forest to the new one.
Reasons being:-
Company A's AD OU/GPO structure is all types of messed up.. Really haven't seen anything like in my life and I die a little on the inside when I have do anything in it.
Also the DNS Namespace is a split-DNS config, which the powers the be want rectified (based off a security audit they had) and it also doesn't represent the business name anymore,
Company B is configured with an '.internal' DNS Namespace and based on the fact that the whole company will be migrating to the Office 365 project I'm also working on and the fact that my ADDS is full of dead DC metadata that wasn't cleanup up.
Also, with the changes in SSL certificates in regards to the TLD I think I'm going to have a hard time in replacing the SAN SSL certificate in 12mths time when it expires and I'm not sure what it will involve to fix.
Therefore based on all that it's been decided that its time for a fresh design for the our ADDS.
Based on the business requirements, I can't really think of any reason that we need to use a single forest/multi domain design. We are expanding globally, however everything will be administer by me and all the infrastructure is located at one place.
Hence, I believe that going a single forest / single domain will be the best course of the redesign. I will then look to create separate AD sites for each of global offices and set them up with a DC/GC at each branch office.
And the security/configuration requirements will be constructed using OU's in a 'Mixed Hybrid' design
I have a fairly good understanding of the OU and GPO design that I plan to use, but I still have a few question regarding the DNS namespace design and requirements for the Office 365 and other DNS design.
I've purchased the 'bfm.com.au' which we have registered and the DNS delegation is controlled by the company that we use for all the other domains we administer (which I can edit/administer)
Now to to avoid the TLD issues again and taking in consideration the Office 365 project, should I therefore create the new root forest/domain name as 'internal.bfm.com.au' or can I use 'bfm.com.au'. Please note that we don't have any dns entries configured for this domain.
Thanks for all you help..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.