by lunarg on July 15th 2021, at 14:50

Occassionally, it may be necessary to perform disk consolidation. If you have a lot of VMs which need consolidation, it can be tedious to do this in the webclient. Fortunately, it's also possible to mass-consolidate via PowerCLI.

Install and log in using PowerCLI.

To show which VM's need consolidation, run:

Get-VM | ? {$_.Extensiondata.Runtime.ConsolidationNeeded}

To actually perform disk consolidation, run:

Get-VM | ? {$_.Extensiondata.Runtime.ConsolidationNeeded} | % {$_.ExtensionData.ConsolidateVMDisks_Task()}
edited by lunarg on June 23rd 2021, at 16:17
Here's a list of common installation options for Cylance. Note that they can also be used with the Cylance Unified installation MSI. Replace <PIDKEY> with the tenant's installation key.

New tenant installation (so Cylance will be running in "learning mode" for a few weeks), where clients are using Windows Defender as the primary AV:

msiexec.exe /i "CylanceProtect_x64.msi" ALLUSERS=1 /qn /norestart /log output.log PIDKEY=<PIDKEY> LAUNCHAPP=1 REGWSC=0

Existing tenant (which is past the "learning period") or a new tenant where clients are using another (supported) anti-virus as the primary AV:

msiexec.exe /i "CylanceProtect_x64.msi" ALLUSE  ...
by lunarg on June 3rd 2021, at 13:34
When deploying Cylance for the first time in a new environment, best practice is to have it run in "audit mode" where Cylance detects but does not act upon it. Of course, this would not be very secure if you don't have another anti-virus in place. Starting from Windows 10 and Server 2016, Windows Defender is automatically installed and active if no other anti-virus product is installed. However, installing Cylance the regular way would result in Windows detecting the presence of Cylance and disabling most of the functionality of Defender. Luckily, you can workaround the issue by having Cylance not register as an anti-virus with Windows Security Center during the installation (or af  ...
by lunarg on May 18th 2021, at 17:57

Starting from Debian 10 ("Buster"), phpMyAdmin no longer exists as a package in the Debian repository. Instead, it needs to be installed manually. I found this article online which seems to explain the process very well:

https://linuxhint.com/install_phpmyadmin_debian_10/

by lunarg on May 11th 2021, at 08:00

Although 3CX has stopped development of the standalone Mac client, the latest version (although now a bit outdated) still works and is downloadable here:

http://downloads.3cx.com/downloads/3CXPhoneforMac16.dmg

by lunarg on May 7th 2021, at 12:03
Here's a quick and dirty guide to the setup of a read-only Domain Controller (RODC) on a Core-based installation.

Deploy your Core-based server like you normally would.

Using sconfig, perform these tasks in order:

Configure network.

Optionally, configure computer name.

Join the computer to the domain.

After the reboot, install the required role via Powershell:

Install-WindowsFeature AD-Domain-Services

After that's successful, using Powershell, promote the server to an RODC (adjust parameter values accordingly):

Install-ADDSDomainController -Credential (Get-Credential) -DomainName domain.local -SiteName "Default-First-Site-Name" -InstallDNS:$true -ReadOnlyReplica:$true -For  ...
by lunarg on May 4th 2021, at 11:44
When syncing a OneDrive business account, the root folder name consists of "OneDrive" followed by the company name as registered in M365, e.g. "OneDrive - My Company Ltd.". For certain companies with longer names, this could result in lengthy folder names. There is a way to change (rename) this folder, though.

Completely quit the OneDrive application.

Using either Finder or Terminal, navigate to the folder: ~/Library/Containers/com.microsoft.OneDrive-mac/Data/Library/Application Support/OneDrive/settings/Business1/

There are a few INI-files in there. One will be a randomized SID-like number, followed by .ini, e.g. a183b583-a64a-28fd-818a-b4918a569c95.ini. Open this fil  ...
by lunarg on May 3rd 2021, at 13:36
Despite of Cylance being supported on macOS 11 Big Sur since build 1580, you may encounter an issue where Cylance would still show a red dot in its icon in the menu bar, and opening the GUI would still show this error message:

Driver Failed To Connect, Device Not Protected

To resolve this, you need to give the agent and the new Cylance ES Extension full disk access:



On macOS Catalina and earlier, Cylance used kernel extensions, providing full disk access via the macOS kernel. Because of the deprecation of kernel extensions and the subsequent introduction of the new system extensions mechanism introduced in macOS 11 Big Sur, you need to explicitly allow full disk access to the system ext  ...
 
 
« July 2021»
SunMonTueWedThuFriSat
    123
45678910
11121314151617
18192021222324
25262728293031
 
Links
 
Quote
« When a bird does poo poo in your eye, be happy elephants don't fly. »