Iomega IX2 and Time Machine Support

As Mr. Simon Seagrave has pointed out, there is a fix available to enable OSX Lion Time Machine support for Iomega IX2 and IX4 NAS storage devices.

I decided to take this a little step further, and try to upgrade my old (and discontinued) Iomega IX2-200 to the new IX2-200 Cloud Edition firmware.

Initially this was a big failure, as I seemingly managed to brick my device. It was only responding to pings (so the TCP/IP stack was loaded and working), but I could not bring up the web based management tool nor connect via telnet or SSH.

Thankfully Will van Antwerpen had investigated the firmware upgrade to cloud edition a bit more than I had, and pointed me to the General NAS-Central Forums where I found a link to a great HowTo explaining the entire process: Upgrading Iomega ix2-200 to Cloud Edition.

As that article also mentions, I had to do the process twice to get it to kick in and un-brick my IX2-200 and get it running with the new Cloud Edition firmware.

After configuring the IX2 with security and setting up Time Machine on the Macbook Air, Time Machine seems to be running without problems.

<MrBurns>Excellent</MrBurns>

Creating and Using a Virtual Floppy in vSphere

My new colleague Olav Tvedt asked me if I could test his method of enabling Bitlocker in a VM, on VMware vSphere. Of course, I was happy to oblige.

I followed the same steps as he did in his Running Bitlocker on a Virtual computer post, and it worked perfectly.

The only real difference between doing this in Hyper-V and on ESXi, is that the virtual floppy drive on ESXi by default doesn’t emulate an empty floppy. So, in order to mount a virtual floppy you need to create a new floppy image. Thankfully the vSphere Client can do this for you!

To use the vSphere Client to create a floppy image you can later mount in a VM, you need to edit a VM’s settings. Find the floppy drive, if the VM doesn’t have one add one, close the window and return to the VM settings once the floppy drive has been added, and select “Create new floppy image in datastore: “.

Click on the Browse button and browse to your preferred location for the floppy image. Name it, and click on Ok.

Click on Ok again to close the VM settings window and return to the vSphere Client.

There you go, an empty virtual floppy image that you can mount in a VM is now created.

To mount the image, find the floppy drive icon in the vSphere client and select the Connect to floppy image on a datastore option.

Browse to the location where you created the floppy image, and select it.

Now, the VM has an empty floppy that you’ll need to format before you can use it.

Follow Olav’s guide to encrypt the boot drive with Bitlocker, without the need for a TPM chip or USB device connected to the VM!

And yes, it works as you can see here:

So much for never needing a floppy disk again. Oh, and by the way, you can of course do this is VMware Workstation 8 as well.