Zsoldier Tracker

Re: Update Guest OS Version

Zsoldier — Mon, 17 Apr 2023 16:59:09 GMT

I think it 'used' to be possible, but the current cmdlet set doesn't allow it. I agree it would be nice if it would 'stage' the change for next reboot, but I think that is problematic because I don't think it actually plays a role until you reboot the VM itself (not just the guest OS reboot).

vCheck may need to be updated to read what the VMware tools report instead. What plugin in vCheck complains?

Re: Update Guest OS Version

Zsoldier — Mon, 17 Apr 2023 14:47:29 GMT

I'm not aware that is possible via standard methods. You could maybe update the configuration file, but that is a lot of work for little gain.

I wouldn't worry about it.

Change the Configured Guest Operating System (vmware.com) < Describes what that setting does.

Re: Disable Quickstart for existing cluster

Zsoldier — Tue, 11 Oct 2022 17:35:32 GMT

$Cluster = Get-Cluster

$Cluster.ExtensionData.AbandonHciWorkflow()

Re: Applying NSXT Tag to a VM

Zsoldier — Tue, 11 Oct 2022 16:25:49 GMT

SkipCertificateCheck is only available via Powershell Core I believe.

Re: Copy NSX-T Tags to VM_replica

Zsoldier — Mon, 13 Sep 2021 16:55:13 GMT

Sorry, haven't had time to dedicate to this as it requires a bit more work than a couple of simply lines. I'll try to get to it this week. Trying to make something "nice", but that's just my OCD kicking in.

You could use a combination of these two methods I wrote previously:

https://gist.github.com/Zsoldier/9eda954f0c972d17c124040d7759054a

https://gist.github.com/Zsoldier/1a42161e53e841e2e3f3d1e02bd159c4

Re: Add security tag to a new vm in NSX-T with powershell

Zsoldier — Fri, 10 Sep 2021 15:31:56 GMT

You could maybe start here then as part of your new VM build script:

https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Applying-NSXT-Tag-to-a-VM/m-p/2863049#M102859

Re: Add security tag to a new vm in NSX-T with powershell

Zsoldier — Thu, 09 Sep 2021 13:41:22 GMT

Based on the API doc, page size is limited to 1000. https://vdc-download.vmware.com/vmwb-repository/dcr-public/d6de7a5e-636f-4677-8dbd-6f4ba91fa5e0/36b4881c-41cd-4c46-81d1-b2ca3a6c693b/api_includes/method_ListAllVirtualMachines.html

Unfortunately, I don't see anyway that you could get a filtered list from this api endpoint in particular. Weird that they would limit it to 1000. Seems like an oversight, but depending on what you are trying to accomplish from this particular call, there might be another way.

What is it that you are trying to do exactly @cvv2 ?

Re: Script Failing to Run

Zsoldier — Tue, 07 Sep 2021 16:03:01 GMT

Assuming that script is using the vmware.imagebuilder module, you'll need to run that particular script in "Windows Powershell" with vmware.powercli module installed.

Powershell Core is OS-agnostic version that not all modules have been ported to.

Re: Report For specific NSXT Tag Phrase

Zsoldier — Tue, 31 Aug 2021 17:11:13 GMT

$report = $Report.Results | where-object {$_.tags -like '*Locked*' -and $_.display_name -notmatch 'vmware-ioinsight'} | Select-Object display_name

Try this. Also, still planning on answering your other question, but more involved.

Re: Copy NSX-T Tags to VM_replica

Zsoldier — Tue, 24 Aug 2021 16:31:41 GMT

I'm not aware of any. My assumption is that you want to get the tags applied in NSX-T on a VM in vCenter, copy the tags associated w/ that and overwrite or append to a new replica VM?

Solved: Re: Applying NSXT Tag to a VM - VMware Technology Network VMTN

Re: Applying NSXT Tag to a VM

Zsoldier — Fri, 20 Aug 2021 14:17:36 GMT

Have you tried running the code I posted above verbatim? There are lots of problems w/ the way that you've modified your script. $apiendpoint is not defined correctly since you've commented it out and is not before you capture your base_url. Commenting out scope doesn't work the way you've done here. I've cleaned up my script example further so you can omit scope if you don't need it and change the get-vm call to base on a vmnamefilter variable.

Also, you do not need to import the PowerNSX module unless you are making additional calls to an NSX-V instance in the same script.

#Requires -Module vmware.powercli $Credential = Get-Credential $skipcertcheck = $true $AuthMethod = “Basic” $NSXMgr=”0.0.0.0” $apiendpoint = "/api/v1/fabric" $base_url = ("https://" + $NSXMgr + $apiendpoint) $tag = "Naka" $scope = "NakaScope" # If scope not required, simply define as $null or "" $vmnamefilter = "nakabuntu" # Not required. Will loop through all VM's otherwise. $vms = Get-VM $vmnamefilter | Get-View -Property "Config" # Add Tags to existing tags (Valid for NSX-T 3.1.2, previous versions only have update_tag) $endpoint = "/virtual-machines" $action = "add_tags" Foreach ($vm in $vms) { $vmid = $vm.Config.InstanceUuid If ([string]::IsNullOrWhiteSpace($Scope)){ $JSON = " { `"external_id`":`"$vmid`", `"tags`": [ { `"tag`":`"$Tag`" } ] } " } Else{ $JSON = " { `"external_id`":`"$vmid`", `"tags`": [ { `"scope`":`"$scope`", `"tag`":`"$Tag`" } ] } " } $Data = Invoke-restmethod -Uri ($base_url + $EndPoint + "?action=" + $action) -Method POST -Body $JSON -ContentType 'application/json' -Credential $Credential -SkipCertificateCheck:$skipcertcheck -Authentication:$AuthMethod }

Re: Applying NSXT Tag to a VM

Zsoldier — Fri, 20 Aug 2021 12:32:48 GMT

Did you change the get-vm filter?

Re: Applying NSXT Tag to a VM

Zsoldier — Mon, 16 Aug 2021 17:39:25 GMT

Basically means malformed json. Here is script cleaned up a bit.

#Requires -Module vmware.powercli $Credential = Get-Credential $skipcertcheck = $true $AuthMethod = “Basic” $NSXMgr=”0.0.0.0” $apiendpoint = "/api/v1/fabric" $base_url = ("https://" + $NSXMgr + $apiendpoint) $tag = "Naka" $scope = "NakaScope" $vms = Get-VM -Name nakabuntu | Get-View -Property "Config" # Add Tags to existing tags (Valid for NSX-T 3.1.2, previous versions only have update_tag) $endpoint = "/virtual-machines" $action = "add_tags" Foreach ($vm in $vms) { $vmid = $vm.Config.InstanceUuid $JSON = " { `"external_id`":`"$vmid`", `"tags`": [ { `"scope`":`"$scope`", `"tag`":`"$Tag`" } ] } " $Data = Invoke-restmethod -Uri ($base_url + $EndPoint + "?action=" + $action) -Method POST -Body $JSON -ContentType 'application/json' -Credential $Credential -SkipCertificateCheck:$skipcertcheck -Authentication:$AuthMethod }

Re: Applying NSXT Tag to a VM

Zsoldier — Wed, 11 Aug 2021 21:21:04 GMT

Scope can be anything really. There are also other methods of tag updates available depending on version you are working against. Which NSX-T version are you using? 3.1.2 gives you more options outside of just update tag to simplify your scripting too. 2.5.x limits to just update.

https://vdc-download.vmware.com/vmwb-repository/dcr-public/d6de7a5e-636f-4677-8dbd-6f4ba91fa5e0/36b4881c-41cd-4c46-81d1-b2ca3a6c693b/api_includes/system_administration_configuration_fabric_inventory_virtual_machines.html

Re: Applying NSXT Tag to a VM

Zsoldier — Wed, 11 Aug 2021 20:58:32 GMT

You need to define $newscope variable is what it looks like.

Re: Report For Tagless VMs with NSX-T

Zsoldier — Tue, 13 Jul 2021 14:28:29 GMT

Looking at the API makes me believe that this is not possible as it seems a tag must be associated w/ a Virtual Machine. As a workaround, might I suggest creating a dummy VM and tagging that. It can literally be a VM w/ no disk, no network card assigned. As long as it's in vCenter inventory, you can tag it, assuming you have NSX-T sync'd w/ vCenter Inventory.

As far as learning Powershell, I learned organically w/ superb help from @LucD's many community post examples. As far as material, I've heard great things about Don Jones 30 days of lunches series. Learn PowerShell in a Month of Lunches: Covers Windows, Linux, and macOS: Plunk, Travis, Petty, James, Leonhardt, Leon: 9781617296963: Amazon.com: Books

This forum in general is also a good place to find many examples too.

Re: Report For Tagless VMs with NSX-T

Zsoldier — Mon, 12 Jul 2021 20:22:45 GMT

To clarify w/ filter:

$Report.Results | where-object {$_.tags -eq $null} | Select-Object display_name # Display_Name is likely what you are looking for, but you can append w/ commas or just leave it at that.

Re: Report For Tagless VMs with NSX-T

Zsoldier — Mon, 12 Jul 2021 20:23:47 GMT

Ah, no worries

Do the following:

#Assuming you are capturing the $data output in my example above into $report instead. $Report.results | Get-Member #Above will return to you the 'properties' you have available for selection. #If you want to look at example of what might fill those properties, you can just grab one like below: $Report.results[0] #To get select only the properties you want: $Report.Results | Select display_name #Display_Name is likely what you are looking for, but you can append w/ commas or just leave it at that.

Re: Report For Tagless VMs with NSX-T

Zsoldier — Mon, 12 Jul 2021 17:57:59 GMT

$report = $report.results | where { $_.tags -eq $null }

#Get-VM is working against vCenter, not NSX-T.

Re: Report For Tagless VMs with NSX-T

Zsoldier — Mon, 12 Jul 2021 15:53:16 GMT

Not perfect by any means, but hopefully this gets you going in right direction. Basically, VM's without tags will not have a 'tags' property when querying realized state. This works in Powershell Core (aka Powershell 7). Will not work as written in classic Powershell.

NSX-T: Finding Tagless NSX-T VMs with Powershell Core (zsoldier.com)

$Credential = Get-Credential

$skipcertcheck = $true

$AuthMethod = “Basic”

$NSXMgr=”NSXTManagerIPorDNSName”

$policyapi = "/policy/api/v1"

$base_url = ("https://" + $NSXMgr + $policyapi)

$endpoint = "/infra/realized-state/virtual-machines"

$Data = Invoke-restmethod -Uri ($base_url + $EndPoint) -Method GET -Credential $Credential -SkipCertificateCheck:$skipcertcheck -Authentication:$AuthMethod

#VMs without tags

$data.results | where {$_.tags -eq $null}

#VMs with tags

$data.results | where {$_.tags -ne $null}