Re: Upgrade from NT4

Super G has given you Excellent advice! I would like to throw one more thing
into the mix! Many NT Domains were Single Place named ie they had no dot
extension like company.local instead were just company This can create a
problem with migration.

--
Frank McCallister SBS MVP
COMPUMAC
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:uWvzawPSGHA.1576@xxxxxxxxxxxxxxxxxxxxxxx
unless you've been down this road before it is VERY likely you would
benefit from the process notes available from www.sbsmigration.com

You don't remove the tempDC, you remove the originDC from the copy of the
domain held on the tempDC. In an NT4-AD migration this is probably better
performed before going to AD, with the tempDC disconnected from the
originDC.

I'm pretty sure Jeff would also promote the NT4 tempDC 'offline', so that
the existing DC still believes it is Primary.

Does Exchange server exist in the NT domain?

I really, really, really encourage you to look at purchasing 'Swing It!!'
docs/process. It, and the included support of the process, would seem to
be valuable in your scenario.

Migration ain't something you want to tackle on your own without practical
experience.

An alternative you may want to consider is to handle it 'MS Style',
http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/sbs45203.mspx
Arriving at a point where the target server has the same name as the
origin server simply requires NT4 domain DC addition of tempDC, removal of
originDC, and installation of SBS with the originDC name (if you don't
have exchange in the mix), while following the papers.

"Hupla" <cymru@xxxxxx> wrote in message
news:%23YUvJbPSGHA.336@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I'm looking to upgrade my network from NT4 to Win 2003 SBS. Having read a
bit I was thinking of doing a swing style migration. My plan is as
follows:-

- Install server named tempdc into the NT4 domain as a BDC and promote to
PDC.
- Upgrade tempdc to Win2003 (with Active Directory)
- Removed tempdc and go native mode
- Add new Win 2003 SBS server to tempdc's domain giving it the same name
as
the "old" NT4 server
- Dcpromo down tempdc ensuring new SBS server has all the FSMO roles, is
GC
etc.
- Remove old NT4 and swap with new SBS server.

Does this seem like a good plan? Can anyone spot any potential pitfalls?
Lastly is this going to be seamless to the clients (i.e. will they log
onto
the new SBS domain not realising it's any different to the NT4 domain)?

Any input/advice much appreicated.

-H






.

Relevant Pages

  • Re: Upgrade from NT4
    ... Frank McCallister SBS MVP ... I'm pretty sure Jeff would also promote the NT4 tempDC 'offline', ... Does Exchange server exist in the NT domain? ...
    (microsoft.public.windows.server.sbs)
  • Re: NT to SBS 2003
    ... careful of certain possible blocking possibilities going from NT4 to 2k3. ... There is a book I am going to recommend you get for a complete guide to SBS ... setup SBS on a new server - however, unless my budget changes drastically, ... We are upgrading our network from Windows NT and Exchange 5.5 to SBS ...
    (microsoft.public.windows.server.sbs)
  • RE: 2003 SBS sevrer cannot trust another domain !!!!
    ... You can not bring the old NT4 server from the old domain into the new SBS ... Windows NT4 into SBS 2003 as a member server. ...
    (microsoft.public.windows.server.migration)
  • Re: Upgrade from NT4
    ... Frank McCallister SBS MVP ... You don't remove the tempDC, you remove the originDC from the copy of the ... Does Exchange server exist in the NT domain? ... origin server simply requires NT4 domain DC addition of tempDC, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2000 migration
    ... Join TempDC to existing domain (Spare IP and Name (diff to Source and target ... SBS servers), add DNS, DCpromo and designate GC. ... >> server and promote it to DC ... must use the Swing Migration methods. ...
    (microsoft.public.windows.server.sbs)
Loading