In order to install a fresh copy of Windows Server on a VM with the VMWare Paravirtual SCSI controller, as the driver for the PVSCSI adapter is not included in the default Windows Server ISO, you would use the built-in floppy images to make the PVSCSI driver available during the installation, avoiding the need to install using a different SCSI controller and then swap the controller after the installation of the guest OS and VMWare Tools.
To facilitate this, you would add a virtual floppy drive, connect the correct floppy image containing the PVSCSI driver, and then load the driver during the disk selection portion of the installation wizard. Unfortunately, since the deprecation of the Flas ...
When attempting to install modules from the Powershell Gallery, you may get errors on older versions of Windows Server (2008-2012R2), even after updating PowerShell to more recent versions. The errors are concerning unable to install the NuGet provider, required to download packages from PSGallery.
Errors are similar to:
WARNING: Unable to download from URI.
WARNING: Unable to download the list of available providers. Check your internet connection.
Unable to find package provider 'NuGet'. It may not be imported yet.
The reason for this is a problem with the cryptographic providers enabled on your system. PowerShell 5.1 enables SSL 3.0 and TLS 1.0 for secure HTTP connections, which are ...
A not so documented feature is the support of VMXNET3 in VMWare Fusion. It cannot be configured through the UI but by manually editing the VM configuration file (VMX-file), you can leverage it (assuming you have installed VMWare Tools and/or are running a supported guest OS).
Open the file with your favourite text editor, but avoid using Apple's TextEdit as it has a tendency to replace regular quotes with opening/closing quotes, which will break your VMX-file. You can use Terminal and open the file using Nano if you want to be sure.
Network adapters are specified with ethernet*. as the starting line, where * = the number of the network adapter (0 is the first, 1 is the second, and so on). ...
You can manually trigger an update of Office Click-to-Run installations, without starting any of the Office applications. This can be useful in VDI-environments where it may be necessary to update Office in the source image.
To trigger the update, start the Click-to-Run client with the /update switch.
Perform the update (will show a progress bar):
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user
Silently perform the update (don't show progress bar and force Office apps to restart):
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user displaylevel=false forceappshutdown=true