In this article I provide the final steps how to virtualize a Windows Server 2008 installation.
You probably run into the same problem that Windows Server 2008 won’t be able to recognize the virtual hard disk you have planned to installed it on. Get the corresponding SCSI drivers as floppy image from the VMware site. Select the image and connect the drive.
Now say ‘Browse‘ and choose drive ‘A:‘ – don’t forget: After selecting the .flp image you also have to connect the drive. Otherwise Windows cannot read the device.
Click on ‘Next‘ and after a few seconds the hard disk will be found. The currently available drivers for Windows Server 2003 seem to work fine also for Windows Server 2008.
Installing the VMware Tools might be a good idea. You can find the image at /usr/lib/vmware/isoimages/windows.iso or just install them from the VMware management console’s menu. While the image is mounted go to ‘Device Manager‘ and install the drivers for the network adapter which probably does not work yet.
In a previous post, I told about he first steps in virtualizing a Windows Server 2008. In this article I describe how to proceed after, the request for my own RIPE subnet was approved. Now I can concentrate on the next point: Installing VMware. Since I want to set up this machine for visualization, I have to perform a few steps first. That way, this post will be mostly about my fight with Debian Linux which is the host system.
After logging in, I just realize that updating the package database might be not the worst idea. Consequently, I do so and install some Norton Commander like tool for real men
apt-get install mc
This actually makes things much easier.
Now, I have to activate IP forwarding in /etc/sysctl.conf by the adding
and bringing the additional IP on the host system by adding
up ip add 192.168.1.1/29 dev eth0
to /etc/network/interfaces. Additionally, I have to add some host-route (by using my gateway 192.168.0.1) so my new subnet is reachable by adding
to eth0 in /etc/network/interfaces. Installing iproute by a
apt-get install iproute
restarting the interface by calling
finally makes my IP ping-able. Quite a fight so far if you don’t do this on a regular base. Additionally I installed the powersave package and reconfigured several settings to increase the performance in /etc/powersave.
I just got the tip to put my virtual machines to the separate disc. Since I have one spare 400GB disc. I have to create some partition and to format it.
cfdisk /dev/sdb mkfs -t ext3 /dev/sdb1
Let’s create some directory for the virtual machines and mount the disc
mkdir VMsmount -t ext3 /dev/sdb1 /Vms
Now some final tweak at /etc/fstab by adding
/dev/sdb1 /VMs et3 defaults 0 0
and I am done.
Finally I start installing the VM. I was pointed to some German How-To written by Till Brehm which is includes quite detailed instructions.
Some prerequisites are required before I start. I do the required 220 MB update by
VMware can be downloaded from http://www.vmware.com/download/server/. I skip the management console since I will use it on my Windows workstation and focus only on the server and management interface binaries using:
wget http://download3.vmware.com/... tar xvz VMware-server-*.tar.gz cd vmware-server-distrib ./vmware-install.pl
Now, I simply accept the defaults for the following installation. only at one point I had to tell the script that my virtual machines will be located at /VMs. No I have to continuing with the management interface
tar xvfz VMware-mui-*.tar.gz
The Web-based management interface seems to work perfectly after installing.
After installing the management console on Windows I run into some trouble. During compilation of the corresponding modules, the VMware script was not able to start the inetd service. Therefore, I was not able to connect to the VMware server. After restarting the service manually it worked perfectly and I set up my virtual machine.
Now, I have to copy the installation files for the Windows Server 2008.
Nick White recently announced the Windows Search 4.0 Preview. The description of the Remote Index Discovery seems to be promising.
The first positive improvement after the installation I realized is a ‘Pause’ button at the ‘Indexing options’. A tray icon, for convenient pausing the indexing, as I did know from the early versions of MSN Desktop Search or Microsoft Research’s Stuff I’ve Seen, is not provided.
On the Windows Server 2003 installation, I find a tab at the ‘Advanced Options’ allowing me to add UNC locations. Since I had no Desktop Search running on my server before I am not sure if this is some new feature.
So far, I haven’t found anything about the Remote Index Discovery, yet. However, I will follow up the development of the Desktop Search in the future.
This update finally supports the new file formats of Office 2007 on your mobile device:
To allow Windows Mobile users to work with Office documents created in the Open XML formats, Microsoft has developed an upgrade for Word Mobile, Excel Mobile, and PowerPoint Mobile applications. This upgrade to the Office Mobile applications allows viewing and editing of Word documents and Excel workbooks and viewing of PowerPoint slideshows created by using Microsoft Office 2007.
Other improvements include:
• Enhanced viewing experience for charts in Excel Mobile.
• Ability to view SmartArt in PowerPoint Mobile.
• Ability to view and extract files from compressed (.zip) folders.
The update need approximately 7 Mb on your device. Therefore, I would recommend using a memory card for the installation.
While charging an iPod on a Windows Vista system without having iTunes installed, you might face the issue that the iPod is not willing to play any music as long as it is charging. Therefore, simply choose Safely Remove Hardware from the Vista task tray.
There you select Generic volume and click Stop. In the second dialog do the same, select Generic volume and click Stop.
After a few seconds your iPod will re-start and awaiting your commands while it is still charging.
I am working on a user interface (UI) for a client tool of our current project. Though, the last two have been a epic battle fighting with a various of minor things. However, each and every of these things does cost a remarkable amount of time.
Starting with WPF many developers will spend mcuh time with skinning in WPF. It’s a cool thing, but you should leave these things to designers. It is a enormous time sink. You make huge progress in the beginning but end up with endless fine-tuning in the end. The first have a look at the Windows Vista User Experience Guidelines. The really thing: you don’t have to read everything online, just download the 630 pages as PDF document. You will see that skinning should be used carefully. Much more important are some new guidelines to keep in sync with the Vista UI. BTW: if you are looking for the Vista icons you should have a look here (but I haven’t told you that and so use them only to inspire you by creating own icons).
In my case, I also had to use strong-named assemblies since they are used within VSIP packages. You will realize that the VistaBridgeLibrary uses friendly assemblies, Junfeng gives a short introduction into friendly assemblies. You’ll discover that is not as easy since there have been some changes in Visual Studio 2005. Adrian figured out how it works. David cover’s the further steps and also provides a small tool to obtain the public key token of a signed assembly ready to be copy ‘n’ pasted into your Assembly.cs file.
“The Microsoft® Windows® Software Development Kit (SDK) Update for Windows Vista provides documentation, samples, header files, libraries, and tools designed to help you develop Windows applications using both native (Win32) and managed (.NET Framework) technologies. This release of the SDK supplies”