Can you cite some conventional errors that are usually formed when the Administrators established DNS on a network with a single Windows 2000 or Windows Server 2003 domain controller? What if the Administrator did not established the DNS correctly? And also, why do I have to indicate my domain controller on its own for DNS?
Windows 2000 and Windows Server 2003 Domain Controller
Upgrading to an Equivalent Operating System
A first step in choosing the best operating system is determining the nearest equivalent to what you are now running. The Web Edition, which is ideal for rack-mounted Web support deployments, is a completely new operating system, and so it doesn’t have an equivalent in the Windows 2000 family of operating systems.
The other Windows Server 2003 operating systems map directly to existing Windows 2000 operating systems, as shown in Table 1.
Windows Server 2003 Family
|
Windows 2000 Server Family
|
Standard Edition
|
Windows 2000 Server
|
Enterprise Edition
|
Windows 2000 Advanced Server
|
Datacenter Edition
|
Windows 2000 Datacenter Server
|
Web Edition
|
No Equivalent
|
Table 1 Upgrading to an Equivalent Operating System.
Note that you can only upgrade to an equivalent or higher operating system. You can’t “downgrade” to a less powerful operating system, as some functionality might be lost in the process.
This means you can’t move from Windows 2000 Server (or other server products in the Windows 2000 family) to the Windows Server 2003, Web Edition without removing the earlier operating system and performing a new installation.
Also note that Datacenter Edition—which provides an integrated hardware, software, and service offering—is not available as an upgrade. It can be purchased through the Windows Datacenter Program and is delivered by Microsoft and qualified server vendors, such as original equipment manufacturers (OEMs).
For more information, see Windows Server 2003 Support or the online Product Documentation for Windows Server 2003.