Start Profile Wizard after you have entered Maintenance Mode
– Select: Create Profile from existing host
– Select host (in maintenance mode)
– Profile details: Reset root password
– Finish the host profile creation
On the left pane select your new host profile and right-click and select edit profile:
– Select: Root password reset > Security configuration > SSH authorized key for root user
Note: check or deselect specific host profile configurations to enable or disable them. A disabled configuration will not be applied when applying the host profile and hosts will not be checked for compliance with that configuration
Now click OK and we’ll start attaching the host of which we want to reset the password. Click ‘Attach Host/Cluster’ and select the right host, click Attach and then OK.
Voila, the root account of the host has been reconfigured and you should be able to log in again. Now the only thing left is to detach the host from the profile.
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
This release resolves the following issues related to vCloud Automation Center:
Attempts to perform vCloud Automation Center tenant administration operation fail with an error
When you attempt to perform any vCloud Automation Center tenant administration operations such as removing an administrator from the default tenant (vsphere.local), the operation fails with a System Exception error.
Attempts to log in to vCloud Automation Center fail if the SAMAccountName contains extra trailing spaces
When you attempt to log in to vCloud Automation Center, the login attempt fails if the SAMAccountName attribute contains extra spaces trailing at the end of the name.
Attempts to log in to vCloud Automation Center fail if the password contains the colon (:) character
While attempting to log in to vCloud Automation Center, if you use a password that contains the colon (:) character, the login attempt fails.
Attempts to use the Windows Session Authentication feature might fail
When you log in to vCloud Automation Center by using Windows Session Authentication on browsers such as Internet Explorer, Google Chrome, and Mozilla Firefox might fail due to an error in the VMware Client Integration Plug-in. An error message similar to the following is displayed:
Windows Session Authentication login has failed as a result of an error caused by the VMware Client Integration Plugin
Attempts to log in to vCloud Automation Center fail if a custom UPN suffix is configured in the alias field for AD over LDAP
When you attempt to log in to the vCloud Automation Center where the custom UPN suffix is configured in the alias field for Active Directory (AD) over Lightweight Directory Access Protocol (LDAP), the login attempt fails.
This issue is resolved in this release.
Attempts to log in to vCloud Automation Center using vSphere Single Sign-On 5.5.0b might fail with an error
If you specify the Global Catalog (GC) port in the AD over LDAP Identity Provider’s (IDP) connection string, attempts to log in to vCloud Automation Center using vSphere Single Sign-On 5.5.0b might fail with an error message similar to the following:
Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 10
You can also see log messages similar to the following in the vmware-sts-idmd.log file:
2014-04-09 14:18:16,564 ERROR [ServerUtils] Exception
'com.vmware.identity.interop.ldap.ReferralLdapException: Referral
LDAP error '
com.vmware.identity.interop.ldap.ReferralLdapException: Referral
LDAP error
at
com.vmware.identity.interop.ldap.LdapErrorChecker$11.RaiseLdapError(LdapErrorChecker.java:172)
at
com.vmware.identity.interop.ldap.LdapErrorChecker.CheckError(LdapErrorChecker.java:826)
at
com.vmware.identity.interop.ldap.WinLdapClientLibrary.CheckError(WinLdapClientLibrary.java:758)
at
com.vmware.identity.interop.ldap.WinLdapClientLibrary.ldap_search_s(WinLdapClientLibrary.java:433)
The vCenter Server 5.5 Update 1c can be downloaded here and the release notes can be found here.
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
After installation of VMware vSphere 5.5 Update 1 connectivity to NFS storage could be randomly lost with volumes reporting All Paths Down state. This issue was noticed around mid April and reported here.VMware documented the issue in KB article 2076392 Intermittent NFS APDs on VMware ESXi 5.5 U1
At June 10 VMware released a patch for this issue as described in KB 2077360. The patch can be downloaded using VMware Update Manager or using VMware download page
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
The release of VMware vSphere vCenter 5.5 Update 1 contains the following enhancements:
vCloud® Hybrid Service™ vSphere® Client Plug-in, is now available in vSphere Web Client.
The plug-in installer icon appears in the Home page, under Inventories. Click the installer icon to install the plug-in. The vCloud Hybrid Service plug-in lets you view and manage your vCloud Hybrid Service resources in the vSphere Web Client. After you install the plug-in and register your vCloud Hybrid Service account with it, you can view all your Dedicated Cloud and Virtual Private Cloud instances in the vSphere Web Client. You can browse each cloud instance and manage its inventory of virtual data centers, gateways, networks, and virtual machines. See the vCloud Hybrid Service vSphere Client Plug-in documentation at https://www.vmware.com/support/pubs/vchs_plugin_pubs.html for more information.
vCenter Server is now supported on Windows Server 2012 R2.
Resolved Issues – This release delivers a number of bug fixes that have been documented in the Resolved Issues section.
The release of VMware vSphere ESXi 5.5 Update 1 contains the following enhancements:
VMware Virtual SAN – Virtual SAN 5.5 is a new hypervisor-converged storage tier that extends the vSphere Hypervisor to pool server-side magnetic disks (HDDs) and solid-state drives (SSDs). By clustering server-side HDDs and SSDs, Virtual SAN creates a distributed shared datastore designed and optimized for virtual environments. Virtual SAN is a standalone product that is sold separate from vSphere and requires its own license key
Resolved Issues – This release delivers a number of bug fixes that have been documented in the Resolved Issues section.
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Last week I updated my vCenter Server Appliance in my homelab, this was too easy:
– Browser: http://vcentername:5480
– Login with root / admin (if AD integrated) credentials
– Tab: Update, click: Check updates
– Available updates: appliance version: 5.5.0.5201 build 1476389 (current: 5.5.0.5100 build 1312297)
– Click: Install updates
– Installing updates..
– Appliance update is completed, reboot the appliance
Status:
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
vCenter Server Appliance 5.0 Update 1a is the first major update since vCenter Server Appliance 5.0 was released
VMware vCenter Server 5.0 Update 1a is a patch release and offers the following improvements:
- vCenter Server 5.0 Update 1a 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.
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Last week I created a little “how-to” for some system engineers to install/upgrade VMware Tools in their test environment. Here’s the translated (public) version:
– VM Summary: VMware Tools – Running (unsupported)
– Select VM > Guest > VMware Tools Install. The Infrastructure Client will mount VMware Tools ISO inside the VM
– Create a directory, type in: mkdir /mnt/cdrom next you need to mount the CD-Rom drive, type in:
mount /dec/cdrom /mnt/cdrom
Read more…
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
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
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
A colleague got some trouble connecting with the VMware Data Recovery appliance, received this warning:
Error: Could not connect to the Data Recovery on the appliance
Please make sure the Data Recovery appliance is powered on. If the problem persists, please restart the Data Recovery appliance
Time for some troubleshooting:
– Ping test was successful;
– Could resolve DNS names;
– Rebooted the appliance;
– No weird error in the event log;
Resolution:
After checking the appliance version (VMware Data Recovery 2.0.1131) and the Plugin-Version (VMware Data Recovery Plugin 1.1.37) I thought.. maybe I need to update the plugin
After upgrading the plugin to version 1.2.1.3 I was able to connect the appliance again:
Result:
More information: Troubleshooting VMware Data Recovery plug-in connection issues
Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC
More Posts - Website
Follow Me:
Recent Comments