Moving VMWare Machines Around

I recently setup a new VMWare server on one of our older Dell servers (2850 with 8GB RAM 6X300GB SAS). And since I’m eventually redoing the primary VMWare server, I wanted to move all the critical virtual machines to the secondary server (for obvious reasons).

So far everything has been moving great, but I did have one issue:
After moving our collaboration helpdesk server, I could no longer remotely access the virtual machine.

ifconfig showed that only the l0 was loading.
nano /etc/networking/interfaces displayed both the l0 and eth0 settings
ifconfig -a informed me that in the transition, the virtual machine decided to change the ethernet device to eth1
nano /etc/networking/interfaces and I changed all the eth0 to eth1
sudo /etc/init.d/networking restart or just reboot the server

Windows Check Disk

Growing up on Macintosh Computers (1988 was my first computer – a Macintosh SE with a whopping 8MHz, 9″ B&W screen, 20MB HD, and 1MB RAM), my knowledge of some very basic Windows operations is sometimes lacking. Moving from the Mac to a linux world probably didn’t help much either. Hey, at least I started to learn what IRQ’s were.

I had no idea how to use the DOS command prompts to do what I wanted. I was used to the linux style commands (who knew that dir was the same as ls?). I was also used to the fact that the Mac had no utilities to defrag, clean up, or otherwise alter data. The Mac just worked.

Windows, however, sometimes needs a gentle (read “harsh”) push to do what I want it to do. This is where my love of the command line and my necessity to Windows comes into play.

We all know that Windows 98 and ME forced you to run the Check Disk utility on startup if you shutdown the computer improperly. Probably a good 99% of the time I would bypass this check as I already knew the issue. That and I’m impatient.

So without further ado, here’s the command to run check disk:
Start >> Run >> CMD
chkdsk This will run Check Disk in read-only mode and will not repair any issues it finds
chkdsk C:/f This will run Check Disk in forced repair mode, but it will not check for bad sectors on the HD
chkdsk C:/r This will run Check Disk in repair mode, locate bad sectors, and recover readable information

With all that out of the way – I’m thinking about moving this site to a new one. The only problem with that is the fact that google has this site already cached for searching. We’ll think about it.

***EDIT***
chkdsk c: /f /r will do the same as both of the commands. This will scandisk your entire system – ie it’ll scan for bad sectors etc.

MCE Remote on XBMC

In case you haven’t noticed, I’m on an XBMC bender. I recently setup an older system as a file server, put a crap load of storage in it, and threw some movie ISOs on there. Then I installed XBMC on my main rig. The rest is history. I was fine with the wireless keyboard and mouse, but The Fiance says we must use a remote control.

My lucky day happened last week: woot had a woot-off AND they had some MCE remotes on sale. I bought two. They’re some crappy Pinnacle ones, but at newegg they run almost $40 and I got both with shipping for less than $35.

Trying to get it to work was another issue. Out of the box Vista will recognize this remote, but XBMC wouldn’t hear anything. Works great on Windows Media Center though. So I ended up trying a program called LMRemoteKeyMap. Pretty nifty, but I didn’t feel like learning all about xml, codes, remotes, and commands. I felt like being lazy.

So then I ended up with another program called IRServer Suite. Now this one worked out of the box. Every function works as advertised. The only change I made was to get the giant green button to act as the Windows key (so I can press start). Others have made it automatically open up XBMC, but for now I just wanted start to work.

Basically you’ll just open the Translator program and follow along to have it automatically do your work for you. See how lazy I’m being?

I might include some screen shots eventually.