|
Home > Archive > alt.certification.mcse > November 2002 > migrating to AD
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hi all,
We have one PDC and 3 BDCs, one BDC is across the WAN, and we have few
membered servers. Some of the membered servers are already Win2k.
We just purchased 2 new servers that we can use for the AD migration.
What is the best way to approach AD migration with minumal downtime.
I have a couple in mind already:
1. add the new server as a BDC, then promote it to PDC, take the other BDCs
offline then inplace upgrade the PDC to AD.
2. use ADMT (i'm not sure how reliable this is)
Any input would be greatly appreciated.
Thanks,
Al
| |
| Michael Dickinson 2002-11-16, 6:24 pm |
| add the new server as a BDC, then promote it to PDC, take the other BDCs
> offline then inplace upgrade the PDC to AD.
well if its win2k u cannot do this as win2k doesnt have BDC/PDC.
what you should do......
make sure all servers are upto date, take 1 BDC offline and store it in a
cupboard as backup incase it all goes titsup. Install 2k on the new server,
do the dcpromo to upgrade to a DC and join it onto the domain, make sure its
in mixed mode. I wouldnt bring the backup BDC online for a good few weeks
after eveything is sorted!!
"al" <allen@somplace.com> wrote in message
news:AqhB9.14$Vu6.2743685@newssvr14.news.prodigy.com...
> Hi all,
> We have one PDC and 3 BDCs, one BDC is across the WAN, and we have few
> membered servers. Some of the membered servers are already Win2k.
> We just purchased 2 new servers that we can use for the AD migration.
> What is the best way to approach AD migration with minumal downtime.
>
> I have a couple in mind already:
> 1. add the new server as a BDC, then promote it to PDC, take the other
BDCs
> offline then inplace upgrade the PDC to AD.
> 2. use ADMT (i'm not sure how reliable this is)
>
> Any input would be greatly appreciated.
> Thanks,
> Al
>
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.413 / Virus Database: 232 - Release Date: 06/11/2002
| |
|
| Yes my network right now has 1 PDC and 3 BDCs, all NT 4.0.
You're saying that I can bring a new Win2K server and dcpromo it to a DC and
join my NT 4.0 domain?
And make sure it's in Mixed Mode?
What are the steps to migrate while I am in mixed mode?
Is that doable and safe to do?
Thanks,
Al
"Michael Dickinson" <michael.dickinson@ntlworld.com> wrote in message
news:7SAB9.5231$C12.106994@newsfep1-gui.server.ntli.net...
> add the new server as a BDC, then promote it to PDC, take the other BDCs
> > offline then inplace upgrade the PDC to AD.
>
> well if its win2k u cannot do this as win2k doesnt have BDC/PDC.
>
> what you should do......
> make sure all servers are upto date, take 1 BDC offline and store it in a
> cupboard as backup incase it all goes titsup. Install 2k on the new
server,
> do the dcpromo to upgrade to a DC and join it onto the domain, make sure
its
> in mixed mode. I wouldnt bring the backup BDC online for a good few weeks
> after eveything is sorted!!
>
>
> "al" <allen@somplace.com> wrote in message
> news:AqhB9.14$Vu6.2743685@newssvr14.news.prodigy.com...
> > Hi all,
> > We have one PDC and 3 BDCs, one BDC is across the WAN, and we have few
> > membered servers. Some of the membered servers are already Win2k.
> > We just purchased 2 new servers that we can use for the AD migration.
> > What is the best way to approach AD migration with minumal downtime.
> >
> > I have a couple in mind already:
> > 1. add the new server as a BDC, then promote it to PDC, take the other
> BDCs
> > offline then inplace upgrade the PDC to AD.
> > 2. use ADMT (i'm not sure how reliable this is)
> >
> > Any input would be greatly appreciated.
> > Thanks,
> > Al
> >
> >
> >
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.413 / Virus Database: 232 - Release Date: 06/11/2002
>
>
| |
| WantToFish 2002-11-16, 11:24 pm |
| Here's what I would do if you're not comfortable with doing the preceding
procedure:
I would bring up a box (old W/S as long as it runs 4.0 ok) as a NT 4.0 bdc
online. I would then take it offline and move it to a test network that is
NOT connected to the production net. Upgrade the BDC to a PDC and setup a
mirror of your production environment or something close (1 PDC, 2 or so
BDCs). This will give you a realistic view of your user accounts and you
can begin planning, which you really should have already done, of your AD.
Then I would follow the procedure outlined on the test net
It's really pretty simple once you do it, but I wouldn't want to do it on a
production net for the first time. Once you have the PDC upgraded to 2k,
you will be in mixed mode. Then you can upgrade each BDC to Win2k and when
all the NT 4.0 BDCs are gone, you can then switch to Native Mode. Michael
has the right idea about putting a 4.0 BDC off the network as a backup for
awhile. If you had to, you could go back to NT 4 with that BDC.
I've done this on a few large networks (100+ servers) and having the test
net saved my butt more than once. I found a few apps that we would never
have known needed upgrading prior to going native.
Good luck and take your time during the planning phase. I've cleaned up
after quite a few people who haven't planned AND documented they're upgrade
procedure. After you have your plan, either hire a consultant or some other
3rd party to look it over. I'll get off the box now...
- Larry
"al" <allen@somplace.com> wrote in message
news:yyDB9.2914$gF5.62466270@newssvr14.news.prodigy.com...
> Yes my network right now has 1 PDC and 3 BDCs, all NT 4.0.
> You're saying that I can bring a new Win2K server and dcpromo it to a DC
and
> join my NT 4.0 domain?
> And make sure it's in Mixed Mode?
> What are the steps to migrate while I am in mixed mode?
> Is that doable and safe to do?
> Thanks,
> Al
>
>
> "Michael Dickinson" <michael.dickinson@ntlworld.com> wrote in message
> news:7SAB9.5231$C12.106994@newsfep1-gui.server.ntli.net...
> > add the new server as a BDC, then promote it to PDC, take the other BDCs
> > > offline then inplace upgrade the PDC to AD.
> >
> > well if its win2k u cannot do this as win2k doesnt have BDC/PDC.
> >
> > what you should do......
> > make sure all servers are upto date, take 1 BDC offline and store it in
a
> > cupboard as backup incase it all goes titsup. Install 2k on the new
> server,
> > do the dcpromo to upgrade to a DC and join it onto the domain, make sure
> its
> > in mixed mode. I wouldnt bring the backup BDC online for a good few
weeks
> > after eveything is sorted!!
> >
> >
> > "al" <allen@somplace.com> wrote in message
> > news:AqhB9.14$Vu6.2743685@newssvr14.news.prodigy.com...
> > > Hi all,
> > > We have one PDC and 3 BDCs, one BDC is across the WAN, and we have few
> > > membered servers. Some of the membered servers are already Win2k.
> > > We just purchased 2 new servers that we can use for the AD migration.
> > > What is the best way to approach AD migration with minumal downtime.
> > >
> > > I have a couple in mind already:
> > > 1. add the new server as a BDC, then promote it to PDC, take the other
> > BDCs
> > > offline then inplace upgrade the PDC to AD.
> > > 2. use ADMT (i'm not sure how reliable this is)
> > >
> > > Any input would be greatly appreciated.
> > > Thanks,
> > > Al
> > >
> > >
> > >
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.413 / Virus Database: 232 - Release Date: 06/11/2002
> >
> >
>
>
|
|
|
|
|