dave-byrne.co.uk

always remember

Nothing is foolproof to a sufficiently talented fool... Make something
idiot proof, and the world will simply make a bigger idiot.

Fix Windows 10 Remote Desktop Mouse “Bump” Glitch w/Multiple Monitors

If you have multiple monitors, and are running Windows 10 v1903 on your local (host) computer, and are connecting to other Windows 10 machines (regardless of version) via Remote Desktop, you may well have experienced the rather annoying mouse “jump” or “bump” as you pass your cursor across the boundaries of the 2, 3, 4 monitors. This problem also manifests itself on occasion as a black box that “sticks” to your cursor and follows it around the screen, blocking out whatever it is you hover over, making it incredibly difficult to continue using.

This is caused by the change v1903 to RDP’s default Graphics Driver used for RDP sessions wo WDDM, prior to 1903 this was XDDM (thanks for the upgrade Microsoft)

To work around this issue, set the following GPO to Disabled on your local (host), and reboot. A gpupdate /force was not sufficient to apply this setting.

“Use WDDM graphics display driver for Remote Desktop Connections” > DISABLED

Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment

As a side note, you may receive a protocol error if you try to open any previously saved RDP files that have the dispaly setting “Visual Styles” ticked. This is a WDDM feature, and needs to be un-ticked for the RDP file to be used.

dave / August 20, 2020 / Guide

How To: Configure multiple VLAN interfaces in SolusVM

There may be times when you wish to give VM’s on one of your SolusVM nodes access to IP resrouces that are segmented into discrete VLAN’s at network level. If this is the case, you need to create network bridge interfaces on the node, and suply them with your VLAN interfaces. This is explained below.

  1. Configure the base interface, in this example, we ahve trunked eno2 with vlan’s 220 and 221, as we have group of VM’s that require to bind IP’s within this VLAN.
    2. [root@solus-node01]# cat ifcfg-eno2
DEVICE=eno2
BOOTPROTO=none
UUID=xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
ONBOOT=yes
TYPE=Ethernet
NM_CONTROLLED=no
  2. Configure your VLAN sub interfaces, note that we designate each interface to its own new bridge interface, this is required.

    3. Read On… ->

dave / October 24, 2018 / Code, Guide

How To Upgrade PostgreSQL From 9.3 to 9.4 (In-Place)

To make use of the JSONB features implemented in 9.4, it is required that you upgrade your existing PgSQL 9.3 cluster to 9.4+. I cover the basics on how to perform an in-place upgrade.

1. Add the PostgreSQL repo to apt:

echo "deb http://apt.postgresql.org/pub/repos/apt/ utopic-pgdg main" > /etc/apt/sources.list.d/pgdg.list

 

2. Install the repo’s key:

wget -q -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add

Read On… ->

dave / April 7, 2016 / Guide, PostgreSQL

How To Setup Binary Replication Between 2 PostgreSQL 9.4 Hosts (Hot-Standby)

Utilising a master/slave (hot-standby) setup to provide a resilience layer at database level can be easy. The following assumes you have 2 PgSQL hosts at 10.10.50.1 and 10.10.50.2, both running Ubuntu 14.04 LTS and PostgreSQL 9.4 (9.4.5).

1. On the master 10.10.50.1, edit the following in postgresql.conf:

listen_addresses = '*'
wal_level = hot_standby
max_wal_senders = 3

listen_addresses can also be scoped down to single or multiple server bound IP addresses, for added security/best practice

Read On… ->

dave / April 7, 2016 / Guide, PostgreSQL