Is there a way to make a report that shows any vms without a security tag attached, print it to html, and add a total at the bottom. Is this doable or is something needed to pull this data from NSX?
Great.
Can you try like this
where {(Get-NsxSecuritytagassignment -VirtualMachine $_) -eq $null}
select name
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
To start you could verify if those tags are visible with the regular tag cmdlets.
Do they show when you do a Get-TagAssignment?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
It does not seem to show up with those commands.
Then you will have to use the PowerNSX module I guess.
Something like this
Get-VM | where{(Get-NsxSecuritytagassignment) -eq $null}
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Sorry it just ask for a security tag:
Then try the one I provided in Re: Security Tags in NSX
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
I am struggling hard on this, no idea why, but this is what I see when I just try to connect to my NSX Manager:
I assume you already saw Kyle's post Getting Started with the PowerCLI Module for VMware NSX-T ?
The only difference I see is the credentials, but the error seems to come earlier.
Does adding the -Verbose switch give any more information?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Could this be a DNS issue?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
No DNS name is used, just IP. Wanted to rule that out to start. I used the verbose tag and didn't show anything new.
Did you check the TLS version(s) your PowerShell session can use?
[Net.ServicePointManager]::SecurityProtocol
If TLS12 is not in there, run the following before trying the connection
[System.Net.SecurityProtocolType]::Tls11,
[System.Net.SecurityProtocolType]::Tls
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Sorry shows this:
PS C:\Windows\system32> [Net.ServicePointManager]::SecurityProtocol
Tls12
PS C:\Windows\system32>
That seems to be ok.
I'm at my wit's end, for now, I'm afraid.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Please forgive me, I am losing my mind slowly and simply typed the IP wrong. Again VERY SORRY, but there is a new error:
Are you getting the same error when you provide all the values on the cmdlet, instead of being prompted for them?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Yes both ways
To eliminate any 'dirty bits', did you stop/start your PowerShell session before trying again?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Ya I did that, no change
I think you might want to open an SR for this.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Sorry where can I put a SR in for this product?