This was a rather annoying error. It seems to stem from having to support multiple different versions of vSphere and thus having many versions of the client installed along with VMware Remote Console (VMRC). There are a couple of articles from VMware on how to try and resolve this: kb2130850 – Uninstall all vSphere clients.

After our recent enforcement of TLS 1.2 for our WiFi setup our Raspberry Pi3 dropped off the network. I spent a fair amount of time running wpa_supplicant in debug mode along with Wireshark on the RADIUS server and it was clear that the Pi was insisting on using TLS 1.0, which was the cause of.

I’ve steadily been working on improving the security on our internal systems. One of the recommendations is to disable SSL 3.0 and TLS 1.0 on your Windows Servers along with weak ciphers. As with all things IT, there is always some unexpected repercussions when making changes 🙂 Shortly after pushing out a GPO update to.

This document applies to the the custom SLES image built for easier SAP HANA deployments located here: www.suse.com/slesb1hana. At the time of writing the link pointed to: sles11_sp4_b1.x86_64-0.0.10.preload.iso. My first problem with using this image is that there is no checksum to validate your dowload. Here is my md5sum: 8b5e4a223b85a7b144b55b86676938e3 I had to do a.

I recently upgraded some internals in my HP ML110 G6 and thought I’d post some useful details on RAM and CPU combinations. The whole thing started with a refresh of my ZFS NAS. I wanted to move from 4x2TB RAIDZ1 to 6x4TB RAIDZ2. The first thing that was needed was some additional RAM. The recommendation.

So as part of my foray into OpenStack I had allocated floating IPs, but had never actually tested that I could access services on them, until recently. I spent quite a bit of time delving into the router config, looking at iptables rules and tracing packets with tcpdump all in vain. Before you get in.

I’ve been experimenting with vSphere 6 and vRealize Automation in my lab environment and hit an interesting problem when deploying CentOS 6 & 7 VMs. I had created a network in NSX for the tenant, which created 2 distributed port groups on my distributed switch: vxw-dsv-XX-virtualwire-1-sid-XXXX-name and vxw-vmknicPg-dvs-XX. For some reason I could only see.

I’ve recently been experimenting with OpenStack Juno on CentOS 7 and hit an annoying problem where the glance image-create and image-list commands would both fail with “Invalid OpenStack Identity credentials”. All my other services were fine, keystone was happy and returned all the correct information. I worked through countless posts online all describing the same.