Follow

Hello,

i can not manage my hyper-v 2012 R2 server with a hyper-v manager on 2019 server (gui). (VM on this hyper-v core server)

With a 2012 R2 gui server i could manage my hyper-v 2012 R2 server without a problem.

using a new 2019 gui server i can not connect to my hyper-v server.

then i update the working 2012 R2 gui server to 2019 gui server, and the hyper-v manager has no the same problem when connecting to the hyper-v 2012 R2 core server.

if i connect to server i get the error: (can not insert picture.. )

Hyper-v Manger popup message with red cross.

"An error occurrd while attempting to connect to server

‘fqdn.ofthe.server’. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.

Hyper- encounterd an error trying to access an object on computer ‘fqdn.ofthe.server’ because the object was not found. The object might have been deleted. Verify that the Virtual Machine Management services on the computer is running."

I have disabled the firewall on the 2012 R2 core server, i can open RDP the the server without any problem ..

is there a compatibility issue ?? between hyper-v 2012 R2 and server 2019 gui with hyper-v manager ??

thanks for helping..

Read full post . . . .

Follow

Background:  I host a windows 10 Enterprise for Development on my Windows 10 pro computer.  Both are updated to latest patches using windows update. Configuration version 9.0.  I have 32GB on my physical computer, about half
reserved for the virtual computer.

The purpose is so that my development environment for my client is separate from my personal computer.

Problem:  After a windows update a few months ago the Enhanced Session that can be chosen on the View from the Hyper-V Manager’s Virtual Machine Connection started not functioning. I can view my computer, but not in enhanced mode.

Attempts to correct: I have waited a few additional windows updates, but nothing yet.  Tried to uninstall and reinstall the GUI Management Tools.  I’ve made sure to keep the configuration version to the latest.

Workarounds: The reason I want the enhanced mode is so that printing, copy/paste, and other things to work while connected, so I can use a remote desktop. However, this can be problematic as I’m also using a vpn from the
vm, so opening the computer up so I can remote desktop from outside the network can at times be a pain. Also, when I use a remote desktop, and something happens that I cannot re-connect, the machine gets into a state where the Hyper V Virtual Machine Connection
won’t be able to see the computer.  So, a shut-down, restart is required to again gain access.

Summary:  I’m looking for suggestions on what I could try to easily resolve.  My guess is that if I rebuilt the computer the problem would go away, but that is a large task for something I can work around.

Would someone please turn on the LIGHT?

Read full post . . . .

Follow

So I’m getting contradictory answers regarding installing Windows Server 2019 Standard on bare metal and installing VMs, so I’m also investigating the possibility of using Hyper-V Server 2019 on bare metal and deploying VMs on that.

It’s to my understanding that Hyper-V Server is basically Windows Core with Hyper-V functionality, but I’ve also heard there are ways of adding GUI components onto it? Does that include the Hyper-V management module? Anyone have any idea of the general pros
and cons that come from running Hyper-V 2019 instead of Windows 2019 with Hyper-V?

Otherwise, how much of a licensing apocalypse would occur if we had a single license of Windows Server 2019 standard and it was running on both bare metal (strictly in a Hyper-V capacity) and two VMs each running Windows Server 2019? Would I use the provided
license key on the server and AVMAs on the VMs? The provided license key on all three systems? Any help would be appreciated on any of these subjects.

Read full post . . . .

Follow

Yesterday one of our VM file-servers crashed some time between 19.00 and 22.15 and any file changes/ additions for the entire day on this server is gone. We know that some files were saved on the file-shares just around 19.00, so in my mind these files should
be available, but no. - There are no event-log entires from 11.00 (mid day) and this morning when I restarted the server 7.34)

Could it be that every transaction to this server the entire day were done in a memory/ temp file and never committed into the VM harddisk file and these files were lost when the server crashed? - It is the only logic that come to my mind. But how can this
happen? - There is no checkpoint on the server.

It is just as if the entire server was restored one day back or the day never happened.?!? (checked my restore-logs and that is not it 🙂 )

Note to mention.

Our Veeam backup start at 22.00 and failed for this server, then started automatically again at 22.30 with a success (allthough the server had Repair startup this morning). But everything is one day old in this backup.

Read full post . . . .

Follow

Hi, I have a dedicated windows 2k16 std hyper-v server that replicates to another hyperv server using standard windows replication. We have 9 VMs. I wanted to check the replication status from hyper-v manager and I saw that for 2 servers, the status was
"planned - reference point creation" (translated from french).

Now all VMs are configured to replicate every 15 minutes with 4 snapshots per hour, all configured the same way. If I check in the hyperv console, like all other VMs, every 15 minutes I see that those 2 servers are replicating successfully, showing in the
status. Looking at "view replication status", all ok, green checkmark, last updated a couple of minutes ago. So all seems fine, but I was wondering why those 2 VMs are showing this in the status column in hyperv manager and how I can remove this.

Hope it’s clear.

Thanks

Read full post . . . .

Follow

Hi, I have a dedicated windows 2k16 std hyper-v server that replicates to another hyperv server using standard windows replication. We have 9 VMs. I wanted to check the replication status from hyper-v manager and I saw that for 2 servers, the status was
"planned - reference point creation" (translated from french).

Now all VMs are configured to replicate every 15 minutes with 4 snapshots per hour, all configured the same way. If I check in the hyperv console, like all other VMs, every 15 minutes I see that those 2 servers are replicating successfully, showing in the
status. Looking at "view replication status", all ok, green checkmark, last updated a couple of minutes ago. So all seems fine, but I was wondering why those 2 VMs are showing this in the status column in hyperv manager and how I can remove this.

Hope it’s clear.

Thanks

Read full post . . . .