Server rooms should be kept dust free and at no more than 20c / 68f.
We mentioned server before and still get some interesting questions regarding what makes a great room to house your equipment. Some are questioning why we bother to mention servers and climate controlled rooms now that many of us are using Cloud based solutions to handle what was once on premise. Continue reading
We reported a while back about Meltdown and Spectre, the two flaws potentially affected most chips used in computers going back as far as 20 years.
We further advised to hold off on the patches and fixes until it became clear as to how taxing they were going to be. As it turns out, a fair number of computers were trashed by the “fix”.
The patches “may introduce higher than expected reboots and other unpredictable system behavior,” wrote Navin Shenoy, general manager for Intel’s data center group in a blog posting Monday.
Organizations that have installed the patches noticed a 12% slowdown of their devices, on average, according to Spiceworks. They also report that 29% of companies with more than 1,000 employees expected to spend 80+ hours dealing with the flaws. 18% of companies reported spending more than $50k to apply the patches and dealing with the issues created by said patches.
In other words… maybe you want to hold off on patching.
Unless you have been avoiding all news lately, you have no doubt seen or heard countless reports on two security flaws discovered in Intel, AMD and Arm processors. These, combined, affect pretty much everything built in the last 15 years or so. Without going into all the details, reports appear to indicate that the only real fix is a hardware replacement. The hardware fix isn’t available, so patches and fixes are being released to prevent someone from getting access to the process that accidentally leaks data. Continue reading
Here is the latest information about the breach directly from the Nicehash web site.
The security breach: what happened?
As has been widely reported, NiceHash’s security system was breached in a sophisticated attack in the early morning of 6 December. Our payment system was compromised and the entire contents of the NiceHash bitcoin wallet were stolen – around 4,700 BTC. Our investigation to determine the nature of the attack and its impact is ongoing, with the support of police investigators and a cyber forensic team, and while we want to be as open and transparent as we can, for obvious reasons we can’t provide all the details of the breach. We are very sorry for any inconvenience that the hack may have caused and have committed every resource in response to the issue since we became aware we had been victims of the security breach. Continue reading
As some of you may know we are hard at work on Bitcoin-related projects. We were affected by the NiceHash Mining theft. Here are the answers to some common questions about the incident.
What was stolen? Their Bitcoin wallet. All of it. Continue reading
Ever since I wrote that article about bitcoins, a fair number of readers have been asking about mining and general investment into bitcoins. We’re putting together a new article. We hope to review some bitcoin gear in the coming months. Continue reading
Just when you thought it was safe to upgrade a Pink Screen of Death (PSoD) is confirmed. If you are thinking of upgrading from 6.5 u2 to update 1 you may want to hold off. This problem has no resolution and was officially documented by VMware on Oct 25, 2017.
- Upgrading to ESXi 6.5 Update 1 produces a PSOD.
- ESXi host using 10GB NICs
As we tweeted on Oct 17, 2017, a major WPA2 flaw has been discovered by Mathy Vanhoef of KU Leuven in Belgium. WPA2’s cryptographic protocols could be exploited to read and steal data that should be secure. Continue reading
Exporting to an OVF file results in an unsupported hardware family vmx-12 error. Here are a few possible fixes.
I spent hours exporting a virtual machine (vm) to an OVF format only to discover that VMware vSphere 6.5 gives me an error when I tried to deploy it.
Error message: Unsupported hardware family ‘vmx-12’ error ( also applies to vmx-10, and vmx-11 )
Cause: You created the VM using Workstation 11 or 12/12.5 and didn’t set the vm version to 10 or below before creating the OVF. Continue reading
If you read my posts then you know we’re been here before. The Windows 10 Pro update called the Creators Edition released in September 2017 (Build 1703) breaks your VMs running on VMware Workstation pro 12 or 12.5. It is possible that 11 or earlier may have this same problem.
Instead of simply sending you back to my old post I thought I would share how to fix this problem quickly.
Summary: The VMs suddenly no longer see the Network Interface Card (NIC) of your computer running Windows 10 Pro. Just to be clear, the VMs can be running any version of Windows and have this issue. The Workstation is running on Windows 10 Pro. Continue reading