Re: Why...Switch From AD Mixed to Native Mode?

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



Hello batfish,

1. sounds you are talking about functional levels, see here about all available options, including 2008 R2
http://technet.microsoft.com/en-us/library/cc771132(WS.10).aspx
2. do it for failover and redundancy, also make them DNS and Global catalog server
3. no, functional levels belong to the Domain controllers only
4. as a member server in the domain it will work
5. 2008 as member servers will work without any problem, for 2008 DCs you have to upgrade the forest/domain before with adprep commands


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


I have read many threads in the forum discussing how to go about
switching from Active Directory Mixed to Native mode.

But...I have not been able to discern why to do it. What are the
advantages/disadvantages.

My environment is as follows.

I have one NT member server outside of my LAN in a DMZ.

I am about to remove via DCPROMO my last two W2K AD domain controllers
leaving one master W2K3 Domain controller.

This W2K3 AD Server runs DNS and DHCP.

I have one W2K8 member server.

I have 6 other new W2K3 member servers.

One is running SQL 2005 server and another my Exchange 2K3 server.

I will not make either one of these servers a Domain controller
because it is not a good practice to.

I understand that it is a best practice to have at least one or two AD
domain controllers for replication of the schema.

I have 23 W2K pro and 70 WinXP Sp2 workstations.

So my questions are,
1) why change to native?
2) promote one or 2 of the new W2K3 servers before I demote the w2k
servers
3) do I need to remain in mixed mode to support the W2K workstations
4) do I need to be concerned about the WINNT box at all since it is a
member
server not authenticating or participating in AD.
5) should I involve the w2k8 server in any way.
Thanks in advance for your answers.

Robert.



.



Relevant Pages

  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... You should check the dirctory services event log and the system event logs for errors and warning in addition to running the dcdiag /c /v command. ... This event can occur if the domain controllers ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... You should check the dirctory services event log and the system event logs for errors and warning in addition to running the dcdiag /c /v command. ... This event can occur if the domain controllers ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... test network connectivity to local domain controllers. ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)
  • Re: Net logon error event id:3096
    ... Verifying that the local machine yblrtgswip1, ... Connecting to directory service on server yblrtgswip1. ... No record of File Replication System, ... interval between domain controllers. ...
    (microsoft.public.win2000.active_directory)
  • Re: GP to force Daily Restart
    ... The Security System could not establish a secured connection with the server ldap/DC01.corp.com/corp.com@xxxxxxxxx No authentication protocol was available. ... The network path was not found. ... domain controllers log these events every five minutes. ... every computer on the network must use DNS servers that can resolve SRV ...
    (microsoft.public.windows.server.sbs)