Hi,

I'm testing cluster upgrade from Hyper-V Server 2012 R2 to 2016. I evicted first node, clean-instaled 2016 and joined it back. Everything seems to work fine, except live migration. I cannot perform the migration from a 2012 R2 host to the new 2016 host because I'm getting processor incompatibility error. I don't have compatibility enabled on my VMs because the hardware is 1:1 the same, especially processors are the same (exactly the same model). Live migrations used to work just fine between 2012 R2 nodes.

Am I missing something? What can I check?

Thanks!

I have configured for 'Production only' checkpoint for a VM in Hyper-V 2016. After taking a checkpoint, when I use Get-VMSnapshot command, it shows 'CheckpointType' and 'SnapshotType' as 'Standard'. Also, the enum type fields does not have a field called 'Production' explicitly. Here are the powershell commands I ran:

PS C:\> Get-VM -Name vm1 | select CheckpointType

CheckpointType
--------------
ProductionOnly

PS C:\> Checkpoint-VM -Name vm1

PS C:\> $snap=Get-VMSnapshot -VMName vm1

PS C:\> $snap | select CheckpointType, SnapshotType

CheckpointType SnapshotType
-------------- ------------
      Standard     Standard

PS C:\> $snap.CheckpointType.GetType().DeclaredFields | select Name

Name
----
value__
Standard
Recovery
Planned
Missing
Replica
AppConsistentReplica
SyncedReplica

Is there a KB update required?

Hello,

I have Standalone Hyper V 2012 R2 Server i have a question

- can i do in-place upgrade to Hyper V 2016 Server or Windows 2016 Hyper V

- Can i Run Windows 2016 Nano server with Hyper V Package on to physical Server

Thanks

FZ2H

Howdy,

We are reorganizing our Cluster Shared Volumes so we can have better redundancy.  We are going to need to move all of our VM's Storage to new folder.  Same Cluster.  Same Host.  Just a different folder.  But we have 100+ VMs we'll need to move

I found this blog that explains the move-vmstorage command but I have a question:
https://blogs.msdn.microsoft.com/taylorb/2012/07/18/performing-storage-migrations-with-move-vmstorage/

Our VMs usually have 3 VHDx files.  C drive, D drive, and Pagefile drive.  What I want to do is move the VM, the main VHDX file, the Pagefile Drive, the snapshots, config files, etc all to one folder.  Except, I want to move the "D drive" to it's own folder.

The blog states how to move individual files but not everything except certain pieces or how to do the snapshots, config filesm etc.

Would it be easiest to do a move-vmstorage to move everything to one folder and then run it again and specify just to move the D drive to its own folder?  Or would it be better to manually specify moving the individual things to the first location and then again to the second?

Does that make sense?

Thanks.

The client has Windows 2008 R2 as Hyper-V host and VM is windows 2003. vhd is located in the C: drive. Since the C drive is low spaces, they shutdown the VM and copied the whole Hyper-v folder to D drive. Re-pointing the vhd file located in D on VM settings. The VM starts, but it doesn't have current SQL data. We found the VM has checkpoint.

Now, shutdown the VM and re-point the vhd back to original location. That doesn't fix the problem. Deleting the checkpoint doesn't fix the problem. I do see the dated 10/13/2016 .avhd file. Then I try to merge .vhd and .avhd. It merges successfully, but still have the same problem. What should I do to fix it?

Bob Lin, MCSE & CNE Networking, Internet, Routing, VPN Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Hi

I am trying to enable VSS daemon, but having issues, so I can not backup this VM,

the error message below,

[root@LANSID3CMPL01 ~]# /etc/init.d/hv_vss_daemon start
Starting Hyper-V VSS daemon                                [  OK  ]

[root@LANSID3CMPL01 ~]# /etc/init.d/hv_vss_daemon status
hv_vss_daemon is stopped

here is my system information and LIS version,

[root@LANSID3CMPL01 ~]# cat /etc/centos-release
CentOS release 6.8 (Final)
[root@LANSID3CMPL01 ~]# uname -a
Linux LANSID3CMPL01 2.6.32-642.6.1.el6.i686 #1 SMP Tue Oct 4 22:41:38 UTC 2016 i686 i686 i386 GNU/Linux

[root@LANSID3CMPL01 ~]# modinfo hv_vmbus
filename:       /lib/modules/2.6.32-642.6.1.el6.i686/weak-updates/microsoft-hyper-v/hv_vmbus.ko
version:        4.1.2
license:        GPL
srcversion:     82B9AE7A2B6BFE26B1AC6A4
alias:          acpi*:VMBus:*
alias:          acpi*:VMBUS:*
depends:
vermagic:       2.6.32-642.el6.i686 SMP mod_unload modversions 686

so any fixes available ?

Please help me, thanks ！

-- Hank

When using Hyper-V Server 2012 R2 (Server Core) I was able to use the following command to encrypt the boot drive (C:) -

manage-bde -on C: -rp

The motherboards I've been using have a TPM 2.0 installed.  With Server 2012 R2 I was able to encrypt the C: drive with either a BIOS or UEFI configuration.

But now with Hyper-V Server 2016 (Server Core) I get the following error message when I try to use the same command to encrypt the boot drive (C:) -

C:\>manage-bde -on C: -rp
BitLocker Drive Encryption: Configuration Tool version 10.0.14393
Copyright (C) 2013 Microsoft Corporation. All rights reserved.

Volume C: []
[OS Volume]
ERROR: Specifying the parameter '-StartupKey' or '-Password' is required to BitLocker-protect the OS volume.

Type "manage-bde -on -?" for more information.

NOTE: If the -on switch has failed to add key protectors or start encryption,
you may need to call "manage-bde -off" before attempting -on again.

With Hyper-V 2016 the motherboard is configured for UEFI and Secure Boot and I used MSINFO32 to confirm both are on as expected.

I have a single RAID10 drive that has a logical C: (Boot) and D: (Data) drive on it.  With Hyper-V Server 2012 R2 the C: drive only needed the TPM to be encrypted and for the D: drive I entered the following commands which allowed it to be automatically unencrypted via the C: drive.

manage-bde –on d: -pw (entered password - which I believe was stored on the encrypted C: drive?)
manage-bde –autounlock –enable d:

The motherboard configuration was setup to automatically reboot if there was a power outage.  

With the Sever 2016 limitation it looks like I cannot use the TPM alone to encrypt the boot drive?  I'd have to use a method like one of those below to encrypt the boot drive and automatically reboot after a power outage?

a) I could either add a 3rd logical drive (for example X:) to my RAID10 drive and use that to store the recovery key for the C: drive.  Or I could leave a USB drive plugged in at all times and it would also contain the recovery key to allow the C: drive to boot.

But in both cases it seems I would be leaving something potentially exposed in an unencrypted location that a hacker could potentially exploit (given both the X: or USB drives would be unencrypted)?

b)  I could use the -TPMAndPIN, -TPMAndStartupKey, or -TPMAndPINAndStartupKey options to encrypt the C: drive.  But that would require me to manually enter in some additional information in order to allow the Hyper-V Server 2016 to reboot (which would be a nuisance).

With Hyper-V Server 2016 is there some way to encrypt the boot drive (C:) with the TPM alone such that these type of issues (a and b above) aren't a problem? Or am I overlooking something in how this can be done on Hyper-V Server 2016?

Thanks for any insight you can provide.

P.S.  I saw there was an option (-sid) that looked like it might depend upon something in an AD domain to allow the C: drive to be encrypted/unencrypted.  But I just have a small home office network and don't have that type of sophisticated environment.

WindOfChange

Hi,

I've got a Windows Server 2012 R2 Cluster which consists of two hosts. I'm trying to live migrate everything from the second host onto the first host however nothing will live migrate unless it is switched off / offline.

I've tried live migrating from Failover Cluster manager and from within VMM and both times I get the same error messages.

The error message from Failover Cluster Manager is here -

I've rebooted Host1 to see if that would help and it hasn't. I've also run the Cluster Validation Wizard to try and see if this would highlight any problems but again it hasn't shown anything up.

I've done a lot of googling into these error messages and the only possible solution I can seem to find is the following -

https://support.microsoft.com/en-us/kb/2853203

This link fits the error and fix but not all of the symptoms or product version.

Any help would be greatly appreciated...

Thanks

Hi,

We have some problem with error messages in our Clustered Scale Out File servers in combination with Clustered Hyper-V environment.

We have 2 SOFS cluster with 2 host each.

Each Server is configured  with 2 Volume with 16,9 TB 

This Volume are shared in the Cluster as Cluster Shared Volumes  

And this share are shared to Hyper-V cluster and on this Shares we have the VM:s

The problem (error messages ) we got on the SOFS Servers is following

EventID 12289:

Volume Shadow Copy Service error: Unexpected error while calling GetStorageDependencyInformation. hr = 0x8007048f, The device is not connected.

.

Operation:

  Automatically choosing a diff-area volume

  Processing EndPrepareSnapshots

Context:

  Execution Context: System Provider

Error-specific details:

  Error: (0x8007048f) The device is not connected.

EventID 8193:

Volume Shadow Copy Service error: Unexpected error calling routine GetVolumePathName is fail on the path \\fasofs01.your.domain.com\vdisk01, winerror 0x0000007b.. hr = 0x8007007b, The filename, directory name, or volume label syntax is incorrect.

We got this error on every SOFS Host every day but different times.

And the amount off the error messages are different on the servers and the times too.

I have tried to find anything on the Internet but not find a good solution.

We use Veeam has a backup system and the backup seems to work from a Veeam perspective.

So what do we have to do to get rid of this errors

Best Regards

Jörg Wiesemann

Hi,

Setting up simple two node windows failover cluster 2012 r2. while configuring quorum disk, we are getting below message,

No Quorum witness has been configured for the cluster. 1 GB disk is there as "Available Storage" under cluster disk console.

Regards,

Hi all,

I am totally new to hyper-V replication so the questions below might sound silly (while i am trying to understand a basic level of how it works)

Initial Replication
q1)how does the initial replication over the network works while the VM is actually receiving writes at the same time when it is being copied over to the replica site ? - wouldn't the initial replica be totally inconsistent or the copy is done base on snapshot created ?

Hyper-V replication log
q2) Came across this phrase in technet
"The log file is replayed in reverse order to the replica VHD in accordance with the replication frequency"

If i have make the following changes
T1) change dataA  -- captured in HRL#1
T2) change dataB  -- captured in HRL#2

Wouldn't i need to replay the HRLs in proper order (#1, then #2), instead of reversed ?? What's the point of replaying the log in reversed (from the latest to the earliest) ?

Regards,
Noob

Hello,

I have created a hyper-v replica setup as described in: http://www.vkernel.ro/blog/configuring-hyper-v-replica-using-certificate-based-authentication-https

The following does apply to my setup:

1. I use a domain CA
2. I have 2 clusters with 2012 R2 hyper-v
3. SCVMM is used to manage the hosts, but I configured everything on the hyper-v console and failover cluster manager
4. I have created a  group policy for auto-enrollment of the computer certificate of the hyper-v hosts
5. I installed the replica broker role with name LOK1HA2BRK.domain.local for cluster LOK1HA2
6. I installed the replica broker role with name LOK3HA2BRK.domain.local for cluster LOK3HA2
7. I created a certificate template (duplicate computer template) as stated in the article and requested certificate for the replica broker with CN as LOK1HA2BRK.wessanen.local and LOK3HA2BRK.wessanen.local on 1 cluster host and imported the certificate on all other hosts in the clusters.
8. I have a replica broker certificate with a subject CN = LOK1HA2BRK.domain.local for the replica broker role on LOK1HA2
9. I have a replica broker certificate with a subject CN = LOK3HA2BRK.domain.local for the replica broker role on LOK3HA2

The replica role setup was successfull, but when I want to enable replication on a VM on LOK1HA2 and use replica server LOK3HA3BRK.domain.local, I get the error message:

Hyper-v could not validate certificate with thumbprint <thumbprint of broker certificate LOK1HA2BRK>. The certificate could not be verified upto the trusted certification authority. The certificate cannot be verified upto the trusted certification authroity. Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. (0x800B0109).

You would think "well just add the root certificate to the Trusted Root Certification Authorities store...", but because I use an Enterprise CA, this is already done ofcourse. There are some certificates in the Personal store of the hyper-v hosts, which also have the CN of the host itself, but they seem to be self signed. I don't know if I can remove them, because I suspect that SCVMM created them for some reasons. Secondly, i don't think it is the problem, becuase if the certificate thumbprint of the error is the thumbprint of the broker certificate. 

What I do think is strange, is that the certificate i can select for the replica server connection is only the AMS1HA2BRK certificate and NOT the computer certificate, as described in the article. I would not think that is incorrect, but it is a difference.

Windows Server 2012 r2

i'm building a sql server cluster and one of the recommendations from our dba are the following:

• to format a guest hd with 64kb allocation unit
• to create a RAID10 for the data disks in D:, E:

i'm asking because i'm of the impression that the above is under the control of the hyper-v master and SAN storage respectively?

Hi,

We have an Hyper-V infrastructure which is composed of 6 nodes running on Windows 2012 R2 (HP servers with the same materials). 4 "Cluster Shared Volume" have been created, together with a Quorum.

When we assign a CSV to another node, we have no problem, except with the node n°5. In this case, when a CSV is assigned to node n°5, only the node n°5 can see the content of the volume in the Windows Explorer. The other nodes cannot.

From the other nodes, we have this error message :

"C:\ClusterStorage\VolumeXXX is not accessible. Logon failure : the user has not been granted the requested logon at this computer".

We also note that the size of the assigned volume doesn't appear on the other nodes in the Windows Explorer.

What is amazing is that we encountered no issues with the virtual machines.

I have read many forum on the Net. Talking about SMB which could be disabled, but like the storage is connected by Fibre Channel, it doesn't seem to apply to us. Furthermore, the components "Clients for Microsoft Network" and "File and Print Sharing..." are enabled on the network cards dedicated to the cluster.

One last information. The node n°5 has been reinstalled from a Sysprep image, but the problem is still there.

Can you help us ?

Best regards.

Laurent

We have a shop with a domain controller that is down because the server has no warranty. What I would like to do is install Hyper V on a data server with Windows server 2008 r2 and install a new VM with windows server 2012 r2. I would like to then promote that vm to be a domain controller.

Since I am new to hyper v, if I have to restart the physical data server, I will shutdown the Hyper Visor VM then reboot the server. When the server comes back online, I would like it to auto start the VM saving us from having to log into the server and manually turn it on.

Is this possible?

Hello folks,

I have one stand alone Hyper-V host with two NICs.  NIC1 I use for management and connecting to it via RDP (untagged VLAN1).  NIC2 I want to use for VMs on multiple VLANs.  I followed these steps so far, but VM is not getting an IP from my DHCP server on VLAN1 that I've specified. 

Any comments or help?  :)

My steps so far:

1. Configure Cisco 2960G switchport connected to NIC2 for trunk and vlans.

interface GigabitEthernet0/11

switchport mode trunk

switchport trunk allowed vlan 1-4

2. Configure Virtual switch on Hyper-V host.  I did not check Allow management, because I am using NIC1 for that.

3. Configure VM NIC and assign VLAN ID, in this case VLAN 1 for a test.

4. Does not get an IP from the DHCP server.  I also tried a static IP, unable to communicate, so I know something is wrong.

my hosts are 2008R2 so the VMs running on the server have integration tools of the same version.. VMs are 2008/2012/ 2012R2... i want to upgrade the integration tools to the latest version like 2012 R2 .. can i do this .. hope this is possible and wont crash my work loads like exchange and PDC.

can you guys please help and guide me to the right link/ KB

Thanks, Happiness Always
Jatin

Hi,

I am looking at deploying SCVMM 2016 for a customer and the VMM Management server has to run on Windows Server 2016.

The VMM server will be deployed as a virtual machine on a 2012R2 Hyper-V host but I can't see anywhere if this is definitely supported.

Supported guest Operating Systems on the Hyper-V 2012R2 page shows 2016 Technical Preview but not the released version - I'm guessing they have not updated the page since 2016's GA release but does anyone know for sure?

https://technet.microsoft.com/library/dn792027.aspx?f=255&MSPPError=-2147217396

Thanks!

This is the complete output:

PS C:\Windows\system32> Remove-VMSwitch "Windows Phone Emulator Internal Switch" -force
Remove-VMSwitch : Failed while removing virtual Ethernet switch.
At line:1 char:1+ Remove-VMSwitch "Windows Phone Emulator Internal Switch" -force+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (Microsoft.HyperV.PowerShell.VMTask:VMTask) [Remove-VMSwitch], VirtualizationOperationFailedException+ FullyQualifiedErrorId : Unspecified,Microsoft.HyperV.PowerShell.Commands.RemoveVMSwitchCommand