riegsa
asked on
Splitting company, AD / Mailflow
Hello.
We are asked to separate a department of the company because it's going to be an independent unit (new company). This means seperate AD / networks, but common e-mail addresses. The company have a single domain today and don't want to change e-mail adresses.
Any suggestions how to achieve this?
I have thought of a possible solution with one front end Exchange to handle webmail, etc. And two other servers for mailbox storage, one for each network. And I intend to let the main company keep it's original AD domain (company.com), and establish a new iAD domain for the new company (e.g. company.net, separate forest). Is this a reasonable approach?
Suggestions / comments appreciated.
We are asked to separate a department of the company because it's going to be an independent unit (new company). This means seperate AD / networks, but common e-mail addresses. The company have a single domain today and don't want to change e-mail adresses.
Any suggestions how to achieve this?
I have thought of a possible solution with one front end Exchange to handle webmail, etc. And two other servers for mailbox storage, one for each network. And I intend to let the main company keep it's original AD domain (company.com), and establish a new iAD domain for the new company (e.g. company.net, separate forest). Is this a reasonable approach?
Suggestions / comments appreciated.
The only reason to have a separate internal domain is to have different security password policies. Creating different internal domains only makes your internal setup more complicated, DNS more complicated and exchange more difficult to run and configure. You would also need to have additional Active directory servers available for the stub/sub domain.
The more reasonable solution( and less complicated) would be to create a different OU for them. You can then apply GPOs directly to the domain. You can do the same for their computers and servers.
If you need more exchange space or additional servers, i would recommend clustering them to obtain higher availablity, responsiveness and capacity.
To be clear, its highly recommended that you do not create a new stub/sub domain for this company.
The more reasonable solution( and less complicated) would be to create a different OU for them. You can then apply GPOs directly to the domain. You can do the same for their computers and servers.
If you need more exchange space or additional servers, i would recommend clustering them to obtain higher availablity, responsiveness and capacity.
To be clear, its highly recommended that you do not create a new stub/sub domain for this company.
I have also tought about Icetoads solution and that would of course be the easiest and most efficient solution. But there are a few legal and public policies so no user "traffic" is allowed between the two networks.
Can this be implemented and still full security be applied?
And what if one of the companies later should be fully separated (e.g. name change); can one OU be converted to an independent domain in a simple way?
Can this be implemented and still full security be applied?
And what if one of the companies later should be fully separated (e.g. name change); can one OU be converted to an independent domain in a simple way?
Sounds like it would be easier to have completely separate forests with separate internal and external IPs. Thats the only way to be sure there is no intermingling.
You would also want routers/firewalls between the server farms to ensure no traffic is passed from end users of one domain to another. If its a small company, you can run DNS/exchange/AD on the same server or use SBS( its a PIA though ). I highly recommend a second server OR use one or two phsycial servers with VMWare and run all the different servers as instances on those two physical boxes. Gives you high availablity, flexibility and mobility.
You would also want completely separate email servers.
You would also want routers/firewalls between the server farms to ensure no traffic is passed from end users of one domain to another. If its a small company, you can run DNS/exchange/AD on the same server or use SBS( its a PIA though ). I highly recommend a second server OR use one or two phsycial servers with VMWare and run all the different servers as instances on those two physical boxes. Gives you high availablity, flexibility and mobility.
You would also want completely separate email servers.
But can the companies still have the same "@company.com" in their e-mail addresses? Or do we have to setup some sort of forwarding....?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your assistance :-)
Yes, I would do as you suggested. Split the Business Unit out to a new domain (either I child domain or new forest with trust permissions if necessary). That way the child domain / other domain has access to the Exchange System / normal @domain.com space and can easily be permanently split if the company goes separate ways.