Re: Keeping NT4 servers in 2003 Native Domain



Thanks for responding Jason.

I thought I was pretty clear in describing the NT4 servers as Member servers
in the 2000 Native Mode domain. They are not BDCs.

"Jason Tan (MSFT)" <v-jasont@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ZbsRD8gMGHA.3504@xxxxxxxxxxxxxxxxxxxxxxxx
Hello,

Thanks for posting!

I suspect you are using Windows 2000 mix mode other than Windows 2000
native mode since you still keep Windows NT 4.0 BDC. Windows 2000 native
only Support Windows 2000, Windows Server 2003 domain controllers.
Additionally, you cannot keep Windows NT 4.0 BDC in Windows Server 2003
mode since Windows 2003 mode only support Windows Server 2003 domain
controllers.

For more detailed information please refer to the following article:

How to raise domain and forest functional levels in Windows Server 2003
<http://support.microsoft.com/kb/322692>

Hope the information helps.

Best Regards,

Jason Tan

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: "Charles_B" <charles.a.braun.spam@xxxxxxxxx>
| Subject: Keeping NT4 servers in 2003 Native Domain
| Date: Tue, 14 Feb 2006 17:03:15 -0800
| Lines: 18
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-RFC2646: Format=Flowed; Response
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| Message-ID: <OXw3aucMGHA.1536@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: 204-89-11-x-cityofpasadena.net 204.89.11.103
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:22485
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Hi,
|
| We are about to upgrade our Windows 2000 Native Mode domain to a 2003
| domain. The current single 2000 DC will be replaced with 2 2003 DCs and
we
| would like to run in 2003 native mode.
|
| Currently in the native 2000 domain are 2 NT4(SP6a) member servers that
must
| remain NT4 for various reasons.
|
| My question is is there anything I need to watch out for do before hand
to
| ensure that these NT4 servers continue to function properly in a 2003
native
| domain?
|
| Thanks
|
| C
|
|
|



.



Relevant Pages

  • Re: Keeping NT4 servers in 2003 Native Domain
    ... The switch to native mode only affects the replication between the NT 4.0 ... BDCs and the AD DCs. ... I thought I was pretty clear in describing the NT4 servers as Member ... I suspect you are using Windows 2000 mix mode other than Windows 2000 ...
    (microsoft.public.windows.server.migration)
  • Re: URGENT! Legacy clients logon and connection unstable problem
    ... The new functional level is native mode, Older versions of windows might not ... > I do not have any other servers in the LAN - only clients! ... > |> I found that several minutes after the client machine starts I can ...
    (microsoft.public.win2000.security)
  • Re: Exchange 2003 Native Mode Benefits
    ... Microsoft Exchange Support ... to a Windows 2003 native mode domain and/or forest prior to implementation. ... I am upgrading my FSMO servers to Windows 2003 this weekend and my AD will ...
    (microsoft.public.exchange.design)
  • Re: SRS and ADC
    ... You can't switch to Native mode until you have removed all the 5.5 ... Groups or Sites with no 5.5 servers and an SRS, ... You can change your Windows Mode to Native at any time that you have ... 2003, or Exchange 5.5 have no dependencies on the Windows mode, so Native ...
    (microsoft.public.exchange.setup)
  • NT4 Client Win2K3 AD Domain
    ... About 6 months ago we upgraded our domain from NT4 to Windows 2003. ... We have only 3 NT4 servers left ... account is listed as "Account Unknown" followed by the SID. ...
    (microsoft.public.win2000.active_directory)