Found my specific issue :) I was using an invalid hostname, and the DNS wasn't resolving properly.
But on a different note, I also found that the Microsoft doc (Remotely manage Hyper-V hosts with Hyper-V Manager) didn't document all the instructions necessary for me to make things work. It was mostly correct, ...
I found the information about deploying Windows Server 2016 TP3 onto an SD card.
This topic describes deploying Windows Server on the SD card, but it was TP3. I guess you can perform the same actions with the release version.
Also, you can take into consideration SATA ...
What you did wrong is adding the key. Which you needed because... ah.
You should have installed Datacenter on Hyper-V. With a proper key that would auto activate any VM on it. Hyper-V on the host is not beneficial licensing wise in most cases, and technically means no auto activation.
There is pretty much zero benefit from installing Datacenter on a VM. ...
LIveMigration is required to avoid service interruption in you case. To enable LiveMigration and/or automatic failover you need domain joined WSFC (domain independent cluster doesn't support LiveMigration) and shared storage.
I can suggest the following cost-effective design:
1) Upgrade license to Windows Server Standard (you need it to license AD VM on ...
If you have the files, both the vhd(x) and the machine vmx file, and your system is configured the same with similar vSwitch names then you should be able to use the command Import-VM -Register path\to\the\file.vmx.
If you no longer have your VMX files then you should just re-create a new virtual machine and when asked about adding storage, use the existing ...
NTFS is not a cluster-aware file system. It was never designed to support simultaneous access from different clients.
In order to allow multiple access: configure MPIO, deploy the Failover Cluster feature on both servers, create the new cluster and add your SAN volume to Failover Cluster as CSV (Cluster Shared Volume).
You can try using StarWind VSAN (Free) to create a highly available (HA) distributed block device between both Hyper-V hosts on top of an existing SANs attached directly to both servers. Since StarWind talks iSCSI / iSER, you can use it instead of Fibre Channel (FC).
P.S. Good walkthrough is here:
Pass-through disks are no longer recommended. They no longer provide higher performance than virtual disks, they aren't supported much beyond basic support, they make backups harder, they have a lack of third-party tools and they make portability harder.
Creating a VHDX and using that virtual disk would be what I suggest.
To read more about why pass-...
I'm a bit new to the SLAT stuff, but from what I have read, you have to run coreinfo BEFORE you install a Hypervisor. It is possible you do have SLAT but coreinfo is reading it incorrectly because you have Hyper-V installed already.
I agree with the previous speaker, MPIO is your best bet if you are considering the performance first. As for the configuration in general, I think you can make it less complicated, more reliable and what most importantly, more performant going with local storage of your nodes instead of physical SAN box. Take starwind free and let it synchronize the data ...
Since the new version of configuration files on Hyper-V doesn't have such option PowerShell will not give exact information either. Try MSVM_ComputerSystem class in order to get the last state change - https://docs.microsoft.com/ru-ru/previous-versions/windows/desktop/virtual/msvm-computersystem but it will also change during the bootup.
I have used Hyper-V replication as a method to migrate VMs. It can work fine. You can't failover(migrate) via replication without stopping the VM during the failover, but that should only take a minute or two.
Just setup replication, of all the VMs you want to migrate. Wait for everything to sync up. When you are ready to migrate, stop the VM(s) and use ...
Verify that you're not using any of the "Legacy NICs" in your Virtual Machines? These are limited to 100mbps. This may be causing the Virtual Network (bound to the physical NIC) to negotiate the lower speed.
Other things to do:
- Update NIC drivers
- Force 1gbps operation in Device Manager
- Replace the patch lead connecting the problem NIC
- check cable. ...
As I understand it you want to build a dev / test environment and crate Checkpoints so that you can roll back changes until you get your environment just the way you want it. if that is the case advice would be
If you revert / delete the CheckPoints then revert / delete all the checkpoints at the same time. This will avoid anytime stamp / replication ...
I encountered this problem recently, and after several days of debugging, I've discovered the issue and fixed it.
After installing Hyper-V Server 2016, use an offline tool (like, say, Windows PE) to mount the SYSTEM hive of the new installation, and change the DWORD ControlSet001\Control\BootDriverFlags from 0x04 to 0x1c. (You should ...
Just expand the description in your link and it will tell you clearly the purpose of this Hyper-V Server 2016 download option:
The Windows hypervisor technology in Microsoft Hyper-V Server 2016 is
the same as what's in the Microsoft Hyper-V role on Windows Server
2016. It is a stand-alone product that contains only the Windows hypervisor, a Windows ...
S2D is uber-expensive for what it does in terms of storage-only deployment. It's Datacenter-only WS feature so while HCI scenario kind of makes sense - segregated / SOFS definitely doesn't. I'd leave things AS IS. If you absolutely want SOFS for whatever reason - look @ StarWind VSAN Free. It's much faster, more reliable within 2-Node deployment and... it's ...
Do I need to leave one core "free" so that the host stays stable/accessible?
No. See, the "host" is a VM. And that particular master VM has a higher priority than any other VM's.
If so, can I leave a partial core free instead of a whole core?
Given that assigned core counts are all INTEGER, how would you even ENTER a non integer number?
Each network is effectively isolated behind a separate NAT router managed by Hyper-V, in a similar way that your home router isolates your home network behind a single public IP address. This is how the networks are accessing the outside world.
The challenge is to connect the two separate networks together within the Hyper-V world and this will need a ...
You can use Hyper-V Replica and PowerShell script automated failover. See:
PoSh Hyper-V Replica Failover Automation
... just make sure you use some mechanism to avoid split brain scenario, say run your automation scripts from Azure or AWS hosted monitoring VM.
I also verified this behaviour in lab.
The documentation about hyper-v replica says :
When you enable Hyper-V Replica for a specific virtual machine, initial replication creates an identical replica virtual machine on a secondary host server. After that happens, Hyper-V Replica change tracking creates and maintains a log file that captures changes on a ...
If you don't set up SOFS, your file server (cluster) has a single point of failure. If one of the storage nodes dies, all the shares that it currently owns will fail over to another node, but all clients will be disconnected, which means that all of those VMs will crash. The share will come back, and the VMs will eventually restart, but this will be very ...
We decided to take the suggestions we got here and modify our network based on them:
We added a second VLAN tagged interface to the LBFO-team which we used to enable SMB MultiChannel
Modified the team's loadbalancing algorithm to Address hash instead of the default Dynamic
We did these modifications a week ago, since then we don't see this error message, ...
UEFI boot options are stored in UEFI variables, not on a disk. This is true for physical machine or virtual machines. Hyper-V stores UEFI variables in one of the VM state files, not the VHD. So when you dissociated the VHD from the VM, you lost the UEFI variables and the boot entries.
If you want to clone a machine which is depending on UEFI variables to ...
To answer your questions:
Can I install the DPM client on a Hyper-V Server 2016? Alas, no, as Greg Askew points out above 2016 isn't one of the supported operating systems for DPM 2010.
If hardware fails on the Hyper-V Server 2016 and I need to restore the VMs on a different physical server, is that easy / even possible using the DPM2010 backup? You would ...
Ensure you have winrm quickconfig setup.
You can use powershell enter-pssession -computername $youurname
get-service to get the services. Then start-service -name $ursrvc
It's more than likely already running if you have VMs on it.
Check that you're a member of the hyper-v administrator groups. It's most likely that.
Indeed, Windows Server 2003R2 is not supported on Hyper-V 2016 but it doesn't mean that it won't work at all.
You can create VM with first (legacy) generation and install integrated services from 2012R2 manually (https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services#install-or-update-integration-...