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.

Similar Messages

Server 2012 R2 Hyper-V and Drivers

Hello all,
Question is regarding drivers on our Dell Systems we are deploying for use in a MSFT 2012 R2 environment. Some of the systems are showing requiring NIC driver updates from Dell. I'm a little leery of replacing the MSFT drivers with Dell Drivers
so want to hear back on recommendations. I'm concerned that MSFT may not have tested fully the drivers and/or Hyper-V has been tested extensively using MSFT drivers versus vendor NIC drivers.

Hi,
Are you concern the Windows update drivers is tested or not? These Updates are typically available on Windows Update. They frequently contain security fixes, and from time
to time also contain reliability rollup packages.
These updates are thoroughly tested and Microsoft highly recommends that you update your computer with these releases. In fact, most are automatically downloaded to your machine
if you have Windows Update turned on. In most cases, Update releases are also available as standalone downloads from the download center.
More information:
Windows Hotfixes and Updates - How do they work?
http://blogs.msdn.com/b/ntdebugging/archive/2008/10/21/windows-hotfixes-and-updates-how-do-they-work.aspx
Hope this helps.
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.

(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.

Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?

Hi All,
Is it possible to create a two node cluster with SQL server 2012 STD on node1 and SQL Server 2008 ENT on node2 on a Windows server 2012?
aa

I think you are confused with the way cluster is installed. Installing SQL on cluster is a two step process. On first node you create a new SQL cluster and on second node you need "AddNode" action.
Same edition media has to be used in above two operation.
you can install two separate instances with one enterprise and one standard.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

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.

Server 2012 r2 Hyper-v guest network speed with 10 GB NIC's

Hi
Setting up a Server 2012 r2 Hyper-v host with an onboard 4 port 1 GB nic and a offboard dual port 10 GB nic. We are using the 1gb quad port for management. The 10 Gb we intend using for hyper-v guest use however we don't seem to be able to achieve very high
speeds though the 10 GB adapter when assigned to a virtual switch. Testing the 10 Gb nic from the host confirms that we can transfer/get 10 GB speeds. When assigned to a virtual switch however the speed drops to about 1-2 Gbps. Has anybody seen anything like
this ?. We've tried a variety of settings and i can confirm that the network traffic is using the 10 GB nic.

Hi,
I am almost certain what you see is by design. I don't want to go into to much detail because I'm in a bit of a hurry. But allow me to explain.
Suppose you have a 10Gb NIC interface and an multi-core CPU. When you have RSS (Receive-Side Scaling) disabled a single core can normally handing
around 2.5-4.3Gbps. When you enable RSS the data streams/traffic is spread across multiple cores.
But RSS is a network optimization feature for the Management OS, not for a vSwitch. Instead you should use VMQ (Virtual Machine Queuing). VMQ is
the equilavant of RSS, but then intended for VMs. But... there is a difference. VMQ does not spread single data streams/traffic across multiple cores. Instead is (dynamically) assigns each vmNIC its own core. So... you don't use multiple-cores at a time for
a single vmNIC. You can't use RSS and VMQ at the same time. Keep that in mind.
But... you can accomplish this by enabling vRSS as well. That's another story.
If you watch the following video, at the end you know all about VMQ.
Hyper-V dVMQ
http://www.hypervrockstar.com/tag/dvmq/
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

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 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.

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

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.

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.

Unable to add File Server Resource Manager Tools on Windows Server 2012 - Errors on restart and roll back install

Unable to install Windows Server 2012 Feature - [Tools] File Server Resource Manager Tools.
Installs, however when I restart the server error messages appears saying feature unable to install, windows reverting changes.
In the Setup event logs have the following information message "Update FSRM-Infrastructure of package FSRM-All failed to be turned on. Status: 0x800f0922"
Does anyone have any idea's on why this Feature can not be installed ??
Scott

Hi Shaun
Tried both of your suggestions, however neither strategy worked.
Strategy 1
Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"
Feature un-installed itself during the restart.
Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services". However
this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
PACKAGE SERVICING COMMANDS:
/Add-Package - Adds packages to the image.
/Remove-Package - Removes packages from the image.
/Enable-Feature - Enables a specific feature in the image.
/Disable-Feature - Disables a specific feature in the image.
/Get-Packages - Displays information about all packages in the image.
/Get-PackageInfo - Displays information about a specific package.
/Get-Features - Displays information about all features in a package.
/Get-FeatureInfo - Displays information about a specific feature.
/Cleanup-Image - Performs cleanup and recovery operations on the image.
Strategy 2
Tried installing via powershell, using the following command DISM
/online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
All up back to where I started?

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..

Windows Server 2012 R2 NIC Teaming and DHCP Issue

Came across a weird issue today during a server deployment. I was doing a physical server deployment and got Windows installed and was getting ready to connect it to our network. Before connecting the Ethernet cables to the network adapters, I created a
NIC Team using Windows Server 2012 R2 built-in software with a static IP address (we'll say its 192.168.1.56). Once I plugged in the Ethernet cables, I got network access but was unable to join our domain. At this time, I deleted the NIC team and the two network
adapters got their own IP addresses issued from DHCP (192.168.1.57 and 192.168.1.58) and at this point I was able to join our domain. I recreated the NIC team and set a new static IP (192.168.1.57) and everything was working great as intended.
My issue is when I went into DHCP I noticed a random entry that was using the IP address I used for the first NIC teaming attempt (192.168.1.56), before I joined it to the domain. I call this a random entry because it is using the last 8 characters of the
MAC address as the hostname instead of the servers hostname.
It seems when I deleted the first NIC team I created (192.168.1.56), a random MAC address Server 2012 R2 generated for the team has remained embedded in the system. The IP address is still pingable even though an ipconfig /all shows the current NIC team
with the IP 192.168.1.57. There is no IP address of 192.168.1.56 configured on the current server and I have static IPs set yet it is still pingable and registering with DHCP.
I know this is slightly confusing but I am hoping someone else has encountered this issue and may be able to tell me how to fix this. Simply deleting the DHCP entry does not do the trick, it comes back.

Hi,
Please confirm you have choose the right NIC team type, If you’ve previously configured NIC teaming, you’re aware NIC teams usually require the assistance of network-side
protocols. Prior to Windows 2012, using a NIC team on a server also meant enabling protocols like EtherChannel or LACP (also known as 802.1ax or 802.3ad) on network ports.
More information:
NIC teaming configure in Server 2012
http://technet.microsoft.com/en-us/magazine/jj149029.aspx
Hope this helps.
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.

WIndows Server 2012 w/ Hyper V and Windows 7

Similar Messages

Maybe you are looking for