0
1
I have a question that may be really easy to answer.
Our company got a new server a while ago. This server acts as our DNS, SQL, Web, NAS, and Active Directory. We are moving to a new office and I thought since a bunch of things are changing we may as well take the old server and make it our SQL/Web server so it is separate from everything else on the new server.
I have the old server booted up (not plugged into the network), and I am wondering if there would be any implications of me connecting this to the network. Would the old and new server so called 'fight' for priority on the network? The old server has all of the user accounts, shares, and everything else?
The new server is running Windows Server 2012, and the old one is running Windows Server 2003.
Additionally, is there any other heads up you can recommend for doing this swap?
Any help is greatly appreciated.
1Have you disabled all network services (DNS, AD, possibly others, ...) on the old server, leaving only SQL Server and a web server? For example two AD servers might not play terribly well if they don't know about each other. – a CVn – 2015-08-26T14:43:38.327
Sorry, I am not too familiar with how to do this. So no, I have not. How would I go about disabling all of the features? Or would a fresh install of Windows Server be easier? – Chase Ernst – 2015-08-26T14:45:19.467
1Just do a fresh install, you'll save yourself lots of grief. – Ƭᴇcʜιᴇ007 – 2015-08-26T17:27:44.363
I'm reformatting as we speak! – Chase Ernst – 2015-08-26T21:53:32.600
@ChaseErnst In that case, I suggest that you delete your question, so people don't spend time answering something that won't help you and might not help others very much. – a CVn – 2015-08-27T07:34:12.650
I cannot, because there is an answer attached. – Chase Ernst – 2015-08-27T14:15:35.503