Wednesday, November 6, 2019

List VMWare VM's with attached ISO's

Problem: I need to find all VM’s with ISO’s attached to the virtual CD-Roms.

Prerequisite: VMWare PowerCLI for PowerShell


Import-Module VMware.VimAutomation.Core | Out-Null
Connect-VIServer -Server $vCenter | Out-Null

#The actual working code to list attached ISO's
Get-VM | Get-CDDrive | Where-Object { $_.IsoPath -ne $null } | Select-Object Parent, IsoPath | Format-Table -auto

Disconnect-VIServer * -Confirm:$false -Force -ErrorAction SilentlyContinue

Good Luck!!!

& Thank you to Adil Arif & Brian Graf :

Written with StackEdit.

Wednesday, October 30, 2019

Veeam PowerShell Enable Encryption on All Jobs

Scenario: Your Veeam Backups have not been set for Storage Encryption. You have a ton of Backup Jobs and Backup Copy Jobs. You have exactly one (1) Encryption Password created.

!!NOTICE!! Once you add even a single encryption password, please re-configure your Veeam “Configuration Backup” because adding a password is known to disable the Config backups!!!

Problem: Manually editing each and every jobs is tedious and time consuming, and possibly prone to error.

Solution Prerequisite: Veeam PowerShell API installed.

Solution: Veeam PowerShell Enable Encryption on all the jobs at once:

Add-PSSnapin VeeamPSSnapIn
Disconnect-VBRServer #disconnect any prior
Connect-VBRServer -server YOURVEEAMSERVER #[-user] -[password|credential] [-port 9392]

$encryptionkey = Get-VBREncryptionKey -Description "YOURENCRYPTIONPASSWORDHINT"

$jobs = ( Get-VBRJob | Sort-Object -Property Name ) #sort is not necessity 
$jobs | Set-VBRJobAdvancedStorageOptions -EnableEncryption $true -EncryptionKey $encryptionkey

Good Luck!

Written with StackEdit.

Monday, August 26, 2019

vcenter VCSA stat=Deferred No Route To Host

VMWare vCenter VCSA sendmail stat=Deferred [aaa.bbb.ccc.ddd] No Route To Host | email alerts failing

Solution 1)
vCenter (6.5+) > Configuration > General > Edit > Mail >
Use DNS hostname rather than IP address

Solution 2)

Written with StackEdit.

Monday, July 29, 2019

Foxeer F405 + Caddx F2 + FrSky Slim+ betaflight settings

FPV Camera Control of the Caddx F2 on the Foxeer F405 AIO (DalRC F405 AIO):

Thanks go to @yo8aiv for cam control settings
Configurator: ports> peripherals>uart3> Camera (Runcam)
Betaflight CLI statements:
camera_control_mode = HARDWARE_PWM
camera_control_ref_voltage = 330
camera_control_key_delay = 180
camera_control_internal_resistance = 490
camera_control_inverted = OFF
serial 2 16384 115200 57600 0 115200


Smart Audio control on the Foxeer F405 AIO :

Thanks go to @Motard Geek for post #15
Configurator: ports> peripherals>uart5>VTX (TBS Smartaudio)
Betaflight CLI statements:
serial 4 2048 115200 57600 0 115200

FrSky Slim+ Telemetry transmission the Foxeer F405 AIO :

Solder Slim+'s RX1 onto FC's TX4
Betaflight CLI statements:
tlm_inverted = OFF
tlm_halfduplex = ON
serial 3 32 115200 57600 0 115200


✅ Foxeer F405 (Reportedly the same as DalRC F405 AIO)
$30 Fox @Foxeer
$56 Fox @Amz
$40 Dal @Gfpv
$40 Dal @Bang
✅ Caddx Turbo Micro F2 FPV Camera
$23 @Amz
$20 @Bang (USA warehouse)
$20 @Gfpv
✅ FrSky R9 Slim+ 915MHz Long Range Receiver
$27 @Bang
$34 @Amz
$29 @Gfpv

You may want to refer to these articles:
and many much more!!!

Saturday, June 15, 2019

Uncontrolled Syncthing *sync-conflict* for all or many files


Uncontrolled Syncthing *sync-conflict* for all or many files.


I had three devices setup with syncthing for maybe a couple years now. I accidentally sudo rm -rf / my laptop. YES, true i fogort that damned period in ./ while on my SD-Card which i was trying to purge. I quickly Ctrl-C, but it was too late – what a disaster! Fortunately ~/ and my external USB Disk stayed intact for the most part. But I had to reinstall Xubuntu from scratch. After reinstalling Syncthing, the syncs kept causing many many sync-conflict files. These were mostly for large 4GB video files and conflict creation was rampant and uncontrollable. My syncs are all in my ~/SYNCfolder, so I kept performing find ~/SYNC/ -name "*sync-conflict*" -delete (after analysis that the originals were good of course), but the conflicts repeatedly resurrected. Some searches were suspect, and some solutions only worked for text files – worthless.

Tentative Solution:

I found the idea of a “database reset” referenced in a github issue, so i looked it up:
Reset the database, forcing a full rescan and resync. Create .stfolder
folders in each sync folder if they do not already exist. Caution:
Ensure that all sync folders which are mountpoints are already
mounted. Inconsistent versions may result if the mountpoint is later
mounted and contains older versions.
I performed syncthing -reset-database on all three devices and so far the conflicts have subsided with the exception of a couple files.
Whew, continuous uncontrollable disaster #2 averted. As for disaster #1, i’m still repairing that one.

As always, Good Luck!
Please comment or tip me or use any/all of my affiliate links; Thank YOU!

Tuesday, April 30, 2019



Problem #1:
Re-launching Shotcut will over-write any error logs saved from the last execution.

Problem #2:
Downloading new versions force you to edit panel shortcuts that you may have created.

Shell wrapper: (read it, know it)
Written with StackEdit.