Month: March 2020

Why my Hyper-V VM created a checkpoint

Q: After installing a Winodws Update on our VM running Windows 2016, it created a checkoing using a lot spaces. We did cerate the checkpoint. Why?

A: When installing a Windows update or restart VM, if there is a problem, it may take a long time to come back. At that time, VM create a checkpoint. In this case, you may not have delete option. Please refer to this post: Missing delete checkpoint option on Hyper-V

This computer can’t connect to the remote computer because of Windows update

Q: I can’t access my remote computer with this message: This computer can’t connect to the remote computer … I have followed these posts, but can’t fix the problem. Help.

This computer can’t connect to the remote computer … site:chicagotech.net – Google Search ChicagoTech.netwww.chicagotech.net › … › IT Forums › VPN, TS and Remote Accesswww.chicagotech.net › … › IT Forums › VPN, TS and Remote Access

This computer can’t connect to the remote computer … site:chicagotech.net – Google Search This computer can’t connect to the remote computer …www.chicagotech.net › remoteissues › remotedesktop3www.chicagotech.net › remoteissues › remotedesktop3

Troubleshooting: In it is Windows 10, it may have a windows update installed and needs to restart.

Missing delete checkpoint option on Hyper-V

Situation: the client tries to delete the checkpoint because of low spaces. However, he doesn’t see delete checkpoint option.

It should look like this:

Troubleshooting:Try this first

  1. Right-click the host server name in the Hyper-V Manager in the left-hand pane and select Refresh.
  2. Close and re-open the Hyper-V Manager.
  3. Highlight the checkpoint and use the Delete key on the keyboard.

If that doesn’t fix the problem, try powershell commands:

  1. Run PowerShell as admin.
  2. Type the following command and press Enter:
    Get-VMSnapshot -ComputerName <Name-of-Computer> -VMName <Name-of-VM> | Remove-VMSnapshot

Name-of-Computer is your host computer name.

Name-of-VM is the VM name.

For example

Get-VMSnapshot -ComputerName “host01” -VMName “SQLServer01” | Remove-VMSnapshot

Another suggestion is highlight the Checkpoint, and press Delete key.

Or you may try to move/export VM. After the move/export the VM, restart the moved VM without checkpoint.

I find these resolution online:

If you do not have enough disk space available, there are three options:

  • If you have Hyper-V 2012R2, you can export the VM to another disk. It will be exported as a merged VHD file. Later on, clear out the original VM and import the merged image.
  • You can live migrate the VM to another server that has ample disk space, complete the checkpoint merge, then move it back. This will minimize downtime since you can live migrate and merge without having to turn off the VM if you have Hyper-V server 2012 R2.
  • You can move the VM to another volume, such as a USB drive, complete the merge, them move it back again.

Moving VM error: Failed to establish a connection because of an unsupported protocol version (protocol version 6.0)

Situation: When move a VM from Windows 2016 to Windows 2012 R2, you may receive this message: Failed to establish a connection because of an unsupported protocol version (protocol version 6.0)

Troubleshooting: 1. This could be CPU compatibility issue, which prevent you move VM between different hosts.

2. Also, any VM’s created on the 2016 start as version 8 for Hyper-V configuration, where as my 2012R2 machines are version 5. If you want to be able to move the VM’s from 2016->2012 R2 you may need to make the VM first on the 2012 R2 machine.  You can’t downgrade it.

Moving VM error: failed to establish a connection with hostname: The request is not support (0x80070032)

Situation: When move a VM from Windows 2016 to Windows 2012 R2, you may receive this message:failed to establish a connection with hostname: The request is not support (0x80070032).

Troubleshooting: 1. This could be CPU compatibility issue, which prevent you move VM between different hosts.

2. Also, any VM’s created on the 2016 start as version 8 for Hyper-V configuration, where as my 2012R2 machines are version 5. If you want to be able to move the VM’s from 2016->2012 R2 you may need to make the VM first on the 2012 R2 machine.  You can’t downgrade it.

Can’t access FatPipe because of ARP

Situation: the client has a FatPipe as internet balance device. They have a problem to access it using https.

Troubleshooting: 1. We can ping it.

2. https may or may not work. If it works, it is very slow.

3. We have check the Palo Alto firewall but can’t find any thing wrong. Test sends teh package to the fatpipe, but not reply.

4. We fixed the problem by clearing ARP on FatPipe.

Where can i download old Google Nik Collection?

You may try these links.

Installer for Windows [430 MB]” http://dl.google.com/edgedl/photos/nikcollection-full-1.2.11.exe
Installer for Mac [590 MB]: http://dl.google.com/edgedl/photos/nikcollection-full-1.2.11.dmg