Working With Virtual Machines

After you have configured the necessary settings, the virtual machine is ready for use. The next step is to install the guest operating system. Optional settings for performance or behavior, for example, include the boot device order, the number of processors the virtual computer should have and the maximum workload of the machine.

No VMware, no BIOS: The configuration settings are chosen through a menu.

Choosing the number of processors. The VM supports a maximum of 8 CPUs.

Network diagnosis made easy: The MAC address is user definable.

The additional Integration Service can also be deactivated if any problems occur.

Since the virtual machines are primarily used in server environments, there are separate configuration options telling the VMs what to do when the host system starts up or shuts down. This allows the virtual machines to save their current status (similar to a normal Windows PC's hibernate functionality). When the host system has restarted, guest systems can be restored to their previous status, including all open and running applications.

Automatic start actions...

...and automatic stop actions for the virtual machine.

You can either install the guest system from a CD/DVD or from an ISO image. The guest system felt very snappy without requiring any additional tools. Thus, the VM doesn't feel as "sluggish" as those of the direct competitor, VMware.

Installing the guest OS

Support for multiple CPUs

Web Server: IIS Version 7

Windows Server 2008 comes with the new version 7 of the Internet Information Services (IIS). Basically, this comprises a Web server package and is thus a direct competitor to the Apache Web server project.

The advantage of Microsoft's solution is the option of using ASP (Active Server Pages) to create dynamic Web pages - without having to install additional software. Thanks to the integration of .NET components, this language has become powerful and versatile. However, in the past the IIS has been plagued by security issues, although this has improved over the past years.

The Server Manager directly after the installation of the IIS

Compared to its predecessor, the configuration of the IIS has been greatly simplified. All settings are now found in the Server manager and the required services as well as the available options are clearly listed.

Overview of the installed components

Settings for the default HTML page

The IIS Manager in version 6 as it was used in the Windows Server 2003 was much less clearly structured and much harder to manage.

Complicated configuration with the old IIs 6 under Windows Server 2003

The SSH Replacement - Windows Remote Shell

Even if there isn't an SSH server integrated into Windows Server 2008, at least Microsoft introduced the Windows Remote Shell. It allows remote command line access over an encrypted connection and uses the SOAP protocol.

Before the Remote Shell can be used, it needs to be activated first by typing in the command WinRM quickconfig.

Configuring the Remote Console for external access.

The connection can be established from other Windows Server 2008 machines or from Windows Vista systems. If the computers are not logged on to the same domain, the server has to be added to the TrustedHosts first.

Adding the server to the TrustedHosts.

Finally, a connection can be opened. It is possible to have the remote system execute only a single command or use the command line interactively, as you would on your local system.

The remote shell lets you execute a single command remotely...

... but also lets you log in to the command line for interactive use.