Follow

Dear Tech Net team, 

I have 2 node cluster Hyper-V where i have 14 VM’s are running. recently i have configured Hyper-V replication on the cluster and replicated VM’s to replica server and most of servers are replicated successfully. 

However, am facing issue with two servers while doing initial replica, the replication is enabled on the VM and replcated copy of VM created on replica server, but replication folder [initial replica via external media ] not creating any VHD files and not creating
any copy of VM in order to import on Replica VM. 

All other VM i did same scenario via External media, and it was successfully but only two servers having this issue. 
Hyper-Replication VM health report shows the error : General access denied error (0x80070005). (Virtual machine ID 5

If anyone face the same issue, or knows the fix for this kindly advise. 

Thank you in advance
The VM HDD Size is 640  GB, 

Faris

Read full post . . . .

Follow

Hi, I am new to this and am trying to set up my R610 with Hyper-v server 2019 Core.  I have followed many steps but am getting hung up on the Set-Item for trustedhost.. below is my error. I am able to ping my server ip of 102.168.13.100 but get the
CredSSP error from my client. I do not have a domain so I am using a "WorkGroup".. Help?

—————————-

PS C:Windowssystem32> Set-Item WSMan:localhostClientTrustedHosts "R610VIRT"

Start WinRM Service
WinRM service is not started currently. Running this command will start the WinRM service.

Do you want to continue?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"):

WinRM Security Configuration.
This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
authenticated. The client might send credential information to these computers. Are you sure that you want to modify
this list?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"):

Set-Item : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
At line:1 char:1
+ Set-Item WSMan:localhostClientTrustedHosts "R610VIRT"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-Item], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.SetItemCommand

—————————-

This is what I have on my Server

——————-

Status   Name               DisplayName
——   —-               ———-
Running  winrm              Windows Remote Management (WS-Manag…

—————————

Read full post . . . .

Follow

Summary - When draining a Server 2016 Hyper-V Cluster node, randomly certain VMs will be left on the source node, even though they get properly moved to the destination node and this is reflected in the Failover Manager.

Long version:

Greetings!  We have run into a rather unique (it appears) situation with our Hyper-V 2016 Failover Cluster. 
Whenever we do maintenance, we follow the standard process of Draining the node, which moves all of the Storage and VM resources over to the other functional nodes. 
While the Drain process appears to complete as far as the Cluster is concerned (no errors or warning generated), we noticed that randomly certain VMs were being left on the drained node, but they also existed at the destination node where the cluster
now says they should be located.   It only affects VMs that are in an Offline state.  
This issue is particularly bad on our Replica/Testing Cluster, where MOST of the VMs are not running (because they are replicas), but it has also occurred on our Primary cluster as well with the few VMs that are not running on there. 
The biggest issue this situation causes is that because the VMs exist on both nodes at the same time, they can both attempt to do their replication process and usually end up screwing it up, requiring a Resynch of the entire VM to the replica.

The issue occurs with VMs both with and without replication enabled. When our clusters nodes were still running Server 2012 R2, this issue never occurred. 
We migrated to 2016 late last year and this issue started occurring periodically during maintenance windows.

At this point, I am just curious if anyone else has ever ran across this or has any thoughts.  
Other than this issue, the nodes and VMs run fine.

Thanks for your time!

Read full post . . . .

Follow

Hi all,

I’ve been searching all night and haven’t found anything yet. So I’ll post my question here.

I work with a VM which has my company VPN Client installed from where go log in into my Office Computer.

Since the VPN Client has no split tunneling enabled (company Policy) I can’t use any other network resource except for the company resources.

Since I still need my S4B locally, because Audio is also restricted, I need to start my S4B Client locally, so far so good everything works. But what annoys me so much is that I need to minimize my vmconnect session all the time i need to use the local S4b
Client.

That’s when I tried to configure the vm connect client to use only 2 Monitors instead of all 3.
This would be possible if the connection is an RDP Connection.
MSTSC Config for that:

use multimon:i:1
selectedmonitors:s:1,2

I can’t find any reference for the vmconnect.config files that are stored in C:UsersuserAppDataRoamingMicrosoftWindowsHyper-VClient1.0

Can you help me if that?

Or even better do you know the config option for multimonitor for vmconnect?

Mycurrent vmconnect rdp file:

   
       
            False
       
       
            True
       
       
            True
       
       
            True
       
       
            AUDIO_MODE_REDIRECT
       
       
            False
       
       
           
       
       
            W10-Work
       
       
            True
       
   

Or can I create a connection to the hyper-v console with mstsc?

If you can help me with that you would be my hero 🙂

Best,
Kim

Read full post . . . .

Follow

Hi 

I can’t remove the hyper-v server 2012 role that show error" The request to add or remove feature on the specified server failed. Teomovel of one or more role, role services, or features failed Access is denied. Error: 0x080070005."

Please see the problem as capture screen.

Could you please advice how to fix issue?

Thank you

Arkom

Read full post . . . .

Follow

Trying to install Kali 2020.0, using Hyper-V in Windows 10 Pro, Error from Kali was Installation Error, Installation Step Failed. Hyper-V options are enabled and turned on in Windows features, I ran an elevated cmd ‘systeminfo’ and error listed with "Hyper-V
requirements" was "A hypervisor has been detected. Features required for Hyper-V will not be displayed." Any thoughts or ideas are greatly appreciated.

Read full post . . . .

Follow

We currently have a 5 node 2016 Hyper-V Cluster using a dual 10GB Team for Management, Cluster and Live Migration virtual adapters. We need to change the IP, subnet and VLAN on the management vNIC for the nodes. The cluster and LM nics are staying the same.

Is the process similar to the answer on this post? https://social.technet.microsoft.com/Forums/en-US/b229869f-b373-40ca-9e2e-bd276aebd12a/change-subnet-mask-for-2012r2-hyperv-cluster?forum=winserverhyperv

It looks like this is an all or nothing change? Once we start, we would need to complete all the hosts and then set the CNO to use the new network? 

Read full post . . . .

Follow

M-L-S

Read full post . . . .

Follow

Hi,

Our main host server got hit with encryption ransomware. We have a replica of the VMs, on our backup server. We paused replication. 
We have not turned started the replica VM’s since the ransomware attack, as we were unsure whether they were infected but we believe they probably aren’t.
 The backup server has ransomware aware protection and is clear from malware, as are all the endpoints on the LAN.  The previously infected (defunct) server is disconnected from the LAN.     

The backup 2012R2 server has been running clean for a few weeks albeit failover DHCP doesn’t function on the backup server which wants authority from the downed VM that holds the 5 attributes revealed by netdom /query FSMO schema master,
domain naming master, PDC, RID pool manager, Infrastructure master. 
The DHCP service is running but we get errors.  The backup servber also has DC role. 

My questions are:

1. Should I transfer all the FSMO roles to the backup host server in the event the VM is infected and before turning on the VM domain controller, with exchange?
2. Apart from deleting replication from the dead server, are there other recommendations before attempting to start the replicas in Hyper-V on the backup server and using those as the live servers?
3. We have Shadow Protect backups of the infected server that we could try to restore.  
   An objective is to minimise man hours and we are happy to instate the backup server as the main server as it’s slightly newer.  We would then use the resurrected server as the backup server - viz reverse the roles;
4. We thought we should go back to raw metal on the previously infected server to totally rid any encrypted files unless there are better suggestions. Do you suggest reinstating 2012R2 so that we can replicate the VMs to it or going straight to 2016, then
   upgrade the environment to the upgraded Windows version?   We know we won’t be able to replicate 2012R2 VMs to a later version of Windows Server without registry hacks; 
   The server hardware is not certified beyond Windows 2016 server.
5. Before rebuilding the old host server do you recommend grabbing anything in particular off it?. 
   Most files are encrypted so there is limited functionality.

Any other recommendations would be appreciated.

Thanks.

Read full post . . . .