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...

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 →

16 Oct 2011


1 comment

If you’re getting a new commercial certificate created, then you can use the GUI tools available in the admin console to create a Certificate Signing Request (CSR) for your SSL provider, and then import the certificates that they provide.

If you’re migrating from an old server that already has a commercial certificate, then you need to migrate everything across, which can’t be done via the admin console… Continue reading →

I always found being able to copy and paste between your desktop machine and a VM through the VI Client a godsend.  In the good old days this was always enabled by default, so you could copy and paste text between your desktop and VM consoles to your heart’s content.

Since ESX 4.1, its been disabled by default in order to provide a more secure, locked down environment out of the box.  There are two main options if you enjoyed the old-skool benefits; use a different app, or just re-enable the old functionality… Continue reading →

Being able to supply appropriate security credentials are a necessary obstacle in today’s security conscious world of IT. When I first started, many moons ago, the systems I managed all had the same (dictionary word) password to the (un-renamed) local Administrator account, you didn’t lock your PC, have to change your password, or have to worry about not being a domain admin on every system by default.

PowerShell scripts inherit the rights of the user that start them, which is normally all well and good if the script only need to run and access local resources, but as it needs to access any remote resources the chances of having to supply credentials grows rapidly.

Credentials are represented by a PSCredentials object , this can then be supplied to a CmdLet that requires it… Continue reading →