VMware: Depreciated VFMS Volume(s) Found On This Host
KB ID 0001383 Problem Well there is a bug on ESX version 6.0.0 that causes this error message, in my case the client had VFMS3 volumes. Depreciated VFMS volume(s) found on the host. Please consider upgrading volumes(s) to the latest version. That’s what was causing the error in my case! Solution I chose to simply update the VFMS3 volumes to VFMS5 > Right click the volume > Upgrade to VFMS5. Select the volume(s) > OK....
Hyper-V 2016 – Missing VM Hardware Versions?
KB ID 0001382 Problem I was helping a colleague with a Hyper-V upgrade this week, he asked if I would upgrade the hardware versions on the guest VM’s Get-VMHostSupportedVersionl However I could not get the cluster to accept a hardware version above version 5 (Server 2012 R2) Solution As it turns out the cluster had had all its nodes upgraded to 2016, but the cluster functional level was still at version 8 (Server 2012)...
PX4-300D Lenovo EMC NAS Device Stuck at 95%
KB ID 0001381 Problem I decided to update the firmware on my PX4-300D 16TB NAS Device, (big mistake!) I had some lunch and went to see how it was getting on, I could no longer connect to the device via web or SSH. It had done this to me once in the past when It had a failed drive, simply removing the drives rebooting and then putting the drives back in got me going last time. So I got on the Lenovo forums, it’s full of posts...
Remote Registry: No Location Found
KB ID 0001379 Problem When attempting to connect to a remote machines registry; Error The program cannot open the required dialog box because no locations can be found. Close this message and try again. Solution The ultimate cause of this problem is, that the machine you are on cannot see Active Directory, either because there are no domain controllers are online, or its DNS settings are incorrect. Related Articles, References,...
PowerShell: Prompt Has Changed To Two Greater Than Signs
KB ID 0001380 Problem What does this mean? Well it means you’ve either got something wrong, or missed something out, and PowerShell is not sat waiting for more input. Which is fine but in most cases you simply need to fix your syntax and sort again so how do you ‘escape’ back to the normal PowerShell prompt? Solution As you can see, (below) typing quit or exist does not help. You need to press CTRL+C. Related...