Sql-server – In a Server migration / move, Do I need to rename the Windows Server name if I change the Server name to Alias (CNAME) the new Server

I am assuming that SERVER and SERVER2 are both member server computers and not domain controller computers.

When I replace old server computers I try and assign the name of the old server computer I'm replacing to the new machine. This is a common practice. (If you're consolidating servers then that's a a whole different "can of worms".)

There's no problem with renaming a domain member server computer after it's joined to the domain. (Supposedly you can rename domain controllers in the Server 2008 version of Active Directory, but I haven't tried it yet.) Of course, in the case of re-using a name that was already assigned to another computer, you'll want to either take the original computer holding that name offline or rename it.

I've done what you're describing many, many times with various versions of Windows. From the point you've described, I'd rename "SERVER" to "OLDSERVER", and "SERVER2" to "SERVER", leaving both joined to the domain throughout the process. You don't have to disjoin "SERVER" from the domain in this process. Once you've renamed "SERVER" while joined to the domain to "OLDSERVER", the object in the AD previously named "SERVER" will change to "OLDSERVER", freeing the name "SERVER" to be assigned to "SERVER2".

As an aside: I have no idea why you'd be running "newsid" unless you installed the system from a disk image (and even then, you should be using SYSPREP to change the SID). You don't need to regnerate the SID unless the SID is a duplicate of another machine's (like if the machine is a disk cloned image of another machine).

I would consider two approaches here, with #2 being my first choice. You could always get the domain and forest level up to 2008 R2 and then look at renaming the domain at that point if needed. I would also recommend that if possible you go with a 2012 server, but that might not be possible in your environment.

1. If you think there is good reason to create a new domain, then I would consider going that route and using something like Forensit Profile Wizard to move the profiles over from the old domain to the new one on the computers/TS. Look at using ADMT as well to swing the users over from the old domain.
2. Keep the existing domain and use the advice I was given when I had to do something very similar. See here: Windows 2003 DC to Windows 2008 R2 DC with same name and same IP This worked well for me, and allowed me to keep the name and IP without any issues.