Update: Patching VMWare ESXi 5.1

So I finally got around to patching my ESXi server which was several months behind. I thought I would just be able to use the same command I used previously wrote about to update it. That proved to be unsuccessful and all I got for my efforts were errors about the profile name. After some searching I discovered a new command to accomplish what I wanted.

esxcli software vib install -d /vmfs/volumes/Datastore/update.zip

Datastore is the name of the datastore the update is on and update.zip will be the patch file name. The complete command would look like this:

esxcli software vib install -d /vmfs/volumes/Storage/Updates/ESXi510-201307001.zip

Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true

   VIBs Installed: etc....
   VIBs Removed: etc....
   VIBs Skipped: etc....

After running the command you should get a message saying something similar to result above. It will usually be followed by a long list of all the individual packages. Reboot your host either through the vSphere client or by typing

reboot

and your host should be updated once it finishes rebooting.

 

Installing Box.net Sync on Windows Server

Anyone who’s tried to install the Box.net Sync client on Windows Server knows how much trouble it will give you. Since Box.net does not officially support server operating systems (which strikes me as odd considering how much they market to businesses) you can’t install it on Windows Server with the regular package. Any attempt will result in a compatibility error. So how do you get around this? Don’t use the regular install package. Box.net offers MSI versions of the sync client which will install without a single complaint on Windows Server (Server 2008 32-bit for mine).

You should be able to find the links on the right side of the Sync page. Just download the version for your server, install and you’re good to go!

Screenshot 2013-07-12 05.38.53

Shell Script: Splunk Syslog Server Update script

Here is a set of upgrade scripts I’ve created to automatically upgrade Splunk Syslog Server on Linux. This is primarily written with ubuntu server in mind, specifically 12.04 LTS, though it’s easily editable for other distributions. You can download the files below (they are automatically zipped with the latest version.

wget -q --secure-protocol="auto" -O "splunkget.sh" "https://raw.github.com/Smokex365/Splunk_Upgrade_Scripts/master/splunkget.sh"
chmod u+x splunkget.sh

Download splunkget.sh Stable
Download splunku.sh Stable

On the Dell CS24-SC Server….


I sure anyone looking for a cheap rackmount server on eBay or many other sites has come across this server. It’s everywhere but information is hard to come by about it. Even Dell Support doesn’t know about this server. I recently purchased one with the intent on using it to upgrade my existing ESXi server (basically a Dell Studio 540 PC). I’ll be returning it but I wanted to do a quick review and list of features and resources I found in researching this.

The Dell CS24-SC are custom, 1U 2-way servers manufactured by a unknown company for clustered and cloud computing. They are full depth, about 28″ and weigh roughly 36lbs/16.3kg with 4×3.5″ drives. It has 2xGBic (1000Mbit) network ports running on the Intel® 82567 Gigabit Ethernet Controller and an additional 100Mbit management port. There are 2 USB 2.0 ports on the front and 2 USB 2.0 ports on the back along with a VGA port, Serial, and PS2 Keyboard/Mouse ports. It has a single PCI-E x8 expansion port on a riser. One major reseller is Stallard Technologies, Inc though most of the server on the market are resold through eBay. The closest PowerEdge server seems to be the Dell PowerEdge 1950 Gen III or one of the earlier PowerEdge C1100 Cloud servers.
Read more of this post

Virusscan Software for Windows Server

Anyone who has tried to install virusscan software on their server knows that the activity can quickly become more of a pain than it is worth. When trying to find virusscan software for Windows Server you typically run into one of three issues:

  1.  There’s no support for Windows Server at all.
  2.  The Windows Server version commands a massive price compared to a home/personal version, sometimes as much as a 2000% markup.
  3. The Windows version somehow manages to lack features that even the most basic of desktop version have.

So what do you do? Read more of this post

Manually upgrading ESXi 5.0 to ESXi 5.1

I finally got around to updating my ESXi server today. Since I don’t have the hardware to run vCenter and thus do not use it I had to do it the manual way. This method involves connecting via SSH but is relatively straightforward.

  1. Download the update from VMware. The following link should take you directly to your My VMware page: VMware
    1. The file should be named VMware-ESXi-<version>-depot.zip
  2. Suspend or shutdown any running VM’s and put the system into Maintainence mode.
  3. The next step is to enable SSH on your ESXi Server by going to Configuration > Security Profile > Properties. Start the SSH service and close the popup.
  4. From there you’ll want to upload the VMware-ESXi-<version>-depot.zip we downloading earlier to the server
  5. Once the zip has been uploaded, open Putty or your preferred SSH client and connect to the ESXi server.
  6. Log into the server from SSH and run the following command where <datastore> is the location of the zip we uploaded earlier and <version> is the version number of the file (in this case, ESXi-5.1.0-799733).
    1. esxcli software profile update -d /vmfs/volumes/<datastore>/VMware-ESXi-<version>-depot.zip -p ESXi-<version>-standard
  7. Once the process is finished reboot the sever. If the update was successful take the server our of Maintainence mode, and resume your VM’s.

You’ll probably have to update VMware Tools for your VM’s but your server should now be running properly on 5.1 ( or whatever version you upgraded to, assuming the command isn’t changed/removed).

Convert a existing Virtual Disk on ESXi from Thick Provisioning to Thin Provisioning and vice versa

I was playing around on my ESXi server and noticed most of my servers were using under 10GB yet most where consuming between 20-45GB of datastore space. This is because when I set them up I went with the default setting of Thick Provisioning like many. So what do you do? I don’t want to reinstall my servers and loose everything. I also don’t want to waste space when I can afford new disks being unemployed at the moment.  After searching around I came across 2 nice articles on using vmkfstools to “convert” (it actually is cloning the disks) to Thin Provision and vice versa.
Read more of this post

Verified by MonsterInsights