The issue is that the old server handles a ton of functions--it's not just a simple file server, I'm afraid. Those functions can't be moved over all at once; I'm doing them one at a time. Until the last function is migrated, both servers will have to stay up and running.
-----Original Message----- From: Don Guyer [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2008 10:46 AM To: NT System Admin Issues Subject: RE: Moving Roaming Profiles & Redirected Folders Yeah, but he said they have to have both servers up at the same time for awhile (didn't say exactly why). So that nixes that idea. :) Don Guyer Systems Engineer Information Services Department Prudential Fox Roach/ Trident 431 W. Lancaster Avenue Devon, PA 19333 Ph: (610) 993-3299 Fax: (610) 650-5306 www.prufoxroach.com [EMAIL PROTECTED] -----Original Message----- From: Miller Bonnie L. [mailto:[EMAIL PROTECTED] Sent: Friday, July 25, 2008 10:44 AM To: NT System Admin Issues Subject: RE: Moving Roaming Profiles & Redirected Folders 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> ~ </pre> <table width="100%><tr><td class="body"> This email and any files transmitted with it are confidential<br> and intended solely for the use of the individual or entity to<br> whom they are addressed. It may contain information protected by <br> state and federal privacy and intellectual property laws.<br> If you have received this email in error please<br> notify the sender immediately and delete this e-mail from<br> your system. If you are not the named addressee you should<br> not disseminate, distribute or copy this e-mail, and you are<br> notified that disclosing, copying, distributing or taking any<br> action in reliance on the contents of this information is strictly prohibited.<br> </td></tr></table> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
