VMpros.nll
new1234.jpg

VMware: Quick stats on [SERVERNAME] is not up-to-date

June 4th, 2015 No comments

Few weeks ago I upgraded for a customer vCenter Server 5.5. to 6.0, today I received a yellow warning in the Summary tab:

Quick stats on [SERVERNAME] is not up-to-date

image

 

Solution

This is a known issue in vCenter Server 5.5 and 6.0.

  • This issue is resolved in VMware vCenter Server 5.5.0b.
  • Currently there is no resolution for vCenter Server 6.0.

To work around this issue, add these quickStats parameters to the Advanced Settings of vCenter Server:

  • vpxd.quickStats.HostStatsCheck
  • vpxd.quickStats.ConfigIssues

Note: Adding these parameters to vCenter Server does not affect future upgrades.

To add the quickStats parameters to the Advanced Settings of vCenter Server 6.0:

  1. Connect to the vCenter Server using the vSphere Client and administrator credentials.
  2. Select Administration > vCenter Server Settings to display the vCenter Server Settings dialog box.
  3. In the settings list, select Advanced Settings.
  4. Add the following parameters:
  5. vpxd.quickStats.HostStatsCheck = False

    vpxd.quickStats.ConfigIssues = False

      
    image

  6. Restart the vCenter Server services. For more information, see:

    More information: VMware

VMware: There is a problem authentication into the legacy vCenter Server using credentials provided by the user

May 16th, 2015 No comments

During upgrade VMware vCenter Server 5.5.0 (based on Windows 2012R2) to 6.0.0 I received a warning message:

Error: There is a problem authenticating into the legacy vCenter Server using the credentials provided by the user.

Resolution: Check if vCenter Server is up and running. Double check provided vCenter Server credentials

 
VMpros.nl

 
Some troubleshooting:

  • All VMware vCenter Server Services are started
  • No warnings/errors in Microsoft Event Logs during setup
  • I can logon at the vSphere webinterface with credentials administrator@vsphere.local
  • When configure wrong SSO password in setup the setup says "The vCenter Single Sign-On credentials are not valid. Check the username and password and try again"
  • I can ping domain controller VMpros.local
  • I canceled the setup and generated a support file, at the time I received the warning message this setup log was generated, so far, nothing special:

MSI (c) (40:88) [17:15:28:813]: Invoking remote custom action. DLL: C:\Users\ADMINI~1.VMP\AppData\Local\Temp\MSI7329.tmp, Entrypoint: LaunchUpgradeRunnerPreUpgradePhase
MSI (c) (40!C8) [08:23:44:055]: PROPERTY CHANGE: Modifying PreUpgradeComplete property. Its current value is ‘0’. Its new value: ‘1’.
MSI (c) (40:D0) [08:23:47:186]: PROPERTY CHANGE: Modifying SSO_PASSWORD property. Its current value is ‘**********’. Its new value: ‘**********’.
MSI (c) (40:D0) [08:23:47:267]: PROPERTY CHANGE: Modifying VC_5X_PASSWORD property. Its current value is ‘**********’. Its new value: ‘**********’.
MSI (c) (40:D0) [08:23:47:288]: PROPERTY CHANGE: Modifying PreUpgradeComplete property. Its current value is ‘1’. Its new value: ‘0’.
MSI (c) (40:D0) [08:23:47:305]: Doing action: VM_LaunchUpgradeRunnerPreUpgradePhaseAsync

 

Solution

Reboot the vCenter Server… I restarted the setup and the installation can continue.. weird!

VMware: vix error code = 21009 during

May 15th, 2015 1 comment

During upgrade installation VMware Tools I received this warning message:

vix error code = 21009

 
VMpros.nl

 

 

Cause

This issue occurs because, for security purposes, updating VMware Tools from within the guest is disabled by default.

 

Solution

  1. Shut down the virtual machine, if it is running.
  2. Open the datastore browser and navigate to the virtual machine directory.
  3. Using the GUI option, download the .vmx to your local desktop.
  4. Create a backup of the .vmx on your local workstation.
  5. Open the .vmx file using a text editor and add this line to the end of the file:

image

Categories: VMware Tags: , , , ,

VMware: Windows could not parse or process the unattend answer file for pass [specialize]

May 13th, 2015 No comments

Today I deployed my new created Citrix XenDesktop 7.6 base image with Windows 8.1 u1 template and Customization file, during the customization process I received this error message:

Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click “OK” to restart the computer, and then restart the installation.

 

http://www.bencremers.nl/wordpress/wp-content/uploads/2014/05/windowscouldnotparse.jpg


Cause

This issue can have multiple causes. Some common causes include, but are not limited to:

  • Bad Product Key
  • Invalid Device Drivers
  • Invalid Computer Names
  • Issue with the Admin Account being used
  • An installed application breaks the unattended install process

Solution

This resolution is based on the source of the error, to troubleshoot this issue, review the Microsoft Setup log setupact.log file.

Note: The Microsoft Setup log file is located at c:\Windows\Panther\unattendGC\setupact.log.

To view the log file from a computer currently displaying the error, press Shift + F10 to open a command prompt and run this command: notepad c:\windows\panther\unattendGC\setupact.log

In my case I configured in the Customization Wizard a Windows 8.1 MAK license key, the configured template OS was an VLK edition…

VMware: Repeated characters when typing in remote console

April 7th, 2015 1 comment

Everyone knows the hanging keyboard console session issue, when you type your username or password the keyboard hangs. If you access a virtual machine console over a slow connection, you’ll encounter keyboard sync issues

If you open a remote console to a virtual machine from a slow network connection (such as a VPN) while tethered to a mobile phone providing Internet access, the experience is not optimal, as keyboard and mouse gestures aren’t timed exactly the same. This is especially problematic if you try to enter a password where the characters are masked.

image

  

Solution

There are two ways to add a extra line in the configuration file of the virtual machine,

 

Option 1. Edit VMX file directly

1. Power off the virtual machine.

2. Add a line, similar to this, at the end of your virtual machine’s configuration (.vmx) file

keyboard.typematicMinDelay = "2000000"

The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it.

image

3. Power on the virtual machine.

 

Option 2. Edit VMX via vSphere Client

1. Power off the virtual machine.

2. Edit settings > Options > General > Configuration Parameters, add new row with text:

keyboard.typematicMinDelay = "2000000"

The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it.

image
3. Power on the virtual machine.

 

Ps. You can edit the .VMX files directly, but a better practice is to configure this value within the vSphere Client for a virtual machine template. When you consider that most of the access to a virtual machine is provided by tools such as remote desktop, there is no harm in configuring this value globally for all virtual machines that originate from a template

VMware: Upgrade vCenter Server 5.5 to 6.0

March 29th, 2015 4 comments

Last week I upgraded VMware vCenter 5.5 server (based Windows 2012R2) at the company environment I work for, the upgrade was very simple.

Pre-install: Please check article “Minimum requirements for the VMware vCenter Server 6.x Appliance (2106572)

 
Installation process

clip_image002

– Select: Install

Read more…

[VMware] Could not start VMX: msg.vmk.status.VMK_NO_MEMORY

March 29th, 2015 2 comments

Last week I had some issues with starting virtual machines on vSphere 5.5 hosts (enough capacity available), when I try to start up the VM I receive message:

Could not start VMX: msg.vmk.status.VMK_NO_MEMORY”

An error was received from the ESX host while powering on VM [name]
Head globalCartel-1 already at its maximum size of 7869288. Cannot expand
Could not start VMX: msg.vmk.status.VMK_NO_MEMORY

image

 

Cause

This issue is caused by a memory leak in the driver which fills the SWAP memory of the ESXi host, making it unable to response to any requests at all. This issue occurs with ESXi hosts running on HP hardware with these versions of AMS:

  • hp-ams 500.9.6.0-12.434156
  • hp-ams-550.9.6.0-12.1198610
  • hp-ams 500.10.0.0-18.434156
  • hp-ams-550.10.0.0-18.1198610


Solution

This is a known issue affecting ESXi 5.x. To resolve this issue, upgrade to AMS version 10.0.1.

For ESXi 5.0 and 5.1, see:

For ESXi 5.5, see:

 

Note: In some cases, commands running on the ESXi host fails with cant’t fork.  In this case the virtual machines running on the ESXi host needs to be powered off and the ESXi host rebooted. To verify the installed versions of AMS, run this command:

esxcli software vib list | grep ams

To remove the package on all hosts running on these AMS versions:

  1. Log in to the host using SSH. For more information, see Using ESXi Shell in ESXi 5.x and 6.0 (2004746).
  2. Run this command to stop the HP service (does not persist on reboot):
    /etc/init.d/hp-ams.sh stop
  3. Run this command to remove the VIB:
    esxcli software vib remove -n hp-ams
  4. Reboot the host.
    More information:

VMware

VMware: VMUG Event 2015 – Agenda

February 26th, 2015 No comments

08.30-09.30

Registratie & Welkom

09.30-10.25

Opening & VMware Keynote: Joe Baguley, CTO EMEA VMware

Limousin 1

Limousin 2

Limousin 3

Dexter 11-14

10.30-11.10

Simplivity

Micro-Segmentation & Security: Geordy Korte, VMware

What does this button do? “The power of Automation” Christiaan Roeleveld & Dennis Hoegen Dijkhof, ITQ

Building a Hybrid Cloud with VMware vCloud: René Bos

11.15-11.30

Koffiepauze

11.30-12.10

Cisco

Real-time applicatie delivery met AppVolumes: Ton Hermes, VMware

vRA Advanced Service Designer Deep Dive: Viktor van den Berg, PQR

SDDC for the VMware minded: Erik Zandboer, EMC

12.15-12.55

Nutanix

vSphere 6 Technical Core: Rob Groenhuis, VMware

vSphere 6.0 VDI en NVIDIA GRID: Ruben Spruijt, PQR

Applicatie distributie in 5 minuten: Marko Elderson, Roel van Bueren & Kevin van Gool, Netflex

12.55-13.45

Lunch

13.45-14.25

Keynote: Joseph Oubelkas

14.30-15.10

Veeam

Introductie in VMware Automation & Orchestration: Erik Scholten, VMware

VMware <> Microsoft: Let’s Look beyond the war on checkbox compliancy: Kenneth van Surksum & Marnix Wolf, Insight24

NSX Bootcamp: Geordy Korte, VMware

15.15-15.45

Koffiepauze

15.45-16.25

VMware vCloud Air: Bouwsteen voor de Hybrid Cloud: Martijn Baecke, VMware

Deepdive VSAN and Virtual Volumes: Jan Smit, VMware

VMware User Environment Management (acquisitie van Immidio Flex+ UEM): Pim van de Vis, Immidio

16.30-17.15

Receptie

Categories: VMug, VMware Tags: , , , , ,

VMware: Yeeaaahhh vExpert 2015!!

February 5th, 2015 1 comment

This year’s vExperts 2015 were announced! Check it out. I’ve been honored again 2010, 2011, 2012, 2013, 2014 and 2015 as a vExpert this year. Great thanks to VMware and vExpert team behind the program!

It’s Correy Romero who announced the news on the VMTN blog, here is the full list of lucky people for vExperts 2015.

Categories: VMware Tags: , , ,