Connecting a Hyper-V instance to my network on Windows 10. Set up External switch in Hyper-V connected to my wireless network adapter that is connected to my LAN. Set up a network adapter in the virtual machine settings connected to the Hyper-V external switch. Started virtual machine. Status is "Undefined network, no Internet". Run trouble shooter inside virtual machine and it keeps returning the same status "...doesn't have a valid IP configuration." DHCP is enabled.

Kevin

We are going to set up a new server to host our VM's. We use Hyper-v and will be using Windows server 2019. The host we have are not clustered. They are set up with the OS on the same hard drive partition are the VMs and configure Raid 6. This server will replace an older one. It will host 6 vm's one of which is a Domain Controller. The new server will be a HP Proliant DL380 Gen10 with 128 GB of RAM and 2 TB of usable space.

How it be better to put the OS on it's own hard drive? If so, should I set the OS hard drive to Raid 1? VM's Hard drive to Raid 5 or 6? This server is located local. I check the drive lights weekly. At what point do I need to up the number of NICs we use? The host servers have 4, we use 2.  

Please let me know if you need additional info.

Hello,

Ive been tasked with finding and reporting all servers running SCCM or Hyper-V hosts.

Is SCCM the best way to find this information or would powershell be a better option?

Any help appreciated.

Thanks!

Hey all,

I am thinking of creating a virtual machine for one of my clients using Hyper-V. It will be a terminal server environment where they will be using a cetralised database and accessing emails and docs. Their documents folder is only around 50GB and they have been getting away with 240GB up until now but I will increase a little when I build it. My question: Is there a need to partition the OS from the data drive.. will this provide any increase in performance or reliability?

FYI We will be running SSD drives with 32GB RAM, 8 vCPU cores which I think is ample.

Dear Experts,

Is there any tutorial or guide in drawing a Hyper-V vSwitch Port Assignment diagram?

I have two 2012 R2 Servers joined to a domain and running HyperV. Both Servers are connected to a SAN via iSCSI and so there are about 8 mapped drives on each server using iSCSI initiators. The previous admin had replication going from Server A to Server B. The VM's have their storage in multiple mapped drives. We upgraded the Backup SAN with bigger drives. The previous Admin setup Replication between the two and then quit.

We failed the HyperV Replication over to the Backup Server and SAN. Everything came up fine, however when we upgraded the Primary SAN and went to set the Replication back up I can't figure out how he did it. When you set the Replication it has a field that says "Specify the default location to store the Replica Files:" under the Authorization and storage section. All of the iSCSI connections have different drive letters.

If I start a replication of VM1 and use it's storage drive letter of H, it comes over fine. But when I try to replicate VM2 with drive letter G, it goes to H as well and the VM's fill up one drive instead of going to their own drive letters and shares.

How can I set this up so they all replicate to their own storage on the iSCSI of the backup Host?

I have a number of Hyper-V servers running Windows 2012 Core which have not been patched in some time.  Can I just patch the Hyper-V hosts or do I need to patch the VM's as well.  

For background, this is a legacy environment and they people that built it have left the company some time ago without any handover.  Windows Update service has been disabled on all the vm's for some reason.  The vm's are a mix of Windows 7 and Windows 2008R2.

Is it just enough to patch the Hyper-V hosts?

I am running Hyper-V  on Svr 2012 R2.
I rebooted the host after installing visual c++ 2015 Redistributable.

when it came back up i saw my VMs stuck in a "Saved" state.
when i try to start the VMs i get the error
"An error occurred while attempting to change the state of virtual machine"
"'Hostname' failed to initialize.

I tried deleting the saved state, but got the same error as noted above.

i check the event viewer and see event IDs 14070 and 15120.


I am also getting error with event ID 1000 as shown below.
Log Name:      Application
Source:        Application Error
Date:          5/13/2019 2:39:48 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HYPERV-HOST.MYDOMAIN
Description:
Faulting application name: vmwp.exe, version: 6.3.9600.19227, time stamp: 0x5c0b5147
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19269, time stamp: 0x5c5e079f
Exception code: 0xe06d7363
Fault offset: 0x0000000000008e6c
Faulting process id: 0x10e4
Faulting application start time: 0x01d509c39fdc6f46
Faulting application path: C:\Windows\System32\vmwp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: ddda0b19-75b6-11e9-80bb-4cd98f608fa5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID …

What is the correct way to licence this Hyper-V situation?

Existing Server 2012 running Hyper-V, licenced. Server has 4 VMs, also licenced. The server is getting old and is going to be made into a replication server for DR purposes.
 
We want to introduce another Hyper-V running Server 2019 and replicate the existing (licenced) VMs onto the new server.

At no point will the VMs be running on more than one server.
 
Do we just need one Server 2019 licence to get the Hyper-V covered?

Hi,

 I have a new server with two INTEL XEON SILVER 4110 @2.1GHZ 8 Core CPUs on MB and like to know how many Windows Server 2019 standard license that I need to purchase.
 I am going to create three virtual machines in Hyper-V server.
 As I understand it, each server license covers two VMs, so I need total two server licenses and end user CALs?

Thanks.