Sep/24
2008

To keep it straight, the guys at Citrix removed some drivers in the new release of Xenserver.
My test machine is a AMD X2 with a nforce 5 board and an AMD74xx chip on it for the P-ATA connections. In addition i've build up a software raid 5 with S-ATA drives for the SR where the VMs are stored and the system is on two software mirrored P-ATA drives. The boot from software raid in xenserver is allways a little tricky, not supported but still not too complicated (Dmitry Komarov wrote this together).
If your fresh upgrade or installation will continue to reboot after the initial splashscreen on and on again, boot from a live-linux (e.g. knoppix), build up a new init-ramdisk as Dmitry wrote in his howto, add up the module (in my case it was the amd74xx.ko) and be sure that the mkrootdev points correctly to your disk, the installation may have done this wrong (e.g. hde1 instead of hda1).

This was the first upgrade with 'problems' since 3.0 ...

Sep/18
2008

The team released the new version 5.0 of Xenserver (http://www.xenserver.com/). The first new thing you get see after the installation is a curses menu in wich you do the basic tasks without need of cli or the XenCenter. The upgrade from a 4.1 system works just fine. If you still have 4.1 or 4.0 servers you will enjoy the option to install the 4.1 XenCenter for compatibility. I'm going to test the new HA-features later these days.

Jul/31
2008

There is a malfunction when you try to install the new Agfeo-TK-Client 4.1.0 on a Vista machine directly. It doesn't start at all!
You can work around this with the following tasks:
- temporary giving the particular user local admin rights
- install the old 3.*-version of the client
- force a server-side update by starting it and let the server push you the right file

Jul/22
2008

A useless change was committed in the new version of RDP. If you want to connect into a console-session you have to give the option /admin instead of /console.
According to this you have to change your rdp-file
from "connect to console:i:1"
to "administrative session:i:1".

http://blogs.msdn.com/ts/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx

Jul/14
2008

If you have modified the logon.aspx from OWA and apply the SP1 Rollup 3, you will probably get a blank page if you try to login to your OWA. I fixed this by applying the Rollup 3 on another machine and copying the patched logon.aspx to the productive server.

It might also work if you update the logon.aspx by hand. You will have to change the links from 8.1.278.2 to 8.1.291.1, but i didn't test it.