Re: Member servers, XP & WIN2K professional clients during In-place upgrade from NT4 to WIN2K3 AD
- From: "Danny Sanders" <DSanders@xxxxxxxxxxxxxxx>
- Date: Thu, 20 Jul 2006 11:22:08 -0600
We have scheduled for the in-place upgrade of our NT4 domain to WIN2K3.
One of the advantages of an inplace upgrade is that you are upgrading the
existing domain not creating a new domain. Your clients will *think* it's
the same domain.
Leave them online.
For fallback pull an NT 4.0 BDC off line. If necessary, promote to PDC and
the NT domain is back.
hth
DDS W 2k MVP MCSE
<puliyadim@xxxxxxxxx> wrote in message
news:1153408019.195906.57210@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
We have scheduled for the in-place upgrade of our NT4 domain to WIN2K3.
During the upgrade process can the member servers, XP & WIN2K clients
be online?
The concern what i have here is, if all are online they will be joined
to the active directory domain and if i need to fall back to NT 4
domain i would have to disjoin & join them again.
If any one can suggest the best practice it would be a great help for
us.
Thanks.
Dinesh
.
- References:
- Prev by Date: Re: Add WS 2003 R2 to a Mixed mode domain (NT 4.0)
- Next by Date: Re: Problem after migrate
- Previous by thread: Member servers, XP & WIN2K professional clients during In-place upgrade from NT4 to WIN2K3 AD
- Next by thread: Duplicate SID & In-Place upgrade
- Index(es):
Relevant Pages
|
