HyperV

Windows 2019 Hyper-V role installation networking issue

On a server that previously had the Hyper-V role installed but since removed. 
Trying to install Hyper-V role again and on reboot no Microsoft Virtual Network Switch Adapter is not created and original nic cannot be accessed or properties viewed. 
No access to Hyper-V Manager.

How do I start figuring this issue out?

Read full post . . . .

Managementos Virtual Adapters do not receive IP address from ICS DHCP Server

Hey,

The goal of the project that I am working on is to create a subnet, with DHCP and NAT, of virtual adapters on the management OS.

(Please do not question why I would do such a thing)

To accomplish this I created a hyper-v Internal Virtual Switch with the command

New-VMSwitch -SwitchName "V Switch" -SwitchType Internal

and I also created multiple virtual adapters connected to that switch.

Add-VMNetworkAdapter -ManagementOS -Name "V Adapter1" -SwitchName "V Switch”
Add-VMNetworkAdapter -ManagementOS -Name "V Adapter2" -SwitchName "V Switch”
Add-VMNetworkAdapter -ManagementOS -Name "V Adapter3" -SwitchName "V Switch”

Then connected a physical adapter (connected to the internet) to the internal virtual switch using Internet connection sharing (ICS). Which turned the internal virtual switch’s adapter into a gateway with Ip address 192.168.137.1. The other adapters, V Adapter1
ect…, should be apart of the subnet and get an Ip address in the range 192.168.137.xxx but they do not get responses from Internet connection sharing’s DHCP server and have APIPA addresses.

I tested to see if I could get an Ip address from a VM attached to the internal virtual switch and the VM was able to get the Ip address 192.168.137.142 from the DHCP server just fine.

I also tested to see if I could get an Ip address using the ManagementOs virtual adapter "V Adapter1" by using a custom protocol driver that spoofed the source mac address (send DHCP discover with different MAC) and set the adapter in promiscuous
mode(Receive messages with MACs other than the adapters own MAC). It was also able to get an Ip address.

Does anyone have any idea why the ManagementOs virtual adapters are not able to get an Ip address from ICS’s DHCP server?

Also forgot to mention that if I set a static Ip address for the ManagementOs virtual adapters they work all perfectly fine. It just seems like the DHCP discover message is ignored by ICS if it is from the ManagementOs virtual adapters.

Any ideas of why this happens or a way to get Ip address for ManagementOs virtual adapters from the ICS DHCP server would be a great help.

Thanks!

Read full post . . . .

Is there a tool that converts VMDK from vSAN to VHD files

Hello, does a tool exist that I can connect my hyperv machine to an existing vmware environment and run it so it can convert the virtual machines into a VHD format. 

I’m being asked this question and unfortunately I don’t know the answer. If it does exist, is there one that runs like vmware converter where it does it on the fly while the machine is on and I simply have to turn the machine on after it is done converting?

Thanks!

Read full post . . . .

Hyper-v replica between hyper-v server 2016 and windows server 2019?

Hi,

Is it possible to have hyper-v replica between hyper-v server 2016 (core) and windows server 2019?

Consider that VM
configuration versions
are the same.

Read full post . . . .

Detecting VM boot to desktop

Hi all,

Looking around I haven’t seen any elegant way to determine that a VM has booted successfully to the desktop (assuming autologon).

Is there a Microsoft approved way of detecting this? Or is it only "check if a service is running", etc semi-hacks?

Thanks for any insights

m

Read full post . . . .

Server problem. ProLiant DL360 Gen9 – VM Windows Server 2016 – Randomly Freezes

Hi.

For some time I have a problem with VM (Windows Server 2016) on the HP Proliant DL360 Gen9 server.

The machine has been freezing for some time. I can’t get to it through RDP, SSH. When I want VM shutdown on Hypervisor, I get the error "VM state does not allow it to close".

I get errors on VM:

DCOM 10010 - "The server did not register in DCOM within the required time."

and

WAS 5010 - "The process serving the application pool did not respond to the ping command. The process identifier.

The problem repeats every few days or once a month.

The problem usually lasts 30 minutes.

I have already tried many solutions. Unfortunately, no result …

Thanks for any help.

Read full post . . . .

WS2106 Evaluation > change host

Hi,

Can i move virtual machine with Windows Server 2016 evaluation (180days) from one Hyper-V host to other?

Will I lost my evaluation time? I had to do lot of changes and installed many programs so I don’t want to do it again, but i have to move this machine to other host.

Read full post . . . .

Connecting Hyper-V servers from Win 2016 console to Win servers Hyper V Cluster 2008

Hello Everyone:

Actually i have a Hyper-v cluster on Windows Server 2012 and i have a server that i use for connecting to this using Hyper-v tools .  Connection in this schema is fine.  Few month we created a new cluster on Windows Server 2016 and in this case
i have other server with win server 2016 that we are using for connecting us to this.  Final idea, would be, this new server allows me connecting to Windows Server 2012 hosts (from first cluster) and Windows Server 2016 (Corresponding new cluster).

Using Failover and trying to connecting me from Win server 2016 to Host on Windows server 2012 (Node or nodes from first cluster).  I obtain the following error:

Actually when i am trying to connect me from Win 2016 (Hyper V Console Server) to Win server 2008 hosts via hyper v Manager and i am not using an administrator user i get the following error

But, if i use a server administrator and i am trying using same console i can to access both servers: Win 2016 and win 2008

So my questions are: 

1) Win 2016 Hyper V Manager Console is not compatible for connecting me old versions hosts?

2) If connection could be possible Would i need a special priviledges?. Because when i trying to do the same connection with an Administrator the error doesn’t appear

Please help me with this

Kind regards

Read full post . . . .

Connecting Hyper-V servers from Win 2016 console to Win servers Hyper V Cluster 2008

Hello Everyone:

Actually i have a Hyper-v cluster on Windows Server 2012 and i have a server that i use for connecting to this using Hyper-v tools .  Connection in this schema is fine.  Few month we created a new cluster on Windows Server 2016 and in this case
i have other server with win server 2016 that we are using for connecting us to this.  Final idea, would be, this new server allows me connecting to Windows Server 2012 hosts (from first cluster) and Windows Server 2016 (Corresponding new cluster).

Using Failover and trying to connecting me from Win server 2016 to Host on Windows server 2012 (Node or nodes from first cluster).  I obtain the following error:

Actually when i am trying to connect me from Win 2016 (Hyper V Console Server) to Win server 2008 hosts via hyper v Manager and i am not using an administrator user i get the following error

But, if i use a server administrator and i am trying using same console i can to access both servers: Win 2016 and win 2008

So my questions are: 

1) Win 2016 Hyper V Manager Console is not compatible for connecting me old versions hosts?

2) If connection could be possible Would i need a special priviledges?. Because when i trying to do the same connection with an Administrator the error doesn’t appear

Please help me with this

Kind regards

Read full post . . . .

Issues connecting to Hyper-V server in WORKGROUP

I might be in the wrong category for this but my issue is really about enabling WinRM so that I can connect to my hyper-v server.

I have set my network connection type to private, but when I try to do winrm quickconfig it reports that it wont work because its public.

PS C:Windowssystem32> Get-NetConnectionProfile                                                                        

Name             : Network
InterfaceAlias   : Ethernet
InterfaceIndex   : 13
NetworkCategory  : Private
IPv4Connectivity : Internet
IPv6Connectivity : NoTraffic

PS C:Windowssystem32> winrm quickconfig                                                                               WinRM service is already running on this machine.
WSManFault
    Message
        ProviderFault
            WSManFault
                Message = WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

Error number:  -2144108183 0x80338169
WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

I’m really stuck on this one. Maybe it would help to connect through a domain but my plan was to run my domain server on this hyper-v host that I’m unable to connect to.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 46 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995