Hyper-V virtual network switch disconnects host machines network connection

When creating an external virtual switch for my Hyper-V machine, my hosts connection is lost immediately when applying the setting and is restored immediately after deleting the virtual switch.
Am I doing something wrong? It seemed pretty straightforward and I've followed steps that others have outlined to create the virtual switch. 

When I checked, "Allow management operating systems to share this network adapter", and checked "Enable virtual LAN identification for management operating systems" another SNAFU happened. I found in network connections, Ethernet properties,
my "Internet protocol version 4 unchecked, and Hyper-V Extensible virtual switch checked, and I no longer had network access.  Again I had to remove my hyper-v external switch in hyper-v manager.  I guess I could try using my WIFI as the switch,
but getting hyper-v Windows Server 2012 R2 has been a real problem.  
I did the following steps:
To install and configure a virtual machine, complete the following steps:
1. Start Hyper-V Manager by clicking Start, Administrative Tools, Hyper-V Manager.
2. In Hyper-V Manager, right-click the server node in the left pane, point to New, and then select Virtual Machine. This starts the New Virtual Machine Wizard. Click Next.
3. In the Name text box, enter a name for the virtual machine, such as AppServer02.
4. By default, the virtual machine data is stored on the system disk. To select a different location, select the Store The Virtual Machine In A Different Location check box, click Browse,
and then use the Select Folder dialog box to select a save location. Click Next.
5. On the Assign Memory page, specify the amount of memory to allocate to the virtual machine. In most cases, you should reserve at least the minimum amount of memory recommended for the
operating system you plan to install. Click Next. 6.
On the Configure Networking page, use the Connection list to select a network adapter to use. Each new virtual machine includes a network adapter, and you can configure the adapter to use an available virtual network for communicating with other
computers. Click Next. 7.
On the Connect Virtual Hard Disk page, use the options provided to name and create a virtual hard disk for the virtual machine. Each virtual machine requires a virtual hard disk so that you can install an operating system and required applications.
Click Next. 8. On the Installation Options page, select Install An Operating System From A Boot CD/DVD-ROM. If you have physical distribution media, insert the distribution media, and then
specify the CD/DVD drive to use. If you want to install from an .iso image, select Image File, click Browse, and then use the Open dialog box to select the image file to use.
9. Click Next, and then click Finish.
10. In Hyper-V Manager, right-click the name of the virtual machine, and then click Connect.
11. In the Virtual Machine Connection window, click Start. After the virtual machine is initialized, the operating system installation should start automatically. Continue with the operating
system installation as you normally would.
It installed and booted, came up to a blue screen asking me to hit Ctrl-Alt-Del to logon, and when I did, it gave the selection to switch user, task manager, ect...  didn't complete the install could not logon - did not have access to the internet to
logon with my Microsoft Account.
 

Similar Messages

  • Windows 2012 Hyper-V Virtual SAN Switch Best Practice

     I have a four node cluster running W2012 Datacenter edition on each.  All systems have Emulex HBA compatible with Hyper-V and Virtual SAN technology. The hosts are connected to a Brocade SAN Switch with NPIV Enabled. I've
    created a Virtual SAN on each host. The vSAN is connected to 2 physical HBA. Each HBA is connected to a different physical SAN Switch.
    I have some questions about the best practice of the whole system.
    1. Do I have to create a vSAN per physical HBA ? Or create one vSAN that include 2 HBA ?
    2. Add 2 virtual HBA per VM to have fault tolerance ? Or one virtual HBA that is connected to a vSAN with 2 HBAs ?
    3.  Do I have to create a virtual port for each VM on the HBA Gui (OCManager) ?
    Any best pratice or advice ?
    Thanks

    Hi,
    first you will do almost the same as you do on a physical SAN, normally you build 2 Fabrics right ?
    In Case you have that in place you will configure also 2 vSANs to build up your 2 seperate ways/pathes.
    Here my top links for that Topic
    Hyper-V Virtual Fibre Channel Design Guide
    http://blogs.technet.com/b/privatecloud/archive/2013/07/23/hyper-v-virtual-fibre-channel-design-guide.aspx
    Very Good Blog with all the Scenarios you can have, sinlge Fabric to Multi ......
    Here the TechNet Info around "Hyper-V Virtual Fibre Channel Overview"
    http://technet.microsoft.com/en-us/library/hh831413.aspx
    and the "Implement Hyper-V Virtual Fibre Channel"
    http://technet.microsoft.com/en-us/library/dn551169.aspx
    A good Advice is also to install this Hotfix -
    http://support.microsoft.com/kb/2894032/en-us
    It is a sexy feature but if one point in the chain is doing wrong things with your NPIV Packets you are lost, so in my personal view you miss the for me most inportant point why i do Hyper-V, the Separation of HW and Software :-)
    One Problem i had once was after live Migration of a VM with configured vFC the Destination Host lost there FC Connection, but only if the Host have been one SAN Hop away from the HP Storage , was a HP Driver Problem, used the original Qlogic Driver and
    everything was fine, so same as with some HP Networking Driver for Broadcom, do not trust every update, test it before puting it in production.
    Hope that helps ?
    Udo

  • IPv6 Network Flood with Wireless Hyper-V Virtual Network

    Recently, on our core switch (also our layer 3 router) we regularly see a high cpu load. This cpu load is the cause of packet loss and bad connections. This is happening for almost two weeks now.
    Network inspection shows us that there is a flood of IPv6 Neighbor Advertisements originating from what seems the same IPv6 Address but from different Hardware (MAC) addresses. In each second there are up to a 1500 packets per second advertising
    the same IPv6 address. See below for more details about these packets.
    Tracing the MAC addresses to their owner learns that all clients are using Windows 8 with Hyper-V and that they have an External Virtual Network bound to their Wireless/WiFi Network Adapter. Removing this virtual network stops sending
    those packets. Because multiple hosts are involved it may be necessary to remove this network on all of these hosts.
    As is visible in the following packet dump this is an unsolicited neighbor advertisements, resulting in an update in the neighbor table on our IPv6 router. These updates are probably the course of the high cpu load.
      Frame: Number = 188594, Captured Frame Length = 86, MediaType = ETHERNET
    + Ethernet: Etype = IPv6,DestinationAddress:[33-33-00-00-00-01],SourceAddress:[00-24-D7-76-C4-68]
    - Ipv6: Next Protocol = ICMPv6, Payload Length = 32
      + Versions: IPv6, Internet Protocol, DSCP 0
        PayloadLength: 32 (0x20)
        NextProtocol: ICMPv6, 58(0x3a)
        HopLimit: 255 (0xFF)
        SourceAddress: FE80:0:0:0:6F7:E4FF:FE4A:2267
        DestinationAddress:
    FF02:0:0:0:0:0:0:1
    - Icmpv6: Neighbor Advertisement, Target = FD00:4953:4E4C:20:6F7:E4FF:FE4A:2267
        MessageType: Neighbor Advertisement, 136(0x88)
        Code: 0 (0x0)
        Checksum: 3593 (0xE09)
      - NeighborAdvertisementFlag: 536870912 (0x20000000)
         R:   (0...............................) Not router
         S:   (.0..............................) Not solicited
    O:   (..1.............................) Override
         Rsv: (...00000000000000000000000000000)
        TargetAddress:
    FD00:4953:4E4C:20:6F7:E4FF:FE4A:2267
      - TargetLinkLayerAddress:
         Type: Target Link-Layer Address, 2(0x2)
         Length: 1, in unit of 8 octets
         Address:
    00-24-D7-76-C4-68
    Because the target address is the same in all packets but the MAC address changes, it seems that there is something on the hosts that is forwarding/proxying these packets (and only those packets) back to the network it came from, but only
    after changing the targetlinklayeraddress in the advertisement. This process is described in
    RFC4389.
    One host with this problem on the network will not resolve in a flood. Only when more hosts with this issue are active the flood occurs. It seems that two or more hosts are required to magnify the packets send by the others.
    Hyper-V on Windows 8 makes use of a Network Bridge in software to enable the use of wireless network adapters. Is this the cause of all those packets?
    Some of the hosts also had Windows Phone 8 SDK installed. The installation of this SDK enables some networks in Hyper-V. Maybe some configuration change is made enabling the proxying of those packets back to the network they came from?
    After removing the SDK the hosts are still transmitting too much packets.
    The first occurrence of this flood was on the day after Microsoft’s update Tuesday. Is it possible that one of the updates may be the cause of this? There is one mayor update
    KB2770917 which includes updates to DHCPv6 and NDIS library’s. Again, removing this update does not solves the problem.
    Updating our switch/router to a higher level of firmware may lessen the impact, this is something I can try. But it shall not solve the problem, the switch is not the source of the packets.
    Hopefully somebody recognizes this issue. All ideas are welcome.
    Regards,
    Martijn

    Hello today we have a little breakthrough. Our Accesspoints are connected to a Cisco C2960S Switch. We have enabled storm control on the switches. This blocks only the multicast packets that were flooding the wireless and the wired network.
    We determined this using PRTG snmpv2 connection to the Cisco. Whenever the network flooding was occurring the packets per seconds went in the thousands. We now have put the following code on the Gbit interface: (The last line with the storm-control setting
    fixed flooding the network at least partially because the multicast packets cannot leave the Accesspoint to travel to other accesspoints or to wired devices.)
    Hope this helps others as well.
    interface GigabitEthernet1/0/7
     description AP06
     switchport trunk allowed vlan 1-99,101-4094
     switchport mode trunk
     speed 1000
     duplex full
     storm-control multicast level pps 200 50
    end

  • Ping and Hyper-V virtual internal switch

    Whenever I create a Hyper-V virtual switch (internal), ping binds to the IP address of the internal network switch instead of the IP address assigned to physical adapter. How do I prevent this from happening?

    This has to do with network binding.
    You can change the network bindings using the following steps
    You must be logged on as an administrator to perform these steps.
    Open Network Connections by clicking the Start button ,
    and then clicking Control Panel. In the search box, typeadapter,
    and then, under Network and Sharing Center, click View network connections.
    Press the Alt key, click Advanced, and then click Advanced
    Settings.  If you're prompted
    for an administrator password or confirmation, type the password or provide confirmation.
    Click the Adapters and Bindings tab, and then, under Connections,
    click the connection you want to modify.
    Under Bindings for‌ connection name, select the protocol that you want to move up or down
    in the list, click the up or down arrow button ( or ),
    and then click OK.
    From: http://windows.microsoft.com/en-us/windows/change-network-protocol-bindings-order#1TC=windows-7

  • Windows 7 Hyper V Guest Network Connectivity

    Hello (I posted this question over in the Microsoft VM Converter forum, not sure if that's the right place)
    I am using Hyper-V Manager in Server 2012 R2 and have created guest vm's that are Windows 8 and Windows 10.  All work fine and can connect to the network and have internet access (this is a dev environment).  However, when I create a Windows
    7 guest, it does not pickup an IP from DHCP and I cannot get it to connect at all.  Ive tried the following:
    1.  Installed Integration Services setup.
    2.  Used both legacy and non legacy network adapters.
    3.  Uninstalled/reinstalled HyperV network adapter in guest OS
    4.  Disabled IPv6 in guest OS.
    5.  Set static IP address in guest OS and reserved in DNS.
    6.  Manually assigned DNS server in guest OS.
    I then tried to create a guest Win7 OS on my Windows 8.1 host and experience the same issue, no connectivity.  In both instances I get a 169.254.x.x. address.  Is this some issue with Win7 and the latest Hyper-V version?  As I mentioned Windows
    8, 8.1, and 10 work just fine. 
    Thanks.

    Hi Marshal21,
    >>However, when I create a Windows 7 guest, it does not pickup an IP from DHCP and I cannot get it to connect at all.
    In vm settings please ensure that the Windows7 VM connects to the correct external virtual switch .
    If there is VLAN setting you also need to check VLan in VM settings .
    Also you may try to download a new Win7 ISO and test again.
    Best Regards
    Elton Ji
    If it is not the answer , please unmark it
    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 to connect USB external Harddisk to Hyper-v virtual machine

    Hi,
    We are running hyper-v server 2008 R2, we have external USB harddisk connected in hyper-v Manager, we are not able connect this USB to virtual machine.. is this option is available in hyper-v? if no is there any document from microsoft stating the same?
    Regards
    Asha

    Hi,
    Unfortunately, USB is not supported on a Hyper-V virtual machine. You can perform the following suggestions:
    1. Offline the USB hard disk on the Hyper-V host machine and connect it to the virtual machine as a pass-through disk(if the USB hard disk is support)
    For more information, you can refer to:
    Configuring Pass-through Disks in Hyper-V
    http://blogs.technet.com/b/askcore/archive/2008/10/24/configuring-pass-through-disks-in-hyper-v.aspx
    2. You can also use some USB over Ethernet application.
    Best Regards,
    Vincent Hu

  • 6 instances of broken Hyper-V Virtual Switch Extension Adapters.

    Hi. I am unable to create a hyper-v virtual network switch (post Windows 8.1 Update installation).  Every time I attempt it, a new corrupted adapter is created and an error is reported.  They all report the same issue:   Code 10
    Operation Failed.    I have tried the following:
    1.  Right click "uninstall".  No error but the adapter is not removed.
    2.  No virtual adapters are currently visible in Hyper-V Management studio .... but not from the lack of trying.  They fail to create and cause the Hyper-V management service to abort.
    3.  Tried to uninstall Hyper-V but it won't uninstall.  Also does a restore at the end.
    4.  Run numerous Microsoft utilities (SFC, FixIt, etc).
    OS was recently updated to Windows 8.1 Update (64bit).  My problems started with the rather painful upgrade.   Also unable to re-install the Cisco VPN after uninstalling to complete the upgrade.  Installing the Cicso VPN client is
    my ultimate goal but was going to run it in a VM if necessary since I couldn't install it.  Hence the Hyper-V cluster.  Any help would be greatly appreciated.  I have spend a couple of weeks on the Upgrade and trying to get my computer
    working again with no luck.  Thank you!

    Hi,
    Was your issue resolved?
    If yes, we will archive this thread temporarily.
    If no, please reply and tell us the current situation.
    If you have any other question, feel free to contact us. We will try our best to help you.
    Karen Hu
    TechNet Community Support

  • Adding a second ExpressRoute connection to an Azure virtual network with networkconfig.xml

    We are trying to add a second ExpressRoute connection to a vNet in an Azure subscription. We have already successfully completed the connection to our first ExpressRoute (we are using the Exchange Provider method) using a combination of the virtual network
    GUI and powershell cmdlet tools.
    However... the GUI only supports adding one site-to-site VPN via ExpressRoute.
    The method for adding a secondary site-to-site connection is to export the network configuration (via the Azure portal) and edit the resulting NetworkConfig.xml file - and then re-import this via the portal.
    All good, in theory.
    The NetworkConfig.xml file exported from the gui:
    <Gateway>
    <ConnectionsToLocalNetwork>
     <LocalNetworkSiteRef name="XXXX">
      <Connection type="Dedicated" />
     </LocalNetworkSiteRef>
    </ConnectionsToLocalNetwork>
    </Gateway>
    In conjunction with MS Support (with whom we are still engaged), we determined the following should work:
    <Gateway>
    <ConnectionsToLocalNetwork>
     <LocalNetworkSiteRef name="XXXX">
      <Connection type="Dedicated" />
     </LocalNetworkSiteRef>
     <LocalNetworkSiteRef name="YYYY">
      <Connection type="Dedicated" />
     </LocalNetworkSiteRef>
    </ConnectionsToLocalNetwork>
    </Gateway>
    However, attempting to import this generates the following error message:
        "The gateway in virtual network site XXX-XXX-XX referenced multiple local network sites and uses a connection type different than 'IPsec' for at least one of the connections. If a gateway references more than one local network site, the connection
    type to all local network sites must be 'IPsec'. 'IPsec' is the default connection type."
    This appears to suggest multiple ExpressRoute connections on a single vNet are not supported, which would be contrary to the MS FAQ here:
        Can I have one virtual network connected to more than one ExpressRoute circuit?
        Yes. You can link a single virtual network with up to 4 ExpressRoute circuits. All ExpressRoute circuits must be in the same continent. They can be ordered through different service providers and in different locations.
    (from <link to ms site snipped>)
    Does anyone have any idea how we should proceed?
    Thanks

    Hi Rich,
    It looks like you are trying to combine S2S and ExpressRoute. Although at some point in the future we will have the ability to have them coexist, you cannot do so today. Therefore, you must delete the S2S gateways and create ExpressRoute gateways.
    You could refer the following link for details:
    https://msdn.microsoft.com/en-us/library/azure/dn606292.aspx
    Can I use site-to-site and point-to-site connectivity for virtual networks in conjunction with ExpressRoute?
    No. A virtual network connected to an ExpressRoute circuit cannot be used with site-to-site and point-to-site.
    Regards,
    Malar.

  • Loss of network connectivity at random times to guests and now hosts Server 2012 R2 Hyper-v on Dell R620...Guests virtual disks reside on a NAS.

    We have set up 2 Hyper-v environments (Server 2012 R2 fully updated) on Dell R620's. The guest machines are configured do that they reside on a NAS (also a Dell R620 with server 2012). We are having an issue on both the environments where the guests will
    lose network connectivity. The servers ran well for about 4 weeks and recently the guests started having issues and we have even had to reboot the host due to network connectivity problems.
    We have 4 virtual switches set up. 1 connected to its own NIC. 1 for management and the 3 others for guests.
    The 3 for guests are not configured to allow host OS sharing.
    We do not have IP addresses on the NICS for the guests. Only on the management port. (all 1 GB NICS)
    We have updated the firmware and drivers for the standard Broadcom Netxtreme cards.
    We do not have Jumbo frames enabled because of some issues with switching compatability.
    I've seen articles recommending to turn off TCP offloading and to disable virtual machine queues. Is this best practice?
    Any thoughts of where I might look to help diagnose this issue?

    Hi ,
    "1 connected to its own NIC. 1 for management and the 3 others for guests."
    Also you mentioned that : " is only hosting these 24 VMs ".
    First please try to disable the RSS in the property of the NICs for guests .
    Then run powershell " Get-NetAdapterVMQ " to check the parameter "NumberOfReceiveQueues"  (NumberOfReceiveQueues – The number of queues that the NIC has available to use and assign to VMs,
    the host and a default queue) .
    If I understand correctly ,when you enable VMQ  the number of connected VMs on that NIC should not be more than the value of  "NumberOfReceiveQueues" -2 .
    For details please refer to following link:
    http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-1-of-3.aspx
    Hope this helps
    Best Regards
    Elton Ji
    If it is not the answer please unmark it to continue
    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.

  • Routing of Network Traffic Between VLANs on a Hyper-V Virtual Switch

    I am trying to discover how network traffic generated by reads and writes to RDVH User Profile Disks is routed through my network.  I have a pool of Hyper-V
    desktop vm’s in their own VLAN (vlan1) with their own NIC bound to a Hyper-V Virtual Switch. On the same server I have another management NIC for the OS on a different VLAN (vlan2) and finally on another server I have a virtual machine which hosts the User
    Profile Disks. The VM that hosts the User Profile Disks is on the same VLAN as the management NIC for the OS (vlan2).
    When tracing the flow of network traffic to and from the User Profile Disk VM it all comes through the vlan2 NIC on the server where the virtual
    desktop VMs reside and nothing comes through the vlan1 NIC on this server.  I would have expected the traffic to the virtual desktop VMs to come in  through the desktop VMs VLAN NIC (vlan1).
    This leads me to two possibilities as to how the desktop vm’s on vlan1 get their  data to and from the User Pofile Disk vm on vlan2 without routing.
    The desktop vm’s Hyper-V Virtual Switch automatically routes the User Profile Disk traffic from vlan1 to vlan2 internally using a virtual switch learning algorithm
    Hyper-V itself handles all reads and writes to the User Profile Disks and since that is using the management NIC for the OS it is already on vlan2 and so the network traffic never leaves vlan2.
    Any comments on the reason for traffic taking the path it does (as outlined above) as opposed to being layer-3 routed from VLAN1 to VLAN2?

    Thanks for your reply Brian. I think your last paragraph above is what I have set up:
    If you simply forward one VLAN to one physical NIC and the VMS on the corresponding External Virtual Switch simply end up on that VLAN without Hyper-V doing anything at all - but this dedicats one physical NIC per VLAN.
    The Virtual Machines NIC that the vSwitch is patched to and the NIC for the OS are on different VLANS (both NICs are plugged into un-tagged ports on my switch).
    The vNICs on the VM's are not tagged to a VLAN (The VLAN ID\ 'Enable virtual LAN identification' box is unticked)
    My vSwitch is set up as connected to 'External Network' and isnt shared with the management network.
    What I am trying to get at is how would network traffic on the VLAN my vm's are on get to the VLAN that the NIC for the OS is on without going through the router (even though a routable path is available)  ?
    Is it possible the 'learning algorithm' referneced in a Technet article below is involved here (sorry I cant post links)?
    For the virtual machine to communicate with the management operating system, there are two options. One option is to route the network packet through the physical network adapter and out to the physical network, which then returns the packet back to
    the server running Hyper-V using the second physical network adapter. Another option is to route the network packet through the virtual network, which is more efficient. The option selected is determined by the virtual network. The virtual network includes
    a learning algorithm, which determines the most efficient port to direct traffic to and will send the network packet to that port. Until that determination is made by the virtual network, network packets are sent out to all virtual ports.
    Thanks,
    Andrew

  • Hyper V virtual machine randomly loses network connectivity

    I have an extremely odd issue happening on one of my Hyper-V virtual machines.  For no apparent reason and completely sporadically my virtual machine will lose all network connectivity.  It is a linux Vyatta firewall image.  Digging through
    the logs shows nothing at all when the machine actually goes offline, but when the machine starts back up I just get a Warning stating the network driver on my virtual machine loaded but has a different version from the server.  Server Version 3.2 Client
    version 0.2
    I've ran the integrated services setup disk and nothing has fixed this.  When the VM loses connectivity it is for no apparent reason, sometimes at 1am sometimes at noon, just happens.  The only solution is to reboot the VM to bring it back online. 
    Has anyone else seen this or know of a fix for it?  Its starting to slowly drive me insane! 
    Hyper V Server - Windows Server 2008 R2 - Hyper V Manager Version 6.1.7601.17514
    VM - Linux Vyatta Core 6.3

    I tried downloading new integrated services disk setup for linux, but Vyatta wouldn't work with it so I was kind of stuck there.  And not sure where you are talking about changing NIC to legacy at.  I did disable some TCP chimpney settings as
    per an article I found, but not sure if it will fix it or not.  Sometimes the machine will stay on for a month before losing network connection and sometimes it comes in spurts and happens like 3-4 times over a couple days.  Its really odd

  • Server 2012 R2 Hyper-V Host Loses Network Connectivity

    Here's the scenario...
    We have two 2012 R2 Hyper-V hosts (VM1 and VM2) in a cluster that have 8 virtual machines that live on them. The servers are each utilizing three network connections that are teamed (Switch Independent, Address Hash).  They all go to the same switch.
    Three nights ago at approximately 11:30 PM VM2 lost network connectivity. The server was up it was just inaccessible from the network. I could not ping in or out from it, no internet connection, yet the network connection icon did not show that it was
    disconnected.
    Two nights ago we had no issues.
    Last night, same thing happened at 11:30 PM. VM2 loses it network connection.
    The only thing that seems to fix the issue is a reboot. Once the server comes back up everything is back to normal.
    Anyone have any idea what is happening here? I do not see anything that sticks out in the logs that could point me in the right direction....

    Hi Sir,
    Based on my experience , first you may need to keep the physical NIC driver up-to-date .
    Also please check if there is "VMQ"/"virtual machine queue" property in advanced properties of physical NICs:
    If yes please disable it for each team member then check the result .
    Best Regards,
    Elton Ji
    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 Subscriber Support, contact [email protected] .

  • The hyper-v virtual machine management service encountered an unexpected error logon failure 0x80070569

    I dont understand why Microsoft people can't make things simpler
    They are LITERALLY MOTHER F%^%RS
    Bill Gate and his team need to learn hot to F^&&IN make things.

    I agree, the use of profanity is completely unnecessary, we've all been in the stressful situation before, it still doesn't call for it.
    The network you're receiving an APIPA IP on, is it the virtual switch you setup when adding the Hyper-V role?  If so you can get the warnings to go away and subsequently hide the adapter by unchecking the 'Allow host to manage this adapter' setting
    in the virtual network manager of Hyper-V manager on each node.
    Tim is also right, while disk resources are only owned by one node, you'll see the mount points for CSVs located under C:\ClusterStorage.
    More importantly, you're logon issue sounds directly related to group policy.  I had the same problem moving to Server 2012.  Yes, it's an annoying process but in the end you will have a working cluster.  I did the following steps:
    1. Install 'Group Policy Manager' on one of the nodes in your Hyper-V cluster
    2. Log on to the node you installed it on with a Domain Admin or appropriately endowed account that can edit the GPO relating to 'Logon as a service right'
    3. Edit the GPO where you specify who can logon as a server, OR if you don't have one, make a new one and link it to the OU with the Hyper-V nodes
    4. Add permission to that right for 'NT Virtual Machine\Virtual Machine Group', save and exit
    5. As an optional step I would reboot the nodes so you make sure they get it
    The problem here is that security group ONLY exists on servers that have Hyper-V installed on them.  If you add the group on a machine that has it to the GPO, the SID for the group is saved and each Hyper-V host will know what group that is.  The
    problem you're having right now is most likely related to a GPO changing 'Logon as a service right' to your needs and setup in Group Policy.  When a Hyper-V node starts up, it automatically adds the right for that group to the local security policy, however,
    group policy's auto refresh will remove it after a certain amount of time.

  • Hyper-V creating external Vswitch disconnects from host

    Hello,
    I have a Windows 2012 R2 Server running HyperV. The moment i create a external Vswitch from the Virtual Switch Manager, i loose connectivity from the host machine. I then have to manually go back and delete the vswitch to have connectivity again.  Is
    this a bug ? Couldnt find any hot fix for it.  What am i missing ?   The network connection for the vswitch is out of a DHCP scope block.

    Hi Neeraj,
    This is by default. When you are creating vswitch, it gives a message that your host will be disconnected. Basically, it binds to a physical NIC and creates a vNIC in your host server. When this is done, it removes the IP address which you had set on
    physical NIC. You need to connect it via ILO or some other method, then perform this task. Also you need to assign IP to vNIC after creating vswitch.
    Thanks,
    Umesh.S.K

  • How to transfer files from virtual machine to host machine

    Hello, 
    I want to know how to copy files from virtual machine o host machine while the virtual machine running. I can't share files from virtual machine because i am just studying for mcsa in company computer. I can't connect my virtual machine to same network so
    i'm using a different ip range and i created a internal network switch for my virtual machines in hyper-v. Please give me a best solution for my studies.
    Regards,
    Ashane Deshapriya.
    Ashane Deshapriya ( MCP )

    Finally I got the solution...
    Here is how you can share files between a Hyper-V host and any virtual machines running on that host.
    If you've used Microsoft Virtual PC or Microsoft Virtual Server, you'll have enjoyed the fact that you can copy and paste between a virtual machine and those platforms. This doesn’t work with Hyper-V however—you can't copy/paste between a VM and the Hyper-V
    host.
    The workaround is to do the following:
    1. On your Hyper-V host, create a shared folder and assign Change permission to Everyone.
    2. On the virtual machine running on the host, open the Network and Sharing Center and enable File and Printer Sharing.
    3. On the virtual machine, click Start and type \\host_name\share_name where host_name is the name of your Hyper-V host and share_name is the name of the share you created.
    4. Press ENTER and an Explorer window will open in the VM showing the contents of the shared folder on the host.
    5. You can now copy files from the VM to the host and vice versa as needed.
    Regards.
    Ashane Deshapriya ( MCP )

Maybe you are looking for