Microsoft Windows 2003 Server Enterprise Ed.;XP on Steroids Without the Frills
Pros:
Support for multiple processors and serious amounts of RAM.
Cons:
You have to justify a shut-down or restart.
The Bottom Line:
So far, so good, but stay tuned as our migration gets underway.
|
|
Overall Rating:
|
 |
|
Author's Review
Reviewers Note: this review is intended for computer laymen who have a very good understanding of the terms used throughout this review, and a broad understanding of Operating System technology and terminology.
The company I provide consulting service for has a very large Windows 2000 Active Directory (AD) forest that covers the entire country. And region by region we are converting to Windows 2003, Enterprise Edition. Why the switch? Simple, our server and application needs have outstripped the current capabilities of Windows 2000 Advanced Server, our platform of choice. In the future we may need the robustness of Windows 2003, Enterprise Edition’s multiple processor capabilities. Windows 2003, Enterprise Edition offers the following higher functionality:
• Eight-way symmetric multiprocessing (SMP): Windows 2003, Enterprise Edition, supports up to eight processors in a single system or partition.
• Eight-node clustering Server clusters up to eight nodes are available only in Windows 2003, Enterprise Edition, and Windows 2003, Datacenter Edition.
• Support for 64-bit computing platforms capable of supporting 8 processors and 64 GB of RAM with the 64-bit version.
• Support for up to 32 gigabytes (GB) of RAM.
• Support for Intel Itanium-based computers.
Installation:
I have been tasked with evaluating the Windows 2003, Enterprise Edition Network Operating System (NOS) for our region. I installed the NOS on a simple Micron PC 2.4Ghz PC with a 40GB HHD, 512MB of RAM onboard. Those familiar with the Windows XP installation process will feel right at home; only difference: there is no accessories install sub process (more on that later). The installation process, not unlike Windows XP took approximately 40 minutes to complete.
When the install was complete the NOS came up as excepted, but some drivers were missing; i.e. network, sound card and motherboard sub-system. I installed the drivers from the original manufactures OEM CD’s without incident. Note: I could not find a Hardware Compatibility List (HCL) for Windows 2003, so be prepared with drivers for your hardware. It is important to note that Windows XP would have installed the drivers. The Window 2003 desktop is short of frills; gone are the rich graphics and plush desktop schemes of Windows XP. After the installation approximately 2.5GB of hard drive space was consumed.
First Impressions:
This is a serious NOS, groomed for applications, file & print services, and heavy database number crunching. This is not an OS for gamers, or those interested in word processing and or surfing the web. Even on this single processor, 512MB of RAM system, the NOS is fast.
Under Windows 2000 the installation of server applets such as Windows Internet Naming Service (WINS), Dynamic Host Configuration Protocol (DHCP), and Domain Naming Service (DNS), was accomplished during the installation of the NOS, but under Windows 2003, Enterprise Edition, you decide after the install is complete and the NOS reboots into the management interface that suggests roles for the server, such as file & print, application, web server, active directory services, terminal services etc. I prefer to make those choices during the installation of the NOS; less work after the system reboots. Choosing to install the applets is simple and straightforward.
Installation of Internet Information Server (IIS) 6.0 (new version) is an option to include with Windows Server 2003 Enterprise Edition. If you plan to install Exchange server you will need to install IIS 6.0 as well.
Funny thing happened on the way to shutting the system down: I was asked to explain why! The system cannot be shut down without a reason chosen from a dropdown box and a corresponding comment! Annoying! Choices include “hardware installation” and “scheduled maintenance.” I am not sure why we should now have to justify shutting down the system, but.
Overall I am pleased with Windows 2003, Enterprise Edition. I have thus far installed three instances of the NOS with no problems. Stay tuned for regular updates from the field as it were, as I forge ahead with our migration from Windows 2000 Advanced Server to Windows 2003, Enterprise Edition.
CompuVest
