AD Member server swap

Hey guys -

We are replacing an aging domain member server with a new server this weekend.
Any advice/best practices/comments out there for this?
We have already pre-built the new server with a temporary name and temporary IP, and joined it to the domain.

For the sake of this discussion:
OLDSERVER Name: Server1
OLDServer IP: 192.168.1.115
NEWServer Name: Server1a
NewServer IP: 192.168.1.215

I am assuming I will:
1. Remove Server1 from domain, and shut it off.
2. Rename Server1a to Server1, reboot
3. Re-IP the newly named Server1 with 192.168.1.115, reboot
4. all is well?

Any thoughts/comments/best practices?
Thanks!
jn1480Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Glen KnightCommented:
The only thing I would add is before you change the IP and name of the new server after removing the other one from the domain is to remove any DNS entries in the forward and reverse lookup.

Apart from that it all looks OK
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
r_panosCommented:
Normally I prefer the following steps:
1. Remove Server1 from domain, and shut it off.
2. Check and clean up DNS from Server1 entries
2. Rename Server1a to Server1, reboot
3. Re-IP the newly named Server1 with 192.168.1.115, reboot
3. Add newly named Server1 to domain (not doing it at the begining)

but if you have special issues and need the Server1a in the domain before replacing the Server1 then the steps you mentioned are ok but clean up DNS (you don't have WINS also, do you?) between steps 1 & 2 and trigger AD replication before you change name to Server1a.

If there's IIS installed on Server1a then you'll have problem with anonymous access after renaming the server. Better unistall IIS and re-install it after name change.
0
ren20atomCommented:
Hi,
Could you please update on the role of the member server?
If it is an application server, then name of the Hosted Application too.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.