You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ChangeLog.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,12 @@
1
1
### ChangeLog for vNugglets.Utility PowerShell module
2
2
3
+
#### v1.next, not yet released
4
+
5
+
-\[improvement] updated function `Get-VNVMByAddress`:
6
+
- greatly increased speed by using `VMware.Vim.SearchIndex` for by-IP searches (does support wildcard, though -- by wildcard still uses slower mechanism); example speed increase: went from 13s to about 0.25s in a vCenter with about 7,500 VMs -- woo-hoo!
7
+
- added new parameters `-GuestHostname` and `-UUID` to support for searching by guest DNS name or VM BIOS UUID (these also use a method of `VMware.Vim.SearchIndex`, so the searches are super fast)
8
+
9
+
3
10
#### v1.1, released 20 Dec 2016
4
11
5
12
-\[new] added function `Find-VNVMWithDuplicateMACAddress` for finding duplicate VM NIC MAC address in vCenter
@@ -10,13 +17,13 @@
10
17
- created module from many of the juicy snippets/functions that we shared at [vNugglets.com](http://vNugglets.com) over the years
11
18
- updated `Copy-VNVIRole` to be a safer function overall by removing old `Invoke-Expression` methodology
12
19
- standardized parameter names across cmdlets in the module and expanded some previously truncated/cryptic parameter names (go, usability and discoverability!)
13
-
- added/updated "by name regular expression pattern" and "by liternal name string" parameters to several cmdlets
20
+
- added/updated "by name regular expression pattern" and "by literal name string" parameters to several cmdlets
14
21
- modernized cmdlets to use capabilities of somewhat newer PowerShell releases (like ordered hashtables) and built-in property return iteration, breaking PowerShell v2.0 compatibility (it's time to upgrade, right?)
15
-
- updated `Invoke-VNEvacuateDatastore`:
22
+
- updated `Invoke-VNEvacuateDatastore`:
16
23
- added feature that uses any/all datastores in datastore cluster (when specifying a datastore cluster for Destination parameter value) for potential destination _per object_ (this allows for a potentially different datastore for each virtual disk on a VM)
17
24
- added ability to exclude a VM/template's files from evacuation process (via parameter)
18
25
- added `-WhatIf` support
19
-
- updated cmdlet names to use standard/approved verbs where they were not already in use. Renamed functions/snippets as follows:
26
+
- updated cmdlet names to use standard/approved verbs where they were not already in use. Renamed functions/snippets as follows:
20
27
-`Get-VNVMByRDM` was "Get-VMWithGivenRDM"
21
28
-`Get-VNVMByVirtualPortGroup` was "Get-VMOnNetworkPortGroup"
- use `VMware.Vim.SearchIndex` for speed for FindAllByIp (does support wildcard, though)
10
-
- support searching by guest DNS name (also using `VMware.Vim.SearchIndex`, via the `FindAllByDnsName` method)
11
8
- update function `Get-VNVMByVirtualPortGroup` to take a standard- or distributed virtual portgroup as a parameter (and, from pipeline)
12
9
- update function `Copy-VNVIRole` to take SourceVIRole as VIRole object, and to accept it from pipeline
13
10
- update function `Get-VNUplinkNicForVM` to give more meaningful VDSwitch identification (currently returns something to the effect of `DvsPortset-1` for the VDSwitch name)
Get VMs with given SMBIOS UUID, return VM name and its UUID
260
+
245
261
.Link
246
262
Get-VNVMByRDM
247
263
Get-VNVMByVirtualPortGroup
248
264
http://vNugglets.com
249
265
250
266
.Notes
251
-
Finding VMs by IP address relies on information returned from VMware Tools in the guest, so those must be installed in the guest and have been running in the guest at least recently.
267
+
Finding VMs by IP address / Guest hostname relies on information returned from VMware Tools in the guest, so VMware Tools must be installed in the guest and have been running in the guest at least recently.
252
268
253
269
.Outputs
254
270
Selected.VMware.Vim.VirtualMachine
@@ -263,21 +279,67 @@ function Get-VNVMByAddress {
## the vCenter name for this SearchIndex (ServiceUrl is like "https://myvcenter.dom.com/sdk", and the .Host property of a .NET URI object is just the DNS hostname portion of the URI)
## the vCenter name for this SearchIndex (ServiceUrl is like "https://myvcenter.dom.com/sdk", and the .Host property of a .NET URI object is just the DNS hostname portion of the URI)
## the vCenter name for this SearchIndex (ServiceUrl is like "https://myvcenter.dom.com/sdk", and the .Host property of a .NET URI object is just the DNS hostname portion of the URI)
0 commit comments