UK Apple Keyboard mappings for Windows

by Sam 12. February 2011 20:02

I have an apple aluminium keyboard attached to my Windows PC, primarily I enjoy typing on apples new keyboards, having had one on my laptop. However I was getting increasingly annoyed with the fact that none of the Windows keyboard mappings match the keys on my keyboard. When you have Windows installed in Bootcamp on a Mac, it installs a key mapping for you, but on a standard Windows PC it does not. After a bit of digging, I cam across this downloadable mapping file, that does exactly that. I can now get my @, " and # symbols from the right keys. It's the simple things that make you happy!

Installing ESXi 4.1 on a USB stick

by Sam 9. September 2010 17:09

Remember all the tutorials about creating a bootable USB stick run ESX off, that needed 1 or more other programs to create a boot image? Well there is now an easier way. I've just discovered that in ESXi 4.1 (and to be fair I have not checked recent earlier versions) you can now install ESXi straight from CD to the USB memory stick, much easier. This made

Installing PHP LDAP (or other) extension after using Web Platform Installer

by Sam 12. August 2010 13:08

I recently used the web platform installer to install IIS 7.5 and PHP on a Windows 7 machine. I also needed to install the LDAP extension, however after some time struggling to use an extension from the PHP site, or from an old install I discovered the best way to do this

  • Go to control panel, programs and select your PHP install
  • Click on change
  • Click next, then change
  • Select IIS fast CGI
  • Expand the Extensions section and tick the extensions you want to install
  • Complete the install

Renew an SSL certificate in IIS using the existing key

by Sam 4. August 2010 23:08

I recently needed to renew an SSL certificate on an IIS 7 server. The usual method to do so would be to generate a renewal CSR on the server, go to the SSL provider and generate a certificate, simple. However in this case I was presented with a renewed certificate that had been created using the CSR that had been used to generate the original certificate, so how do I get this into IIS, I can't just add it to my certificate store, as the machine doesn't believe it has the private key for this cert. The certifcate managment console has an option to renew a cert with an exisiting key, great I thought! but

However this just gives an error about a template. So, after some research I found a way to deal with this situation, so that I can assign the private key from the old cert, to this cert and therfore use it in IIS.

1. Open up the Certificate Services MMC, and connect to the local computer store

2. Import the new certificate into the Local Computer Personal store.

3. Export the “old” certificate including the private key do NOT set the option to delete the private key on success!

4. Delete the “old” certificate in the MMC

5. Get the the serial number from the new certificate and run this command from an elevated cmd prompt:

certutil –repairstore my “put serial here”

6. Assign the new certificate to the IIS website

Once that is done, the certificate works perfectly, without having to generate a new CSR. Thanks to Andreas Klein for his blog post that lead me to this solution

VMWare ESX: NFS Error: unable to Mount filesystem: Unable to connect to NFS server

by Sam 2. March 2010 02:03

Recently I was trying to get an ESX blade to connect to a NAS data store. 2 Other blades had happily connected to this data store, and this blade was already connected to a different data store, but when ever I tried to connect to this particular store, I got this error:

NFS Error: unable to Mount filesystem: Unable to connect to NFS server

So I struggled with this problem for quite some time, until I found the solution - Name Resolution. Now firstly, I would like to point out that I was connecting to this blade from ESX by IP, not name, so didn't think resolution was a problem. However what ended up fixing this was ensuring that the NAS could resolve the ESX blade by name. I'm not sure why this was needed, as the other 2 blades had worked fine without needing proper name resolution setup, as had the connection to the other blade, but I added an entry in DNS for the ESX blade, and hey presto, it works. 

Recent tweets

© Copyright 2011 Sam Cogan.