I recently learned that it’s possible to use Google Authenticator (or any other authenticator app) with Office 365 for 2-step verification. That’s great as I’ve always believed it was Microsoft Authenticator or the highway. I’m sure Microsoft Authenticator works fine, but I don’t want multiple authenticator apps on my phone.

About one and a half months ago I experienced a lot of botnet traffic originating from major cloud providers including Microsoft Azure. Against my better judgment I decided to see if reporting a few bad IP’s to the MS CERT team would make a difference.

My plan to install the latest Windows 10 Creators Update fell short during the weekend due to an error identified as 0xc1900200. I was using the “Windows 10 Update Assistant” to perform the upgrade, and the assistant did initially confirm that my system was ready for the upgrade.

On my Windows 10 computers I always work with a standard account and keep a separate administrator account. This provides some additional security as any operation needing administrative privileges will require an administrator’s approval.

After reading the latest horror stories depicting the Windows 10 anniversary update as a merciless destroyer of everything Linux, I was somewhat concerned before applying the latest and greatest from Redmond. Sure, it would make absolutely no sense if Microsoft was actually deleting data from their customers devices, but mistakes do happen so I made sure to back everything up before upgrading.

First up was my primary Windows 10 / Slackware 14.2 based notebook, an ASUS G771JM with 256GB SSD and 1 TB HDD running under UEFI/GPT with secure boot disabled.

When using a client other than Skype for Business (formerly known as Lync) to connect with your Office 365 account, you’ll need to provide the Microsoft Lync servers with a user-agent string they recognize as an “acceptable” client. The reasoning behind this is surely to give you the best possible experience and not at all to lock out other messaging clients.

The Windows Update service will provide you with drivers for the Asus USB-N13 adapter, but in my experience, none of these drivers function reliably. They all suffer from the “limited connection disease” thus forcing me to reattach the dongle and play an endless game of connect and disconnect.

After Windows 8.1 had performed an unscheduled reboot, I was greeted with the following error message when trying to start up a virtual machine in VMware Player:

This virtual machine appears to be in use.
If this virtual machine is not in use, press the “Take Ownership” button to obtain ownership of it. Otherwise, press the “Cancel” button to avoid damaging it.

Trying to start the game Kane & Lynch: Dead Men from the Steam client on a default Windows 8.1 installation will not work. Furthermore, you’ll get no error message other than the obvious lack of the gameplay.

As usual with these kinds of errors, a good starting point is to locate the actual game folder. From Steam’s Game library, right click on “Kane and Lynch: Dead Men” and select properties, then select the tab called “Local files” and finally click the button labeled “Browse local files”. You’ll now find yourself in the game directory. By trying to execute “kaneandlynch.exe” you’ll get an error message stating that “xlive.dll is missing from your computer”. Thankfully, Steam has already included the necessary libraries inside a folder named XLiveRedist which contains the installer package XLiveRedist01.02.0241.00.msi.

With the release of OTRS Help Desk 4, it seems that running OTRS on a native Windows environment for all intents and purposes is no longer viable. By killing off the Windows installer and recommending migration into the OTRS appliance, the OTRS Group seems to be subtly hinting that OTRS on Windows is dead in the water.

Switching to the OTRS appliance might be a good solution for some Windows installations, but in my case OTRS is configured with MS Active Directory as a customer and agent backend, and we’re relaying on IIS for single sign on. It might be possible to do a source based update and subsequently hack it all back together, but who really wants to travel down that road.