vThinkBeyondVM's Posts

Unfortunately no easy way to rebuild. Backup and restore of the entire VC is one safe but heavy option. In latest releases, user can not disable DRS from UI client (vSphere client) if cluster has Supervisor enabled (i..e vSphere with Tanzu)

Below articles will help you to understand vMotion and EVC behavior post the patches you applied. 1. Confirming whether entire EVC cluster is patched or not and see new cpubits are available on all hosts (new cpu bits got introduced into these patches) http://vthinkbeyondvm.com/pyvmomi-script-confirm-whether-evc-cluster-patched-not-spectre-vulnerability/ 2. This is again related post: http://vthinkbeyondvm.com/adding-host-empty-evc-cluster-fails-simple-workaround/

Here is the KB related to this :VMware Knowledge Base With latest vSphere releases, there is little change in vMotion and EVC behavior if your cluster has some hosts does not have these patches applied. Quoting from KB: vMotion and EVC Information An ESXi host that is running a patched vSphere hypervisor with updated microcode will see new CPU features that were not previously available. These new features will be exposed to all Virtual Hardware Version 9+ VMs that are powered-on by that host. Because these virtual machines now see additional CPU features, vMotion to an ESXi host lacking the microcode or hypervisor patches applied will be prevented. The vCenter patches enable vMotion compatibility to be retained within an EVC cluster. In order to maintain this compatibility the new features are hidden from guests within the cluster until all hosts in the cluster are properly updated.  At that time, the cluster will automatically upgrade its capabilities to expose the new features. Unpatched ESXi hosts will no longer be admitted into the EVC cluster. Can you confirm whether your source cluster has all hosts patched with build you specified i.e. 7967664 ? Post applying these patches, whether power cycle was done? Whether your destination cluster has all hosts with "8169922" build?

Recently I have written couple of articles on Proactive HA for lab/educational purpose only. -Tutorial: Part-1: How to configure & manage Proactive HA using pyVmomi? - vThinkBeyondVM - http://vthinkbeyondvm.com/tutorial-part-2-how-to-simulate-proactive-ha-using-pyvmomi/

since you have VSAN in your env, whether VSAN license required? Here is VSAN licensing guide: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsan/vmware-vsan-66-licensing-guide.pdf I will come back if I get additional data.

Since this thread is about SDRS VM overrides, I thought to share my article on the same, which was written long back Refer: Editing Storage DRS VM overrides : Java vSphere SDK and PowerCLI script - vThinkBeyondVM This post will answer: What is SDRS VM overrides, how to configure and how to use PowerCLI or Java SDK to re-configure it.?

MOB is client for all vSphere SOAP based APIs. Tags are not part of these vSphere APIs. As part of vSphere 6.5, VMware released REST APIs as well and tag APIs are included there. Here is REST API getting started tutorial: http://vthinkbeyondvm.com/getting-started-with-vcenter-server-rest-apis-using-python/

I have modified earlier pointed “CreateNFSDatastore” class to work for both VC and ESXi. And also I have written another class “AddNFSDatastoreinESXi” which will work only for ESXi to add the NFS datastore. Please take a look. CreateNFSDatastore.java à Now it works for both VC/ESXi to add NFS datastore ,        Usage: CreateNFSDatastore url username password hostip/fqdn        Note:: In ESXi case both url & hostip/fqdn ip should be same. AddNFSDatastoreinESXi.java à It works only for ESXi to add NFS datastore.      Usage: AddNFSDatastoreinESXi hostname username password Let us know if you need more help.

As per me,        Nov patch no longer exists as it has been recalled by MS – a.       https://www.askwoody.com/2016/microsoft-pulls-ms-3197868-the-win7-security-rollup-that-blew-apart-malwarebytes/comment-page-1/ b.       Search for 3197868 @ https://technet.microsoft.com/en-us/security/bulletins.aspx. It seems, it is unrelated to KB 3814779 Overall, As per me, this is an issue from MS side, thus uninstalling the issue may fix this problem. Let me know if you need any more info

This is just for info 1. https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2146439 2.There is video at the end of article: vCenter Server Migration Tool: vSphere 6.0 Update 2m - VMware vSphere Blog

Hi Friend, As we discussed in other discussion, creating NFS datastore using API (using vCenter session ) was successful and it is added on sample exchange: Create NFS Datastore using vSphere API - Samples - VMware Developer Center I have decided to try to create the same using ESXi server session. I will get back as soon as possible. please stay tuned. Nonetheless, You can request any API sample/requirement now on VMware sample exchange here: All Samples - Samples - VMware Developer Center   It is one point shop for any  API related activity across any product, any SDK

Your code looks similar to mine. When I looked for the fault that you are getting https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.fault.PlatformConfigFault.html Fault Description A PlatformConfigFault is a catch-all fault indicating that some error has occurred regarding the configuration of the host. Data about the fault is available and will be presented as a platform specific string. is your environment configured properly?