Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Replace 2003 Member Server with New 2008 Member Server - Keeping Same Name

Posted on 2011-09-21
4
Medium Priority
?
183 Views
Last Modified: 2012-12-16
Hi Everyone,

We are currently in the process of replacing a Fax application server which is running on a Windows 2003 member server.

Due to a number of reasons, mainly down to legacy applications, it would be preferable to keep the original servers name on the new server ( windows 2008 R2 64Bit )

My question is this: What is the best method to achieve this?

My Original plan was

1.      Shutdown current server
2.      Reset the computer account in AD Users and computers
3.      Name the new 2008 server the same as the original server
4.      Attach the new 2008 server to the network
5.      Join to domain

However, I have been told that this will cause a number of issues including naming conflicts?

I am now looking at this method

1.      Rename the existing server while it is on the network(  via computer/properties )
2.      Wait for the AD to replicate the changes to the DC’s
3.      Add the new server with the “original name”

Any help would really be appreciated.

Thanks in advance,

Phil
0
Comment
Question by:Pipster
[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
4 Comments
 
LVL 70

Accepted Solution

by:
KCTS earned 2000 total points
ID: 36573330
Either method will work

Personally I would be minded to remove the computer account, and then recreate the account again when the new server is added, rather than reset it - but that's maybe just me
0
 

Author Comment

by:Pipster
ID: 36573372
Hi KCTS,

Thanks for the response.

I think the rename option may be best for me as ( i think im right about this!? ) it will essentiall change the name within AD so when i then add the orignal name back in AD wont get confused as the original computer name wont be there anymore.

does that sound right?

thanks
Phil
0
 
LVL 26

Expert Comment

by:Pber
ID: 38695548
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

670 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