Recently a colleague had an issue where they were unable to add a newly built ESXi 4.1 server to vCenter; it failed with the message ‘The name “hostname” already exists.’ However, at first glance in vCenter the hostname didn’t exist. The vCenter vpxd log contained more info, an error below: Found host with duplicate IP x.x.x.x: host-xxxxx You can track down the hostname from the host-xxxxx info with PowerCLI Get-VMHost | Where-Object {$\_.

Following on from the highly successful first PowerShell Deep Dive conference held in Las Vegas in Feb 2011 the PowerShell team have announced details of a European equivalent to be held at TEC Europe 2011 in Frankfurt on October 17 & 18 2011. Registration info and details on how to submit session propposals can be found on the PowerShell team blog: -——————————————————————————————————————————————————- Here’s some more info on the 2nd PowerShell Deep Dive that will be at TEC Europe 2011 in Frankfurt on October 17 & 18.

The question we have been asked the second most was back in April, “Why is the Kindle version more expensive than the paperback?”. At the time we went back and forth with both the publisher and Amazon and received conflicting answers. Well now that is back in the various Kindle stores again, this situation also seems to have improved and typically it is slightly less than the paperback in price.

The here. OK, so there are already a ton of blog posts out there on this topic which cover the pros and cons of this change. A couple I found useful are below: Understanding vSphere Licensing - Barry Coombs vSphere Licensing - the good, the bad and the ugly - Ed Grigson Initially I thought this licensing change might be a bit of a problem for us, but thought I would wait for the dust to settle and spend some time figuring out what the impact could be.

When working with PowerCLI in a large environment and retrieving large amounts of data, particularly when using the Get-View cmdlet, you may receive the following error: Get-View Exception of type ‘System.OutOfMemoryException’ was thrown Looking at the available memory on your system may cause you to wonder why you receive this error message. It may occur because you are running the 32-bit version of PowerCLI where the size of the heap is limited to 1.

Having been using the beta for a while, I was very pleased to see that PowerGUI V3 has been released. Some of the new features / fixes that I like the best are: Create Executable from Script One click install for PowerPacks PowerCLI 4.1 Support in the VMware PowerPack Have a look at Kirk’s site for full details http://poshoholic.com/2011/07/15/powergui-pro-and-powergui-3-0-are-now-available/

Thanks to everyone who came to my session today, always enjoy presenting here. Here are the slides: Save Time With PowerCLI View more presentations from jonathanmedd

The UK is a funny country to live in sometimes. If we do succeed at anything, it’s almost despite ourselves and once we have succeeded - well we don’t really like to talk about that kind of thing. I’ve spent more than a decade working in various IT infrastructures in this country and it doesn’t take much to see that those which are the most successful are those which spend the time and money - on both good people and quality equipment.

The next London VMUG on 14th July 2011 is only a few weeks away and again looks like it will be a great event. This will be the second time it has been run as a full day event with split-track breakout sessions in the afternoon, so that there is more of a choice for those topics your are particularly interested in. There will also be a vCOPS focused lab and a Genius Bar staffed by VMware GSS to help deal with any issues you might bring along.

By default, Data Encryption Standard (DES) encryption for Kerberos authentication is disabled in Windows Server 2008 R2, this is a change from Windows Server 2003. If you are running an application which uses DES encryption for Kerberos application, such as SAP, then you may see issues authenticating users against 2008 R2 DCs. You will see errors in the System Log like the below for the users in question: “While processing a TGS request for the target server %1, the account %2 did not have a suitable key for generating a Kerberos ticket (the missing key has an ID of %3).