CarlPower's Posts

Heres a couple of scripts I've developed, to assist in updating 160 clusters at our company - I'm sharing these to help out those who still may be struggling wtih vLCM, being not as quick to change settings at the old baselines method The first script requires you to export a working JSON - what I have done is build a JSON with all the components I need for every cluster, so it can be applied to all my single image clusters.  I also don't use a remote location, as its easier to use a local folder on the computer running the script. I'm not a pro at scripting, so I comment a lot to ensure I know where I am, and this helps with running the scripts line by line.   ############################################################################## ### Update the Single Image Cluster settings for multiple cluster branches ### ############################################################################## # Author: Carl Power # Description: Setup multiple clusters with a common single image # Status: Test # Date tested: 20 Oct 2023 #----------------------------# #-- development change log --# #------------------------- --# # 20 Oct 2023: refined script and removed remote JSON path option. # 7 Aug 2022: created script. #-------------------------------# #-- set the initial variables --# #-------------------------------# <# set the JSON local folder #> $folder_json = "D:\Scripts\_Data" <# set the JSON local file #> $file_json = "70U3o.json" <# set the temporary cluster for script checking#> $cluster = "LABESXCL01" <# set the cluster path 1 #> $path_cluster1 = "Auckland" <# set the cluster path 2 #> $path_cluster2 = "Wellington" <# set the vcenter path #> $vctr = "vcenter.site.co.nz" #-------------------------------------------------# #-- script start - do not modify anything below --# #-------------------------------------------------# Clear-Host "`n" # Create consolidated variables $path_json = "$folder_json\$file_json" # Connect to the vCenter server connect-viserver –server $vctr # Create a function to call later for each cluster branch Function UpdateImage { Foreach ($cluster in $clusters) { Write-Host "Updating cluster $cluster" Import-LcmClusterDesiredState -Cluster $cluster -LocalSpecLocation $path_json } } # Update path 1 clusters $clusters = get-cluster -Location $path_cluster1 UpdateImage # Update path 2 clusters $clusters = get-cluster -Location $path_cluster2 UpdateImage # Disconnect from the vCenter server disconnect-viserver $vctr       ##################################################################### ### Update baselines for witnesses outside a cluster single image ### ##################################################################### # Author: Carl Power # Description: attach or remove baselines on additional Witness hosts not updated with the single image cluster, where they end with a common string # Status: Test # Date tested: 20 Oct 2023 #----------------------------# #-- development change log --# #------------------------- --# # 20 Oct 2023: refined script # 19 Oct 2023: created script #-------------------------------# #-- set the initial variables --# #-------------------------------# <# set the Baseline to detach#> $base_detach = "ESXi 7.0 U3n (21930508)" <# set the Baseline to attach#> $base_attach = "ESXi 7.0 U3o (22348816)" <# set the Witness search argument #> $wit_mask = "*witness2.site.co.nz" <# set the temporary Witness for script checking#> $witness2 = "labwitness2.site.co.nz" <# set the cluster path 1 #> $path_cluster1 = "Auckland" <# set the cluster path 2 #> $path_cluster2 = "Wellington" <# set the vcenter path #> $vctr = "vcenter.site.co.nz" #-------------------------------------------------# #-- script start - do not modify anything below --# #-------------------------------------------------# Clear-Host "`n" # Connect to the vCenter server connect-viserver –server $vctr # Create a function to call later for each cluter group Function UpdateWitness2 { Foreach ($witness2 in $witnesses) { Write-Host "Updating Witness named $witness2" #Detach old baseline from Witness, ensuring no empty value if ($base_detach -ne " ") { get-baseline $base_detach | Detach-Baseline -entity $witness2 } #Attach new baseline to Witness, ensuring no empty value if ($base_attach -ne " ") { get-baseline $base_attach | Attach-Baseline -entity $witness2 } } } # Update Path 1 clusters $witnesses = get-vmhost -name $wit_mask -Location $path_cluster1 UpdateWitness2 # Update Path 2 clusters $witnesses = get-vmhost -name $wit_mask -Location $path_cluster2 UpdateWitness2 # Disconnect from the vCenter server disconnect-viserver $vctr     I hope this helps someone out!

I'd like to think I've done a fair bit with single image clusters, now supporting around 160 single image clusters, but theres a number of points that really bug me at present... 1. No linked single image: Of all our single image clusters, they all use the same hardware with the same addons and components, so it would be really beneficial to link to a common image (much like a baseline), rather than set each of my 160 single image clusters individually - no matter how I do it, I need to either script to update 160 clusters (which is not as easy as it sounds), or manually update 1 by 1. 2. VMware tools is not a base image item: You would think out of all the components to add to the single image main screen, the esxi version should be the first item as expected, but the vmtools version should be the next item as theres often security updates for it - having to dig through the components list to find such a key component seems really short sighted to me. 3. The firmware version is not showing in parent folder summaries: It might be minor, but the summary page in the parent folder tree does not show the firmware version - this is really beneficial for quick checks to see which single images need updating, while there is no linked single image. I'm sure theres countless others to add, but after really good help from the Denver support team, they have managed to resolve most of my other issues...

Hi team, I'm trying to simplify making changes to 160 of our single image clusters, and I'm looking to set ESXi to 7.0 U3m with VMware tools 12.3.0 What variables and related arguments would I need to add to the below, to update the existing VMtools version to 12.3.0 without removing any other components? $LcmImageESXi = Get-LcmImage -Version "7.0 U3n - 21930508" $LcmImageVMtools = ????? Get-Cluster -Name $LcmCluster | Set-Cluster -BaseImage $LcmImageESXi -Component $LcmImageVMtools

Hi peoples,  What I am trying to do is get the some information from the Updates/Clusters menu from my vCenter I can connect to my vCenter server, I can get a list of hosts with build IDs, but I cannot find the commands to get the information on the following fields: The correct cluster name, not the parent folder name (we have several levels of folders to get to the clusters) The ESXi build The vendor addon, with version The firmware addon, with version Is this even possible from a Powershell script, or is this still a manual process?