Windows 2016

Hyper-V virtual machine failed to start on RODC site

If you shutdown a VM and you cannot restart it again this might be caused by Read Only Domain Controller (RODC).

If you may seen an error message that a VM cannot start with error code 0x80070569 check if the site the VM is running on has an RODC only. If this is the case you may missed to add the new VM to the "Allowed RODC Password Replication Group" of this site. The error 0x80070569 point to a Logon Failure per https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/starting-or-live-migrating-hyper-v-vms-fails.

Search on the Hyper-V host for System Eventlog for ID 5723 and you may see the VM machine name is not trusted by the local RODC server. Also search Hyper-V-VMMS > Admin eventlogs for event ID 15500 to find error code 0x80070569.

Now add the VM machine name into your "Allowed RODC Password Replication Group" and reboot the RODC and VM. When it comes up again the machine account will be cached locally on RODC and you can start/stop the virtual machine successfully.

Commvault: Agent install fails on Windows 2016 Core

We just installed Windows 2016 CORE. As recommened you typically should install all available Windows Updates before you move forward and install other software.

When we started to install Commvault File Agent and Virtual Server Agent setup failed with errors in eventlog and never completed. If you search Application event log you will find two errors logged:

Log Name: Application
Source: .NET Runtime
Date: 8/3/2017 3:59:44 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOST1.example.local
Description:
Application: setup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception

Windows 2016