RE: 4.0 to 2000 Questions

From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 12/10/04


Date: Fri, 10 Dec 2004 08:20:01 GMT

Hi Doug,

Thanks for your posting here.

I suspect that the original synchronization was not performed perfectly. In
general, we can use the steps you tried to rollback to NT 4 domain.

As for the problem about the icon of BDC1, would you please provide a
screen capture for it?

When you upgrade NT 4 domain, the netbios name is kept and you can input a
new DNS domain name you desired. Then there is two names for a Windows 2000
domain. The NETBIOS domain name and DNS domain name. They are not
conflicting. As for domain mode, it will not affect the domain name.

When users login domain, the domain NETBIOS name is list in the logon
dialog.

Have a nice day!

Regards,
Bob Qin
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
      From: "DOUG" <none@nospam.com>
      Subject: 4.0 to 2000 Questions
      Date: Thu, 9 Dec 2004 09:04:41 -0500
      Newsgroups: microsoft.public.windows.server.migration

      
      Hello All:
      
      Have a few questions as a result of some LAB work we are doing in
      preperation of Migrating from 4.0 to 2000. Here is a brief rundown of
our
      Network which was duplicated in the LAB emvironment
      
      - All Clients are currently running windows 2000 Pro
      - All servers except for our DC's are running Windows 2000 Server
      - PDC1 4.0
      - BDC1 4.0 - also running Exchange 5.5 (I inherited this)
      
      My game plan is this - and these are a few issues I noticed
      
      - I plan to bring up a spare BDC (BDC2) and sync it up prior to the
upgrade
      and then bring it down prior to actually starting to upgrade. This
will give
      me a rollback
      
       I have done the above, performed the upgrade and then killed the new
2000
      server - palnning to see what rolling back to 4.0 would look like.
What I
      have seen is this. When I bring by BDC2 back on line, naturally I get
the
      PDC cannot be found error. But, when I look in server manager, I
cannot even
      see this BDC to promote it. What I wound up doing in the lab
environment was
      promoting BDC1 (which was online during the upgrade) to PDC. When I
did
      this, I immediately saw BDC2. I promoted BDC2 to PDC...all wnet well.
      
      What was strange was the fact that when BDC1 (formerly promoted during
      rollback) was demoted in the above step, it showed up as a 4.0 backup
domain
      controller but with the 2000 icon next to it, not the standard BDC
icon. I
      am concerned about this siince I want to have a rollback plan that
will work
      in the event of failure. Can anyone comment on why this spare BDC was
not
      recognized when I brought it back online after the simulated failed
upgrade?
      
      I also have one other question. I realize that during the upgrade
process,
      the old NT domain <called just that NTLAB> will remain as the netbios
name
      until the domain is switched to native mode. My question is this -
Once I
      upgrade the First PDC to 2000 - should it see itself as the newly
created
      2000 Domain/Forest 2000LAB or still see itself as NTLAB. Once it
native
      mode, will all machines then see the newly created/upgrade 2000LAB
domain ?
      (I am referring to the logon screen where it lists domains)
      
      Thanks
      
      
      



Relevant Pages

  • 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: after in-place upgrade sql need to re-join domain
    ... > user in SQL server, or on the machine which running SQL Server? ... > Based on your post, it seems that the NT domain Netbios name is domain.com, ... DCPromo during the upgrade. ... we call this issue as "Perioded Windows NT Domain ...
    (microsoft.public.windows.server.migration)
  • Re: Will FC4 test 1 version up when FC4 goes gold
    ... "server" you called it in your previous posting. ... Although an upgrade with yum should do. ... To which Alexander need not reply. ... you want to upgrade a running Fedora Core _server_ ...
    (Fedora)
  • RE: NT to 2K3 migration - Problem with existing NetBios NT domain
    ... upgrade of a PDC does not allow me to modify the NetBios name. ... > NetBIOS and DNS names, we call this issue as "Perioded Windows NT Domain ...
    (microsoft.public.windows.server.migration)
  • RE: NT to 2K3 migration - Problem with existing NetBios NT domain Name
    ... Based on my research, for NT has ".com" netbios name, that means the same ... NetBIOS and DNS names, we call this issue as "Perioded Windows NT Domain ... it is a bit difficult to resolve this problem and may ... Upgrade using a new DNS domain name. ...
    (microsoft.public.windows.server.migration)