Windows server 2012 Datacenter Hyper-V Cluster -- Failed to validate Operating System Installation Option?

Hi I have a 4 node Windows server 2012 Hyper-V cluster. When I try to run a cluster validation report, everything else is fine but it fails at validate the Operating System Installation Option step. I did some research but couldn't really find any solution.
Anyone knows how to pass this test? Thanks.
Here's the error I get when run the test:
An error occurred while executing the test.
The operation has failed. An error occurred while getting the operating system installation option for node "server1"

Hi JasonLiu2002,
Please post the original error information, the current information is so wide that difficult to determine where may have issue and please offer more information about your
server configuration, you can refer the following article to prepare your cluster environment first.
Windows Server 2012 Hyper-V Best Practices (In Easy Checklist Form)
http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx
When you preparing the new cluster on Server 2012 please install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters updates.
http://support.microsoft.com/kb/2784261
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Server 2012 R2 Hyper-V Cluster, VM blue screens after migration between nodes.

I currently have a two node Server 2012 R2 Hyper-v Cluster (fully patched) with a Windows Server 2012 R2 Iscsi target.
The VMs run fine all day long, but when I try to do a live/quick migration the VM blue screens after about 20 minutes. The blue reports back about a “Critical_Structure_Corruption”.
I’m being to think it might be down to CPU, as one system has an E-2640v2 and the other one has an E5-2670v3. Should I be able to migrate between these two systems with these type of CPU?
Tim

Sorry Tim, is that all 50 blue screen if live migrated?
Are they all on the latest integration services? Does a cluster validation complete successfully? Are the hosts patched to the same level?
The fact that if you power them off then migrate them and they boot fine, does point to a processor incompatibility and the memory BIN file is not accepted on the new host.
Bit of a long shot but the only other thing I can think of off the top of my head if the compatibility option is checked, is checking the location of the BIN file when the VM is running to make sure its in the same place as the VHD\VHDX in the
CSV storage where the VM is located and not on the local host somewhere like C:\program data\.... that is stopping it being migrated to the new host when the VM is live migrated.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

(Request for:) Best practices for setting up a new Windows Server 2012 r2 Hyper-V Virtualized AD DC

Could you please share your best practices for setting up a new Windows Server 2012 r2 Hyper-V Virtualized AD DC, that will be running on a new WinSrv 2012 r2 host server. (This
will be for a brand new network setup, new forest, domain, etc.)
Specifically, your best practices regarding:
the sizing of non virtual and virtual volumes/partitions/drives,
the use of sysvol, logs, & data volumes/drives on hosts & guests,
RAID levels for the host and the guest(s),
IDE vs SCSI and drivers both non virtual and virtual and the booting there of,
disk caching settings on both host and guests.
Thanks so much for any information you can share.

A bit of non essential additional info:
We are small to midrange school district who, after close to 20 years on Novell networks, have decided to design and create a new Microsoft network and migrate all of our data and services
over to the new infrastructure . We are planning on rolling out 2012 r2 servers with as much Hyper-v virtualization as possible.
During the last few weeks we have been able to find most of the information we need to undergo this project, and most of the information was pretty solid with little ambiguity, except for
information regarding virtualizing the DCs, which as been a bit inconsistent.
Yes, we have read all the documents that most of these posts tend point to, but found some, if not most are still are referring to performing this under Srvr 2008 r2, and haven’t really
seen all that much on Srvr2012 r2.
We have read these and others:
Introduction to Active Directory Domain Services (AD DS) Virtualization (Level 100),
Virtualized Domain Controller Technical Reference (Level 300),
Virtualized Domain Controller Cloning Test Guidance for Application Vendors,
Support for using Hyper-V Replica for virtualized domain controllers.
Again, thanks for any information, best practices, cookie cutter or otherwise that you can share.
Chas.

Adding nodes to Windows Server 2008 R2 Hyper-V Cluster..

Currently we have a 3 node Windows Server 2008 R2 Hyper-V Cluster in production. There are about 3 terrabytes worth of VMs running across these nodes.
It is over-committed, so i've setup two new nodes to add to the cluster.
I've done this before in a SQL cluster but never a Hyper-V cluster.
If I don't run validation when adding the nodes, will there be downtime?
The quorum is setup for disk majority, everything is identical on all nodes that needs to be. Shared storage is recognized and ready on the new nodes. I've gone through every checklist that Microsoft has. I'm just curious if the virtual machines will go
offline on the current nodes when i add the two new nodes.
Everything is identical down to the wsus updates installed. From networking to storage everything is perfect.
I don't want to run validation as I know that'll take everything offline.

Hi,
It is recommend to run a validation test. You can select custom test. (skip storage).
When add the new node to existing cluster . it will not bring down existing VM.
Lai (My blog:- http://www.ms4u.info)

VMM Agent install fails on Windows Server 2012 R2 Hyper-V

Hi,
We are unable to install VMM 2012 R2 agent on Windows Server 2012 R2 server either from VMM console or manually on the hyper-v server.
Error on VMM Console:
Error (410)
Agent installation failed on chsicoecdh03.casper.com.
Fatal error during installation (0x80070643)
Recommended Action
Try the operation again. If the problem persists, install the agent locally and then add the managed computer.
==================================================================
Error on Hyper-v server:
MSI (c) (E8:D0) [16:53:24:726]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Agent (x64). Product Version: 3.2.7510.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success
or error status: 1603.
Also, I suspect may be issue with WMI then checked WMI repository and it is in consistent state. winmgmt /verifyrepository.
Please help on this issue.
Any help would be appreciated.
Thanks
Kumaresan Lakshmanan

So, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now.

Windows Server 2012 R2 - ALL HF's Failing to install as "Does Not Apply to this computer"

Hi,
A general question about hot fix installs.
I have multiple servers that are all Windows 2012 R2. They do not have internet connections, so I have to install the Hotfixes manually. I download the HF's from the ISO download page (https://support.microsoft.com/en-us/kb/913086) every month. I collect them and install in a bulk install during a release cycle ( a couple times a year). I just realized that NO HF's have installed since JUNE 2014. Every HF that shows up in WindowsServer2012R2 directory fail to install with a message of "The update is not applicable to your computer". Which is fine if that was true, but.... I get this message for every HF from the ISO's since June 2014. NOT one HF thinks it is applicable to my computer. Could that be the case? No HF's apply to my Server 2012 systems since June of 2014?
This is my system info, and below that is the results from attempting to install 95 HF's.
C:\TEMP>systeminfo
Host Name: MYHOST
OS Name: Microsoft Windows Server 2012 R2 Datacenter
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 00252-80025-36226-AA727
Original Install Date: 6/13/2014, 8:04:39 AM
System Boot Time: 3/16/2015, 2:34:45 PM
System Manufacturer: Dell Inc.
System Model: PowerEdge R720
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
[02]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
BIOS Version: Dell Inc. 2.2.2, 1/16/2014
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
Total Physical Memory: 262,099 MB
Available Physical Memory: 249,337 MB
Virtual Memory: Max Size: 301,011 MB
Virtual Memory: Available: 288,015 MB
Virtual Memory: In Use: 12,996 MB
Page File Location(s): C:\pagefile.sys
Domain: mydomain.sgn
Logon Server: \\MYHOST
Hotfix(s): 25 Hotfix(s) Installed.
[01]: KB2862152
[02]: KB2868626
[03]: KB2876331
[04]: KB2888505
[05]: KB2892074
[06]: KB2893294
[07]: KB2893984
[08]: KB2898785
[09]: KB2898868
[10]: KB2898871
[11]: KB2900986
[12]: KB2901125
[13]: KB2901128
[14]: KB2909210
[15]: KB2909921
[16]: KB2912390
[17]: KB2916036
[18]: KB2919442
[19]: KB2922229
[20]: KB2923392
[21]: KB2925418
[22]: KB2930275
[23]: KB2931358
[24]: KB2931366
[25]: KB2936068
Network Card(s): 6 NIC(s) Installed.
[01]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: ISCSI
DHCP Enabled: No
IP address(es)
[01]: 192.168.1.30
[02]: fe80::38c9:e59c:5ac2:e0a1
[02]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: NIC3
Status: Hardware not present
[03]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: MGMT
DHCP Enabled: No
IP address(es)
[01]: 7.48.64.32
[02]: 7.48.64.30
[03]: fe80::f14e:9339:9326:c7fd
[04]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 1_swport_VMRepwan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[05]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: NIC2
Status: Hardware not present
[06]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 2_swport_VMOpswan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
Hyper-V Requirements: A hypervisor has been detected. Features required for
Hyper-V will not be displayed.
I have a script that runs each HF install.. If I run them manually without the tool I get the same results so it is not the script..
Installing 95 patches
for Microsoft Windows Server 2012 R2 Datacenter x64
Repository path: U:\Patch Repository_4_1\2012_R2_HFs\
1. Windows8.1-KB2894852-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
2. Windows8.1-KB2894856-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
3. Windows8.1-KB2920189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
4. Windows8.1-KB2926765-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
5. Windows8.1-KB2928120-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
6. Windows8.1-KB2931358-x64.msu patch status: ALREADY INSTALLED - SKIPPING
7. Windows8.1-KB2931366-x64.msu patch status: ALREADY INSTALLED - SKIPPING
8. Windows8.1-KB2933826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
9. Windows8.1-KB2939576-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
10. Windows8.1-KB2953522-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
11. Windows8.1-KB2957151-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
12. Windows8.1-KB2957189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
13. Windows8.1-KB2957689-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
14. Windows8.1-KB2961072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
15. Windows8.1-KB2961887-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
16. Windows8.1-KB2962872-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
17. Windows8.1-KB2964718-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
18. Windows8.1-KB2964736-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
19. Windows8.1-KB2965788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
20. Windows8.1-KB2966072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
21. Windows8.1-KB2966826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
22. Windows8.1-KB2966828-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
23. Windows8.1-KB2971850-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
24. Windows8.1-KB2972213-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
25. Windows8.1-KB2972280-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
26. Windows8.1-KB2973114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
27. Windows8.1-KB2973201-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
28. Windows8.1-KB2973351-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
29. Windows8.1-KB2974008-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
30. Windows8.1-KB2976627-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
31. Windows8.1-KB2976897-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
32. Windows8.1-KB2977292-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
33. Windows8.1-KB2977629-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
34. Windows8.1-KB2978668-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
35. Windows8.1-KB2982794-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
36. Windows8.1-KB2982998-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
37. Windows8.1-KB2987107-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
38. Windows8.1-KB2987114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
39. Windows8.1-KB2988948-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
40. Windows8.1-KB2992611-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
41. Windows8.1-KB2993651-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
42. Windows8.1-KB2993958-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
43. Windows8.1-KB3000061-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
44. Windows8.1-KB3000483-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
45. Windows8.1-KB3000869-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
46. Windows8.1-KB3001237-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
47. Windows8.1-KB3002657-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
48. Windows8.1-KB3002885-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
49. Windows8.1-KB3003057-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
50. Windows8.1-KB3003381-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
51. Windows8.1-KB3003743-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
52. Windows8.1-KB3004150-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
53. Windows8.1-KB3004361-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
54. Windows8.1-KB3004365-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
55. Windows8.1-KB3005607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
56. Windows8.1-KB3006226-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
57. Windows8.1-KB3008923-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
58. Windows8.1-KB3008925-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
59. Windows8.1-KB3010788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
60. Windows8.1-KB3011780-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
61. Windows8.1-KB3013126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
62. Windows8.1-KB3013455-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
63. Windows8.1-KB3014029-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
64. Windows8.1-KB3018943-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
65. Windows8.1-KB3019215-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
66. Windows8.1-KB3019978-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
67. Windows8.1-KB3020393-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
68. Windows8.1-KB3021674-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
69. Windows8.1-KB3021952-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
70. Windows8.1-KB3023607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
71. Windows8.1-KB3036197-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
72. Windows8.1-KB3021953-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
73. Windows8.1-KB3022777-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
74. Windows8.1-KB3023266-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
75. Windows8.1-KB3023562-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
76. Windows8.1-KB3024663-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
77. Windows8.1-KB3029944-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
78. Windows8.1-KB3030377-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
79. Windows8.1-KB3031432-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
80. Windows8.1-KB3032323-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
81. Windows8.1-KB3032359-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
82. Windows8.1-KB3040335-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
83. Windows8.1-KB3033408-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
84. Windows8.1-KB3033889-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
85. Windows8.1-KB3034196-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
86. Windows8.1-KB3034344-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
87. Windows8.1-KB3035017-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
88. Windows8.1-KB3035034-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
89. Windows8.1-KB3035126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
90. Windows8.1-KB3035131-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
91. Windows8.1-KB3035132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
92. Windows8.1-KB3037634-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
93. Windows8.1-KB3039066-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
94. Windows8.1-KB3044132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
95. Windows8.1-KB3046049-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
Thanks,
Dave

Hi Dave,
Would you please check CBS lg file and other relevant event logs if find more clues? On current situation, please refer to following article and check if can help you.
Update is not applicable to your computer- but it is
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maximum number of processor sockets in Windows Server 2012 Datacenter and Standard

I have found no documentation on the technical number of supported processor sockets supported by Windows Server 2012 for the Standard and Datacenter editions.
Some donation websites like Techsoup claim that Datacenter supports 64 physical processors and Standard 8, but I can find no authoritative confirmation of this and those look like extrapolation from Windows Server 2008 R2.
So what are the maximum supported # of processor sockets, assuming you have licenses for all of them, for Datacenter and Standard? Do they differ by edition?
In addition, is it true that the total # of supported logical processors in a single system is 640 w/o Hyper-V? It was originally reported to be that, but since Hyper-V's number doubled from 160 in the Beta to 320 in the RC and RTM, did this double too?

You might find some of the information you are looking for here -
http://download.microsoft.com/download/2/C/A/2CA38362-37ED-4112-86A8-FDF14D5D4C9B/WS%202012%20Feature%20Comparison_Hyper-V.pdf. I know there is one change that is not reflected there. Recently the maximum number of virtual machines supported
in a cluster was raised to 8,000 instead of the 4,000 reflected in this document.
The maximum number of sockets for Standard would be two because that is the maximum number that the license supports. Standard has never supported 8. Prior to 2012, it supported 4, and then the licensing changed with 2012 so that Standard would
be sold per processor (socket) with a maximum of two. Technically, the binaries are the same for Standard and Datacenter, so you can most likely get it to run with more somehow, but it is not a supported configuration.
The maximum number of sockets for Datacenter would be 64 - that has not changed from 2008. I make this statement based on the fact that Datacenter supports a maximum of 64 virtual CPUs when run as a virtual machine. Virtual machines don't have
the distinction of socket versus hyper-thread versus core. They see what is presented to them as a processor. But, I doubt very much that you will find any off-the-shelf 64 socket systems; most vendors are relying on the core densities instead
of socket density in order to deliver the horsepower. The above referenced document still shows 320 as the maximum number of logical processors, with or without Hyper-V.
tim

DPM 2012 R2 - Windows Server 2012 R2 Hyper-v backup of Windows Server 2003 R2 - Non-retryable error 0x80070490

Hi,
I have a hyper-v host running Windows Server 2012 R2 Standard with Hyper-V on it, and on that host I got 5 virtual machines running and of those 5, 4 of those the DPM are able to backup but when DPM tries to backup a server running Windows Server 2003 R2
I get the following errors in the eventlog.
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 2013-11-28 10:46:58
Event ID: 18014
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPERV05.domain.local
Description:
Checkpoint operation for 'SERVER01' was cancelled. (Virtual machine ID 5221623F-C80C-4B92-AD02-F545D118C859)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>18014</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-11-28T09:46:58.365308800Z" />
<EventRecordID>411</EventRecordID>
<Correlation />
<Execution ProcessID="2116" ThreadID="4248" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPERV05.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>SERVER01</VmName>
<VmId>5221623F-C80C-4B92-AD02-F545D118C859</VmId>
</VmlEventLog>
</UserData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 2013-11-28 10:46:58
Event ID: 18012
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPERV05.domain.local
Description:
Checkpoint operation for 'SERVER01' failed. (Virtual machine ID 5221623F-C80C-4B92-AD02-F545D118C859)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>18012</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-11-28T09:46:58.365308800Z" />
<EventRecordID>412</EventRecordID>
<Correlation />
<Execution ProcessID="2116" ThreadID="4248" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPERV05.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>SERVER01</VmName>
<VmId>5221623F-C80C-4B92-AD02-F545D118C859</VmId>
</VmlEventLog>
</UserData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 2013-11-28 10:46:58
Event ID: 10150
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPERV05.domain.local
Description:
Could not create backup checkpoint for virtual machine 'SERVER01': Element not found. (0x80070490). (Virtual machine ID 5221623F-C80C-4B92-AD02-F545D118C859)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>10150</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-11-28T09:46:58.365308800Z" />
<EventRecordID>413</EventRecordID>
<Correlation />
<Execution ProcessID="2116" ThreadID="4280" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPERV05.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>SERVER01</VmName>
<VmId>5221623F-C80C-4B92-AD02-F545D118C859</VmId>
<Parameter0>%%2147943568</Parameter0>
<Parameter1>0x80070490</Parameter1>
</VmlEventLog>
</UserData>
</Event>
What I have done to try to troubleshoot this issue is:
Reinstalled DPM - No sucess
Restarted the Hyper-v Host - No sucess
I'm at the point where I am out of ideas and google hasn't given me much.
/Joseph

i have the same error.
"vssadmin list writers" shows last error unknown for all writers
disk space is sufficient
ntbackup of systemdrive and systemstate runs fine.
i installed KB940349 which fixes some vss related issues but the problem is still there.
any ideas?
Thanks.
When you have vssadmin reporting unknown error the only way to reset the vsswriters (as I understand it please correct me if I'm wrong :) ) is to restart the machine. The Fellenator is correct, make use that the vsswriter is working correctly since this
is the main function DPM is using when taking backup. He's also right in saying that it's outside the scope! Create a new thread on your error, then you will get much better responce!
/Joseph

Windows Server 2012 R2 - Hyper-V NIC Teaming Issue

Hi All,
I have cluster windows server 2012 R2 with hyper-v role installed. I have an issue with one of my windows 2012 R2 hyper-v host.
The virtual machine network adapter show status connected but it stop transmit data, so the vm that using that NIC cannot connect to external network.
The virtual machine network adapter using Teamed NIC, with this configuration:
Teaming Mode : Switch Independent
Load Balance Algorithm : Hyper-V Port
NIC Adapter : Broadcom 5720 Quad Port 1Gbps
I already using the latest NIC driver from broadcom.
I found a little trick for this issue by disable one of the teamed NIC, but it will happen again.
Anyone have the same issue with me, and any workaround for this issue?
Please Advise
Thanks,

Hi epenx,
Thanks for the information .
Best Regards,
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How many licence for Windows Server 2012R2 in hyper-v cluster base on free Hyper-V Server 2012R2

Hi
I build cluster consist 4 nodes (2 procesors, 4 core per procesor=8 virtual processors per node). I installed free Hyper-V Server 2012 R2 on each node and created cluster.
I've got one Windows Server 2012 R2 Standard. How many VMs (with Windows Server 2012 R2 Standrard as OS) can I run on this cluster using this DVD? 1, 2 or none?
Thank you in advance
Tomasz
Kind Regards Tomasz

The detail here is this:
You are asking about the 'virtual instance granting' license.
- this only applies if Windows Server is installed on the bare metal with the Hyper-V Role added. (regardless of the edition)
- this only applies to licensing, it does not limit the number of VMs that you can run.
- If there is a cluster, all nodes should be the same edition to remove any licensing ambiguity.
This is strictly OS licensing for the VMs and has absolutely nothing to do with how many VMs you can run:
Most likely your hardware will run out of physical resources before you reach the maximums outlined here:
http://technet.microsoft.com/en-us/library/jj680093.aspx
If you have a cluster - there can be a maximum of 8,000 running VMs
If you have individual Hyper-V Servers there can be a maximum of 1,024 running VMs
Do the math - you would need a minimum of ~8 cluster nodes to touch that 8,000 number. But as you add nodes, you don't add HA VM capacity. But you can run a combination of HA and non-HA VMs up to a the maximum of 1,024 running VMs per node.
In other words, mix and match if you want to push the boundary.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Windows Domain Controller on Windows Server 2012 R2: Hyper-V roaming profiles not loading due to slow connection

I have racked my brain and done everything that I know to do for about two weeks now. I am setting up a new system at our fire department and I am having the worst luck with getting the workstations to login to the domain controller with roaming
profiles. It keeps telling me that the roaming profile could not be loaded because of a slow connection. These are workstations that are connected directly to the switch that the DC is connected to. I have tried multiple connections regarding
the layout (DC into the router, router into the switch). The router is a Cisco RV220W. I have two VLANS, one for public and one for private domain. The Private VLAN has DHCP turned off since I am providing it through the DC. I currently
have a connection from the Private VLAN going to the unmanaged switch that the workstations and server are plugged into.
The server is a Dell PowerEdge R420 that has 6 NIC ports (1 dual port and 1 quad port). I have a virtual switch setup on Hyper-V for an external port (let's say Card 2 Port 3) that is assigned to the WS 2012R2 Domain Controller. The DC can see
the internet fine and the workstations can connect to the shared folders on the server. I can retrieve files by just using the computer name or FQDN. The DC is also running DNS and DHCP. The DNS has the _msdcs setup from when I installed
the active directory role. I have attempted to assign static IP addresses to the workstations:
IP:                     10.0.0.80
Subnet:             255.255.255.0
IPV4 Gateway: 10.0.0.1
IPV4 DNS:        10.0.0.12
I've attempted "append the specific DNS suffix", I've "registered the connection in DNS", I've used "use this connections suffix in DNS registration".
The server is assigned:
IP:                     10.0.0.12
Subnet:             255.255.255.0
IPV4 Gateway: 10.0.0.1
IPV4 DNS:         10.0.0.12
The DNS entries have forwarders that forward to my ISP DNS servers for lookup
I've enabled and disabled DHCP, I've installed a new VM just to create another DC to make sure that I didn't goof up when I created it.
I've lost my patience with this project and am sinking fast. Can someone please offer some advice as to what I've done wrong? I've created this exact scenario at work many times but, I've never done it with Windows Server 2012. Is this
possibly something to do with the Dell PowerEdge server (Generation 12) with the SR-IOV? I am going to attempt to work on it some more tomorrow when I get over there. I think there may be an issue with the SR-IOV not being enabled on the machine
through the Dell Bios. Would the SR-IOV really cause the workstations to report a slow connection? When I login at the domain controller the roaming profiles and folder redirection work fine so, I know the GPO settings are correct. I don't
have "ignore slow connections" or any of those GPO's set. I need to get it working the correct way so, I didn't want to fool the server when there is another underlying problem. Any help that someone can offer, I am more than willing
to listen. If you need more information, please ask.
Thanks,
Jay

So, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now.

WIndows Server 2012 w/ Hyper V and Windows 7

I have been able to create every imaginable virtualization in a test environment except for Windows 7. It asks for drivers. I have a driver CD but when I put the CD in the D: drive. It will run but suddenly the command line screen states that a file on
the F: drive does not exist. Where is this F: drive coming from?

I might have misstated my situation. I have Windows Server 2012 outfitted with Hyper-V. I'm trying to virtualize a Windows 7 operating system.
I found a another W7 media disk that seems to bypass this problem.

HP DL380 G5 Windows Server 2012 R2 Hyper-V

Hello. I have a HP DL380 G5 server & a have a problem. OS installation proceeds normally, the installation takes the role well, but the virtual machines is running weird. When using a network inside a virtual machine (for example, copy of iso file from
the network to virtual machine) CPU inside of the VM at 100%. 50-60% is process System interrupts. All terribly slow, up until the copy end.
I do not know
what to do. Maybe somebody faced with
something similar? Thnx!
HP DL380 G5:
Intel Xeon 5130 2.0 GHz * 2
Ram 32 Gb
Raid Smart Array P400i 512mb + battery
Network Broadcom BCM5708C 1 Gb * 2
Host OS - raid 1
VMs - raid 10
BIOS P56
HP Service Pack for ProLiant 2014.06
Windows Server 2012 R2 + all updates + all newest drivers

Hi Andrey ,
First , I would suggest you to keep the driver up-to-date for physical NIC .
Then check if the integration service was installed .
Allocate more Vcpu for that VM .
If the issue persists please try to disable "offload" for that VM :
http://blog.nicholasrogoff.com/2010/09/24/windows-2008-r2-hyper-vguests-vms-have-slow-performance-change-you-adapter-settings/
Best Regards
Elton JI
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Hi Elton!
I have already installed
the latest driver for NICs. From here:
Broadcom
The integration service was installed of course.
I added one additional virtual processor per VM. 2012 R2 works better. In 2018 R2 the task manager
freezes
when copying. Load is 100%..
Disabling"offload"
does not help..

Upgrade a Domain Controller running Windows Server 2012 Datacenter Eval

Hello,
because I couldn't wait for Server 2012 to show up on Dreamspark Premium I installed the Datacenter evaluation version after I found this blog
post telling me, I could simply enter my key when I get it to upgrade to the full version.
After entering the command I get notified that "Changing this Windows edition is not supported online for a domain controller.".
The TechNet article for upgrading evaluation versions states the following:
"If the server is a domain controller, see http://technet.microsoft.com/library/hh472160.aspx for important steps to follow before proceeding."
and taking me to an article for installing/uninstalling ADDS without further comments.
Simply typing "slui 3" and entering my key states that I have to enter an eval key.
My question is: Is there a painless way to upgrade my 2012 DC without losing my AD config?
Regards,
Hans

Hi,
Please refer to the following Microsoft TechNet article to confirm if the steps of converting to full retail version are correct.
Evaluation Versions and Upgrade Options for Windows Server 2012
http://technet.microsoft.com/en-us/library/jj574204.aspx
If the warning persists, it means Windows Server 2012 Domain Controller does not support such convert. If so, please install another Windows Server 2012 full retail version or
convert to full retail version and then promote it to an additional Domain Controller for this domain. After that, transfer FSMOs to this new Domain Controller and demote the original Domain Controller.
Regards,
Arthur Li
TechNet Community Support

How to activate Windows Server 2012 Datacenter evaluation version with product key provided on MSDN's student account

Hi,
I downloaded
Windows Server 2012 Evaluation Version recently. Actually, I wanted to check whether i could run Windows Phone 8 emulator on Win server 2012 using my core2duo (Non-SLAT PC). Now i wanted to activate the evaluated version by using product key of my
MSDN's student account. But its giving error when i enter my product key. I checked this article about converting evaluation version to full retail version. The article
says :
"If the server is a domain controller, you cannot convert it to a retail version. In this case, install an additional
domain controller on a server that runs a retail version and remove AD DS from the domain controller that runs on the evaluation version."
So kindly guide as to how I can install this additional domain controller and how to remove AD DS from domain controller. Currently, I have Dual Boot PC( win 8.1 and win server 2012).
Hoping to get a brief response....

Unless you have configured a whole lot of things into the DC running on the evaluation copy (should never install production on an evaluation copy), it would be simplest to start from scratch and reinstall.
Or, you simply go into Server Manager > Manage > Add Roles and Features to remove the AD role. Then you will be back to a workgroup server.
The evaluation version is good for 180 days plus three re-arms of 30 days each. So you can do a lot of experimenting with the evaluation copy without the need for using an MSDN key.
.:|:.:|:. tim

Windows server 2012 Datacenter Hyper-V Cluster -- Failed to validate Operating System Installation Option?

Similar Messages

Maybe you are looking for