A few months ago I was asked by a couple of people, “What is a good product for connecting remotely to my machines at work/home, but isn’t going to cost me a bundle”. Good question, as I really never had a solid utility for my home lab environment. At work, we have always had some sort of enterprise VPN product like CheckPoint, F5, or Sonicwall. So I did some searching around, and of course there are many solutions out there. The criteria I was setting for myself was I wanted something somewhat easy to install, preferably open source, and something that could expand and/or grow if needed. I also wanted something that would work with my Windows boxes and Linux boxes. After playing around with a couple of products, I settled on OpenVPN (http://openvpn.net). The access server is available as Linux or Windows, or as a VMware or VHD appliance. The clients available are for Linux, Mac, and Windows. The server install was rather simple as I just downloaded and VMware image and added it to my existing ESXi environment. Made the proper changes after the install and on my firewalls and that was good to go. Of course you have to make sure you register so you can get your free 2 clients. The client software was pretty much the same. I loaded it on my Windows 7 laptop and my Linux netbook. I also tested it on Windows XP and no complaints there as well. The web GUI interface for the admin piece was pretty straight forward. Only problem I had going on was with setting up the profiles for downloading the client. Once I figured that out, I was good to go. Also one of the other things I really liked about the product is I could really test drive it and buy more licenses as I saw fit. Right now I don’t have a need for more than two connections, but that could change. I think this could be a happy medium solution for some home office/small business environments. They also have a pretty good community out there for help in case you get stuck.
I finally got around to updating my netbook with Windows 7 Ultimate this last week and all went well on it (for the most part). As most people have discovered, the vSphere client does not work native in Windows 7 and is stated here on VMware’s support site. I didn’t want to run it in Windows XP mode, but also didn’t want to wait until VMware fixes the issue either. So I did a trusty google search and found this article for the vSphere Client, and this article for the Host Update Utility. Both worked as advertised and haven’t encountered any problems since then.
A long while ago I was taking a look at an open source application called FOG to look at a method of quickly deploying server images at that time, our MS Virtual Server environment. Flash forward to now, I got some time in the office to look at this again, but now we are using VMware ESXi (until we get our Enterprise licensing this summer sometime). This will probably become obsolete when we get the Enterprise version, but I also wanted to look at this as a solution for my home network as I usually like to get something built on the fly and not have to invest a lot of time into the build. Continue reading Using FOG to deploy server images in VMware ESXi
I recently got a decommissioned HP ML 350 G3 server to use for my VMware ESXi 3.5 environment at home. I have been bumping into a couple of challenges with it. Even though the server is supported according to their hardware specs, some of the stuff I am trying to attach doesn’t seem to be. I am trying to build this environment with only equipment I have, not purchasing anything. First off, here is the existing server configuration:
- Dual Xeon 2.8 Processors
- 4 Gigs of memory
- About a 280gig RAID5 partition (with hot swap drives)
Server works fine as is, but I really wanted to add more external disk space so I could house images on a separate drive array, plus want to setup a backup routine as well (another article on that later). As I have been finding out with VMware ESXi, there are certain challenges, one big one being hardware. It seems VMware has taken the approach that it will support only newer Server hardware, which is fine if you are buying new stuff, but not fine if you are doing the piece meal approach like myself. One of things I would like to attach is a SCSI drive tower box with 6, 72 gig drives and I wanted to do a RAID5 configuration for backup/storage. After about a week of trying different SCSI cards I had laying around at home and extra from work, I was finally able to get one to work, but the drive array itself was not stable and literally took 48 hours to format a RAID5 partition! So back to the drawing board for the external storage.
I found somebody that was willing to buy my 72gig drives for about $50/piece, and I had 8 of them. So after some paypal exchanges I had some extra cash to get my drive array. I went and found an Adaptec 2410SA SATA RAID card on ebay, and 2 500gig SATA II drives over at newegg.com, all for a reasonable price. So I went against what I wanted to do originally and not buy anything, but since I was able to sell the unusable SCSI drives, I was able to purchase what I needed and actually had a few bucks left over. Nice!
Now I am in the process of testing out the external mirror array, I am putting on it the latest beta of Windows 7. So far it seems to be working OK. I also started to load a Windows 2008 image to see how it works out.
Now, if I could only find 2gig chips so I could get this server up to 8 gigs of RAM (well, I did find them, but at about $150 a stick). 4 gigs works, but I can tell the performance hit when I have too many VMs running on it.
Hey, at least the price has been right.
Found this little bit of information for enabling ssh on our ESXi servers. Been useful so I can do a vmkfstools on one of our older Windows 2000 servers.