Archives

Monthly Archives: April 2019

Windows 1809 can’t connect to VM in Hypervisor

I setup a new windows 2019 Standard sever with HyperV.  I can create the Windows 2012R2 VM with no problems.  I can Start the VM with no problems.  I can see the VM started in the bottom window.  I can’t connect to the VM to do
the Windows install.  When I double click or right click->Connect, I just get a spinning circle for a few seconds and it disappears.

All of a sudden now I noticed on my windows 10 PC version 1809 using HyperV, I can’t connect to any VMs anymore…?

I just noticed using a different windows server 2018R2 and Hypervisor, I can connect to the newly created VM on the new 2019 server.

Any thoughts on how to connect to a VM using a windows v1809 Hypervisor…?

Thanks,

Tom….


Tom Karpowski…

Read full post . . . .

Can not access to internet virtual machine

Hello,


I have a server 2016 STD with role Hyper V, and a virtual machine SRV2019 STD

I have on my physical server an "Ethernet" card with ip as a public IP of my provider
Internet works perfectly

In the Hyper V Manager I created an "External Network" virtual switch using my Intel physical adapter

in the configuration of the virtual machine, I assigned him the virtual card "VSwitch"

When I start the VM, it does not have internet.

note: Hyper-V Extensible Virtual Switch is checked on the "Ethernet" card and not "vEthernet", I do not know if it’s good

OnPhysical Machine :

Carte Ethernet vEthernet (VSwitch) :

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
   Adresse physique . . . . . . . . . . . : 00-25-90-D5-xx-xx
   DHCP activé. . . . . . . . . . . . . . : Non
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::6961:b193:bc21:xxxxx(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 37.187.xx.xx(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.255.0
   Passerelle par défaut. . . . . . . . . : fe80::205:73ff:fea0:xxxx
                                       37.187.xx.xx
   IAID DHCPv6 . . . . . . . . . . . : 385885584
   DUID de client DHCPv6. . . . . . . . : 00-01-00-01-24-58-E9-A2-00-25-90-D5-FE-xx
   Serveurs DNS. . .  . . . . . . . . . . : 213.186.xx.xx
   NetBIOS sur Tcpip. . . . . . . . . . . : Activé

On the virtual machine

Carte Ethernet Ethernet:

   Suffixe DNS propre à la connexion. . . :
   Description. . . . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Adresse physique . . . . . . . . . . . : 00-25-90-D5-xx-xx
   DHCP activé. . . . . . . . . . . . . . : Oui
   Configuration automatique activée. . . : Oui
   Adresse IPv6 de liaison locale. . . . .: fe80::6961:b193:bc21:xxxxx(préféré)
   Adresse IPv4. . . . . . . . . . . . . .: 169.254.178.75(préféré)
   Masque de sous-réseau. . . . . . . . . : 255.255.0.0
   Passerelle par défaut. . . . . . . . . : fe80::205:73ff:fea0:xxxx

I understand that in 169 it can not work but I do not understand what I have to do

Can you helping me ?

Thanks

Read full post . . . .

The Windows patches were failed to apply on the secondary Hyper-V host server(KB4493446)(KB4493467)(KB4493435)

Dear Sir/Madam, 

The Windows patches were failed to apply on the secondary Hyper-V host server yesterday. Tried 3 times but still fail. Please give advice to this issue. The patches list is stated as below. Thanks.

 

2019-04 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4493446)            

2019-04 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4493467)

2019-04 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 R2 for x64-based systems (KB4493435)

Best Regards,

Read full post . . . .

Investigate a Hyper-V Host Failure

Today all of the VMs on one of my stand-alone Hyper-V hosts were not responsive but the host itself was OK. After rebooting the host server, all the VMs were back to normal. I checked Windows event logs, under Hyper-V-Hypervisor but couldn’t find any related
error. How to investigate and get to the root cause of the incident.

Read full post . . . .

Recommended pagefile configuration of a replicated guest

Dear all:

Windows expects to have a Pagefile. So if I configure replication for a guest and I don’t want to replicate the Pagefile, which is constantly changing, I will have to create the page file on a separate disk which is excluded from replication.

However, there is a problem: If you suspend that guest machine and resume it or you shut it down and restart it, sometimes it freezes. This happens from time to time, say one out of three times. It ONLY happens if the Pagefile is on a separate virtual disk.

Why would that happen? Well, according to https://www.altaro.com/hyper-v/excluding-paging-file-from-hyper-v-replication/ "Relocating the
paging file to a VHD connected SCSI controller is not supported" and that is what I did, since I had no other choice: this is a hyper-v generation2 guest, which does NOT SUPPORT or offer IDE-connected virtual disks.

Furthermore, https://www.altaro.com/hyper-v/hyper-v-page-file-settings/ explains: "you cannot place a virtual machine’s swap file on a VHD that is attached
to the virtual SCSI chain. This is because the SCSI driver is synthetic, so it doesn’t load until after the virtual machine’s operating system has attempted to initialize its page file. You must place swap files for virtual machines on VHDs attached to the
IDE chain."

If that is true, who can tell me what I can do to exclude the Pagefile from replication, if possible at all?

(Ah no, I don’t want to run a gen1 machine 🙂

Read full post . . . .

Hyper-V VM snapshot deletion job is stuck

VM snapshot deletion Job is stuck at 50% for windows server 2012R2 VM. Snapshot size is only 110GB and it has been 5hr still job is running. VM is running fine, any suggestion how to fix this without downtime. 


Abhishek

Read full post . . . .

Remove VM from SCVMM and readd it.

One of the Hyper-V VM shows configuration error in SCVMM console, but VM is running fine in Hyper-V host. There is no issue with the VM, its working fine. But due to configuration error in SCVMM console backups are getting failed.

Repair option is not able to fix this issue, other options are greyed out. How can I remove the VM from SCVMM and re-add it. 

Any help on this will be much appreciated. 

Thanks, 


Abhishek

Read full post . . . .

Changing host PC name (effects on hyper-v installation)

Hi all,

I would like to know if it is safe to change my host PC name while running Hyper-V

Will my VMs be affected by this change?

Thanks in advance

Read full post . . . .

VMMS Windows Service missing on Windows 2012 R2 host

Original Issue: Was the VMMS services stops and starts every minute

Issue now: VMMS services is missing by running the vmms /regserver

On a Windows Server 2012 R2 host server how can we get the vmms service back into windows services? Can we do this without uninstalling the Windows Role Hyper-V.

What has happened is the  /regserver has deleted the service and we need to put it back any suggestions will be welcome.

Read full post . . . .

KMS activation problems

I part-time manage a branch office IT infrastructure. (More formally, I am developer who has unofficially assumed the IT role.) There are other sites within the company running a common domain. Originally we were not connected  via site-to-site VPN
to other sites, so we created our own separate domain. After a number of years things have changed and we are now connected and are moving our IT infrastructure to the common domain. This has been progressing for a few months, generally fairly smoothly.

We also have two Hyper-V hosts, one running Windows Server 2008 R2 Datacenter. I set it up a number of years back and until now have not had any problems. Recently I noticed one of our VMs that I had moved from the old domain to the new domain a few weeks
back had failed to register its IP in the DNS. Checking the event log indicated KMS failures. I naively tried to re-activate it: slmgr /ipk 74YFP-3QFB3-KQT8W-PMXWJ-7M648. The screen turned black and indicated that Windows is not genuine.

I have checked several of the other VMs, but there does not seem to be any significant issues so far. Please note that the VM host is still in the original domain. Googling around I found this,
I found this indicating to check the SRV record for _vlmcs._tcp. The domain had changed, so this was pointing to the old domain. (Still available if necessary.) I updated it in the new domain DNS. I have also verified that the VM host server is available over
port 1688 via telnet.

I then ran the above slmgr /ipk again. It indicates that the key was successfully applied, but Windows still indicates that the environment is not genuine. I’d appreciate some help in resolving this.

Here is the output for slmgr /dlv on the Hyper-V VM host.

(Please let me know if this contains any keys that I should not post here and I will gladly edit it.)

—————————

Windows Script Host
—————————
Software licensing service version: 6.1.7601.17514

Name: Windows Server(R), ServerDatacenter edition

Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_C channel

Activation ID: 8fe15d04-fc66-40e6-bf34-942481e06fd8

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 55041-00168-305-513198-03-1033-7601.0000-2252011

Installation ID: 017750272912111325448091054514636704605876070861877344

Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342

Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343

Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345

Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344

Partial Product Key: K8W74

License Status: Licensed

Remaining Windows rearm count: 3

Trusted time: 4/25/2019 2:55:52 PM

Key Management Service is enabled on this machine

    Current count: 1

    Listening on Port: 1688

    DNS publishing enabled

    KMS priority: Normal

Key Management Service cumulative requests received from clients

    Total requests received: 2

    Failed requests received: 0

    Requests with License Status Unlicensed: 0

    Requests with License Status Licensed: 0

    Requests with License Status Initial grace period: 0

    Requests with License Status License expired or Hardware out of tolerance: 0

    Requests with License Status Non-genuine grace period: 0

    Requests with License Status Notification: 2

—————————
OK   
—————————

And here is the same output for the problematic VM client.

====================

—————————
Windows Script Host
—————————
Software licensing service version: 6.1.7601.17514

Name: Windows Server(R), ServerDatacenter edition

Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel

Activation ID: 7482e61b-c589-4b7f-8ecc-46d455ac3b87

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 00496-00168-001-000128-03-1041-7601.0000-1152019

Installation ID: 007722422601855746498885195842058945462581432133218512

Partial Product Key: 7M648

License Status: Notification

Notification Reason: 0xC004F056.

Remaining Windows rearm count: 3

Trusted time: 2019/04/25 14:58:42

Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

—————————
OK   
—————————

Read full post . . . .

Go Que Newsroom Categories

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