Recently I am investigating NLB VIP unstable issue. I also found another issue with ARP, it's might be same issue with NLB.

environment info please see this thread: https://social.technet.microsoft.com/Forums/en-US/df4722a9-62fa-4d34-a1d3-9dd2de0fa8cd/hyperv-nlb-vip-unable-to-ping-from-some-clients?forum=winserverClustering

I found when NLB VIP get unstable, some VM nodes within this NLB cannot ping it's GW of NLB dedicate NIC. but the LAN NIC ping gateway is pretty fine.

After configure port mirror on TOR switch, I can capture ARP reply package from Cisco Switch. but on Hyper-V host, I can only see ARP package send out, but without any ARP response inbound.

Reboot V-Host or just disable then enable NIC on Hyper-V host, can fix this issue temporary. but after hours or one day, this issue will repro again.

by netsh trace log, found two strange reason. all VM have been disabled MAC Address spoofing and never use NIC bridge.

[0]0000.0000::‎2017‎-‎01‎-‎18 14:08:42.090 [Microsoft-Windows-Hyper-V-VmSwitch]NBL destined to Nic 5ABC7209-83A0-4034-A30C-1D34B066AC9C--71761E64-BF59-4A0D-93CC-3F7C25021AEF (Friendly Name: Network Adapter) was dropped in switch 037C29CB-B632-498B-B1B3-D676884AF17D (Friendly Name: VLAN_693_10.185.76.96_27), Reason Bridge is not allowed to run inside VM 

[24]0004.29E8::‎2017‎-‎01‎-‎18 12:47:07.651 [Microsoft-Windows-Hyper-V-VmSwitch]NBL originating from Nic 0C493B45-B40B-46BC-BD2D-835A95D7C19A--B56F8597-A216-406E-B1C3-187246E51EA4 (Friendly Name: Network Adapter) was dropped in switch 766ED074-5690-4A47-9819-8CF160B99D7E (Friendly Name: VLAN_692_10.185.76.64_27), Reason Spoofed MAC address is not allowed 

Hello 
This may have nothing to do with hyper-v but can't find anything on this when I google so I am taking a chance people here will know something.

In my hyper-v windows 10 machine I have some certificates that I would like to delete.  So I go mmc - add snapin - certificates - my user account. Mark the certificate and delete it. 

Now it is gone. Until I restart the machine, then it is back again... Why is this and how do I remove it permanently. I first thought it came back from the server on start up but it comes back when there is no server too.

Hello,

Where I can find the latest information on Hyper-V 2016 Backup and Recovery APIs for VSS less (RCT) backup and recovery? I am using some of the WMI APIs with a C# program what Taylor Brown discussed in his Europe-2014 TechEd talk. Few things are working but few things are giving error, e.g. 

1. I am not able to use DestroyReferencePoint API using WMI, some parameter seems to be missing, but do not get detailed information as what needs to be done.

2. Not able to find any parameter to set incremental snapshot during CreateSnapshot WMI API.

Any help and pointer to latest documents about API are highly appreciated.

Thanks,

-Upanshu

We have a number of 2012 R2 Hyper-V hosts working just fine in domains with 2012 R2 domain controllers (forest/domain functional level same).

However, two of these 2012 R2 Hyper-V hosts are in a domain with 2008 R2 domain controllers (forest/domain functional level same) and both hosts are seeing 3 of these 14050 errors every 2 minutes.  Replication works just fine.  Just the annoying errors spewing into the Microsoft-Windows-Hyper-V-VMMS-Admin log.

We've created the outbound firewall rules for port ranges 5000-5400 and 9000-9999 (based on other KB articles) and verified with "Get-NetFirewallRule -PolicyStore ConfigurableServiceStore".

We've restarted the VMMS service, rebooted, turned off the firewall.  Still getting the errors!

We have 2 server at our building and we would like to upgrade them to newer more recent machines. 

Currently, Server1 is acting as the Domain Controller and Sage DB server. Server2 is the Terminal Server/RDS which usually have about 20-30 people online at once. What we like to do is split Server1 into 2 VM on a new machine, VM1 and VM2. We would also like to be able to convert Server2 into VM3 sometime later.

Here are the specs of the servers and their resource usage:

Server1 (DC+DB)

PowerEdge 2900 Windows Server 2003

Intel(R) Xeon(R) CPU 5130 @ 2.00GHz x1 (4C/4T total)

4GB RAM

Resource Usage: 30-60% CPU, 30-40% RAM

Server2 (TS/RDS)

PowerEdge R410 Windows Server 2008 R2

Intel(R) Xeon(R) CPU E5630 @ 2.53GHz x2 (8C/16T total)

32GB RAM

Resource Usage: 30%-60% CPU, 60-85% RAM

Seeing as we are able to run both the DC and DB role on a very old machine, I take it would be no problem to split the role and virtualize two VM on new machine with new OS. What if I add the TS to the VM as well, would it be able to handle the load just fine?

What specs are the minimum and recommended to handle just the DC and DB virtual machine? And what specs are the minimum and recommended to handle all 3 as virtual machines? This will all be on WS2016. Please include processor, memory, hard drive types, and raid configuration, and any other information. Thanks

Hi,

I have a new Hyper-V environment using Windows 2016 Standard and have run into an issue with restarting the VM's from the start menu inside the VM.

The VM will start the restart process but when it has finished stopping the services it shuts down and does not restart unless I manually start the VM from the Hyper-V console.

Thanks in advance

Bill

I am setting up a Hyper-V Lab and I am stuck on getting the switching/routing to work.

The machine I will be using as host is a Windows 10 Desktop Computer with Hyper-V Installed.

I know I need an external switch to get internet access to lab, but I only want my Domain Controller to get internet access and server out DHCP/DNS to my workstation clients and then other servers in lab will be static IP with Internet access.  I am having trouble accomplishing this and am looking for simple guidance.

Thanks!

We have Windows Server 2012 R2 Domain Controller.. and have 4 ADC at different location.

when I take new PC in domain it gives me following error first. when I restart PC 2-3 times it connect to domain ..

It should connect to nearest Domain Controller but it's not connect to nearest DC... showing logon server after this cmd set l..

....

Hi,

I have two identical physical servers: 8 core Xeon with HT, 96 GB RAM, 2 x OS SSDs in RAID 1, 4 x 4 TB HDs, 2 x 180 GB SSDs, dual 10GbE NICs, and 6 x 1 Gbps NICs. Each server has Server 2016 Data Center with Desktop Experience installed on the RAID 1 SSDs.

I want to configure this hardware into a Hyper-V cluster that does fail-over whilst also using S2D as the data storage mechanism, and I have some questions. The 4 x 4 TB will form the storage area for S2D on each server with the 2 x 180 GB SSDs being the S2D cache. These 6 HDs are configured as pass-through in each server's BIOS.

1) Does the Server 2016 Data Center OS that are acting as the Hyper-V hosts have to be attached to a domain to do Hyper-V clustering? I really want to set this up in the lab before getting it to the customer and then attaching the Hyper-V guests to the domain. But I'd rather leave the Hyper-V hosts off the domain.

2) Am I right in thinking I can achieve what I want with Hyper-V clustering and S2D? I imagine the S2D will give me storage space on each physical server through the Hyper-V host, and also replicate itself over to the other server. So when I have my Hyper-V guests stored on the S2D space I will have a resilient infrastructure that can quickly deal with a physical server going down (the dead server's data will be on the other server's S2D space, and the Hyper-V host easily be able to spin up the VMs that were running on the dead server).

3) When setting this up, should I be configuring the Hyper-V clustering first, or the S2D first?

4) I have 2 x 10 GbE NICs on each server, and a switch with 4 x 10 GbE ports on. Should I use both 10 GbE ports on the Hyper-V hosts for S2D replication. or one for S2D replication and one for something else like RDMA?

There's not that much good documentation out there atm. A lot of stuff refers to technical previews of Server 2016 which has since changed. A lot talks about CSV but not S2D. The stuff that talks about S2D doesn't talk about Hyper-V failover, etc.

Thank you for reading.

I create a new virtual machine and connected with one of existing virtual switch.

Virtual machine which was before connected to this virtual switch is still visible in HvConect.

Is there any way to remove it from list in HvConect.

Thanks

Batocanin

Dear All

I have the following setup.

1. Host Server which is also ADS server and DNS Server. This is the physical server. WS2012R2 is the Base OS.

2. 4 x Hyper-V Guest Servers running WS2012R2 Std Edition configured  onto this server.

3. One of the Hyper-V Servers is a Terminal Client Server. We have about 50 Thin Clients connecting to this server. Another is the application Server.

4. The Thin Clients have Win7 OS embedded on them. The Thin Clients connect to TS server first and then they can access the application server.

Problem :

Sometimes when Thin Clients try to log in ; they get message TS-Server could not be located ; i.e. the TS-Server is not accessible. But when the Thin Client is rebooted

Some times the problem goes away after a few minutes. Without doing anything.

Sometimes we have to reboot the TS Server ( Virtual).

Sometimes we have to shutdown all servers and reboot the physical host server and restart everything all over again. But the problem comes up again in next 2-3 days.

We have installed all the windows updates and patches and we do it weekly for all servers.

Any suggestions ?

Hi Guys,

I have had a quick look through the forum but cant seem to find anything on my problem.

The setup I have is as follows;

3 x Hyper V 2012R2 (Domain) Servers - IP 192.168.1.x

1 x Hyper V 2012R2 (Workgroup Test) Server - IP 192.168.9.x

I have on my Windows 10 1607 Machine the OS built it Hyper V Manager. - (Domain)

Now the problem starts here;

I can contact the other Hyper V Servers on the Domain (which I expected) but I'm having problems connecting to the workgroup server.

I have tried HVREMOTE tool to setup the trust relationship between my windows 10 machine and the workgroup server so that the manager can connect.

The HVREMOTE tool reports NO errors regarding the configuration.

There is no doubt a problem with trust relationship between W10 and the HyperV server but WHERE!!!!.

I have trawled through hundreds of internet fixes and broken many a hyperv server by doing so but nothing so far fixes the problem.

The message I get is below showing a very generic error.



But if I use different credentials (that I know has admin rights on that server) I get this error;

So I'm at a loss of where the problem lies and how to resolve it.

Has anyone had a similar problem using the Windows Hyper V Manager to contact a Domain -> Non Domain server.

Any information would be grateful.

Regards

I have an AD with a range of Server 2008R2 machines that I wish to migrate from their old physical hosts to new Hyper-V infrastructure.

My question; if I host on Hyper-V Server 2016, do all my 2008R2 server user CALs have to be replaced with 2016 Server CALs despite my users actually accessing the 2008R2 servers?

thanks.

Hi, i have a doubt.

I have an Microsoft Hyper-V Server 2016. On this server its running an Oracle Linux VM with a Oracle Database on top. The Oracle Database its configured to use ASM storage (standalone with local disks, not a RAC Cluster).

Actualy the server phisical disks are old 512 bytes SAS disk (here its Brazil Guys, i bougth a new Dell Poweredge 630 server and Dell send me these old technology disks), not the new 4K disks.

We all know that for database servers, larger blocks/stripe sizes are better for performance, but now im limited by the phisical hardware.

I want to know if i move the already in use VHDXs to a new storage (new local 4k disks or even a better iscsi storage) the linux will automaticly be beneficied by the changes or if i will have to use new VHDXs (or format the old ones) to use the updated phisical disks enhancements?

To exemplify my problems here are some the disks configurations on Hyper-V Server and on the Linux VM

PS C:\Users\administrador.CN> Get-PhysicalDisk | sort-object SlotNumber | select SlotNumber, FriendlyName, Manufacturer,
 Model, PhysicalSectorSize, LogicalSectorSize | ft -autosize

SlotNumber FriendlyName         Manufacturer Model            PhysicalSectorSize LogicalSectorSize
---------- ------------         ------------ -----            ------------------ -----------------
           FreeNAS iSCSI Disk   FreeNAS      iSCSI Disk                   131072               512
           FreeNAS iSCSI Disk   FreeNAS      iSCSI Disk                   131072               512
           DELL PERC H730P Mini DELL         PERC H730P Mini                 512               512
           DELL IDSDM           DELL         IDSDM                           512               512
           WD My Passport 0741  WD           My Passport 0741               4096               512


PS C:\Users\administrador.CN> exit

C:\Users\administrador.CN>wmic partition get BlockSize, StartingOffset, Name, Index
BlockSize  Index  Name                   StartingOffset
512        0      Disco #4, Partição #0  135266304
512        0      Disco #3, Partição #0  33685504
512        1      Disco #3, Partição #1  17408
512        0      Disco #0, Partição #0  1048576
512        1      Disco #0, Partição #1  315621376
512        2      Disco #0, Partição #2  554696704
512        3      Disco #0, Partição #3  85900394496
512        0      Disco #2, Partição #0  135266304
512        1      Disco #2, Partição #1  17408
512        0      Disco #1, Partição #0  4194304

Physical Disks on Hyper-V Server

PS C:\Users\administrador.CN> Get-VHD -Path "g:\vhds\*" | FT Path, LogicalSectorSize, PhysicalSectorSize -Autosize

Path                               LogicalSectorSize PhysicalSectorSize
----                               ----------------- ------------------
g:\vhds\nostromo-oracle-bin.vhdx                 512               4096
g:\vhds\nostromo-oradata01.vhdx                  512               4096
g:\vhds\nostromo-oradata02.vhdx                  512               4096
g:\vhds\nostromo-oradata03.vhdx                  512               4096
g:\vhds\nostromo-oradata04.vhdx                  512               4096
g:\vhds\nostromo-redo-ctlvhdx.vhdx               512               4096
g:\vhds\nostromo-root.vhdx                       512               4096
g:\vhds\nostromo-swap.vhdx                       512               4096

Virtual Disks on the server

[root@nostromo ~]# cat /sys/block/sdh/queue/optimal_io_size
0
[root@nostromo ~]# cat /sys/block/sdh/queue/minimum_io_size
4096
[root@nostromo ~]# cat /sys/block/sdh/queue/physical_block_size
4096
[root@nostromo ~]# cat /sys/block/sdh/queue/max_sectors_kb
512
[root@nostromo ~]# cat /sys/block/sdh/queue/max_hw_sectors_kb
512
[root@nostromo ~]# cat /sys/block/sdh/queue/hw_sector_size
512
[root@nostromo ~]# fdisk -l /dev/sdh | grep "Sector size"

WARNING: GPT (GUID Partition Table) detected on '/dev/sdh'! The util fdisk doesn't support GPT. Use GNU Parted.

Sector size (logical/physical): 512 bytes / 4096 bytes
[root@nostromo ~]# parted -l
Model: Msft Virtual Disk (scsi)
Disk /dev/sda: 85,9GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Sinalizador
 1      1049kB  2098MB  2097MB  fat32              boot
 2      2098MB  4195MB  2097MB  ext4
 3      4195MB  85,9GB  81,7GB  ext4


Model: Msft Virtual Disk (scsi)
Disk /dev/sdb: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdc: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdd: 215GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name     Sinalizador
 1      2097kB  215GB  215GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sde: 215GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name     Sinalizador
 1      2097kB  215GB  215GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdf: 34,4GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system     Name  Sinalizador
 1      1049kB  34,4GB  34,4GB  linux-swap(v1)  SWAP


Model: Msft Virtual Disk (scsi)
Disk /dev/sdg: 107GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name  Sinalizador
 1      1049kB  107GB  107GB  ext4


Model: Msft Virtual Disk (scsi)
Disk /dev/sdh: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdi: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdj: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary


Model: Msft Virtual Disk (scsi)
Disk /dev/sdk: 53,7GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Sinalizador
 1      2097kB  53,7GB  53,7GB               primary

Partitions inside Linux VM

Ps.: Sorry about my bad english.

Hi all,

Windows Server 2003 is not supported as a guest VM on Hyper-V 2016.

But I have a case where we need to keep an old Windows Server 2003 running for approx another 5 years.

Has anybody tried to run Windows Server 2003 as a VM under Hyper-V 2016?

If yes - any problems/fixes/need-to-know-trics I should be aware of?

Thx.

PS: I know Windows Server 2003 is EOL and should be long gone, but it's not going to happen in this case!

We have a 2 nodes Hyper-V cluster.

Failover VM setting "Cluster-controlled offline action" is Save

Hyper-V VM setting "Automatic Stop Action" is Shutdown

1) What happens if a shutdown a host ?? Will VM move to other host ??

2) What happens if a move a VM (domain controller) to other host ?? Is supported live migration on DC without shutdown computer ??

I just finished building 2 new Server 2012 R2 Hyper-V Hosts.  Each running 3 VMs (All Server 2012 R2 as well).  I use Veritas Backup Exec.  Started a backup of each and AVHD files were created during the backup that did not merge back into the parent file after the backup ran.  To "fix" this I manually merged the AVHD file into the parent.  I then re-ran the backup and the same thing happened again.  So I merged the files again.

Now I have checkpoint that I can NOT delete in the Hyper-V Manager.  I started researching and tried some commands in Powershell but nothing seems to work.

Please help....

Brian Modlin