The company I work for has decided to merge with its Sister Company on the lower floor. While we share the same room to house our independent servers, both companies have separate physical networks. Each with their own separate File Servers & SQL servers. Allowing Company "A" employees to log into Server "A" (only) and access SQL server "A" (only). Company "B has a similar setup (Server "B" & SQL Server "B" can only be accessed by Company "B" employees
Because of the merger, we would like to be able to allow our employees to use one login to access both networks since there is data that some people need to have to access to is from both domains.
Some Current Configuration items to consider:
• Company A is running MS Server 2000 (File) & SQL Server 2000 on Win Server 2000
• Company B is running MS Server 2003 (File) & SQL Server 2005 on Win Server 2003
• Each company has its own separate Internet connection, router, switches, printers, etc
Where do we start & what problems should we be aware of?? I'm not comfortable with the approach the Admin for Company B want to take to do this lovely task. His approach has always been "Do it cheap and simple" (piece it together) & pay the price later for poor design. I want to make sure we do this right the 1st time so we don't create problems for ourselves.
Any advice is greatly appreciated!!
January 16, 2009 10:46 PM
February 2, 2012 8:27 AM