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

If your working in an environment where your users are in the same domain as your Microsoft Exchange environment, then Auto Discovery should take care of the configuration of your Outlook email clients.  If you need to use Outlook Anywhere so that your Outlook clients can connect as if they were on a foreign or untrusted network, it can be a bit of a pain to configure.  This would be fine if Autodiscover could take the strain. but if your local users are not in the same domain as Exchange, then this may not work. Continue reading →

When trying to connect to a printer share you get the following error…

Operation could not be completed (error 0x00000709). Double check the printer name and make sure that the printer is connected to the network.

Error message when trying to add network printer share

Operation could not be completed (error 0x00000709). Double check the printer name and make sure that the printer is connected to the network. Continue reading →

This post covers how to redirect a users login to a different profile to that which was originally defined by the Operating System.

If a user has been logging in locally to  machine for a while, and you now want to add the machine to the domain, or if you need to move a machine from one domain to another; you may have the need to effectively give the user a new account, whilst maintaining the original desktop that they are used to. Continue reading →

This article covers how to keep the same desktop profile, the look and feel, when a user logs in, when changing the user’s login name.  This would commonly occur when migrating machines (workstations, desktops, laptops) between domains, or when moving a standalone machine into a new domain.

To be clear, what we’re actually talking about is retaining a profile when the user’s underlying security ID (SID), needs to change. If a user’s login name is changing, but they’re staying in the same domain, you can just rename the login name, as the actual user account doesn’t change, the impact is purely the cosmetic login name change, everything else stays the same. Continue reading →

16 May 2012

Tech Notes

1 comment

This is a quick follow-up post on restoring a saved config for a Vyatta router.  I recently created a PowerShell script that checks my Vyatta routers and takes a backup of the config if its new than any existing backup (see Backup Vyatta Router configs with PowerShell).

Taking backups is all well and good, but its of little use if you don’t know how to restore… Continue reading →

Being able to create scripts to complete repetitive tasks and complete work that would otherwise give you headache is a wonderful thing, being able to schedule those scripts increases the available fire-power in your arsenal.

Like most things in IT, it can be a bit of a head scratcher to sort out the first time, but once you’ve seen it once you can just copy and paste. See below for a few examples…. Continue reading →

The memory sticks in HP blades (as in any server) will occasionally experience errors, more often than not these are recoverable, and are handled without pulling down the software that’s running on it.  However, a tally is kept, so that poorly memory stick can be identified and dealt with.

Non-critical (recoverable) memory errors that have breached an acceptable level generate an error through to the HP Onboard Administrator (OA) as a degraded memory state.  This will be visible as a yellow warning triangle on the OA, will propagate through to your monitoring system (eg SCOM), and through the vCentre Hardware Status for the affected ESX.

Once the problematic memory stick is swapped out, the alert will clear from the OA (and SCOM), but will still be visible through vCentre.  In order to clear down, the server’s System Event Log needs to be reset, and this refreshed through the CIM provider… 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 send an email from a script is always a useful tool to have in your back pocket. Be it for sending out an alert for a bespoke check, an email over the weekend to let you know that that big task script has completed (un)successfully, a regular report mail, or some other reason.

Sending a basic text email is incredibly easy (2 lines), and it doesn’t take much more effort to be able to send fully formatted HTML email with attachments (though obviously you’ll need to put some effort into creating the HTML).

Continue reading →

Came across an odd problem today, whereby nobody could use any of the deploy template options as they were all greyed out…

  • Clone…
  • Convert to Virtual Machine…
  • Deploy Virtual Machine from this Template…

We’re all admins with full rights over everything, so it wasn’t a permissioning issue (although I suspect it might be a permissioning bug).  The fix is to just re-add the Templates into the vCenter inventory (fuller details below if you don’t know how this is done). Continue reading →