We do this a LOT (keep the same name). I get around the name remnant issues by building server2 off the network with the original name first--a trick our network admin taught me. Rename to newserver1 shortly before plugging in (and joining the domain).
Rename the original server1 to oldserver1 at the right moment and then rename newserver1 back to server1. Just make sure you don't install anything important in between the renames, like IIS (adds Iusr accounts) or SQL. You also have to clean up DNS (and WINS if you are using) to get everything to come up just right, but it works really well. -Bonnie -----Original Message----- From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2008 6:22 AM To: NT System Admin Issues Subject: RE: Moving Roaming Profiles & Redirected Folders >Wouldn't naming the replacement server the same name and assigning it >the same IP as the retired server handle that? I have done both, removed the old server after a robocopy and share reg import, and change it in AD. Its been my experience there are sometimes places in the reg that retain the old server name. At any rate, both methods work with the former being the easiest *if* the old system can be removed or renamed as well. jlc ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
