Internet Explorer is Dead – Long live Internet Explorer Compatibility mode in Edge

Microsoft Edge with Internet Explorer mode will replace the Internet Explorer 11 desktop app, which will be retired on June 15, 2022.
IE mode support follows the lifecycle of Windows client, Server, and IoT releases at least through 2029

If you have websites that require Internet Explorer 11 in your business still, you have some work to do before it will work in Edge. – This guide shows you how it works in an Domain Controlled Environment. Remote workstations and Laptops can use InTune as well if they have no Domain Controller.

Your Mileage may vary and this might not be the best practise at time of reading. – I read the Microsoft guides in Feb 2022 and based all this on them. This has been rolled out at my work and has worked so far correctly.


This article applies to Microsoft Edge version 77 or later.
To Download the latest version of Edge – visit

How to deploy the Edge Policy in ActiveDirectory – Source

The Policy template files are downloaded from the website –

To take advantage of the benefits of .admx files, you must create a Central Store in the sysvol folder on a Windows domain controller.
The Central Store is a file location that is checked by the Group Policy tools by default.
The Group Policy tools use all .admx files that are in the Central Store. The files that are in the Central Store are replicated to all domain controllers in the domain.

To use ADMX files in Group Policy the following needs done on the Domain Controller

On the domain controller – Copy the PolicyDefinitions folder to your SYSVOL PolicyDefinitions Folder

Create a Sites.xml – SiteList
To configure the sites list – Source :
The Enterprise Site List Manager is an in-browser version of the standalone Enterprise Mode Site List Manager tool that lets you create, edit, and export your organization’s site list.

Or Edit the XML file manually, very carefully as any mistakes invalidates the list

 Each Entry needs to be in the format :

  <site url=”website-name”>

Now open up Group Policy Management and Create a new Group Policy Object and Link it to root

Name this Internet Explorer Compatibility Mode – Edge

Configure the Group Policy – Source :

1.    Click User Configuration/Computer Configuration > Policies > Administrative Templates > Microsoft Edge.
2.    Double-click ‘Configure Internet Explorer integration.’
3.    Select Enabled.
4.    Under Options, set the dropdown value to Internet Explorer mode – Press Apply OK
5.    Double-click Configure the Enterprise Mode Site List.
5.    Select Enabled.
6.    Under Options, type the location of website list. You can use one of the following locations:
o    Set this too your domain share where you copied the sites.xml at the start – ie. \\DOMAINCONTROLLER-NAME\SYSVOL\DOMAINNAME.LOCAL\Policies\sites.xml
7.    Click OK or Apply to save these settings.
8.    Double-Click Configure the Enterprise Mode Cloud Site List (Only if you are using a Cloud Site List in Office 365)
9.    Click Not Configured
10.     Set the List option to your Cloud Site List ID
11.    Double-click Send all intranet sites to Internet Explorer
12.    Select Enabled
13.    Click OK or Apply to save these settings.

Create another group policy and name this Internet Explorer Compatibility Mode – Trusted Sites

  • Open the Group Policy – Internet Explorer Compatibility Mode – Trusted Sites.
  • Go to User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer > Internet Control Panel > Security Page.
  • Select the Site to Zone Assignment List.
  • Select Enabled and click Show to edit the list. Refer to Figure 1 below. The zone values are as follows: 1 — intranet, 2 — trusted sites, 3 — internet zone, 4 — restricted sites.
  • Click OK.
  • Click Apply and OK.

Test your Policies

On a target client device, open Microsoft Edge and navigate to edge://policy to see all policies that are applied. If you applied policy settings on the local computer, policies should appear immediately. You may need to close and reopen Microsoft Edge if it was open while you were configuring policy settings.

I’ve made a new WordPress Plugin after a 12 year gap

So, I enjoy playing computer games as a hobby and over the years there has been clip service websites popping up to show off your best moments. is one of these.

However there’s no plugin for WordPress to bring these videos in to posts automatically.

That was until today –

This plugin I’ve created allows you to use the short code medaltv to show your latest videos which you have uploaded to there service via the MedalTV API

Example of this running below

Removal of Helicopter made to look easy

Challenges I’ve faced making this, WordPress and PHP have come a long way since I last looked at how a WordPress Plugin worked.
Securing Input and Validation as I’ve also added a Admin Menu to this code.

Back to the Amiga – Pt. 1

Well with Retro being the new thing I thought it was time to get my Amiga 1200 singing and dancing again and also document all the things I’ve done to make it work.

For a start the amount of things they have improved on the Amiga scene since 1999 has peaked my interest up again.

If you don’t know what the Amiga is the Wiki page here goes through the lot :

I will publish various Parts to this series when I get time to write about them, but to start you off this is Part 1 which shows you what you require to get your Amiga to output to VGA

What do you require to start?

First you will need a Commodore Amiga A1200

If you just want to use the system to play games from Disk and want to use this with a VGA monitor you only require the following extra equipment:

GBS8200 CGA/EGA/VGA converter – This can convert the Amiga’s RBG output and to work on VGA out.
A 680 ohm resistor to create this lead and Heat-shrink to make it neat.
Amiga DB23 to VGA Adapter to pull apart for the lead to the GBS8200
Optional but Recommended : Wemos D1 Mini Pro ESP8266 – This allows you to make the GBS8200 better by using the application GBS Control
On how to build the hardware for GBS Control the instructions can be found on there Wiki –

GBS8200 Setup for Video Output to VGA

Creating the DB23 to GBS Lead – the GBS8200 comes with a lead which can be soldered straight to a the pins of the DB23 connector – the Wiring diagram below shows you which wires need to be connected – Yellow and Brown are not used in this setup and can be removed by pressing in to the rectangle tab and pulling the wire out.


The 680 ohm resistor is soldered inline on the grey wire and heat-shrink is applied to keep it protected

The grey wire with the resistor soldered
Cable tidy mesh used around the completed wire

GBS8200 + ESP8266 (Optional but recommended)

If you build the optional GBS Control unit, the ESP8266 joins on to the GBS8200 like the following pictures and gives you finer control (via. a webpage) and better picture output whilst using the GBS8200

GBS Control Webpage
The Amiga A1200 outputting a Disk Based game via the GBS8200 + ESP8266

ACA1231 on OS3.1.4.1

After installing Amiga OS3.1.4.1, I’ve noticed that the 68030.library and MMU support with ACATune does not work correctly on my older ACA Card.

Running ACATune -status shows that the ACA1231-41Mhz card is being detected as a ACA1230-28Mhz card with not features enabled.

To fix this problem please follow the guide below

1 : To check if you have a problem with your ACA Accelerator card, Open up a Shell and type acatune -status

I have a ACA1231 but in ACATune it’s coming up as a ACA1230 with the wrong clock speed and also no features enabled.

2: Download the latest version of Mu680x0Libs – and extract to a folder, In there run the Install in the Install folder – I picked Novice Level and let it install where it wanted

3: Once installed, Copy the ACAInit file from the Mu680x80Libs/Libs/MMU folder to your Libs:MMU

4: Now edit the file ENVARC:MMU-Configuration and add ACAInit to the line before ;that’s all folks!

5: Turn the Amiga off and wait a few seconds, then back on. Once it’s booted try ACATune -status to make sure it’s working OK

Solarwinds – An exception occurred during polling processes. Error: Invalid class – Using WMI or RPC to poll

in Solarwinds SAM I was getting this error when trying to check for a running Process using Solarwinds Agents + WMI

After a bit of digging I found that on the computer in question, Opening windows Performance Monitor would give the error

Unable to add these counters:

\Memory\Available MBytes
\Memory\% Committed Bytes In Use
\Memory\Cache Faults/sec
\Memory\Cache Faults/sec
\PhysicalDisk(*)\%Idle Time
\PhysicalDisk(*)\Avg. Disk Queue Length
\Network Interface(*)\Bytes Total/sec”

The problem is that some of the WMI Querys have been disabled on the computer so will need to be reenabled
Following this technet article : fixed my issue

Short instructions on how to fix

Open CMD as administrator
CD C:\Windows\System32
lodctr /r
CD C:\Windows\SysWOW64
lodctf /r
lodctf /q
This will query the Performance Metrics library’s installed on the machine
Copy this list in a notepad and check for items that are disabled
For each disabled entry you will need to run the command lodctr /e:<provider name>

Once done you should be able to use your monitor in Solarwinds

Teamspeak in Amazon AWS EC2

Well for a little 30 minute project I decided to see how well TeamSpeak v3.9.0 runs in Amazon AWS EC2 t2.micro instance.

This project is based on the Reddit Guide
and this GazBlog Guide –
but the instructions needed changing slightly due to Teamspeak differences and also I wanted the firewall and SSH access secured.

My reasons for this is ever since i3d stopped hosting Teamspeak getting a good UK server has proved hard so having a AWS server as a backup / used as our main comms server would be helpful.

Amazon offer 12 months free of a t2.micro instance the cheaper t2.nano is not free at the moment

To try this out for yourself you will need to sign up to Amazon AWS EC2 Services using the following link :

Fill in your details for a Personal account and verify with a Debit or Credit Card

Once signed up go to your AWS Console –
Select the region you want to host your server on – I used London as I’m based in the UK

Select ‘Launch a virtual machine with EC2’

Search for Ubuntu Server 18.04 LTS

Select t2.micro ‘Free tier eligible’

Next configure your Instance Details – I left all settings at Default
Next Add Storage – I used SSD with 8Gb’s of space for /dev/sda1

Next create a Network security group to allow TeamSpeak traffic and also Private SSH traffic back to your Home IP – I called my Group ‘ Teamspeak Server Firewall’

Now click Review and Launch – If you get a error can’t launch, wait another 10 minutes as your account may be waiting verification from Amazon.

Once launched – Change the first dropdown box to “Create a new pair” and give it a name like “Teamspeak-Access” and hit “Download Key Pair”. Then hit “Launch Instances”

Move you private Key to somewhere safe – as without this you won’t be able to SSH in to the instance

Connecting to SSH

Now I used Putty to connect to the instance – but there is a Java Client as well which can be used.
To use PuTTY, Amazon have some instructions here –
PuTTYgen has to be used to save your Key in to a accepted Putty format

To use the Java Client (Not tested as I don’t have Java) – you need to select connect with Java SSH client. Set the Private key path as the location you saved you key pair and tick Store in browser cache. Then hit Launch SSH Client
Accept the terms for everything, Press Next a few times. When the MindTerm screen opens, hit “Enter”


Setup Teamspeak 3 server on Ubuntu 18.04

Run the following via SSH to upgrade your Distro
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Next create a user to run Teamspeak using the following command
sudo adduser --disabled-login teamspeak
sudo su teamspeak
cd /home/teamspeak

Run the following commands to:
Download Teamspeak, extract it and tidy up.
tar xvfj teamspeak3-server_linux_amd64-3.9.0.tar.bz2
cd teamspeak3-server_linux_amd64
cp * -R /home/teamspeak
cd ..
rm -r teamspeak3-server_linux_amd64
rm teamspeak3-server_linux_amd64-3.9.0.tar.bz2
touch .ts3server_license_accepted

Next start the TS3 Server with the following command
./ start
It should start up – copy out the text that spits out as it will contain your access token and Server Query admin account details – Don’t lose it!

Press Enter to return to the command prompt
Finally stop the server and Exit the Teamspeak user with the following commands
./ stop

Now we will create a restart script using systemd to restart it on boot.
Run the below command (This should open a blank pape)
sudo nano /lib/systemd/system/ts3server.service

Copy the below and paste it:

Description=Teamspeak Service

ExecStop=/home/teamspeak/ stop
ExecReload=/home/teamspeak/ restart


Now we need to save it
Press CTRL and X together, then Press Y

Now we need to enable it, by typing in the following command
systemctl enable ts3server.service

Type the following to reboot you server
sudo reboot

Connecting to the TeamSpeak instance

Connect using your Public DNS bookmark – for example

Then claim ownership using the Teamspeak client with your access Token (Right click – Manage Virtual Server)

And the performance seems great

MDT / SyncThing / SnipeIT / API Asset Tracking / Logmein One2Many

I’ve been working on a system to deploy a Master Windows 10 image from MDT to remote sites that have no direct LAN to LAN connection. And also update the Asset Registry at the same time.

MDT / WDS / PXE Server

The MDT / WDS / PXE server is hosted on the HQ LAN, this can only PXE / Litetouch computers on the same LAN.


SyncThing SyncTrayzor makes it possible to share the DeploymentShare which hosts the MDT image with other sites by making a receive only sync on the remote file servers. Setup the DeploymentShare$ on the remote site as you would be on the local LAN and install Deployment Workbench / ADK for completeness.

This gives the Option to use the LiteTouch script to upgrade computers remotely

SnipeIT + API

SnipeIT is a free open source application for asset management – by itself it’s a manual process to enter assets and track them. It does have an API to use however which allows you to automate this process.

Marksman creates a new asset in SnipeIT from the local computer details but cannot update an asset already in the system.

Recon (Created by me but unreleased as of yet) updates the asset details in SnipeIT from the local computer details.

This can be run as a one off, inside the Litetouch process (So when a computer is imaged the asset details are automatically put in to SnipeIT).

Logmein One2Many

Logmein One2Many allows you to run an exe file on all controlled computers, so putting in Marksman and Recon you can update your computer asset database with one click.