Part 3 of this series provides practical examples for the Get-View command. This is a great way to save time.

PowerCLI is an extremely useful extension to PowerShell designed specifically for managing VMware infrastructures. It allows administrators to perform a wide range of management and automation tasks quickly and efficiently. In this article, we will focus on the Get-View command, which provides a powerful way to access, filter, and sort advanced information about virtual machines (VMs).

The series is composed of the following articles:

• Introduction and VM inventory management (part 1)
• Creating snapshots and VMware templates (part 2)
• General VMware navigation and advanced information (part 3)

Basics of Get-View

The Get-View command is a key element of PowerCLI that provides access to advanced information and functionality in the VMware vSphere API. Unlike the Get-VM command, which is often used for basic administrative tasks, Get-View provides greater performance and flexibility, especially when dealing with complex queries and automation scripts.

An example of how Get-View can be used to quickly access advanced information is the following command:

$vmView = Get-View -ViewType VirtualMachine -Filter @{"Name"="WebServer01"}

This command returns a comprehensive list of information about the VM "MyVM" that is retrieved through the vSphere API.

Praxisbeispiele und Anwendungsfelder

Get-View is especially useful if you want to get advanced information about your VMs, or if you want to filter and sort this information specifically. For example, you can use Get-View to get the memory (RAM) and CPU usage of all VMs in your environment:

$vmViews = Get-View -ViewType VirtualMachine 

foreach ($vmView in $vmViews) {

	$vmName = $vmView.Name 

	$vmMemory = $vmView.Summary.Config.MemorySizeMB 

	$vmCpuUsage = $vmView.Summary.QuickStats.OverallCpuUsage 

	Write-Output "VM Name: $vmName" 

	Write-Output "Memory: $vmMemory" 

	Write-Output "CPU Usage: $vmCpuUsage MHz" 

}

This script prints the name, memory, and CPU usage of each VM in your environment.

You can also use Get-View to filter VMs based on certain criteria, such as VMs older than 30 days:

$limitDate = (Get-Date).AddDays(-30) 

$allVMs = Get-View -ViewType VirtualMachine



$oldVMs = $allVMs | Where-Object { $_.Config.CreateDate -lt $limitDate }



foreach ($oldVM in $oldVMs) {

	Write-Host "Old VM Name: $($oldVM.Name)" 

}

Get-View can also be integrated with automation scripts, for example, to generate regular reports or to perform maintenance tasks. You could use Get-View in combination with automation solutions like ScriptRunner to schedule and run regular tasks without manual intervention.

Another practical example of using Get-View is to monitor the state of VM space usage. You could create a script that identifies VMs with a high percentage of thin-provisioned memory in use, and store that information for later review or optimization:

$vmViews = Get-View -ViewType VirtualMachine 

$threshold = 80



foreach ($vmView in $vmViews) {

	$vmName = $vmView.Name 

    $vmProvisionedSpace = $vmView.Summary.Storage.Committed 

    $vmUsedSpace = $vmView.Summary.Storage.Uncommitted 

    $vmTotalSpace = $vmProvisionedSpace + $vmUsedSpace 

    
    if ($vmTotalSpace -ne 0) {

    	$vmUsedPercentage = ($vmUsedSpace / $vmTotalSpace) * 100

        
        if ($vmUsedPercentage -gt $threshold) { 

        	Write-Output "VM Name: $vmName"

            Write-Output "Used Space Percentage: $vmUsedPercentage %" 

		} 

	}

}

    

This script prints the name and percentage of used space of each VM where the threshold of 80% was exceeded.

Tips and tricks for using Get-View

When using Get-View, you should note that some properties are not available directly in the View object. You might need to retrieve additional objects or call methods to get the information you want. The vSphere API documentation is a helpful resource to learn what properties and methods are available for each object.

Another important aspect is performance optimization. For large environments with many VMs, Get-View queries can be time-consuming. To improve performance, use filters to limit results to VMs relevant to your task. You can also use the -Property option to retrieve only the properties you need, which reduces the amount of data returned. The following code example shows the use of the Property parameter. Only the "Name", "Summary.Storage.Committed" and "Summary.Storage.Uncommitted" properties are retrieved. Using the filter and -Property option reduces the amount of data returned and improves query performance.

$vmNameFilter = "TestVM*" 

$requiredProperties = @( 

	"Name", 

	"Summary.Storage.Committed", 

	"Summary.Storage.Uncommitted" 

) 

$ params = @{ 

	ViewType = 'VirtualMachine' 

	Filter = @{"Name" = $vmNameFilter} 

	Property = $requiredProperties 

} 

$ vmViews = Get-View @params

Conclusion

In a nutshell, the Get-View command in PowerCLI provides administrators with a powerful way to access and efficiently manage advanced information about their VMware infrastructures. By combining Get-View with automation scripts and solutions such as ScriptRunner, administrators can save time and reduce the effort required to manage their environments.

Related links

• The best PowerCLI commands for admins – part 1, part 2, part 3
• Take a look at our product here (neither download nor registration necessary)
• ScriptRunner ActionPacks for VMware
• Setting up a VMware vSphere PowerCLI Module (from unserem Trial Guide)
• VMware PowerCLI Documentation