How to switch windows server 2003 to native mode

Because each upgraded DC will continue to interoperate with the others, you can take your time with the upgrade and not be concerned with an immediate domain restructuring. Using Windows Server in mixed mode takes away a lot of the flexibility you would otherwise have in structuring your Windows Server domains. Some of the Windows Server features mixed mode does not support include: Nested security groups although nested distribution groups are supported Universal security groups SID history The domain controller rename tool Because of its limited functionality, Windows Server mixed mode is useful only when Windows Server must be introduced into an existing Windows NT domain or when cross-domain functionality is needed for one or more existing Windows NT domains.

Where no Windows NT domains are present, you should consider one of the other three modes, starting with Windows Server native mode. Windows Sever native mode eliminates the restrictions imposed by Windows NT compatibility.

Unlike mixed mode, native mode supports universal groups, nested groups, conversion between security and distribution groups, and SID history to allow migration of security principals from one domain to another. Moving to native mode disables NT domain controller emulation, however, removing the capability for replication with Windows NT domain controllers. In addition, Windows clients earlier than Windows must use the add-on Active Directory client software to enable interaction with the Active Directory.

Moving up to native mode also provides for greater security because you can switch to Kerberos for authentication of Windows or later clients. Windows Server native mode is the choice to make when your Windows Server domain controllers must function within an existing Windows domain or when Windows DCs will be introduced into the Windows domain, if only temporarily.

Windows Server modes Windows Server introduces two additional Active Directory modes, the first of which is Windows Server interim mode. Interim mode is available only when upgrading the first Windows NT domain to a new forest and supports Windows NT and Windows domain controllers.

Interim mode does not support Windows DCs. Interim mode provides much the same capability as Windows mixed mode, with a few improvements for replication.

Interim mode is intended solely as a stop-gap to provide compatibility with NT domains until they can be upgraded to Windows or Windows The fourth Active Directory mode is Windows Server , which you can consider to be Windows Server native mode although it isn't called that to avoid confusion with Windows native mode. Windows Server mode offers some very useful enhancements, including all of the improvements inherent in Windows native mode. Windows Server mode also supports the domain controller rename tool, making it relatively easy to rename domains and domain controllers.

Select multiple user objects. Modify attributes of lots of user all in one go. This feature actually works like NT 4. For a variety of reasons, multiple selection was not availably in W2K which made it tedious to change several users home directory in one operation. Drag-and-drop ability. One irritation of W2K is that you cannot drag and drop users and computers between OUs. This has been corrected in the latest Active Directory. Save your queries. Tip save search queries that you use often in Active Directory Users and Computers, it saves time when you have to repeat the query later.

Application directory partitions. Universal group membership cached. Avoid the need to locate a global catalog across a WAN link during logons by storing user universal group memberships on an authenticating domain controller. Domain rename. Rename any domain in the Windows Server forest. Domain controller rename tool. Forest trusts.

Create a two way transitive trust to join two forests. Very useful for amalgamating companies. Replication enhancements. To determine which mode your Exchange organization is currently running in:. Start Exchange System Manager.

Before you can change an organization from mixed mode to native mode, all of the computers in the organization must be running Exchange Exchange Remember that this change to native mode cannot be reversed.

After you upgrade or remove all versions of Exchange Server prior to Exchange , you can switch your Exchange organization to native mode by using Exchange System Manager:. Exchange Mixed Mode An organization running in mixed mode can accommodate all versions of Microsoft Exchange. Exchange running in mixed mode is subject to the following limitations: Exchange Server 5. Administrative groups are mapped directly to Exchange Server 5.

Servers cannot be moved between administrative groups. Routing group membership consists only of servers that are installed in the administrative groups.