I work for a company that is technically "one" company located in two different cities. Both offices are so independant of each other. They actually act like two separate companies. They have separate IT infratructure, separate payroll and account and separate revenue. Which may be changing.
I have created a domain for one city last year and was told at that time, that the two cities would never need to have a common netowrk infrastructure. (I did state my case on why they should be and was informed that if the other city chose to create an AD they would be in their own separate forest and domain and manageit their own way). So with that being said, I created my domain name based on corp.city1.comapany.ca with the knowledge that the two offices will never need any sort of common IT infrastructure. I figured it was a nice designation of the single network.
Now that management in the other city has changed, the company is evolving and resources from both offices needing access to IT resources in both cities, the talk of deploying exchange corporate wide is now on the table. The other city will be creating a domain in order to deploy exchange and I've been tasked to lead this whole creation.
With that being said, what would be the best naming convention/deployment solution for the new network.
I would love to rename my domain to corp.company.ca and have two sites in one domain (one in each city), but that is not an option. I have thought about this and since I have never worked in a multi domained environement (and never deployed one) I would love some feedback.
Can the other domain be the same one I have created (corp.city2.company.ca) and still be part of the same forest?
I "think" that with the corp in the front and users logging into "corp", it will not know if it's city1, or city2. That's my concern.
Or should I rename mine to city1.company.ca and the new domain to city2.company.ca? Thius making people logging into their respective cities, which is their respective domain.