Windows Server 2008

Windows Server 2008

Summary: Windows Server 2008 is easier to install and manage than previous versions, and has many new and improved features that should encourage organisations to upgrade.

SHARE:


Server Core


Windows Server 2008 includes a ground-breaking new installation option called Server Core that installs a Windows Server system with a minimalist graphical user interface (GUI) and a limited set of roles. This requires much less RAM and patching than a normal Windows system. Microsoft estimates around half the RAM than an equivalent GUI version, and 40 per cent fewer patches than an equivalent Windows Server 2003 configuration. Customers have long complained about the need to install numerous patches to Windows servers, and it appears Microsoft has taken heed.

The downside to Server Core installations is largely short term. IT staff will need additional resources and training to learn how to install, configure and manage applications running in the Server Core environment.

Server Core installs a Windows Server 2008 system with a minimalist graphical user interface (GUI) and a limited set of roles.

In ZDNet UK's lab tests, we installed an Enterprise Edition Server Core system from the normal installation utility. Unfortunately there's no way to convert an existing system between a Server Core and full GUI-based configuration. The installation utility proceeded in the same way as for the GUI versions of Windows. Likewise, we needed to set a strong password before we could log into our Server Core system for the first time. Once logged in we found that basic networking was enabled. For example, we could ping another device on our network. But as with the other versions of Windows, Windows Firewall was configured to block all incoming connections except Core Networking services, such as handling router broadcasts.

However, one of the useful things about Server Roles-based installations is that, in addition to installing the necessary software components, the Server Role installation tool reconfigures the Windows environment to work with the applications that make up the role. So in order to make a functioning IIS7 system, we needed to type only one command into the Server Core CLI to install the software and reconfigure Windows Firewall.

For a default installation of IIS, we typed the following at a command prompt and pressed "ENTER":

start /w pkgmgr /iu:IIS-WebServerRole;WAS-WindowsActivationService;WAS-ProcessModel

With setup complete, Windows started the IIS service automatically — all we needed to do was connect to the server via a web browser and confirm that IIS was working normally. To select specific IIS modules for installation would have involved typing the name of each required module on the command line, which would probably have resulted in a much longer command.

Next, we reconfigured Windows Firewall to allow incoming connections to the Microsoft Management Console using the following command:

netsh advfirewall firewall set rule group="Remote Administration" new enable=yes

At this point you can run Computer Manager on a Vista SP1 desktop or another Windows Server 2008 system and connect it to a Server Core environment. However, only a subset of management tasks can be performed using a remote MMC connection to Server Core. For example, you can't use Computer Manager to add or remove roles or features. The following command enables management via a remote desktop:

cscript C:\Windows\System32\ Scregedit.wsf /ar 0

Although this would be useful in many datacentre environments to provide remote access to Server Core systems, it's not a solution to the problem of using scripts and text-based commands to manage a Server Core system. The command enabled our Server Core desktop to be accessed remotely from a Terminal Services client, but the remote desktop was just as spartan as the local one, with only a command prompt, Task Manager and a few other graphical tools available.

We also tested Server Core running in a virtual machine hosted by VMware Workstation 6, so we wanted to install the VMware Tools utility into our system. We found that the normal method of installation using the VMware 'Install VMware Tools' menu item didn't work. However, having selected this menu item, we used the command prompt to install the software by changing to drive 'D', which was the local drive letter assigned to our DVD drive. From here we found it best to copy the software to a directory on the 'C' drive and execute the 'VMWare Tools.msi' file from the command line.

At this point the installation utility launched properly and we could use its graphical dialogue boxes to begin the installation. Unfortunately the installation utility froze near the end of the normal process, so we waited a few minutes for disk activity to stop and then 'Cancelled' the VMware Tools installer and forced a reboot of the system.

We found that some elements of VMware Tools had indeed been installed correctly. Although there are reports that some beta versions of Windows Server 2008 need VMware Tools to be installed for networking to function, the network connections on the launch version worked without requiring this step.

 

Specifications

There are currently no specifications for this product.

Prices

There are currently no prices available for this product.

Topics: Operating Systems, Reviews, Servers

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

0 comments
Log in or register to start the discussion