Archives

Hi, I’ve created an internal switch with NAT (Windows 10 Pro for Workstation, OS Build 17763.529) and added to the switch some VMs. I set the profile to private using Power Shell, in order to allow the host and the guests to see each other. The internal
switch is bundled with the Default Switch as Unidentified network, and executing the Power Shell command on it changes the Default Switch’s network profile to private too.

But after reboot the profiles of Default Switch and the internal switch are reset to Public. Changing the Networks List Manager Policies ofUnidentified network to private with secpol.msc leads to problems in the creation of the Default Switch on startup.

Is there a way to preserve the Internal Switch private status after reboot, without having to execute the Set-NetConnectionProfile every time?

After running Windows Update we are unable to restart the Hyper-V Windows 2016 server: when restarting the Hyper V Server it shuts down instead, and we need to physically push the power button on the server in order to start it again.

The Virtual Windows 2016 server does not have this problem, and restarts fine.

In the event Viewer we have the following information:

The process C:WindowsSystem32RuntimeBroker.exe (HYPERV) has initiated the restart of computer HYPERV on behalf of user HYPERVAdministrator for the following reason: Hardware: Maintenance (Planned)
Reason Code: 0x84010001
Shutdown Type: restart
Comment:

Event ID: 1074

*****

The kernel power manager has initiated a shutdown transition.

Shutdown Reason: Button or Lid

Event ID: 109

*****

The WinRM service is not listening for WS-Management requests.

User Action
If you did not intentionally stop the service, use the following command to see the WinRM configuration:

Restarting the Management agents in ESXi L1TF related “esx.problem.hyperthreading.unmitigated” vCenter Server Updates: CVE-2018-3646 “503 service unavailable” error when connecting to the vCenter Server using the vSphere Web Client How to reset the lost or forgotten root password in vCenter Server Appliance 6.5 Troubleshooting an ESXi/ESX host in non responding state Unable to log in to

I am facing a problem, my hyper V server has only one physical network card, and my provider is not able to interconnect my two servers via their solution (Vrack) which requires a physical network card dedicated to this
interconnection.

My configuration:

HV1:1 VM of production + 1 VM Domain controller

HV2:1VM which will be the replicate of the production VM + 1 testing VM