Tool: Tripwire Config Check for ESX 3.0 and ESX 3.5


Download de tool hier:

Daarna pak je de zip file uit.


Mocht je onder Vista werken zoals ik, dan moet je de configcheck.bat starten met Administrator rechten.

Even de license agreement accepteren.


Nu kun je de esx host opvoeren en op check configuration klikken.


Ik heb deze test gedaan op een ESX 3,5 VM die net was geïnstalleerd. Ik had root access voor ssh nog niet aangezet en kreeg daardoor de volgende foutmelding.


Gelijk even PermitRootLogin op Yes gezet


en /etc/init.d/sshd restart uitgevoerd.

Nu kon de test uitgevoerd worden.


Nadat de test klaar is kun je via de onderstaande link de Remediation Guide aanvragen.

VMware: Citrix on VMware Recommendations

Sven Huisman heeft weer een goede post geplaastst op zijn weblog.

Verron Martina from VMware dropped me an e-mail with a lot of recommendations for running Citrix in a VI3.x environment. These recommendations come from other system engineers from VMware working in the field. Thanks Verron, for sharing this.

Technical Recommendations:

  • I used the ballooning driver. Some Citrix forums will tell you not to use it but for us the ballooning driver made a complete difference.
  • Start by using only one vCPU per VM and if possible use affinity to make sure that the VM is not running on the same core as the console or another VM.
  • The sweet spot we found was to assign only 2GB to the VM and something between 30 and 40 users per VM.
  • Our target was not to beat a physical CPS server with a single VM but get more aggregated users using 2 or 3 VMs (depending on the number of cores available) with no more than 40 users per VM. Do not over commit the cores as that will lose advantage.
  • The final target for us was to demonstrate that the VMs running simultaneously on the same physical server can get a higher number of users (between 70 and 90% more) than a normal CPS installed on the same HW while user experience (keyboard-screen response times, login times, app launch times, etc) are very similar.
  • Some times we have to be patient and wait a few minutes for the VM to get steady, then the magic shows up and the VMs will surpass the physical server regarding load tolerance.
  • Regarding login times, the VM can show longer times; however, once the user is in, the VMs will look fast. Check than DNS servers are not getting messy as this is commonly the problem with long login times.
  • Make sure that the network interfaces are using fixed speed when connecting to the network, do not leave auto negotiated speeds. The best is to use 1000 mbps FULL DUPLEX. :-s
  • Use one virtual disk for Windows and CPS and a different virtual disk for Windows paging of the same VM.
  • When installing VMware tools use a custom installation and remove the shared folder feature. This is very important as Citrix seems not to like that and it is a useless feature on ESX as it’s meant for Workstation.

  • Follow VMware’s best practices for performance tuning on ESX (
  • Build your template Citrix virtual machine from scratch (don’t convert an existing physical server).
  • Use a single virtual CPU for the template vm
  • This will allow the Windows operating system in the guest to use a uni-processor HAL, as opposed to a SMP HAL, streamlining the guest operating system.
  • Configure the template vm for 2-4 GB RAM..
  • Configure separate virtual disks (VMDK files) for the operating system and the pagefile.
  • Ensure you align the NTFS partition in the VMDK prior to the Windows installation in the guest (at Netapp –;  at VMware –
  • Use a 64-bit Windows installation. :-s
  • Have an understanding of what an ‘acceptable’ threshold of users will be… Some customers see an increase in the number of users per Citrix instance when virtualized, some see fewer.  You should go into it with the expectation that you may get fewer users, as well as what you would like to see (ie 80% of physical or better?  70%?).


Bear in mind that even if you get fewer users per vm than in a physical environment, there are many other benefits to using virtualized Citrix servers:


  • One of the things many Citrix shops struggle with is their deployment process – how do we maintain an up-to-date image for the farm that incorporates the required applications and accommodates the hardware in question… rolling out Windows, including updates and patches, and the Citrix software (though this could be handled by Citrix Installation Manager).  Either way, you are maintaining server images somewhere  either through the use of a complicated installation script, or through imaging software such as Ghost.
  • Deploying a virtual machine through the use of templates is far quicker and more efficient than any other physical imaging process you might have used.  VMs can be deployed in a matter of minutes using templates.  The templates themselves can be created from existing virtual machines, and can be copied and used with VMware snapshots or SAN/NAS snapshots, giving you the ability to easily maintain a library of templates for different types of operating systems, applications, etc.

Disaster recovery:

  • Setting up a Citrix farm to failover to another site requires a large investment in hardware, and man-hours to configure the remote site to handle all the applications necessary.  Furthermore, the hardware in the remote site has to be of the same type as the primary, or your deployment strategy has to take hardware differences into account.
  • Using virtual machines, all you need to do to enable a DR site is have a copy of the required virtual machines in the remote location – hence you only need to set up the farm once, and maintain a copy of it in the remote location.  Spinning up your DR or business continuity site is a matter of ‘powering up’ the virtual machines.  VMware Site Recovery Manager may even help automate that process.


  • Since the citrix system is accessed by users like a PC on a regular basis, a Citrix server is more prone to failure than a regular server (though, with proper maintenance, hopefully less prone than a desktop).  Server outages mean lost productivity for your users, and a significant effort in troubleshooting the problem, since Terminal Services is a good deal more complicated than a regular server.
  • To properly design for the outages we know we will have, you have to have extra capacity in the farm to handle the overflow users when one of the servers is down.  This is true for both planned and unplanned downtime.
  • VMware ESX has been recognized in the industry as one of the most stable platforms to be introduced… ever.  This means fewer outages due to host failures.  Also, since we standardize and virtualize the hardware of the guest operating systems, this holds true across different hosts, enabling your virtual machines to run across hosts from different manufacturers and chipsets.
  • See

Application Deployment:

  • Many Citrix shops do a good deal of work maintaining multiple images – deploying applications in ‘stovepipe’ configurations…  that is to say, multiple small groups of Citrix servers, each dedicated to a specific set of applications.  Frequently, this is due to largely due to application incompatibility.  However, it results in the Citrix admin being required to maintain several different images for the Citrix farm.
  • Even if the shop has standardized on a single Citrix image, they will not be using the company’s standard application deployment methodology…  Terminal Services is too funky with regards to application deployment, and requires much handholding.  Most Citrix shops has compeletely separate processes for packaging applications for a PC versus a Citrix server.
  • VMware ThinApp ( can be used to image your applications separately from the Citrix image… In fact, an application that has been packaged with ThinApp on Windows 2003 will work on Terminal Services, Citrix, Windows XP, and Vista, eliminating the need to package that application for the different platforms.  Furthermore, ThinApp includes a ‘sandbox’ to prevent applications from conflicting with each other.  You simply place the packaged application on a file share on the network, accessible to the Citrix servers (or PCs, or both), and you are done.  Your users simply execute the application from the shared directory, and they are off and running.  This results in a win-win for the customer – the ability to package an application once, and use it for either a PC environment or a Citrix environment.


VMware: Clustering VirtualCenter 2.5 with MSCS

Eric Sloof heeft een document op zijn blog geplaatst over hoe je VC 2.5 kunt clusteren met MSCS. Dit document is geschreven door Chris Skinner een Technical trainer van VMware.


This paper documents the steps to successfully implement a high availability solution for VirtualCenter 2.5 using Microsoft’s cluster services. There are some basic requirements to start the process. Microsoft requires Active Directory for cluster services. Additionally, Windows 2003 Enterprise server or higher will be necessary. This document was compiled from several sources. It demonstrates creating a VC cluster on the same ESX host (cluster-in-a-box) with a SAN-based quorum disk. The hyperlinks at the end of the document has more detailed information for other types of configurations, such as, cluster-across-boxes and physical-to-virtual.


Chris and Eric, thanks for sharing


VMware: Deploying VI with Cisco

Anyway, so what better time is there to announce the publication of an in-depth deployment paper jointly authored by Cisco and VMware. We posted this paper about a week ago on the site. It’s around 90 pages, so no short read; but it delves into many of the considerations, architectures, etc in deploying VI with Cisco switches.

Download de pdf hier:



VMware: Recreating Missing VMDK Descriptor Files!

Paul Shannon heeft een post geschreven over hoe je VMDK descriptor files kunt aanmaken.

A few times over the years VMDK files have been ‘lost’ when a customer has had to shutown their storage in a less than graceful fashion.

In every case so far, touch wood, it is only the desciptor files that have been deleted so the raw data is still present in the *-flat.vmdk file.

It is actually quite simple to rescue the situation you simply restore from backup. Ahaha what if you do not have a backup, then there is another way.

Lees de rest van de post hier:

NetApp: Open Systems SnapVault for VI3


Paul Shannon poste het onderstaande op zijn blog:

OSSV installs directly into the VMware ESX service console and acts as a very light-weight interface to backup Virtual Machines on NetApp storage and non-NetApp storage. It works best with NetApp Protection Manager, but works well as a stand-alone product.  There’s also an excellent Best Practice guide for OSSV available here.



VMware: VCB Demo

Over at VMware Learning they have what I call a “secret” video that they don’t promote. This 15 minute video covers how to implement, configure, and use VMware VCB. This video is hard to find so I wanted to share it with all of the VMware Video readers! Click on the video icon to check it out!

You can watch the video over here: vcb-live-demo


VMware: Podcasts

Introduction to Virtualization

Rob and Jaleh from our product marketing team give a gentle quick overview of this whole virtualization thing. It’s a six minute intro even your boss will get, although it’s probably not quite right for your Mom.


Server Consolidation

  • 5/12 – Server Consolidation using VMware Infrastructure
  • 5/19 – Building an Adaptive Infrastructure with VMware and HP
  • 5/26 – Server Consolidation Best Practices with VMWare and HP

    VMware VDI

    • VMware VDI Podcast: Desktop Virtualization in Global Enterprise
    • VMware VDI Podcast:  Customers Success VMware VDI Podcast: The Desktop Revolution
    • VMware VDI Podcast: Thinstall 


    Download the podcasts here: