vCenter appliance 6.5 is one of the latest & stable release of vCenter . vSphere 6.5 adds an X-Large deployment size, the update manager and a fully supported migration assistant to the appliance. So it’s time to migrate your Windows based vCenters to appliance with vSphere 6.5. vSphere 6.5 is fully dependent on webclient. So no more vSphere client or C# client. VCSA 6.5 Enhancements Supports up to 2000 ESXi Hosts and 35.000 Virtual Machines Guided Installer (Interactive Installer, instead of OVF Template) Robust deployment (Separate Deployment and Configuration to prevent failed deployments Migration Assistant (Migrate vCenter Server 5.5 or 6.0 for Windows to vCenter Server Appliance) Native High Availability VMware Update Manager Built-In Backup+Restore Improved Appliance Management HTML5-based vSphere Client Photon OS (Replaces SUSE Enterprise 11) Compatibility  To view the compatibility of Esxi,

Issue: Cannot join a VMware vCenter Server Appliance (VCSA) to an Active Directory domai n While trying to connect to domain from VAMI page of VCSA, getting below error. Error: Invalid Active Directory domain. T o resolve this issue to join the VCSA to Active Directory domain, we can use domainjoin-cli join command Example: To join VCSA to Active Directory domain please follow below process Login to VCSA from SSH 2     Cd /opt/likewise/bin 3     Enter below domainjoin-cli command to join VCSA from command line ./domainjoin-cli join domain-name username password 4     Verify by login to VAMI page of VCSA about the Active directory connectivity by clicking Authentication tab. 5     You will see Active Directory Enabled Check box enabled. Happy Sharing

                    Yesterday, I was working into my vsphere Lab where I have deployed one virtual machine into the environment. After deployment virtual machine was working perfectly fine. After some time, I have added 2 huge hdd of size 800 GB using PVSCSI. Once I added the hdd into the VM, and after accepting the change, I tried to open the console and found vm has rebooted and stuck at "Operating System not found" That’s look wired, as I have just added the hdd online and suddenly it rebooted and stuck at this stage. To troubleshoot this issue I tried to gracefully shutdown the VM and tried to bring online in hope, it will detect the changes, but again it stuck at same level "Operating System not found" I checked my OS drive which is  created with the LSI SCSI controller, and the 2 new hdd I created with PVSCSI controller. Here is what the problem exists!!!!! Basically, When the virtual machine is created with the LSI SCSI controller,

  Some time back I had an issue while I tried to connect my Vcenter from powercli but unable to connect and getting below error  ################################################## Connect-VIServer :  6/08/2015 3:31:27 AM        Connect-VIserver          Could not connect using the requested protocol. At line:1 char:1 + Connect-VIServer itvc001.age.com +         + CategoryInfo               : ObjectNotFound: (:) [Connect-VIserver], ViServerConnectionException         + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_ProtocolError, VMware.VimAutomation.ViCore.Cmd     lets.Commands.ConnectVIServer ################################################## This is all because, there are proxy setting configured into your explorer or into your system from where you are trying to connect the vcenter from powercli.  To resolve this Issue pls follow below KB articile. 2011395   http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=display

Virtual Volume (VVols) is basically a latest introduction into Vsphere 6.0 environment which has significantly change the architecture of storage part. Traditionally into vsphere environment we are having a concept of LUN to provide storage into ESXi into which VMware administrator used to provision virtual machine into that peace of storage (LUN). In this process all vm’s which are deployed are depended into that LUN having dependency into it. Like, if that LUN having any issue like all path went down or its loosed its connectivity from ESXi or storage, into this case all its derivative vm’s will get affected. That dependency has moved out into VVol VVol has introduced where virtual machine is directly connected to SAN (Raw area of storage), not on LUN concept.  Architecture of VVol In Virtual Volumes storage has altogether changes compared to old architecture of Vsphere. VVols completely change the way storage is presented, managed and consumed and certainly fo