Hi Guys .... We have the luxury of building a new Windows Server 2003 network from scratch with no legacy issues to get in our way. Of course we want to do this correctly right from the get-go so I'm looking for a little (or a lot) of suggestions on how we should roll this out.
We are going to implement a network model where an independent organization will provide centralized IT services to a number of related but seperate companies. Although we'd like to have complete administration control of the "enterprise" we can't have any of the companies able to access or even see the existence of the other companies involved. All of the related companies currently have their own internet domain names and POP3 mail servers. We'd also like to eventually migrate them to Exchange but with their own identity so that there is no hint of their participation in the multi-company IT structure.
All companies have to be setup with the minimum of dependencies since they may be spun off or sold at any point in time.
How's that for a start? I'm sure the nuts & bolts available can do the job but if anyone else has been down this road I would certainly appreciate your input. Nobody likes to reinvent the wheel.
Thanks in advance for your help on this. Regards - Jamie G.