Re: Upgrade from NT4
- From: "Hupla" <cymru@xxxxxx>
- Date: Thu, 16 Mar 2006 14:57:44 -0000
Thanks for the advice. Exchange doesn't exist currently - whcih obviously
simplifies things.
I think I have enough info to go ahead and do this now, so thanks again for
your help!
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:O#dy0fQSGHA.5552@xxxxxxxxxxxxxxxxxxxxxxx
just gotta point out Frank,no
those 'single place' names you are referring to are NETBIOS domain names,
and my (and all ecept the badly configured) SBS's will have a single level
NETBIOS domain name
(ends up I got this far through this and Frank IM'd me) we chatted and
discussed Exchange repercussions. So the question still stands, does
Exchange live in the current mix?
"Frank McCallister SBS MVP" <anonymous> wrote in message
news:uviRdNQSGHA.5108@xxxxxxxxxxxxxxxxxxxxxxx
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
createdot extension like company.local instead were just company This can
thea 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
betterdomain held on the tempDC. In an NT4-AD migration this is probably
thatperformed before going to AD, with the tempDC disconnected from the
originDC.
I'm pretty sure Jeff would also promote the NT4 tempDC 'offline', so
It!!'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
todocs/process. It, and the included support of the process, would seem
http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/sbs45203.mspxbe 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',
don'tArriving 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
readhave 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
namea
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
isas
the "old" NT4 server
- Dcpromo down tempdc ensuring new SBS server has all the FSMO roles,
pitfalls?GC
etc.
- Remove old NT4 and swap with new SBS server.
Does this seem like a good plan? Can anyone spot any potential
domain)?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
Any input/advice much appreicated.
-H
.
- References:
- Upgrade from NT4
- From: Hupla
- Re: Upgrade from NT4
- From: SuperGumby [SBS MVP]
- Re: Upgrade from NT4
- From: Frank McCallister SBS MVP
- Re: Upgrade from NT4
- From: SuperGumby [SBS MVP]
- Upgrade from NT4
- Prev by Date: Re: Cannot get access to router on SBS server
- Next by Date: Internet Proxy GPO
- Previous by thread: Re: Upgrade from NT4
- Next by thread: Upgrade from NT4
- Index(es):
Relevant Pages
|