I have been fielding a few calls very recently where a computer was upgraded to Windows 10 from Windows 7 automatically to a user’s surprise, so they then downgraded back to Windows 7.

Mostly things work after the revert to Windows 7, however I’m seeing so many issues with Task Scheduler corruption.

The task image is corrupt or has been tampered with.

It is a long and tedious task to fix these problems, but it CAN be done. Follow the Microsoft KB article. DO NOT delete all the tasks in the Subkey as mentioned in a few Microsoft Social networks.

Instead of visiting sites like Speedtest.net through a browser, you can install speedtest-cli package on Linux and test bandwidth speeds from the command line.

$ apt-get install speedtest-cli

Here’s an example running the command.

root@zabbix:~# speedtest-cli
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Level 3 Communications (
Selecting best server based on latency...
Hosted by Armstrong (Butler, PA) [44.33 km]: 13.106 ms
Testing download speed........................................
Download: 14.40 Mbits/s
Testing upload speed..................................................
Upload: 0.65 Mbits/s

Run the esxcli storage vmfs extent list command to generate a list of extents for each volume and mapping from device name to UUID.

You see output similar to:

Volume Name VMFS UUID Extent Number Device Name Partition
------------ ----------------------------------- ------------- ------------------------------------ ---------
esxi-local 4e0d86e1-0db6f826-6991-d8d3855ff8d6 0 mpx.vmhba2:C0:T0:L0 3
datastore1 4d4ac840-c1386fa0-9f6d-0050569300a7 0naa.6006016094602800364ce22e3825e011 1
vmfs5 4dad8f16-911648ca-d660-d8d38563e658 0naa.600601609460280052eb8621b73ae011 1

Had some troubles with an ESXi 5.5 host the past week and rebuilt some of the networking which included removing a vmkernel and re-adding to a standard vSwitch and then setting up VMotion and Management tags on it.

Came across the following error on my host in vSphere Client:


To resolve this issue, I needed to make sure that there is a default gateway on the port group that the VMotion vmkernel is on.

Click on the ESXi Host then navigate to Configuration > Networking and on the VMkernel Port that I’m using for VMotion, click Properties…


Next, I examine properties of the VMotion VMkernel.


Looking at the IP Settings tab, I see there is no VMkernel Default Gateway defined, so I clicked Edit…


I entered in my default gateway and clicked OK and then OK again to exit the switch properties dialog.


Finally, I right-click on the ESXi host and click Reconfigure for vSphere HA


At this point, no additional errors are reported for my ESXi host.  =)

IBM IMM Default Username: USERID
Default Password: PASSW0RD

Access KVM:

compose new post
go to top
go to the next post or comment
go to the previous post or comment
toggle comment visibility
cancel edit post or comment