Re: NT4 to Win 2K3 upgarding

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thank you very much. Ziek. But it looks
like it's better to keep the same DNS and Netbios name. I am wondering if I
can use the following method:

1. Change current NT domain name to Corp.
2. Upgrade NT to Win2k3. Use Corp.company.com as FQDN and Corp as Netbios
name.

Will it be possible to do the above?


"Ziek" wrote:

> since you are upgrading your domain, you will not have the option to change
> the netbios name. You only have a netbios name option when you do a fresh
> dcpromo installation. Since this is an upgrade, and not fresh, it will
> automatically use "newyork" as your netbios name. You will only have an
> option for your active directory dns name, which you can choose to be
> corp.company.com.
>
> Your windows NT and windows 95 machines will still believe that they are
> part of the "newyork" domain and not see a difference.
> Your WIndows 2000 and WIndows XP machines, will automatically detect your
> Active Directory domain controller, and realize that they are now part of
> the corp.company.com domain.
> Either way, you will not have to change any settings on the client side.
> That's the beauty of a domain upgrade...
>
>
> "Jun" <Jun@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A126FDFC-21B6-49F9-B9E4-D4F7DA238797@xxxxxxxxxxxxxxxx
> > Hi
> >
> > We are going to upgrade NT4 domain to Win2K3 domain. I have two questions
> as
> > follows:
> >
> > 1. The current NT4 domain name is Newyork. We would like to change to
> > Corp.company.com in Win2K3 domain after upgarding. During the Active
> > Directory installation, I can specify Corp.company.com as the root domain
> > name. But how about the Netbios name of the new domain? Is it still
> Newyork
> > or Corp?
> >
> > 2. If we change the domain name, will it affect the clients? Do we need to
> > rejoin the clients into the new domain and migrate the profile? Or the
> client
> > will recognize the new domain automatically?
> >
> > Thanks in advance for any help.
>
>
>
.

Relevant Pages

  • RE: Migration NT4->W23 with same WINS/DNS Namespace
    ... perform an in-place upgrade as you have mentioned.We call this issue as ... "Perioded Windows NT Domain Name" issue. ... NETBIOS domain name for Windows NT, you may encounter the following problem ... Upgrade using a new DNS domain name. ...
    (microsoft.public.windows.server.migration)
  • Re: Adding Client PC issue
    ... All signs point to an issue with NetBIOS. ... From the client PC in Network Connections if I right-click ... Windows could not finish repairing the problem because the ... This indicates the SBS Server and Router are not to blame. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server alias.
    ... >> an issue with duplicate NetBIOS names with clients. ... The windows 2000 server has ... > I tried disabling DNS and WINS configuration on the windows 98 client ... But yes, mutliple NICs can be an issue, ...
    (microsoft.public.win2000.dns)
  • RE: after in-place upgrade sql need to re-join domain
    ... Thanks for your response. ... when prior to the upgrade all they entered ... this issue is caused by the wrong Netbios name. ... >> user in SQL server, or on the machine which running SQL Server? ...
    (microsoft.public.windows.server.migration)
  • Re: Windows Me Client cant connect to 2003 server
    ... In the WinME Windows Networking Client, use the NetBIOS name of the domain - ... match the last level of your FQDN, you will probably need to change it. ...
    (microsoft.public.windows.server.networking)