vThinkBeyondVM's Posts

Hi Nagendra, I assume you are using below vSphere management API to extend the VMDK of the VM. " ExtendVirtualDisk_Task(extendVirtualDisk) If yes, please refer the attached screenshots for m... See more...
Hi Nagendra, I assume you are using below vSphere management API to extend the VMDK of the VM. " ExtendVirtualDisk_Task(extendVirtualDisk) If yes, please refer the attached screenshots for more clarity. That should solve your problem. If you want more help on this, let me know. If you want to learn Java SDK for vSphere for automating your needs: Refer my blog : http://vthinkbeyondvm.com/getting-started-with-yavi-java-opensource-java-sdk-for-vmware-vsphere-step-by-step-guide-for-b…
As per me, it is highly recommended to have NTP/Time sync configured properly to avoid any issues.  I usually do not configure NTP and never faced any issue, however, all my deployments were test... See more...
As per me, it is highly recommended to have NTP/Time sync configured properly to avoid any issues.  I usually do not configure NTP and never faced any issue, however, all my deployments were test/Dev (Most of the time,  my deployments were embedded as well, everything on one machine). If it is production, it is must to have NTP settings configured. DRS rules configuration can be your own choice. (Either VM host affinity or anti affinity.)
Yes, adding SSDs as datastore is nothing different from adding Non-SSD datastores as usual. These SSDs will be formatted with VMFS as specified in above response. If you want to automate taggi... See more...
Yes, adding SSDs as datastore is nothing different from adding Non-SSD datastores as usual. These SSDs will be formatted with VMFS as specified in above response. If you want to automate tagging non-ssd as SSD: Refer my blog post, there is new API in vSphere 6.0 to mark HDD as SSD or vice versa: http://vthinkbeyondvm.com/vsphere-6-0-cool-apis-to-mark-local-host-hdd-to-ssd-ssd-to-hdd-sample-api-script/   Other manual way is to refer the KB specified in first response. vFRC: vFRC only works with local SSD devices -Adding vFlash resources to the host: Refer: http://www.yellow-bricks.com/2013/08/26/introduction-to-vsphere-flash-read-cache-aka-vflash/ -Configuring vFlash read cache (vFRC): Refer: https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc%2FGUID-211CE783-51A8-4B65-BFF6-434D1C272308.html
Not sure if you have looked into below post by William Lam on relocate VMs from one VC to another (even to VC completely different SSO domain) PowerCLI Did you know of an additional cool vMot... See more...
Not sure if you have looked into below post by William Lam on relocate VMs from one VC to another (even to VC completely different SSO domain) PowerCLI Did you know of an additional cool vMotion capability in vSphere 6.0? | virtuallyGhetto Below is my post on the same but using Java vSphere SDK. Want to vMotion a VM from one vCenter server to another vCenter using vSphere API? Here you go | vThinkBeyondVM You can refer these posts for your use case. Let me know if you need any more help.
There are several vCenters alarm and script will change as per the alarm you would like to configure. Below is the VMware blog on how to get started with managing alarms using PowerCLI. htt... See more...
There are several vCenters alarm and script will change as per the alarm you would like to configure. Below is the VMware blog on how to get started with managing alarms using PowerCLI. https://blogs.vmware.com/PowerCLI/2010/12/managing-vsphere-alarms-with-powercli.html Let me know if you need more help on this. 
Hi birdylarry, I have recently installed PowerCLI 6.0 R3 and I just executed "Get-Module" command and it shows all the modules we have as follows: PowerCLI C:\> Get-Module ModuleType... See more...
Hi birdylarry, I have recently installed PowerCLI 6.0 R3 and I just executed "Get-Module" command and it shows all the modules we have as follows: PowerCLI C:\> Get-Module ModuleType Version    Name                                ExportedCommands ---------- -------    ----                                ---------------- Script     0.0        Initialize-VMware.VimAutomation.... Script     0.0        Initialize-VMware.VimAutomation.... Script     0.0        Initialize-VMware_VimAutomation_Cis Script     0.0        Initialize-VMware_VimAutomation_Vds Script     0.0        Initialize-VMware_VumAutomation Manifest   3.1.0.0    Microsoft.PowerShell.Management     {Add-Computer, Add-Content, Checkpoint-Computer, Clear-Content...} Manifest   3.0.0.0    Microsoft.PowerShell.Security       {ConvertFrom-SecureString, ConvertTo-SecureString, Get-Acl, Get-Auth Manifest   3.1.0.0    Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable, Compare-Object...} Manifest   3.0.0.0    Microsoft.WSMan.Management          {Connect-WSMan, Disable-WSManCredSSP, Disconnect-WSMan, Enable-WSMan Binary     6.0.0.0    VMware.VimAutomation.Cis.Core       {Connect-CisServer, Disconnect-CisServer, Get-CisService} Binary     6.0.0.0    VMware.VimAutomation.Cloud          {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, Get-Catalog Script     6.0.0.0    VMware.VimAutomation.Core Binary     6.0.0.0    VMware.VimAutomation.HA             Get-DrmInfo Binary     1.0.0.0    VMware.VimAutomation.License        Get-LicenseDataManager Binary     6.0.0.0    VMware.VimAutomation.PCloud         {Connect-PIServer, Disconnect-PIServer, Get-PIComputeInstance, Get-P Manifest   6.0.0.0    VMware.VimAutomation.Sdk Binary     6.0.0.0    VMware.VimAutomation.Storage        {Export-SpbmStoragePolicy, Get-NfsUser, Get-SpbmCapability, Get-Spbm Binary     6.0.0.0    VMware.VimAutomation.Vds            {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, Export-VDPo Binary     1.0.0.0    VMware.VimAutomation.vROps          {Connect-OMServer, Disconnect-OMServer, Get-OMAlert, Get-OMAlertDefi Binary     6.0.0.0    VMware.VumAutomation                {Add-EntityBaseline, Copy-Patch, Get-Baseline, Get-Compliance...} See if your installation has some issues. I am running PowerCLI on Windows 7. Also, look for this : Local Operating System Support You can install VMware vSphere PowerCLI 6.0 Release 3 on the following operating systems: OS Type 64-Bit Server Windows Server 2012 R2 Windows Server 2008 R2 Service Pack 1 Workstation Windows 8.1 Windows 7 Service Pack 1 Refer: Compatibility Matrixes for vSphere PowerCLI 6.0 Release 3
vSphere replication is supported with vSAN: VMware Virtual SAN Interoperability: vSphere Replication and vCenter Site Recovery Manager - VMware vSphere Blog - VMwar… SRM also is supported on v... See more...
vSphere replication is supported with vSAN: VMware Virtual SAN Interoperability: vSphere Replication and vCenter Site Recovery Manager - VMware vSphere Blog - VMwar… SRM also is supported on vSAN: VMware Virtual SAN Interoperability: vSphere Replication and vCenter Site Recovery Manager - VMware vSphere Blog - VMwar… Whats New – VMware Virtual SAN 6.1 - Virtual Blocks Storage DRS is still not supported on vSAN. However, SRM and VR works with SDRS : http://www.yellow-bricks.com/2015/02/09/what-is-new-for-storage-drs-in-vsphere-6-0/
In vSphere 6.0, we have some cool APIs available around this Refer my blog post on API sample script : Mark local HDD as SSD and SSD as HDD : http://vthinkbeyondvm.com/vsphere-6-0-cool-apis-to-m... See more...
In vSphere 6.0, we have some cool APIs available around this Refer my blog post on API sample script : Mark local HDD as SSD and SSD as HDD : http://vthinkbeyondvm.com/vsphere-6-0-cool-apis-to-mark-local-host-hdd-to-ssd-ssd-to-hdd-sample-api-script/
Yes. PowerCLI is specific to VMware. In order to connect to Hyper V, I believe, you can use PowerShell (By MS)
Hi PowerCLI experts,   Here is my requirement, I have a VM in source cluster (cluster is DRS enabled) and SDRS enabled cluster. Now I would like to migrate that VM from source cluster (DRS ... See more...
Hi PowerCLI experts,   Here is my requirement, I have a VM in source cluster (cluster is DRS enabled) and SDRS enabled cluster. Now I would like to migrate that VM from source cluster (DRS and SDRS cluster) to destination DRS cluster and SDRS cluster. There is NO shared storage between these 2 clusters. XVMotion is the way to go but I want DRS and SDRS enabled so that these features will take care of migrated VM placement (as part of initial placement). PowerCLI C:\> Get-VM -Name VM | Move-VM -destination host-2 -datastore DSC (This is datastore cluster) It seems above cmdlet does not work when we send DRS cluster as destination. What is the workaround for this? I was thinking as below. - Get all the VMs to be migrated ( to other cluster/datastorecluster.) -In a loop, initiate the vMotion per VM on to destination DRS cluster. This is initial placement scenario, hence DRS will recommend some hosts, pick the first host from list of recommendations for that VM : (How to achieve this using PowerCLI that we need to figure out) - Once we pick the host from above step for first VM, use the powerCLI Move-VM cmdlet (as  specified above). -Repeat the same for all the VMs to be migrated. My VC and Hosts are on 5.5u2 builds. Do we have any direct way to achieve this? Any suggestions to achieve this using PowerCLI would be great.
Can you please provide more details? such as how many hosts/VMs in DRS cluster. what are the exact rules you have created etc?
Arniczek wrote: If my vsphere is 5.0 and i will connect to it with client 5.0 update 3 is it ok ? Does client 5.0 U3  not mess up with vsphere 5.0 ?? Yes, you can manag... See more...
Arniczek wrote: If my vsphere is 5.0 and i will connect to it with client 5.0 update 3 is it ok ? Does client 5.0 U3  not mess up with vsphere 5.0 ?? Yes, you can manage ESXi 5.0 by using vSphere client 5.0 U3. It will not mess up
At the moment, its not possible. As per me, its good to have feature. I had proposed this earlier. Let me take this forward based on your feedback. On the other hand, you can fine tuned the D... See more...
At the moment, its not possible. As per me, its good to have feature. I had proposed this earlier. Let me take this forward based on your feedback. On the other hand, you can fine tuned the DPM behavior so that DPM will be conservative at the first place to put the host into standby mode. Refer: VMware KB: Changing the default behavior of Distributed Power Management in vSphere
It is surprising. It might work in certain case (as per ur testing) but officially not supported on 5.5.  In vcenter 6.0 its officially supported as per the announcement, even across vCenter its ... See more...
It is surprising. It might work in certain case (as per ur testing) but officially not supported on 5.5.  In vcenter 6.0 its officially supported as per the announcement, even across vCenter its supported.. Refer: https://www.vmware.com/files/pdf/vsphere/VMware-vSphere-Platform-Whats-New.pdf
Fully agree with Marc.
Define the Role to Be Assigned To provide for more granular access to your vSphere environment, first create a new role. You can create a custom limited vCenter Server role by using the vS... See more...
Define the Role to Be Assigned To provide for more granular access to your vSphere environment, first create a new role. You can create a custom limited vCenter Server role by using the vSphere Web Client. A custom role is a set of privileges that you define. Procedure 1 Log in to the vSphere Web Client as the vCenter Server administrator. 2 Browse to Administration > Role Manager. 3 Select your vCenter Server system from the drop-down menu. 4 Click Create role action. 5 Type a name for the new role. Type Deployer of virtual machines from template . 6 Select privileges for the new role. ■ Datastore.Allocate space ■ Datastore.Browse datastore ■ Global.Cancel task ■ Network.Assign network ■ Resource.Assign virtual machine to resource pool ■ Scheduled task.Create tasks ■ Scheduled task.Run task ■ Virtual machine.Configuration.Add new disk ■ Virtual machine.Inventory.Create new ■ Virtual machine.Provisioning.Deploy template 7 Click OK. You created the new vCenter Server role Deployer of virtual machines from template. Refer :VMware vSphere 5.1? As per above example, you can try creating other custom roles
Just for your info. Below are best practices to unmount datastore from vCenter. Below checks should be considered. -No VM resides on the datastore -The datastore is not part of Datastore ... See more...
Just for your info. Below are best practices to unmount datastore from vCenter. Below checks should be considered. -No VM resides on the datastore -The datastore is not part of Datastore cluster -The datastore is not managed by storage DRS -SIOC is disabled for this datastore -The datastore is not used for vSphere HA heartbeat. If you are connected to vCenter using VI client, all above checks are handled by VI client itself. If you want to do the same using script : Refer: Datastore Mount/Unmount Detach/Attach functions
This is strange. All right let me know the SR number once you open ticket with VMware.
I checked in my environment and if you get Version 5.5.0 Build 1441077 from web client about page then build version number corresponding  to it is 5.5.19839. This web client build Version 5... See more...
I checked in my environment and if you get Version 5.5.0 Build 1441077 from web client about page then build version number corresponding  to it is 5.5.19839. This web client build Version 5.5.0 Build 1441077 was shipped with VC 5.5 0b  (Release notes: vCenter Server 5.5.0b Release Notes)) are you sure you are log in to the correct web client & not the one which is installed as part of VC 5.5 0b?
The version number that you are getting for web client from programs and features is correct for VC55u2d .ie.. Version 5.5.0.14567. So its latest already. In fact, this is build version number an... See more...
The version number that you are getting for web client from programs and features is correct for VC55u2d .ie.. Version 5.5.0.14567. So its latest already. In fact, this is build version number and the one I told in last update is web client build number. Build version number is the one used internally in the windows registry also. If you are upgrading your environment, build version number that you see from programs and features will be checked to decide whether upgrade is required or not. if existing build version number (from programs and features ) is lower that the build version number of the build you are installing then upgrade is required. Otherwise you are already on the latest. I hope you got this difference. Just confirm the build number from web client now. If its same as the one I have mentioned( most probably it should be same).