Techstarts's Accepted Solutions

Check if you have more than one .jar file in that folder. Move the older Jar file in other folder and run. it works. But remember if your version 8.4.x, then the jar file older than 8.4.x should  b... See more...
Check if you have more than one .jar file in that folder. Move the older Jar file in other folder and run. it works. But remember if your version 8.4.x, then the jar file older than 8.4.x should  be removed. in my case, the older jar file was 8.1.1 (e.g.vmlcm-service-8.1.1-SNAPSHOT.jar)
Hello Team, I followed this article https://kb.vmware.com/s/article/2147284 and the problem was resolved. In case you came across this bug, can be helpful as others amazing thread on this communitie... See more...
Hello Team, I followed this article https://kb.vmware.com/s/article/2147284 and the problem was resolved. In case you came across this bug, can be helpful as others amazing thread on this communities.  
so I can confirm it is bug. Password did not expired. It is just that message does not away when you change the password to non-expiry. Hope it helps someone.
since you define network profile in vCAC, it is vCAC who manages, assigns and releases it. Hope it helps, Preetam vZare.com
Log file says "VMware VirtualCenter-build-623373: 03/22/12 15:45:23 Failed to install SPS." Check if Storage profile service is present in Services (Services.msc).
VMware and Storage Vendors recommend Don’t defrag VMs!, refer http://www.ntpro.nl/blog/uploads/Mythbusters_Dutch_VMUG.pdf
Unfortunately these features are offered from vCenter. You can look for any 3rd party tool which offer such features. e.g. veeam monitor
jpawlicki wrote: 2-What happens when you exceed LUN size/ 3-What happens when you over provision? Thank you if you are using vsphere5.0 then all the VM's which runs out of space will be pau... See more...
jpawlicki wrote: 2-What happens when you exceed LUN size/ 3-What happens when you over provision? Thank you if you are using vsphere5.0 then all the VM's which runs out of space will be paused. This is vsphere5.0 storage feature.
From your reply am I right in saying without changing my licence I will always be limitted to four vCPU. davejc           yes you are right.
So am I right in thinking that my processor has 6 cores. Aslong as I dont give my sql vm more than six cores I will only need the one physical license.           yes you are right and ke... See more...
So am I right in thinking that my processor has 6 cores. Aslong as I dont give my sql vm more than six cores I will only need the one physical license.           yes you are right and keep this sheet for reference in case some one s questioning you
It is the default behaviour of ESX architecture. Create resource pool, leave every thing default. Entire resources will be shared among the VM's
Upgrade guide is available here -> http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade-guide.pdf Licensing: use tool from VMware called Licensi... See more...
Upgrade guide is available here -> http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade-guide.pdf Licensing: use tool from VMware called Licensing advisor –Download from here à http://www.vmware.com/products/datacenter-virtualization/vsphere/upgrade-center/vsphere-licensing-advisor.html, also contains how to use it Vcenter is x64 or x32? If it is 32 bit you will have to re-install it on x64 bit. If it is x64 bit, path is straight forward. For detailed information on upgrade refer upgrade guide Thanks, Techstarts
Please note when swap file is located on local datastore(unshared), when you vMotion the VM from one esx host to another esx host, vMotion time increases because during vMotion even swapfile is m... See more...
Please note when swap file is located on local datastore(unshared), when you vMotion the VM from one esx host to another esx host, vMotion time increases because during vMotion even swapfile is migrated as it has memory state of VM. So this explains why there is an impact. Now coming to the point of storing VM Swap file on shared storage. In fact this is the best practises for two reasons. 1. You do not end up backuping the swap file 2. Your storage space is efficiently utilized 3. If you are replicating LUNS to remote site, you can exclude this LUN If you need further details Please refer this white paper from netapps. NetApp and VMware vSphere Storage Best Practices (TR-3749) Hope it helps Thank you, Preetam Zare