Re: A difficult migration (2000 -> 2003)
From: Massimo (barone_at_mclink.it)
Date: 11/18/04
- Next message: nospam_at_cristalink.com: "Re: Veritas Backup and Sony LIB-D81 problem"
- Previous message: Jim Van Sickle: "Re: Login Script Help"
- In reply to: Herb Martin: "Re: A difficult migration (2000 -> 2003)"
- Next in thread: Herb Martin: "Re: A difficult migration (2000 -> 2003)"
- Reply: Herb Martin: "Re: A difficult migration (2000 -> 2003)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Nov 2004 22:16:09 +0100
"Herb Martin" <news@LearnQuick.com> ha scritto nel messaggio
news:ebLyK%23azEHA.2568@TK2MSFTNGP11.phx.gbl...
> 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.
Luckily, I tought in advance about possible NetBIOS conflicts (the two
domains are running on the same physical network), and gave the new domain a
different NetBIOS name (it's also more suited to the organization's name);
only the DNS name should remain the same.
Anyway, the old domain needs to be renamed for ADMT to work, even if only
the DNS name is the same, so I'm already prepared for this.
> 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 thought about this, of course, and I'll use it if the ADMT solutions
doesn't work; but, as you can see, the most difficult part is not typing in
usernames... it's preserving and migrating their user profiles and their
documents (which are all stored locally on their computers).
> I am however a BIG believer in UPGRADES, especially where the name
> must not change.
Ordinarily, I would've done it... but, as I described, the old domain is in
such an awful state I doubt it can be ever cleaned up.
> 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?
That's the simplest solution, of course.
But there is a defunct Exchange 2000 organization in the old domain, and it
can't be removed because its one and only Exchange server died and was
dismissed without properly uninstalling it; In the user's accounts there are
attributes about non-working e-mail addresses and unreachable mailboxes that
were hosted on that server, and so on. I'm quite sure a new Exchange
organization won't install in such a mess, so I went for the "whole new
domain" approach.
> Remove the old DCs; add the other new DCs and clean up the mess
> (whatever that is.)
It's mainly the one I described above, and there are also lots of wrong
and/or broken GPOs (lots of testing was done by former network
administrators).
> No, the client computers would need to be removed and joined to the
> new domain.
Really?
How can the users continue to work after a domain rename operation, then?
So, the domain rename (which is only a step to migrating users) is going to
take almost as long as simply joining the new domain? It can't be like
this... what is domain rename good for, then, if it doesn't have any
advantage on creating new domains?
> You cannot rename a Win2000 Domain -- you can only rename a Win2003
> (or NT) domain under SPECIAL cases.
As I said before, if I'm to rename the old domain, I'll upgrade its DC to
Windows 2003.
BTW; are you sure a NT domain can be renamed? Never heard about this...
Massimo
- Next message: nospam_at_cristalink.com: "Re: Veritas Backup and Sony LIB-D81 problem"
- Previous message: Jim Van Sickle: "Re: Login Script Help"
- In reply to: Herb Martin: "Re: A difficult migration (2000 -> 2003)"
- Next in thread: Herb Martin: "Re: A difficult migration (2000 -> 2003)"
- Reply: Herb Martin: "Re: A difficult migration (2000 -> 2003)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
