Resetting the VMWare vCenter appliance (VCSA) root password

Ok this is strange problem I came across during my VMWare lab setup. For some reason the password I’ve setup during my vcenter appliance setup is not detecting. Yes I waited enough time for appliance to bootup Smile 

So here I’m wondering how to move to next step without wiping and starting my test lab from the scratch. Based on my research around found out we can reset the root password on Linux appliance. This going to be a post which I will be helpful for me as well as for yo all when struggling through root password issues in VCSA

To provide some background I’m testing VMWare Esxi and vCenter (VCSA) 6.7 setup running on VMWare workstation 14. For this lab setup I did import the VCSA OVA file directedly into the VMWare workstation instead of setting up inside the ESXi server (yes you can do that Smile)

Please note VMware using their own OS called “Photon OS” for their VCSA appliance. 

Ok for the steps guide now.

1. Take a snapshot or backup or your VCSA appliance. Restart the VM and hit letter “e” in your keyboard when you see the “Photon OS splash screen. This will take you to the GRUB boot menu. In the end of first sentence append the parameter rw init=/bin/bash


2. After that press F10 to continue the boot. After few seconds you’ll be prompted with  root login. Type passwd. You’ll be prompted to enter the new password. Type the new password and repeat the again for verification. If you’re successful you’ll be prompted.



3. Once the steps are completed you can type reboot –f and let the system restart. After that once the system reboot try connecting to vcsa login screen with the new password.

Hope this small steps will save you lot of time. From what I heard if there is new updates to the Photon OS there is a possibility password we setup might not work. Remember these steps to overcome that.

Kindly note I’ve only test this on VMware 6.7 version only. I do believe same will work on 6.5 version as well.


System Center Universe 2016 @ APAC

One of the best System Center summit happening around the world. As a Infront employee I’m happy to announce our company did host the event for the third time in APAC region. This time in Malaysia soon after that in Australia. All the well known System Center experts in one room sharing their knowledge. I’m glad that I got the opportunity to be among those experts and carry out two sessions.

Azure becoming key topic for developers and IT Professionals. How we can save time be leveraging templates. This is where we can leverage Azure Resource Manager Templates. Carried out a session to show how ARM really can help for IT Professionals in their journey.

Disaster recovery can be taken to next level by leveraging the Azure cloud. Delviered another session covering how Microsoft extend their love to protect VMWare customers as well Smile In this session we covered about Azure Site Recovery for HYPER-V, VMWare & Physical servers. We also demo what is “Enhanced mode for VMWare” and what that is so cool.


VMware or HYPER-V or be in heterogeneous environment?

We are in the IT era of moving towards virtualization due to several factors. But from the IT business Decision makers are in the doubtful position of deciding which virtualization platform to consider. now it has become a boiling question of VMware ESX, Vsphere or Microsoft HYPER-V  v2.0.

Unfortunately for IT managers this is not a black and white question or a decision to take (at least most of them). So what the expert advise for this? Try and see both environment before moving to one platform, but this is not an easy task for busy admins. but if you carefully consider it makes real sense, most of the blogs and web sites talk about the product in biased method instead of been unbiased. Even a person who tried to be fail will be falling into biased method sine he must have been practically using one version more than the other.

The reasons for a heterogeneous environment are, well, heterogeneous. Some companies are in transition, moving their virtual environments from VMware to Hyper-V. Others choose to segment their servers according to geography or department. Still others pick their virtualization platform according to the underlying physical platform or application. As you can see moving to a vitalization platform is not all about the features but balance and reducing of the cost as well.

Most of the early virtualization adopt customers are coming from VMware background. Some are considering moving to HYPER-V  due to the software licensing cost in VMware. Some deciding keep existing VMware environment as it is and move new requirements to HYPER-V  to reduce cost and balance everything. So in that case heterogeneous environment come it picture automatically. So next question is how to manage heterogeneous environment? Well that is not that difficult as we think, since most of the ISV’s has already predict that and given solutions for that. As an example Microsoft Virtual Machine Manger (VMM 2008) is already supporting VMware ESX management as well. But of course this manageability will be depend on how the IT manger want to accept it (Hope you get what I mean 🙂 )

So cross virtualization platform is not a bad thing from my point of view. You’ll get your hands dirty on both technologies and will get the chance to evaluate them. But you may decide to move to one platform later since heterogeneous is a temporary transition period for most of the companies. So for the summarization I want to point out selecting the virtualization platform is not based on the features itself but various other factors as well.