Finally the Owncloud people got their updater to work for me, and I went ahead and updated. As a result I had to make some tweaks to CloudPress to keep my users active. Check it out and let me know if it works for you. Find my this new version here.
As a longtime OpenVPN user on Linux I thought it would be an easy task to set up OpenVPN as a service on Windows. Well, I was right… and couldn’t be wronger. Setting up the service is part of the installation notes for OpenVPN. Just search for “Running OpenVPN as a Windows Service” in the notes and you will find a pretty good description that should get you up and running in no time.
It seems that Microsoft’s products creating more and more foos. This time it is Lync, also known as Skype for Business.
It is okay, that Lync uses the Enter key to send a message or the CTRL-Enter combination start a call. But it is not okay that there is no way to change these key combinations. Especially when all other instant messengers that I use, default to CTRL-Enter to send a message.
So now I have to use Lync at work, which starts a call when I want to send a message and no direct way of changing it. The only thing that is possible, is removing the CTRL-Enter key combination so that I don’t accidentally start a call.
A solution is described in a TechNet blog post. So here is what worked for me in Lync 2013 (a.k.a. Office 15.0).
First open the registry editor (regedit.exe) and navigate to the following key. If you have a different Lync/Office version you might just change the version number. Create the missing pieces of the key, if necessary. In my case I only found the Microsoft part and had to create everything else.
Create a new string value inside that key:
Value Name: CtrlEnter Value Data: 13,8
Restart Lync and the CTRL-Enter foo should be gone.
Update: Fixed the registry key (Lync, not Office). Thank you Karel, for pointing that out to me.
Windows continues to kick my behind. Out of the blue the Windows 8.1 installation on my workstation didn’t want to open the store app. Not that I really need or want it. But the same happened for the settings app, which was a little bit of a problem.
I should have taken a screenshot but the error message was something along the lines of “This app can’t open” and “Refreshing your PC might help fix it”.
It seems that I was not the only one with that problem there is even a Microsoft blog post about it. The reason seems to be that the affected apps are not registered anymore with Windows.
So here is how it can be fixed. In a command prompt that runs as administrator I ran the following commands. When you look at the blog post it seems that you don’t need administrative rights but you never know. Now enter the following commands to re-register the system apps:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.XML
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\camera\AppxManifest.xml
File Manager (One Drive) app:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\FileManager\AppxManifest.xml
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\ImmersiveControlPanel\AppxManifest.xml
These execution of these commands, especially for the store app, might take a while.
This would have been easy, but of course a Microsoft products never make things easy on me. So I hit the problem that the a registry key doesn’t have the right owner and I got the error 0x8007064A.
So you have to open the registry editor (Windows + R and then regedit) and navigate to the registry key:
And then change the ownership of this key to SYSTEM:
- On the Edit menu, click Permissions.
- Click Advanced, and then click the Owner tab.
- Under Change owner to, click the new owner, and then click OK.
I was using SquirrelMail and the Sieve plugin avelsieve for quite a while. And I once made the commitment on the mailing list to do some further development on avelsieve to make it work with newer PHP versions and fix other problems. The result was my own little update and some not yet released stuff that I only used myself.
But things changed and I moved on to Roundcube. And more importantly the spare time that I could spend on this project got less and less. I am really sorry, but I won’t be doing any further development on avelsieve. For anybody who wants to use my patched version, it is still and will be up there for download.
MS Outlook is in itself already a very annoying and not very pleasant piece of software. But sometimes you have to use it, no matter what. I will live.
But running again and again into the problem that Outlook conveniently forgets the correct calendar view really became a problem. Especially when it happens to everybody and they come to me to fix it.
At least it is easy to fix, but let me describe the problem first. It happens quite frequently that Outlook simply forgets the saved calender view. In our case that was usually the monthly view. It happens when you run a filter on your calendar. Outlook assumes the filtered view to be the new default. Well, that is just wrong.
Depending on the version of Outlook you have to perform one of the following steps.
Menu bar > View > Arrange By > Current View > Day/Week/Month
Menu bar > View > Change View > Manage Views > Select view name "Calendar" in the list Click "Apply View"
Re-installing MacOS should be a piece of cake. Just go into recovery mode by pressing Command+R during boot and start recovering. It should be…
But that is only true for the common case. If you perform the internet recovery and you are using a brand new Apple ID, then you are screwed. In that case you will see a message like this:
This Apple ID has not purchased Lion. You must sign in with an Apple ID that was used to purchase OS X Mavericks.
This happened to me, when I purchased a Mac online with a new Apple ID and tried to activate it. Well, it simply doesn’t work out of the box.
But fear not, there is quite simple fix, although it requires an activated Mac.
On that activated Mac log into the Mac App Store with your fresh Apple ID. Then find the MacOS version that you want to install, in this case Mavericks. Click download and it will give you some hard time, because it is already installed. But simply ignore that. Click continue to download the installer. You will see the download process in purchase area. You can go there and pause the download, because you don’t really want to install it. Now you should log out of the Mac App Store, if this is not your machine. And now, as a last step restart the Mac. Of course the one that you want to re-install. You can now use your fresh Apple ID that just “bought” MacOS.
Cleaning up old kernel images on a Ubuntu machine is a quite annoying task. If you forget it and you have a separate /boot partition, then you will sooner or later run out of disk space. And then of course all your updates will fail.
Doing the clean up manually is, as mentioned, more than annoying and very tedious. But other smart people have spent some time and created a nice little one-liner that will get rid of old kernel versions. This command line will of course make sure that the currently running kernel is not removed. So it is very important to reboot after a kernel upgrade before you run this script!
And without further ado I present….
dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' | xargs apt-get -y purge
Not a big deal but a sudo snuck into the xargs call. It is now removed and shouldn’t cause any trouble anymore.
If you are using Apache on Ubuntu, then you most likely ran into the annoying warning about determining the fully qualified domain name of your server. Something like this will show up in your logs, on start of the server or on log rotation:
apache2: Could not reliably determine the server's fully qualified domain name, using 10.10.0.40 for ServerName
Luckily there is an easy fix it. All you have to do is adding the ServerName directive to your Apache configuration and specify a good server name. Usually localhost will do fine, unless you are using the machine without virtual hosts, just as a base server.
A quick and dirty way would be adding the following line to /etc/apache2/httpd.conf or to /etc/apache2/apache2.conf and restart your Apache service.
And then restart your Apache service with the following command:
Or on newer systems with:
service apache2 restart
Now, if you have a name in /etc/hostname, then you can use that instead. But you have to make sure that the name resolves to something real. If it is not in the DNS, then add it to your /etc/hosts and let it resolve to another loopback address. Here is a sample:
But as I said, this is quick and dirty and there are much better ways of doing it. So lets take a look at the preferred method. This one differs depending on the Ubuntu version, because the default Apache version changed from 2.2 to 2.4.
Ubuntu 13.04 and older (Apache 2.2)
Apache 2.2 loads additional configuration files from /etc/apache2/conf.d. Just add a file to that directory and add the above mentioned ServerName directive and restart Apache.
Create the file:
Add the directive:
service apache2 restart
Ubuntu 13.10 and newer (Apache 2.4)
Apache 2.4 has the additional configuration organized similar to the modules and sites. All configuration files need to be added to the directory /etc/apache2/conf-available and need to have the extension .conf. Each configuration file can be enabled with a2enconf and disabled with a2disconf.
Create the file:
Add the directive:
Activate the configuration:
service apache2 restart
HP’s Windows recovery installation seems to be a little bit broken. Or at least for me it was. While restoring the Windows 7 on an HP Elitebook 8540w I ran into some issues when the drivers installed. The system just stalled and nothing was moving anymore. After a reboot I saw this nice error message:
The Computer Restarted unexpectedly or encountered an unexpected error
Well, not nice at all, but there is a way you can continue from here. Here are the steps:
- On that very same screen press SHIFT-F10 and a command prompt should appear.
- Enter “regedit” (without the quotes) into the command prompt and press enter.
- In the registry editor navigate to HKLM/SYSTEM/SETUP/STATUS/ChildCompletion
- Double click on the entry setup.exe and change the value from 1 to 3.
- Close the registry editor.
- Click OK in the error window, which will restart your machine.
After these steps you should be able to continue with your Windows setup. In my case I had some trouble getting all drivers to work, but that is a different story.