Solved

Server 2008 name change

Posted on 2014-02-25
3
438 Views
Last Modified: 2014-03-03
We are swapping hardware on a server 2008 R2 server with SQL 2005 64bit SP3.

The current production server is working  "server1", we added a new server "server2" to the LAN but have not joined it to the domain yet.
 
We have installed SQL 2005 64bit SP3 on Server2 and will set up the SQL instance and move the database from Server1 to server2. Once done we will shut down Server1 and change the IP address of Server2 to Server1's IP address and then rename Server 2 to Server1 and join the domain.

I think this will work but not 100%,

When i join the re-IP'ed, re-named and rebooted Serve1 to the existing domain will there be a problem with the DC? Do i have to drop the server name from the DC before joining the new Server1 server?

How will that impact the SQL instance if at all?
If i have to drop the server1 from the DC first how does that impact mapped drives to the Server1 from the existing workstations?

Note: the DC is a SBS2008 server.

Thanks
0
Comment
Question by:mspencer100
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 58

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 167 total points
ID: 39887500
Overall the idea should work, but SQL 2005 was a little funny about machine renames, so honestly if you can retool your process to avoid that, I would.

You will have to remove the old machine account from Active Directory to join a new machine using the same name. Otherwise the attempt to join will fail.

Joining the domain after installing SQL shouldn't impact SQL at all, as it sets up local accounts for management. It may impact how you choose to authenticate to the instance though, but that is extremely application-specific, so it isn't so much about "SQL" in this situtaion, but how the app has set up their requirements.

The fact that your DC is SBS has no particular impact in this situation.
0
 
LVL 75

Assisted Solution

by:Anthony Perkins
Anthony Perkins earned 166 total points
ID: 39887782
How will that impact the SQL instance if at all?
Once you have renamed the server, you will also need to rename SQL Server so that SELECT @@SERVERNAME is correct.  It is pretty straight forward:

EXEC sp_dropserver <old_name>
EXEC sp_addserver <new_name>, LOCAL
 
-- Restart SQL Server instance.

SELECT @@SERVERNAME AS 'Server Name';
0
 
LVL 38

Accepted Solution

by:
Jim P. earned 167 total points
ID: 39889642
Actually a better method -- Call Server2 whatever.

Then go into your DNS and create a CName record for Server1 that points at Server2.

That saves a lot of time.

And while you're creating CName records create one for every app/DB that points at Server2. Then later when you move a DB to Server3 you just repoint the CName record and don't have to touch the clients.
0

Featured Post

Comparison of Amazon Drive, Google Drive, OneDrive

What is Best for Backup: Amazon Drive, Google Drive or MS OneDrive? In this free whitepaper we look at their performance, pricing, and platform availability to help you decide which cloud drive is right for your situation. Download and read the results of our testing for free!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question