Archives

Get Schedule Task ACTUAL TASK!

I placed this in the Hyper-V section since I am running Hyperv 2012 R2 standalone server, so no GUI. I would of placed this in a powershell/cmd or CLI section had there been one.

I put in some schedule task, but I am finding it hard to SEE what the actual task is suppose to run. It blows my mind that this wasn’t something I could easily find with google or through the help menu.

I tried schtasks /query /tn NAMEOFTASK

but it only returns the Taskname, Next Run Time, and Status

How do I see what the actual task will do?!?!

also tried

Get-ScheduleTask TaskName | Get-ScheduledTaskInfo

Also just as useless. Am I crazy or does this information simply not obtainable through the command line, at least without a simple command and switch.  Any Insight or Windows BASHing is welcomed. Thanks in advance.

Read full post . . . .

VMM2016 can’t build new VM

Hi,

I am running VMM 2016 and HyperV Core 2016 and it used to function fine when building new VMs, now it fails each time with the following error:

Error (20408)

VMM could not get the specified instance Scvmm_EthernetSwitchPortInternalSettingData.InstanceID="Microsoft:Definition1f59a509-a6ba-4aba-8504-b29d542d44bbDefault" of class Scvmm_EthernetSwitchPortInternalSettingData on the server xxx.xxx.xx.xxx.co.uk.
The operation failed with error HRESULT 0x80338000 The WS-Management service cannot process the request. The class Scvmm_EthernetSwitchPortInternalSettingData does not exist in the root/virtualization/v2 namespace.

However, if I use HyperV manager then I can build the VMs OK and VMM2016 will then allow control of most functions, my othe rHyper-V Core 2016 servers running under the same VMM2016 instance are working just
fine.

Can anyone shed some light on this please?

Read full post . . . .

Cannot use mouse and remote to Hyper-V VM suddenly

Dear Support, 

We cannot use mouse on Hyper-VM suddenly. 
Besides, we cannot remote the VM. 

Could you have idea to solve the issue?

Thanks!

Best Regards,
Daniel

Read full post . . . .

Could I virtualize win2008R2 DC with root CA to hyper V?

Hei all,

I have a closed domain with 2 failover clusters. one is hyper V failover cluster, with 3 nodes, in a Dell VRTX enclusure. The other failover cluster is a two-node VMware cluster with a direct-attached storage box. I have 3 DC in my environment: one physical
DC-1 in a blade chassis with windows 2012R2, a virtual DC-2 on the VMware cluster running windows 2008R2, a third DC-3 physical blade running windows 2008R2. DC-3 used to be the DC with all the FSMO roles and enterprise root CA function. I have migrated FSMO
roles to DC-1 (which is newer).

Now my primary wish is to virtualize DC-3 to hyper V cluster such that I can easily failover should anything happen. I read a few posts and have the feeling that to migrate root CA is a very cumbersome process and I just want a easier and safer way to guard
hardware failure of the aging DC-3.

the security concern is not the major issue, as the domain is closed with no internet connection, and the servers are in a secure locked location with very few persons that can access. the users connect to the domain and RD session hosts/VDI thorough RDP.
the domain is guarded with firewall, with only port 443 open for RDP gateway server.

My question is: is it OK to virtualize root CA? in my case if I use P2V, and put the virtualized DC-3 to hyper v failover cluster, would it be any problem /issue?

thanks a lot for help.

regards

Read full post . . . .

Cannot remotely manage Hyper-V core 2016 from Win10 (winrm cannot complete the operation)

I’ve followed all the instructions - it actually worked and then suddenly stopped working.

I am NOT in domain.

Symptoms: in server manager, I get: "Online - Verify that WinRM 3.0 service is installed, running, and required fw ports are open"

in Hyper-V manager, I get: An error occured while attempting to connect to server XXXXX. Check that Virtual Machine Management service is running and that you are authorized to connect to the server. More specifically, "The operation on computer xxxx
failed: WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer…."

I followed everything on this page: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Remotely-manage-Hyper-V-hosts

On server: I created local administrator (it works via remote desktop), enabled PSRemoting, Enabled WSManCredSSP -role Server, added my client computer to trusted hosts, added computer to hosts file.

On client, I also added server to trusted hosts, I went into gpedit and allowed delegating fresh credential,….

I did winrm quickconfig on both machines, set all networks to private,… disabled firewall completely, tried telneting onto 5985/5986 ports on both computers (works OK)…

I also followed some forum posts (additional command to allow more stuff) and it still does not work.

Any ideas? :-S It worked but it stopped working suddenly - I’m guessing some update or something broke it?

— edit: yes, services are running:

PS C:windowssystem32> get-service winrm

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

PS C:windowssystem32> get-service vmms

Status   Name               DisplayName
——   —-               ———-
Running  vmms               Hyper-V Virtual Machine Management

Read full post . . . .

Cannot remotely manager Hyper-V core 2016 from Win10 (winrm cannot complete the operation)

I’ve followed all the instructions - it actually worked and then suddenly stopped working.

I am NOT in domain.

Symptoms: in server manager, I get: "Online - Verify that WinRM 3.0 service is installed, running, and required fw ports are open"

in Hyper-V manager, I get: An error occured while attempting to connect to server XXXXX. Check that Virtual Machine Management service is running and that you are authorized to connect to the server. More specifically, "The operation on computer xxxx
failed: WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer…."

I followed everything on this page: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Remotely-manage-Hyper-V-hosts

On server: I created local administrator (it works via remote desktop), enabled PSRemoting, Enabled WSManCredSSP -role Server, added my client computer to trusted hosts, added computer to hosts file.

On client, I also added server to trusted hosts, I went into gpedit and allowed delegating fresh credential,….

I did winrm quickconfig on both machines, set all networks to private,… disabled firewall completely, tried telneting onto 5985/5986 ports on both computers (works OK)…

I also followed some forum posts (additional command to allow more stuff) and it still does not work.

Any ideas? :-S It worked but it stopped working suddenly - I’m guessing some update or something broke it?

Read full post . . . .

Some virtual machines can not be networked.

I built multiple virtual machines. When I used them, part of the network of virtual machines was not working. 

I don’t know why.

For example, I have a and B two virtual machines. They are all connected to the same virtual switch, which is default by network settings. But B can not access the network, DHCP client can not deliver messages, router can not receive DHCP requests, and manually
fill in the IP invalid

I restart the virtual machine, the fault is still. I can only get rid of a physical computer failure by restarting it, but it’s only temporary, and when I run the new virtual machine it may fail again

I need to solve this problem, and I want to know how to test the network of virtual switches and virtual machines.

Read full post . . . .

Some virtual machines can not be networked.

I built multiple virtual machines. When I used them, part of the network of virtual machines was not working. 

I don’t know why.

For example, I have a and B two virtual machines. They are all connected to the same virtual switch, which is default by network settings. But B can not access the network, DHCP client can not deliver messages, router can not receive DHCP requests, and manually
fill in the IP invalid

I restart the virtual machine, the fault is still. I can only get rid of a physical computer failure by restarting it, but it’s only temporary, and when I run the new virtual machine it may fail again

I need to solve this problem, and I want to know how to test the network of virtual switches and virtual machines.

Read full post . . . .

Hyper-V server CPU resource loading

We have installed Windows server 2016 server with Hyper-V on Dell R430 server, 2×16 Core 32Threats CPU.  We have build 2 guest Windows 2012 servers for each have 16 vCPU only. 

We found that even the guest servers CPU running over 70%, the host server only have 1 core full loading and other CPU only have few% loading running.

Is that anything we set wrong? Or anyway we can make the balance CPU load on the physical host?

Thanks a lot

Read full post . . . .

Failing Production Checkpoints in Windows Server 2008 R2 VM running on top of Windows Server 2016 Hyper V

We have windows server 2016 running Hyper V services. Two VMs with Windows Server 2008 R2 Enterprise is running and are failing to create Checkpoints. The error shows: "An error occurred while attempting to checkpoint the selected Virtual Machin(s).
Checkpoint Operation failed. ‘VMNAME’ could not initiate a checkpoint operation."

In the Hyper V host of Windows server 2016, when I run Get-IntegrationService -VMName "VMNAME" command in powershell; all the Hyper-V services are running and are listed as true in enabled and OK in Primary Status Description.

Upon checking the version of Hyper V integration services in the VMs; the version number is 6.3.9600.18080

Can anyone point me out to what I am missing here? I updated the Hyper V integration services previously; as there was an irreversible error in VSS service.

Also, when I restart these services in the Windows server 2008 R2 VMs; the checkpoints are scucessful: BITS, SENS, NtFrs, DFSR, EventSystem and VSS. But after a restart of VMs, the condition is same. Another VM with windows server 2016 is running fine and can
create checkpoints easily.

Any suggestions here?

Read full post . . . .

Go Que Newsroom Categories

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