Hello fdisks,
What do you mean with 'account reset' in AD? If the new server, hopefully
a MEMBER server and not DC, shold use the old name you have to rename the
server on the server properties. Also i would do the renaming in 2 steps.
Either the old server will be removed from the domain before complete, so
you can reuse the name and will not go into any problems in the domain AFTER
replication to all DCs and checking all DNS zones or you have to rename the
old server to a temp name, wait for AD replication and check DNS zones, and
then rename the new server to the now free name of the old server.
Advantage of the latter, the old server is still domain member and you can
easy access all old information within the domain, maybe copy data or whatever.
This would be my preferred way.
With a domain controller there will be more steps included with renaming.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Hi all
>
> I am in the process of migration an existing 2003 F/P server to an new
> server. It will be the same OS. I have secure copied the data over
> from the old server to the new server and have it scheduled to sync
> nightly until I cut over to the new server. I plan to keep the same
> servername by taking the old server offline and doing an 'account
> reset' in AD on the computer object and then join the new server to
> the domain with the same computername. I plan to use MS Print Migrator
> 3.1 to bring over the printer configs(As I understand it by keeping
> the same servername this will in turn not affect the users mappings
> they currently have?)
>
> Can anyone see anything I am missing here for the migration?...Any
> steps I have missed etc?...
>
> Any feedback will be much appreciated
>
> http://forums.techarena.in
>