While I’m sure there are probably plenty of reasons that could cause the following error: Error 29120. Database schema already exists I’ve encountered this error twice while installing vSphere 5.1 (Build 880146) and thought I’d
Problem You have an existing vCenter deployed in your environment and you would like to deploy a second node in Linked Mode so you proceed with the install of SSO on the second node: Select
While this is probably not going to be a common problem to many administrators out there, I figure I’d blog this issue I encountered today in case I come across it again. You have just
Problem You have Windows Server 2003 virtual machine running on VMware vSphere 4.x or 5.x and you need to expand one of the data drives (non-system) so you proceed with increasing the size of the
I’ve been calling one of my recent VMware View 5.x upgrades bad luck because of all the issues I’ve had with version 5.1.1 (799444): The first issue I had was with the 5.1.1 View Agent
Wanting to be an early adopter of Windows 8, I went ahead and upgraded my laptop over the weekend and one of the first issues I immediately noticed was when I attempted to install the
Problem Environment Information: vCenter: 4.1.0, Build 345043ESXi: 4.1, Build 348481 You attempt to create a snapshot for a virtual machine: … but receive the following error: Create virtual machine snapshot VirtualMachineName Cannot complete the operation
Problem Environment Information: vCenter: 4.1.0, Build 345043ESXi: 4.1, Build 348481 You need to move a virtual machine that is a part of a Microsoft Clustering Services (MSCS) to a new datastore and since this virtual
——————————————————————————————————————————————————————– Update December 17, 2012 I received an update from the engineer I was working with on this case today to inform me that the new 5.1.2 agent was out and to try it and
I’ve recently been asked a few times over the last 2 months as to whether it is possible to update the VMware View Agent to 5.1 if the View Connection server was still at version
