I’m working for Xylos as you might have read on my about page. At Xylos we are constantly looking for new colleagues. Have a look at the list of current job offerings or consider a spontaneous job application instead.

If you prefer a more informal approach, or you’d like to watch the new “The Three Musketeers” movie, than you might be interested in our job event:

Date: Saturday, 1 October 2011
Time: from 09:30 till 13:30
Location: Utopolis Mechelen

As a matter of fact I will be present myself, but I’d like to see some people to come and talk to me.

Check out http://www.xylos.com/musketeers/ for more info.

Note: you can do me a favor by referring to me during your application.

$vCenter = Connect-VIServer -server(Read-Host "Please enter the name of your vCenter Server.")
$Cluster = Get-Cluster -Name (Read-Host "Please enter the name of the cluster whose servers need to be reconfigured.")
$vSwitch = Read-Host "Please enter the name of the vSwitch on which the portgroups need to be created."
$PGfile = import-csv -Path (Read-Host "Please enter the path to the csv file with the new portgroups to be added to the vSwitch")

$Cluster | Get-VMhost | `
Foreach{
$vSwitch = Get-VirtualSwitch -Name $vSwitch -Vmhost $_
$PGfile | `
Foreach {
$vpg = New-VirtualPortGroup -VirtualSwitch $vSwitch -Name $_.PortGroupName
Set-VirtualPortGroup -VirtualPortGroup $vpg -VLanId $_.Vlanid
}
}

Disconnect-VIserver -Server $vCenter -Confirm:$False

The script asks for

• vCenter IP or FQDN
• Cluster Name
• vSwitch name
• Path to the csv file

The csv file contains the portgroup names and vlanid’s.

PortGroupName,Vlanid
VLAN900,900
VLAN901,901
VLAN902,902

We saw this issue on all our Terminal servers once they were joined to the domain. We finally nailed down the cause of these problems to be an group policy who configures the language settings.

Apparently this GPO changed also the language settings for the local system account. Which caused these services not to start anymore.

Pieter Wigleven posted already about a similar problem he had with Hyper-V and how he fixed it.

Update: Microsoft released a hotfix for this problem: KB951430.