Repeated Characters when Typing in Remote Console

I’m attending a training class this week – vSphere Troubleshooting – and have used the vMA (vSphere Management Assistant) for the first time. In the lab guide we began by deploying the virtual appliance for vMA. One of the first steps said to define the “keyboard.typematicMinDelay” on our new VM. I wasn’t familiar with this setting, so I Googled it and found this VMware KB Article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=196

This setting resolves a possible issue where characters are repeated in the console when accessing it over a slow WAN link.  I’ve ran into this problem before, but never took the time to find a resolution.

Posted in Virtualization | Tagged | 1 Comment

Storage vMotion with Thin-Provisioning in PowerShell

In an earlier post I mentioned a script written by a co-worker to determine all of the non-thinprovisioned virtual machines.  This script is a follow-up to that, which allows actually uses storage vMotion to resolve the problems.  It is important to note that this script does not provide ANY error checking — if you try to move virtual machines to a datastore that does not have enough capacity you’ll be in trouble.  However, I have used this script to re-arrange many virtual machines and it was successful (I always verified I had enough target capacity before starting the script).

$dsView = Get-Datastore -Name "target-datastore" | Get-View -Property Name

Get-VM "vm-num1","vm-num2" | % {
$vmView = $_ | Get-View -Property Name
$spec = New-Object VMware.Vim.VirtualMachineRelocateSpec
$spec.datastore =  $dsView.MoRef
$spec.transform = "sparse"
$vmView.RelocateVM($spec, $null)
}
Posted in Scripting, Virtualization | Leave a comment

Get Thick Provisioned Disks

Another interesting PowerCLI script from today.  My proof of concept environment uses thin provisioned disks — this lets us have a lot more test machines than we really have disk space.   The other day we ran out of space — a new admin had been creating test machines for a project using oversized disks and thick-provisioning.  A coworker actually came up with this script to help find those disks so we could turn thin provisioning back on:

get-vm | get-view | %{
 
$name = $_.name
 
$_.Config.Hardware.Device | where {$_.GetType().Name -eq "VirtualDisk"} |  %{
 
if(!$_.Backing.ThinProvisioned){
 
"$name has a thick provisioned disk"
 
}
 
}
 
}
Posted in Scripting, Virtualization | 1 Comment

Guest OS Mis-match

I’ve been working on cleaning up my vSphere environment and found a very handy one-liner today.  The full article can be found here:

http://frankdenneman.nl/2009/12/impact-of-mismatch-guest-os-type/

I took the suggestions in the comments and came up with the following:

Get-View -ViewType VirtualMachine | Where { $_.Guest.GuestFullname -ne $_.Summary.Config.GuestFullName } | Sort Name |Select-Object Name, @{N=”InstalledOS”;E={$_.Guest.GuestFullName}}, @{N=”SelectedOS”;E={$_.Summary.Config.GuestFullName}} | Out-GridView
Posted in Scripting, Virtualization | Leave a comment

Server Cloning with Presentation Server 4.x

I’ve been reading up on requirements and performance information for virtualizing Citrix servers.  I’ve actually been P2Ving a few – to save my Citrix guys from having to reinstall a bunch of legacy apps.  Even though all the recommendations I can find oppose this method, it appears to be successful in our environment.  Since there are a lot of dependencies and overlap we are in the habit of creating a pair or three Citrix servers for each legacy app.  This gave us redundancy at the app level but gave us more servers than we probably really need (since many of these applications are not heavily used).

One of the articles I was reading linked to this article on scaling out Citrix VM’s by cloning them:

http://support.citrix.com/article/CTX107406

Going forward I may use this to assist with cleanup of these old P2V’s.  As time permits we may rebuild one server and then clone copies if the app is heavily used.  If its not heavily used, we will probably rely on VMware’s HA to provide redundancy in case of hardware failure.

Posted in Virtualization | Leave a comment