Re: A difficult migration (2000 -> 2003)
From: Herb Martin (news_at_LearnQuick.com)
Date: 11/18/04
- Next message: JackW: "Server 2003 Can't install or uninstall NICS - i.e. no network"
- Previous message: Mike: "Re: Event ID 5504"
- In reply to: Massimo: "A difficult migration (2000 -> 2003)"
- Next in thread: Massimo: "Re: A difficult migration (2000 -> 2003)"
- Reply: Massimo: "Re: A difficult migration (2000 -> 2003)"
- Reply: Massimo: "Re: A difficult migration (2000 -> 2003)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Nov 2004 14:35:58 -0600
"Massimo" <barone@mclink.it> wrote in message
news:eDwA6uazEHA.3416@TK2MSFTNGP09.phx.gbl...
> I'm in the process of migrating a Windows 2000 domain whose old servers
> encountered some major hardware failures to a new Windows 2003 domain
hosted
> by new, top-of-the-line servers; the old domain is in a quite dirty state,
> due to lots of misconfigurations, hardware problems and a dead Exchange
> server, so we tought it was better to create a completely new one instead
of
> just replacing the domain controller.
>
> The new domain must have the same name as the old one (it's a public
domain
> name, and it also has to be used for the new, Exchange-2003-based e-mail
> system), and must be joined by the same client computers and the same user
> who are now using the old one; so I installed two of the new servers using
> available IP addresses on the same network, promoted them to DCs creating
a
> domain with the same name and installed the DNS service on them. Now I'm
> looking for the easiest and quickest way to migrate users and computers.
It is very difficult if not impossible to migrate from a domain to another
with the SAME NAME. Generally this just doesn't work since trusts
(NetBIOS based) are required and there are other conflicts.
> The number of users is quite low (around 60), so it *could* be possible to
> just re-create the accounts, assign new passwords to them, join all the
> computers to the new domain, log in with the user account, log out, re-log
> in as an administrator and copy the old user profile over the new one; all
> of this on each machine; but, altough possible, it would be quite
> time-consuming and prone to errors, so I'm looking for something better.
If you are determined to use a "new" domain then this may be your best
course. You could export and import the users (they will be new users
in a new domain of course) to avoid most of the "prone to errors" issues.
LDIFDE can do such export/import.
I am however a BIG believer in UPGRADES, especially where the name
must not change.
> I tought about the ADMT, but it can't be used because the two domains have
> the same name; This can be worked around by upgrading the old DC to
Windows
> 2003 and renaming the domain, but I'm not sure about two things here;
first,
> I fear a hardware incompatibility between the old SCSI controller
installed
> on the DC and Windows 2003, and I just don't want to run the upgrade
wizard
> only to get a blue screen after rebooting; I never ran a direct upgrade (I
> don't trust them), so I'm asking here: is there any way to supply hardware
> drivers to Windows 2003 during the upgrade phase, if the old ones aren't
> working (they are for Windows 2000) and the system doesn't have its own
> ones?
Why not just put one of the "new" DCs in the old domain, DCPromo it,
and thereby upgrade the old domain with the new DC?
Remove the old DCs; add the other new DCs and clean up the mess (whatever
that is.)
> The second problem is, how does the domain rename operation impact on
client
> computers? Do they continue to work as if nothing happened, or do they
> require a domain rejoin or something similar? In the latter case, the
whole
> operation would be useless... better to join them to the new domain
> altogether.
No, the client computers would need to be removed and joined to the
new domain.
> Anyway, let's suppose I manage to rename the old domain, so I can use the
> ADMT to migrate users to the new one. I've read lots of documentation
about
> this, and I know the whole procedure quite well, so I think I can handle
it
> (damn, I'm a MCSE... if I can't do it, who can? :-) ), but I still have
some
> doubts.
You cannot rename a Win2000 Domain -- you can only rename a Win2003
(or NT) domain under SPECIAL cases.
> First one: the old domain used to have an Exchange 2000 server, which
died;
> so, Exchange attributes are still wandering around the directory, users
have
> non-working e-mail addresses and mailboxes, and there is a whole Exchange
> organization relying on a server which isn't there, so it can't simply be
> uninstalled. I've tried the Exchange setup with the /removeorg switch, but
> it failed with some errors... and I don't want to manually edit the AD.
Can
> I try to re-install Exchange on a server in the old domain, so to be able
to
> remove it afterwards? Will it work? And, the most important thing, how
does
> this affect the ADMT when migrating users? Can I configure it to not
migrate
> Exchange-related attributes?
> Second doubt: after running the ADMT, what needs to be done on each client
> to have it running on the new domain? Does it need a rejoin and/or
something
> else? I know the user account will work (at least as long as the trust
> relationship is still there) and the user profile will be preserved, but
> what steps are to be actually done for each computer?
-- Herb Martin > > Thanks for any help. > > Massimo >
- Next message: JackW: "Server 2003 Can't install or uninstall NICS - i.e. no network"
- Previous message: Mike: "Re: Event ID 5504"
- In reply to: Massimo: "A difficult migration (2000 -> 2003)"
- Next in thread: Massimo: "Re: A difficult migration (2000 -> 2003)"
- Reply: Massimo: "Re: A difficult migration (2000 -> 2003)"
- Reply: Massimo: "Re: A difficult migration (2000 -> 2003)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
