by lunarg on July 17th 2020, at 12:35

The official information page about the long-standing Windows DNS Server Remote Code Execution Vulnerability:

by lunarg on June 26th 2020, at 12:34

By default, the FortiClient will start up automatically when starting macOS. This may not always be desirable but fortunately, auto-start can be disabled quite easily.

The FortiClient launch agent is located at /Library/LaunchAgents/com.fortinet.forticlient.fct_launcher.plist. Use any text editor to open and edit this file, but you probably will need to do this using Terminal and using sudo to launch a text-based text editor (e.g. vi or nano).

With the file open, look for these lines:


Change true to false and save the file. Note that updates to the FortiClient may overwrite the change.

by lunarg on June 13th 2020, at 16:05

When you're using your Synology exclusively as a iSCSI target, and have assigned the complete disk space to your LUN's, you will get notifications about the volume being (almost) completely full. Obviously, in this case, you may not want to receive these notifications. Luckily, you can turn these off:

  1. Log on to your DSM.
  2. Navigate to Control Panel → Notification → Advanced tab. In the list, expand Internal storage.
  3. Uncheck the notifications for Volume in low capacity and Volume in extremely low capacity. Click Apply to save the changes.

Note that this will only disable the notifications (e-mail, SMS, etc.). The widget and WebUI will still show the alerts.

by lunarg on May 14th 2020, at 12:20
You can force-trigger storage DRS recommendations (and possible subsequent storage vMotions) through PowerCLI.

Run the snippet below, replacing the value of $dscName to match the name of the datastore cluster you wish to trigger the DRS recommendation on:

$dscName = 'DatastoreCluster1'$dsc = Get-View -ViewType StoragePod -Filter @{'Name'=$dscName}$si = Get-View ServiceInstance$storMgr = Get-View -Id $si.Content.StorageResourceManager$storMgr.RefreshStorageDrsRecommendation($dsc.MoRef)$dsc.UpdateViewData()if($dsc.PodStorageDrsEntry.Recommendation){ $dsc.PodStorageDrsEntry.Recommendation | %{ $storMgr.ApplyStorageDrsRecommendationToPod_Task($dsc.MoRef,$_.Key) }}

by lunarg on May 14th 2020, at 12:17

If the webclient is letting you down, you can also use PowerCLI to expand datastores.

First, as usual, expand the volume on the storage level. Then, fire up PowerCLI, log on to the vCenter/host and run the following script, replacing the name of the datastore you wish to expand:

$name = 'Datastore1'
$datastore = Get-Datastore $name
$esxi = Get-View -Id ($Datastore.ExtensionData.Host | Select -Last 1 | Select -ExpandProperty Key) 
$datastoreSystem = Get-View -Id $esxi.ConfigManager.DatastoreSystem
$expandOptions = $datastoreSystem.QueryVmfsDatastoreExpandOptions($datastore.ExtensionData.MoRef)
by lunarg on May 13th 2020, at 10:00
This article is a reference guide for updating the firmware on switches. As I handle a broad range of switch vendors and models, I got tired of looking up the commands, and decided to bundle it all here in one place for easy reference.

Note that this document is not a step-by-step guide to update a specific switch but rather a reference for which CLI-commands to use.

First, look up current version and active boot bank. Can be either A: or B:

show boot system stack-unit 1upgrade system tftp:// B:conf tboot system stack-unit 1 primary system://Bendwr memreload

When upgrading from USB-stick, change tftp:// to usbflash://. USB-stick needs to be FAT32.

To do

by lunarg on May 8th 2020, at 09:30

The certificate for HiveManager NG has expired on October 23, 2019. As a result, Dell N Series switches running an older firmware or an older version of the HiveAgent, can no longer connect or be connected to HiveManager NG after this date.

The solution is to either update the switch firmware to at least, or manually update the HiveAgent to 1.1.29.

More information:

by lunarg on April 20th 2020, at 09:50
When attempting to add new Remote Desktop Session Hosts (RDSH) to a session host collection, you may run into the following error message:

Unable to retrieve the session collection properties

This error can possibly be accompanied by additional messages.

When checking the logs, you apparently cannot find anything wrong with the collections: they show up correctly in Server Manager and users can still log on to the collection using existing servers.

Sometimes it can happen that the security descriptors of one of the collections get corrupted, in which case it is not possible to add a new session host, whether it's through Server Manager or through Powershell.

The problematic collec  ...
« August 2020»
« Debating Windows vs. Linux vs. Mac is pointless: they all have their merits and flaws, and it ultimately comes to down to personal preference. »