The greatest challenge to any thinker is stating the problem in a way that will allow a solution

Bertrand Russell

Welcome to vBlog, a personal record of my techy tinkerings and particular ponderings.

I tend to focus on VMware virtualisation, and the interaction/automation of it using PowerCLI (VMware's PowerShell Snapin), but anything that I happen to stumble across that seems like it might be of use at a later date, may well get recorded here.

I also maintain vWiki, which was a predecessor to this blog. Wiki's are great for quickly recording snippets of info, but tend not to look that great; Blog's are better looking things, but seem to require more effort so that the posts/articles are accessible in their own right. As a result I tend to update both interchangeably as available time, and depth of thought, permit.

If you happen to find anything of use, or in need of correction please leave a comment. Knowing that my ramblings are of some use is a great reward; and similarly I'd hate to waste anybody's time by feeding them duff info.

See these pages for me info about me, and my vBlog, and below for my recent posts...

Or more specifically, how does server or desktop computer virtualisation work?

The purpose of virtualisation is to enable to be able to run more things on less hardware.  To allow you to run numerous virtual instances of a machine on a single computer.  But how do you do that? Continue reading →

Or in the US – virtualization.

Virtualisation enables you to reduce the number of computers and other equipment that you might have, whilst still getting done what you need to.

There are many different types of virtualisation, but desktop computer virtualisation and server virtualisation are the most common. They work by enabling a single computer to do the job of many computers. The single computer will have to work harder. But modern computer hardware has been developed over the decades to be more and more powerful, and so is up to the job. Continue reading →

One of the great problems with creating scripts that will be run when you’re not around is how to provide them with the credentials that they need.  Microsoft have intentionally tried to make it difficult to simply include username and password information in the raw, in scripts.  This is a good thing, but it can be an initial stumbling block when you’re getting started.

To get around this irritation, without bypassing the security it provides, I store my password in an encrypted file, which called upon by every script that needs it… Continue reading →

Powershell is now the standard for Windows based scripting, providing a route into the wealth of .NET Microsoft objects available and now being commonly provided for by 3rd-party applications by API Cmd-Lets.  If you administer a Windows world, then you need to get used to Powershell.  Its an object-orientated environment, which takes some getting used to if you’re not familiar with it, but its very versatile once you’ve got some confidence. Continue reading →

VMware’s support of PowerShell is laudable, personally I’ve tried (and failed) to become au-fait with Perl too many times to recall, so being able to script for your virtual infrastructure in PowerShell has been a god send for me.  If you know nothing of PowerShell, don’t let that put you off, nor did I before I started PowerCLI scripting.  There are a wealth of support pages out there to help, and here is my attempt to get you on your way…

Continue reading →

All servers have one purpose, to serve.

To facilitate this, one or more applications or services need to run, and it is these applications or services, that provide the server’s function to its clients. These are utterly dependant on physical resources in order to be able deliver, but its the applications/services and their configuration or data, that distinguish one server from another. Continue reading →