CLI

Certificate error: Outlook 2007 & Exchange 2007

This one is from a while ago. I originally used this back in May of 2009 and just realized that I hadn’t posted the link and info. Basically, shortly after migrating to Microsoft Exchange 2007 in-house, we purchased an SSL certificate for various reasons. Long story short, Outlook 2007 clients starting throwing certificate errors upon opening. So, our outside clients now trust the Exchange box, but the inside clients do not. I went round and round trying to resolve this on my own before searching the internet for a solution. Finding the solution was not easy at all, but I eventually located this link. After following the instructions, everything was up and running as one would expect.

I didn’t really think that this would have been such a PITA, but maybe thats what I get for naming a mail server Newman.

–Himuraken

Enable SSH on VMWare ESXi 3.5 & 4.0

I have been playing around with ESXi and needed to upload some files via SCP and discovered that SSH is not enabled by default. There are many sources out there for accomplishing this but I found the following information to be the easiest to follow.

1) At the console of the ESXi host, press ALT-F1 to access the console window.
2) Enter unsupported in the console and then press Enter. You will not see the text you type in.
3) If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.
4) You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command *vi /etc/inetd.conf*).
5) Find the line that begins with #ssh and remove the #. Then save the file. If you’re new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in :wq to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.
6) Restart host or try kill -HUP `ps | grep inetd`

The original blog posting can be found here.

–Himuraken

GDesklets won’t run in Ubuntu 7.10 Gutsy Gibbon

After a clean install/upgrade of Ubuntu 7.10 (Gutsy Gibbon) you may be unable to get gdesklets to run. I have noticed several threads out there with no resolution so I thought I would post a fix. Most users will get the app installed successfully but when they run the gdesklets shell, the app begins to load, goes gray, and then has to be closed using force quit. Also, running gdesklets start from a console shows that the daemon is starting but it never does. By default Gutsy Gibbon uses Python 2.5 while gdesklets is looking for 2.4. This is pretty straight forward to resolve using these steps. Install python2.4 by running sudo apt-get install python2.4 from a console. After that is complete we need to tell gdesklets to use Python2.4. From the console we need to add a few entries to the gdesklets config files. Locate the line that says “#! /usr/bin/env python” and append it with a 2.4. So each line should now look like “#! /usr/bin/env python2.4”. This line needs to be updated at the top of each of the files listed below.

/usr/lib/gdesklets/gdesklets
/usr/lib/gdesklets/gdesklets-shell
/usr/lib/gdesklets/gdesklets-daemon
/usr/lib/gdesklets/gdesklets-migration-tool

After updating the files with your favorite text editor, start the app by running gdesklets start from a console. This should have you up and running in no time.

–himuraken