When connecting to your vCenter server via PowerCLI, one can use the -menu option. This will give a list of entries you recently used. You can manage the entries here:
C:\Users\username\Appdata\Roaming\VMware\PowerCLI\RecentServerList.xml
Connect-viserver -menu
Start the ssh service on all hosts:
|
1 2 3 |
Get-VMHost | Foreach { Start-VMHostService -HostService ($_ | Get-VMHostService | Where {$_.Key -eq "TSM-SSH"}) } |
If you want to start the ssh service on a single host, change ESXiHostName to your ESXi FQDN:
|
1 2 3 |
Get-VMHost -Name ESXiHostName | Foreach { Start-VMHostService -HostService ($_ | Get-VMHostService | Where {$_.Key -eq "TSM-SSH"}) } |
If you want to stop the ssh service on all hosts:
|
1 2 3 |
Get-VMHost | Foreach { Stop-VMHostService -HostService ($_ | Get-VMHostService | Where {$_.Key -eq "TSM-SSH"}) } |
If you have multiple cluster in vCenter, are connected to multiple vCenters, be sure to launch the command only to the necessary hosts:
|
1 2 3 |
Get-Cluster -Name ClusterName | Get-VMHost -Name ESXiHostName -Server vCenterServerName | Foreach { Stop-VMHostService -HostService ($_ | Get-VMHostService | Where { $_.Key -eq "TSM-SSH"} ) } |
These are other services I frequently use:
There are other services available but I have never used them in this context (yet):
Change the startup policy for a service:
|
1 2 3 |
Get-VMHost | Foreach { Set-VMHostService -HostService ($_ | Get-VMHostService | Where {$_.key -eq "TSM-SSH"}) -policy On } |
The following Get-EsxCli command will unconfigure your diagnostic partition and reconfigure with smart selection. This was needed because the install partition uuid had changed due to an option in the NetApp system while doing system testing.
|
1 2 3 4 5 6 7 8 9 10 |
$server_list = Get-VMhost Foreach ($srv in $server_list) { $esxcli = Get-EsxCli -VMhost $srv #$esxcli.system.coredump.file.add($null,"VMFS_log_partition","$srv.name",$null) $esxcli.system.coredump.partition.set($null,$null,$null,$true) $esxcli.system.coredump.partition.set($true,$null,$true,$null) $esxcli.system.coredump.partition.get() } |
Many thanks to http://www.virten.net/2014/02/howto-use-esxcli-in-powercli/
These are powercli goodies I use on a regular base. I have collected them here to find them easily. Some I wrote myself, some are copied from other sites. If I didn’t reference the source, I don’t know anymore where I found it.
Testing with one vm
|
1 |
get-vm my_vm_name | Get-NetworkAdapter |where {$_.networkname -eq "current_network_label"} | set-networkadapter -portgroup "new_network_label" -confirm:$false |
Reconfigure all vm’s with the string “vdi” in the name
|
1 |
get-vm *vdi* | Get-NetworkAdapter |where {$_.networkname -eq "current_network_label"} | set-networkadapter -portgroup "new_network_label" -confirm:$false |
|
1 |
(get-view -viewtype virtualmachine).summary.config | where {$_.numcpu -gt 8} |
While executing the NetApp MetroCluster testplan, the syslog service stops logging to the presented syslog datastore. To restart the logging reload the syslog service on all impacted hosts. The following command will reload the syslog service on all hosts in the connected vCenters. Check the $global:defaultviservers to know which vCenters are connected.
|
1 2 3 4 5 6 7 |
$server_list = Get-VMhost Foreach ($srv in $server_list) { $esxcli = Get-EsxCli -VMhost $srv $esxcli.system.syslog.reload() } |
This needs to be done for each registered version of PowerCLI. This one worked for me on Windows Server 2012 R2
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install “VimService55.XmlSerializers, Version=5.5.0.0, Culture=neutral, PublicKeyToken=10980b081e887e9f” /ExeConfig:c:\windows\system32\WindowsPowerShell\v1.0\PowerShell_ISE.exe
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
#get connected esxi hosts $vmhostlist = get-vmhost |sort|select name #for each host show the power management policy setting foreach ($entry in $vmhostlist) { #list power management policy on all connected esxi hosts get-vmhost |sort|select name, @{ N="CurrentPolicy"; E={$_.ExtensionData.config.PowerSystemInfo.CurrentPolicy.ShortName}},@{N="CurrenPolicyKey"; E={$_.ExtensionData.config.PowerSystemInfo.CurrentPolicy.Key}},@{N="AvailablePolicies";E={$_.ExtensionData.config.PowerSystemCapability.AvailablePolicy.ShortName} } #for each host change the power management policy to high performance foreach ($entry in $vmhostlist) { $view=(get-vmhost $entry.name|get-view);(get-view $view.configmanager.powersystem).configurepowerpolicy(1)} #list power management policy on all connected esxi hosts get-vmhost |sort|select name, @{ N="CurrentPolicy"; E={$_.ExtensionData.config.PowerSystemInfo.CurrentPolicy.ShortName}},@{N="CurrenPolicyKey"; E={$_.ExtensionData.config.PowerSystemInfo.CurrentPolicy.Key}},@{N="AvailablePolicies";E={$_.ExtensionData.config.PowerSystemCapability.AvailablePolicy.ShortName} } |
Apparently there were some errors (curly brackets missing or in the wrong place) in the previous code.
It also ran several times per host because per host there was a Get-VMHost in the ForEach iteration. So If you had three hosts it would run three times per host.
The updated and optimized code:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
$VMHosts = Get-VMHost #for each host show the power management policy setting ForEach ($entry in $VMHosts) { #list power management policy on all connected esxi hosts $entry | Select Name, @{ N="CurrentPolicy"; E={$_.ExtensionData.Config.PowerSystemInfo.CurrentPolicy.ShortName}},@{N="CurrenPolicyKey"; E={$_.ExtensionData.Config.PowerSystemInfo.CurrentPolicy.Key}},@{N="AvailablePolicies";E={$_.ExtensionData.Config.PowerSystemCapability.AvailablePolicy.ShortName}} } #for each host change the power management policy to high performance ForEach ($entry in $VMHosts) { $view=($entry | Get-View);(Get-View $view.ConfigManager.PowerSystem).ConfigurePowerPolicy(1) #list power management policy on all connected esxi hosts $entry | Select Name, @{ N="CurrentPolicy"; E={$_.ExtensionData.Config.PowerSystemInfo.CurrentPolicy.ShortName}},@{N="CurrenPolicyKey"; E={$_.ExtensionData.Config.PowerSystemInfo.CurrentPolicy.Key}},@{N="AvailablePolicies";E={$_.ExtensionData.Config.PowerSystemCapability.AvailablePolicy.ShortName}} } |
|
1 |
$Global:DefaultVIServers |
|
1 |
connect-viserver -menu |
|
1 |
get-vm Win* | move-vm -Datastore (Get-Datastore sdc-t*) |
Mount NFS datastore
|
1 |
get-vmhost | New-Datastore -Nfs -Name Datastore_Name -Path /vol/Name_on_NFS_host -NfsHost NFS_host_IP |
Remove NFS datastore
|
1 |
get-vmhost | Remove-Datastore -datastore Datastore_Name |
ESXi servers will by default search for the group ‘ESX Admins’ in Active Directory. The following command will change this to ‘my_group_name’.
|
1 |
get-vmhost | Get-AdvancedSetting "Config.HostAgent.plugins.hostsvc.esxAdminsGroup" | Set-AdvancedSetting -value "my_group_name" -Confirm:$false |
