Wetek OpenELEC is a small box running OpenELEC. OpenELEC is a media center based on Kodi. In comparison to a Raspberry Pi running OpenELEC, Wetek OpenELEC includes a TV tuner (DVB-C/T, DVB-S oder ATSC). So you don’t have to find a compatible tuner by yourself and have everything integrated in a nice little box. Shipment includes an AirMouse. This is a remote which can be used as a mouse due to built-in motion sensors. Because I already use a Logitech Harmony as an universal remote I also wanted to control Wetek OpenELEC with this remote. Wetek OpenELEC is a special edition of Wetek Play (differences between these two). So getting an infrared remote to work with Wetek Play should be pretty similar.

As mentioned in the article regarding acme-tiny you need to create a script to renew your Let’s Encrypt certificate regularly. In this script you download the intermediate certificate of Let’s Encrypt which was used to generate the certificate for your domain. Only if you include the intermediate certificate in your web server configuration the browser can get the complete chain. If you do not offer the intermediate certificate your rating at SSL Labs drops to “B”.

Sometimes you have to use passwords in PowerShell. For example if you want to shut down a remote computer and have to authorize with another user than the current. You can prompt for the username and password while running the script with Get-Credential:

1
2

$Credential = Get-Credential
Stop-Computer -Computer 192.168.2.10 -Credential $Credential -WhatIf

This article is part of a series.

Disaster Failover is very similar to a planned failover described in part 9 of this series. Because the master is not available unexpectedly the vFiler cannot be stopped and the temporary replication from slave to master has to be set up later before the rollback. When the master is powered on again you have to take care that the vFiler is not started automatically. Otherwise the vFiler is running on master and slave simultaneously. In comparison to the planned failover steps 1, 4 and 5 are moved from failover to rollback.

This article is part of a series.

With the configuration tasks of the previous parts you now have an environment where netapp01 can be considered as master and netapp02 as slave. Clients use the share of the vFiler running on the master (netapp01) and the data is replicated to the slave (netapp02). Because of this replication if the master fails you can also start the vFiler on the slave without data loss.