Re: Question on planning



Yah, maybe you're right.. It's just that the NT domain is soooo much
messyyy.. And the box, way to small to handle Win2k3.. What's the trick
you were talking about?


I am going to say it straight out (with no intention to
criticize, only to state the case):

Anyone who has a "messy" NT domain will soon have
a messy (probably worse) AD domain.

Clean it up -- now or after you upgrade, but don't use
this phony reason to avoid upgrading. This idea has
been propagated largely by those who aren't very good
at maintaining there domains.

Trust those who are GOOD at Domain Administration
and you will find that the normal recommendation is
"upgrade".

These systems were DESIGNED to be upgradable and
you will definitely avoid far more problems in almost
all cases by doing so rather than "starting over".

Chances are, even the "import" itself would propagate
most of the mess junk so there isn't even a reasonably
chance you wouldn't be just as "messy".


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

"Michel Chiasson" <Ihatespam@xxxxxxxxxxx> wrote in message
news:s7N1g.62929$VV4.1177896@xxxxxxxxxxxxxxxxxxxxxxxxxx

"Herb Martin" <news@xxxxxxxxxxxxxx> a écrit dans le message de news:
uPSZaXIZGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
"Michel Chiasson" <Ihatespam@xxxxxxxxxxx> wrote in message
news:ccM1g.62895$VV4.1177525@xxxxxxxxxxxxxxxxxxxxxxxxxx
Finaly migrating from a 3 server NT domain(1 PDC, 2 BDC), to a Win2k3
active directory environement. The AD on our new win2k3 is up and
running, and ready to welcome the new users! : )

Most people will be FAR BETTER off (fewer problems
and issues) if they JUST UPGRADE to Win2003.

My bigest concern is the File server..

One of the major reasons for UPGRADING rather than
trying to re-create the uses on a 'new domain.'

Would it be possible to like emulate the NT domain on our new AD domain
to migrate users and still access their old file server in the NT
domain? I don't want to migrate all at once, and would like to do it
gradually, if that's possible.

Everything that seems to concern you would be solved
by upgrading.

Even if you hardware doesn't (directly) support such
upgrades there are (easy) tricks to still upgrade the
NT domain.

If not, is the other way arround possible? Migrate the File server to
the new AD, and still be accessible to the NT users??

You are likely going to have security and permissions
issues with any form of migration -- all this can be
avoided by upgrading.

Also, with User Profiles which just work when you
upgrade.

Yah, maybe you're right.. It's just that the NT domain is soooo much
messyyy.. And the box, way to small to handle Win2k3.. What's the trick
you were talking about?



.



Relevant Pages

  • Re: Need Recommendations on NT4 > WS2003 Migration
    ... I understand that you want to have a win2k3 ... Both the migration and the upgrade as Jeff has suggested are OK. ... 2.Promote the BDC to the PDC, upgrade the new PDC to Windows Server 2003. ...
    (microsoft.public.windows.server.migration)
  • RE: Windows 2000 upgrade to Windows 2003
    ... 325379 How to upgrade Windows 2000 domain controllers to Windows Server ... Install win2k3 on your new machine and join it to abc.com. ... Install AD-integrated DNS on DC11. ...
    (microsoft.public.windows.server.migration)
  • RE: About to do an in-place upgrade..just checking...
    ... How many clients do you have in the NT4 domain? ... It is best if you perform the upgrade process during a non-business time ... Exchange 5.5 will be functioning well in a member server in the win2k3 ... Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)
  • RE: NDS for NT Migration
    ... It is hard to say which is the easiest way to do the migration. ... I believe you can upgrade NT to win2k3 first and then use ... MSDSS to migrate files from Novell. ...
    (microsoft.public.windows.server.migration)
  • RE: In Place Upgrade of Win2K DC to 2003
    ... daily after upgrading another Win2k3 server to be DC in Win2k3 domain. ... raise the functional level to Windows Server 2003 and what's the result? ... >I performed an in place upgrade of a Win2K DC, ... >Event Source: NTDS Replication ...
    (microsoft.public.windows.server.migration)