by lunarg on December 14th 2017, at 14:03

Sometimes, you need to temporarily start a service (such as SSH) to perform some maintenance task. PowerCLI can help you with this:

To start the SSH server on each host of a vCenter:

Get-VMHost | Get-VMHostService | ? {$_.Key -eq "TSM-SSH"} | Start-VMHostService

To stop the SSH server:

Get-VMHost | Get-VMHostService | ? {$_.Key -eq "TSM-SSH"} | Stop-VMHostService -Confirm:$false

As always, you can make adjustments to the oneliner to select another service to start/stop, or further limit the selection of hosts to a cluster or a group of hosts (e.g. filtered by name).

by lunarg on December 14th 2017, at 14:00
If you're making changes to the datastore, setting up a new cluster and have a lot of hosts, and wish to set up system logging, you can do so very quickly using PowerCLI.

First, add all the hosts to the vCenter like you normally would. Then, connect to the vCenter server and run this cmdlet:

Get-VMHost | % { $vm = $_ $vm | Get-AdvancedSetting "" | Set-AdvancedSetting -Value "True" -Confirm:$false $vm | Get-AdvancedSetting "" | Set-AdvancedSetting -Value "[DataStore01] ESXiLogs" -Confirm:$false}

The cmdlet above will set the system log location to a folder on DataStore01 and enables unique log di  ...
by lunarg on December 12th 2017, at 12:35
When performing large storage migrations, it may be useful to get a list of VMs and the datastore and/or folder they are located in. PowerCLI can provide this very quickly:

Get-VM | Select Name,@{N="Datastore";E={[string]::Join(',',(Get-Datastore -Id $_.DatastoreIdList | Select -ExpandProperty Name))}},@{N="Folder";E={$_.Folder.Name}}

You can further pipe this to other cmdlets (such as Where-Object to filter even more), or export it to a CSV.

You can also go into more detail and determine the location of each virtual disk (VMDK) of each VM:

Get-VM | Get-View | % { $name = $_.Name $_.Layout.Disk | % { New-Object PSObject -Property @{ Nam  ...
by lunarg on November 23rd 2017, at 09:59

For all you Belgians (Flemish) out there, a list of live-streams (MP3) for people who don't want to use the online player of VRT, or simply can't use the player (e.g. linux users?)

Simply load these up in your favourite player supporting MP3 streaming through HTTP (such as VLC Player).

Where are the URLs? (UPDATE Aug-2017)

Readers that have read this page before will notice all streaming URLs are gone. VRT has switched to another streaming provider, causing all streaming URLs to change. The new list can be found here:

by lunarg on October 27th 2017, at 09:09

For those that do not wish to use OneDrive and want it removed from the folder tree in Explorer, can do so by a simple registry change:

Open regedit and locate the key: HKEY_CLASSES_ROOT\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}

Change the value of System.IsPinnedToNameSpaceTree to 0

When using 64-bit, repeat the process for the key: HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}

Note that starting from Windows 10 Creator, you can also remove OneDrive by uninstalling it:

  • Right-click OneDrive in the start menu and click "Uninstall"
  • Go to Control Panel → Add/Remove Programs and uninstall it from the list.
by lunarg on October 23rd 2017, at 11:28

As found on, a list of bandwidth consumption per codec.

It's worth mentioning that the table also indicates the total consumption including IP overhead. When making assumptions about bandwidth requirements, it is useful to take this overhead into account.

G.711 64 Kbps 87.2 Kbps
G.729 8 Kbps 31.2 Kbps
G.723.1 6.4 Kbps 21.9 Kbps
G.723.1 5.3 Kbps 20.8 Kbps
G.726 32 Kbps 55.2 Kbps
G.726 24 Kbps 47.2 Kbps
G.728 16 Kbps 31.5 Kbps
iLBC 15 Kbps 27.7 Kbps
by lunarg on October 19th 2017, at 12:00

You can easily verify whether an ADFS implementation is working by using a browser and trying to log on:

Replace accordingly.

Note that in 2016, this no longer works unless you re-enable this feature through Powershell:

Set-AdfsProperties -EnableIdpInitiatedSignonPage $true
by lunarg on October 10th 2017, at 14:36
To properly shut down the NetApp (through the CLI):

First, close down all I/O to the NetApp by dismounting volumes, turning off servers, etc.

Log in on the NetApp through the CLI, using either a console cable or via SSH. Note that if you use SSH, you will not be able to see the complete shutdown sequence.

On the first controller, turn off cluster failover: cf disable

Shut down the controller: halt

Log on to the other controller (using SSH or swap the console cable), then shut down that controller too: halt

Wait until the shutdown sequence has completed before removing power from the controller chassis, then turn off the enclosures. You can use a console cable to verify whether th  ...
« December 2017»
« If the batteries of a TV remote run out, why do we press the buttons so much harder? »