Last week I cloned some Citrix XenApp servers by a customer, after multiple reboots I saw boot message:
VMware image customization is in progress …
Solution:
Open the Registry Editior, path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\BootExecute
Remove the value: sysprepDecrypter.exe , result:
Press OK, reboot the server and.. the problem is solved!
- Press [Enter] to continue
Read more…
VMware vCenter Server 5.0 Update 1b is a patch release and offers the following improvements:
- vCenter Server 5.0 Update 1b introduces support for the following vCenter Databases
- Oracle 11g Enterprise Edition, Standard Edition, Standard ONE Edition Release 2 [11.2.0.3] – 64 bit
- Oracle 11g Enterprise Edition, Standard Edition, Standard ONE Edition Release 2 [11.2.0.3] – 32 bit
- vCenter Server Appliance Database Support: The DB2 express embedded database provided with the vCenter Server Appliance has been replaced with VMware vPostgres database. This decreases the appliance footprint and reduces the time to deploy vCenter Server further.
- Resolved Issues: In addition, this release delivers a number of bug fixes that have been documented in the Resolved Issues section.
vCenter Server 5.0 Update 1a has been removed from the VMware download site due to issues encountered when upgrading with an Oracle database for Windows. vCenter Server Update 1a is replaced by vCenter Server 5.0 Update 1b, which is functionally identical to vCenter Server 5.0 Update 1a and includes the fix for the issue encountered when upgrading with an Oracle database for Windows. Please refer to KB 2032277 and the Resolved issues section of the release notes for more information.
VMware vCenter 5.0 Update 1b Patch is available for download at: https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_0.
More information: VMware Release notes
Lots of VMware / Windows administrators can extend virtual disks on-the-fly in a few seconds, but what is the easiest way to shrink a / the (OS) volume?
In this post I’ll show a (simple) method how-to shrink the system disk size from a virtual machine from 60 to 40 GB.
In all cases, confirm the following before shrink the size of the virtual disk:
- All snapshots have been removed;
- The virtual machine is powered off;
How-to:
Install VMware Converter and connect you’re vCenter server running that specific virtual machine
- Start the VMware Converter by clicking “Convert machine”;
- Select source server (virtual machine on vSphere host);
- Select destination server (same vSphere host, new VM name);
- Select target datastore;- Options: select “Data to copy” and press Edit;
^ you can see the source volume (60 GB) and used space (23,45 GB)
Read more…
Last week I was writing a Technical Design for a customer to create a brand new vSphere 5 environment based on HP hardware (HP P4300 G2 storage and HP DL380G7 servers). I found HP Sizing Tools for VMware vSphere tool at the HP website to size and design storage and server components to run my new vSphere solution.
Here some installation and sizing facts:
Read more…
Today VMware released ESXi 5.0 Update 1 with a download size of 564 mb
The update contains multiple bug/hotfixes bundled in Update 1, some more information:
This patch release contains the bug fixes for ESXi. For more information, see the KB articles for the individual bulletins.
For information about the issues fixed with the ESXi-5.0.0-20120301001s-standard image profile, see KB 2012673.
For information about the issues fixed with the ESXi-5.0.0-20120301001s-no-tools image profile, see KB 2012674.
For information about the issues fixed with the ESXi-5.0.0-20120302001-standard image profile, see KB 2012671.
For information about the issues fixed with the ESXi-5.0.0-20120302001-no-tools image profile, see KB 2012672.
Host Reboot Required: Yes
Virtual Machine Migration or Shutdown Required: Yes
Source: VMware
After trying to install vCenter Server I received a warning from Windows Installer:
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installed package
With some troubleshooting at the VMware vCenter Server MSI package to start this package with a logfile, command:
msiexec /l*vx c:\install.log /i "E\vCenter-Server\VMware vCenter Server.msi"
I received this installer Install.log output:
=== Verbose logging started: 2/21/2012 4:23:12 Build type: SHIP UNICODE 5.00.7600.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (DC:D8) [04:23:12:689]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (DC:D8) [04:23:12:689]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (DC:60) [04:23:12:704]: Resetting cached policy values
MSI (c) (DC:60) [04:23:12:704]: Machine policy value ‘Debug’ is 0
MSI (c) (DC:60) [04:23:12:704]: ******* RunEngine:
******* Product: D:\vpx\VMware vCenter Server.msi
******* Action:
******* CommandLine: **********
MSI (c) (DC:60) [04:23:12:704]: Note: 1: 2203 2: E\vCenter-Server\VMware vCenter Server.msi 3: -2147287039
MSI (c) (DC:60) [04:23:12:704]: MainEngineThread is returning 1620
=== Verbose logging stopped: 2/21/2012 4:23:12 ===
Read more…
Last week I’ve converted a .VHD (Microsoft Virtual PC) to .VMDK for a customer with the application WinImage, the process was very easy.. a little how to:
WinImage 8.5: Download
Read more…
