Re: Moving to Active Directory From NT4 Please Help

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> >
> > "Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
> > news:%23Zy1L1pHFHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
> > > "Joel Kaminsky" <jkaminsky@xxxxxxxxx> wrote in message
> > > news:etlz4KpHFHA.1172@xxxxxxxxxxxxxxxxxxxxxxx
> > > > This is what I have accomplished:
> > > >
> > > > I'm trying to do a clean install for AD 2003. I've moved a
> > > > BDC from my production LAN to my testing lan and promoting it
> > > > to a PDC.
> > > > Since we use Linux boxes for DNS in production. I loaded a
> > > > testing linux box and also moved it over for DNS. I started
> > > > a fresh install of windows 2003 Standard Server. My domain
> > > > name is IITMAIN and that my
> > > DNS
> > > > is linuxserv.itt.org on the linux box. In order for me to
> > > > continue using the same Domain name of IITMAIN I think I need
> > > > to do the following Start
> > > DNS
> > > > up in the 2003 server give it the name of iitmain.iit.org.
> > >
> > > It is VERY difficult if not impossible to migrate to a
> > > new domain with the same NetBIOS name -- migration
> > > (e.g., ADMTv2) is dependent on trusts which are dependent
> > > on NetBIOS which doesn't allow for duplicate names.
> > >
> > > [You will be much happier in the long run if you use
> > > MS DNS to support the MS Domain but Linux CAN
> > > work.]
> > >
> > > You really should (re-)consider an Upgrade. Most
> > > people who think they cannot upgrade their domain
> > > from NT4 do Win2003 are misinformed.
> > >
> > > It is DESIGNED to be upgradable.
> > >
> > > > I get The Default NetBIOS domain name IITMAIN0 was selected
> > > > due to the
> > > name
> > > > conflicts on the network.
> > >
> > > Right so the trust is possible but the new name
> > > is different.
> > >
> > > > Can someone tell me how this process should work because it
> > > > apears that I must be doing something wrong. I trying to
> > > > stay within the same Domain name.
> > >
> > > Not really -- you are just misunderstanding the
> > > issues.
> > >
> > > Upgrade and make it easy on yourself. (We haven't
> > > even started talking about user profiles and home
> > > directories.)
> > >
> > > > Thank you in advance in any help you can provide me
> > >
> > >
> > >
> >
> > I tried to upgrade my NT4.0 BDC to Windows 2003 Small Business
> > Server and it immediately complained that I needed to do a clean
> > install. It's certainly possible that I am "misinformed", but the
> > "misinformation" is coming from the Microsoft CD.
>
> I don't recall you mentioning it was an upgrade to SBS.
>
> SBS is weird -- different upgrade paths and restrictions.
> (I am not much of an SBS fan -- good idea, questionable
> rules and implementation although they have improved it
> much in the last few versions.)
>
> Also, you can NEVER upgrade a WinNT domain by upgrading
> the BDC.
>
> All NT domains must be upgraded to Active Directory at the
> PDC ONLY.
>
> No choice -- anything else will fail, or create a new domain,
> or a stand-alone server.
>
> > So explaining this like I am 8 years old, I put the w2k3 SBS CD
> > in the running, production NT4.0 BDC and do what?
>
> Ask in the SBS group but recognize IF they can offer a method
> that you must upgrade the PDC.
>
> Since NT SBS doesn't have BDCs it is almost certain that you
> don't have NT SBS and there may not be (probably is NOT) an
> upgrade path from non-SBS to SBS. (Going the other way wasn't
> even originally available for SBS.)
>
> And remember, only the PDC can upgrade a domain in any case.
>
>

Thanks very much for the info, folks. For the benefit of others
reading this thread and having similar issues- someone was kind
enough to tell me that Windows 2003 SBS has some pretty severe
limitations for the kind of environment I am trying to use it in
(migrating an NT4.0 network to 2003). The short of it is that SBS
will not work if there are any other domains on the wire. You cannot
set up trust/trusting relationships with anyone and clients that
already know about an existing windows domain will refuse to talk to
SBS.

The fellow who clued me into this said I needed the "full blown"
windows 2003 server, whatever product name that happens to be. So
for us, it's back to rip on the sales guy.

I have to agree with you. I guess if you have no windows network and
are a small shop, SBS might work for you. But other than that, I
think I will spend the rest of my life steering clear of it.



-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
Comment: foobar

iQA/AwUBQl3wflPfRV42MJPXEQKTzACg3TNW32jePyhbUw+BukBc1UPSpL0AoMLi
wZqnXlgywP/cyVhAKzlt8QwN
=WHHF
-----END PGP SIGNATURE-----


.

Relevant Pages

  • Re: Secondary DNS and PIX
    ... SBS SP1 was a very specific service pack comprising several ... Root hints for DNS means you leave the forwarders ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Standard edition Updgrade
    ... you can upgrade your SBS 2003 sp1 Standard to SBS ... To upgrade to Windows Small Business Server 2003 R2, ...
    (microsoft.public.windows.server.sbs)
  • Re: Secondary DNS and PIX
    ... Windows 2003 SMALL BUSINESS SERVER ... SBS SP1 was a very specific service pack comprising several ... Root hints for DNS means you leave the ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2000 to 2004 upgrade cd...
    ... Thanks for the response but this upgrade was free + $5 for shipping. ... I suggest you order or buy SBS 2003 R2 Premium ... If you want to upgrade an existing computer to Windows SBS 2003 R2 that is ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Secondary DNS and PIX
    ... SBS SP1 was a very specific service pack comprising several ... Root hints for DNS means you leave the forwarders ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ...
    (microsoft.public.windows.server.sbs)