Re: Migration from SBS 4.5 to Windows 2003 Server

I haven't looked at sbsmigration.com but will.

I wasn't sure whether I could simply turn on the SBS4.5 after I had already
promoted a BDC to PDC. So I created the second BDC to be able to promote in
the event the 1st one failed. Maybe being over cautious but I had the extra
box sitting around.

Do you know the number of days a BDC can be disconnected? Are you saying if
I exceed this I would need to reinstall the box?

as for my original questions:
1. Do I do this upgrade with the box disconnected from the rest of the
network or while on the network "LIVE"

2. Since I have DNS already installed on another Windows 2000 member server,
do I need to disable it prior to installing the new DNS server on the DC?

3. Can the SBS box be used as a DC again if the upgrade fails on the new
promoted DC?

Thanks
Diane

"Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:OkqtFVHqHHA.3368@xxxxxxxxxxxxxxxxxxxxxxx
Have you looked at sbsmigration.com ?
Not sure why you have two BDCs and the one you have off line...there is
hard #of days you have have a DC "disconnected" from the PDC.

But your other steps are correct. You'll have some Active Directory
stuff to clean up because of SBS
I would have them Disconnected
And you'll need the windows 2000 box to be DNS, WINS, DHCP, Global
Catalog.

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"DianeA" <DianeA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AB17B5BF-6CB3-4F03-A16C-A85F3F219DE3@xxxxxxxxxxxxxxxx
Not sure if this is the correct group but hopefully someone can answer a
couple of questions or give comments on my method.

I have SBS4.5 running on a very old server. But i want to move to
Windows
2000 full version and then 2003 in the future (Just due to some legacy
applications we need to get rid of before we go to 2003)

So my plan is:
Install NT4.0 as BDC on new box (this step is done) (sychronize before
upgrade)
Have another BDC offline (this is done - will do final sychronization
before
upgrade)
Take SBS4.5 offline
Make new BDC the PDC
Upgrade to Windows 2000 Server

A couple of questions:
1. should I upgrade the server while on network or should I take it off
the
network
2. If upgrade fails, can the SBS4.5 be brought back online (or are the
desktops have some sort of connection to what is knows as the new Domain
Controller?)
3. DNS is currently running on a member server running Windows 2000...
do I
need to disable this and install on new Windows 2000 server or can I
leave it
running on the other server?

any assistance is appreciated.
Diane




.

Relevant Pages

  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
Loading